From 55a8021ad31e5b7e746dc71e9b71041920e62f17 Mon Sep 17 00:00:00 2001 From: Gerhard Sittig Date: Mon, 22 Jun 2020 20:13:15 +0200 Subject: pjon/pjdl: add capture of minimal PJON frames over PJDL link layer The PJON protocol can use several link layers. These captures run on PJDL, demonstrate a minimal PJON frame (with TX info) and a response. And also contain a few exceptional conditions: Glitches in the signal, outside and inside of frames. Lack of recipient's response, too. The snippets were extracted from a capture that was Submitted-By: Julio Aguirre --- pjon/pjdl/README | 40 +++++++++++++++++++++ .../pjon-pjdl-glitch-and-ack-and-failed-ack.sr | Bin 0 -> 1355 bytes ...pjdl-incomplete-frame-missing-ack-repetitive.sr | Bin 0 -> 6472 bytes 3 files changed, 40 insertions(+) create mode 100644 pjon/pjdl/README create mode 100644 pjon/pjdl/pjon-pjdl-glitch-and-ack-and-failed-ack.sr create mode 100644 pjon/pjdl/pjon-pjdl-incomplete-frame-missing-ack-repetitive.sr (limited to 'pjon/pjdl') diff --git a/pjon/pjdl/README b/pjon/pjdl/README new file mode 100644 index 0000000..25423e9 --- /dev/null +++ b/pjon/pjdl/README @@ -0,0 +1,40 @@ +------------------------------------------------------------------------------- +PJON over PJDL +------------------------------------------------------------------------------- + +This is a collection of example PJON communication which uses the PJDL +link layer. Which does serial communication on a single wire, and the +reference library happens to implement it by means of software bitbang +(which affects the timing of signals on the wire). + + +Logic analyzer setup +-------------------- + +The capture was taken with a logic analyzer at a samplerate of 4MSa/s. +Communication is done on a single channel. + + Probe PJDL + ---------------- + 1 data + + +pjon-pjdl-glitch-and-ack-and-failed-ack.sr +------------------------------------------ + +Two STM32F103 (Blue Pill boards) run the example code which resides in +the examples/ARDUINO/Local/SoftwareBitBang/SendAndReceive/Device1/ and +Device2/ directories. Communication mode 1 translates to 44us and 116us +for data and pad bits. Device addresses are 44 and 45. The letter 'B' is +sent as the payload data in both directions. Synchronous responses get +requested, but one device won't respond. The capture also contains a few +glitches which as a byproduct exercise the decoder's robustness, and +recovery after synchronization loss. + + +pjon-pjdl-incomplete-frame-missing-ack-repetitive.sr +---------------------------------------------------- + +This is a longer capture taken from the above setup. Some of the glitches +happen to fall into a PJON frame's period and can prevent or can disturb +the accumulation of the frame's content. diff --git a/pjon/pjdl/pjon-pjdl-glitch-and-ack-and-failed-ack.sr b/pjon/pjdl/pjon-pjdl-glitch-and-ack-and-failed-ack.sr new file mode 100644 index 0000000..e130f90 Binary files /dev/null and b/pjon/pjdl/pjon-pjdl-glitch-and-ack-and-failed-ack.sr differ diff --git a/pjon/pjdl/pjon-pjdl-incomplete-frame-missing-ack-repetitive.sr b/pjon/pjdl/pjon-pjdl-incomplete-frame-missing-ack-repetitive.sr new file mode 100644 index 0000000..c6aaf62 Binary files /dev/null and b/pjon/pjdl/pjon-pjdl-incomplete-frame-missing-ack-repetitive.sr differ -- cgit v1.2.3-70-g09d2