summaryrefslogtreecommitdiff
path: root/pjon/pjdl/README
diff options
context:
space:
mode:
authorGerhard Sittig <gerhard.sittig@gmx.net>2020-06-22 20:13:15 +0200
committerGerhard Sittig <gerhard.sittig@gmx.net>2020-06-24 19:30:37 +0200
commit55a8021ad31e5b7e746dc71e9b71041920e62f17 (patch)
tree024111ed157221294760b8e8adbabb380ab199f8 /pjon/pjdl/README
parentb91f86e7b7c51e637dac58fd207ee2238d47e4d1 (diff)
downloadsigrok-dumps-55a8021ad31e5b7e746dc71e9b71041920e62f17.tar.gz
sigrok-dumps-55a8021ad31e5b7e746dc71e9b71041920e62f17.zip
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 <jcallano@gmail.com>
Diffstat (limited to 'pjon/pjdl/README')
-rw-r--r--pjon/pjdl/README40
1 files changed, 40 insertions, 0 deletions
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.