X-Git-Url: https://sigrok.org/gitweb/?a=blobdiff_plain;f=pjon%2Fpjdl%2FREADME;fp=pjon%2Fpjdl%2FREADME;h=25423e95df7ec199ced4faf077a510962d6736bf;hb=55a8021ad31e5b7e746dc71e9b71041920e62f17;hp=0000000000000000000000000000000000000000;hpb=b91f86e7b7c51e637dac58fd207ee2238d47e4d1;p=sigrok-dumps.git 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.