/* Milan, Italy Originally published: 10/04/2010 latest revision: 24/09/2017 PJDLR (Padded jittering data link Radio) v2.0 Invented by Giovanni Blu Mitolo, preamble proposed by Fred Larsen released into the public domain Related implementation: /src/strategies/OverSampling/ Compliant versions: PJON v9.0 and following Changelog: - Added frame separation - Added communication modes specification */
PJDLR (Padded Jittering Data Link Radio) is a simplex or half-duplex data link layer, that can be easily software emulated, enabling one or many to many communication in both master-slave and multi-master configuration optimized to obtain long range and high reliability using radio transceivers. It has been engineered to have limited minimum requirements, and to be efficiently executed on limited microcontrollers with poor clock accuracy. No additional hardware is required to apply PJDLR, and, being implemented in c++, in less than 350 lines of code, it is easily portable to many different architectures.
- Define a synchronization pad initializer to identify a byte
- Use synchronization pad's falling edge to achieve byte level synchronization
- Use 3 consequent synchronization pads identify a frame
- Use a frame preamble to support gain regulation before reception
- Detect interference or absence of communication at byte level
- Support collision avoidance and detection
- Support error detection
- Support 1 byte synchronous response to frame
Every byte is prepended with a synchronization pad and transmission occurs LSB-first. The first bit is a shorter than standard logic 1 followed by a standard logic 0. The reception method is based on finding a logic 1 as long as the first padding bit, synchronizing to its falling edge and checking if it is followed by a logic 0. If this pattern is detected, reception starts, if not, interference, synchronization loss or simply absence of communication is detected at byte level.
_____ ___________________________ | Pad | Byte | |_ |___ ___ _____ | | | | | | | | | | |1| 0 | 1 | 0 0 | 1 | 0 | 1 1 | 0 | |_|___|___|_____|___|___|_____|___|
Padding bits add a certain overhead but are reducing the need of precise timing because synchronization is renewed every byte.
Before a frame transmission, the communication medium is analysed, if logic 1 is present ongoing communication is detected and collision avoided, if logic 0 is detected for a duration longer than a byte transmission plus its synchronization pad and a small random timeframe, a packet preamble is transmitted, composed of a long 1 and a long 0, to let a potential receiver to adjust its gain to the transmitted signal magnitude. The duration of the preamble bits have to be selected considering hardware sensitivity and gain refresh time. Frame transmission starts after preamble, with 3 synchronization pads, followed by data bytes. The presence of synchronization pads with their logic 1 between each byte ensures that also a frame composed of a series of bytes with decimal value 0 can be transmitted safely without risk of third-party collision.
INITIALIZER DATA _________ ___________ __________ _______________ ______________ |Preamble |Pad|Pad|Pad| Byte |Pad| Byte |Pad| Byte | |_____ |_ |_ |_ | __ |_ | _ _|_ | _ | | | | | | | | | | | | | | | | | | | | | | | | | 1 | 0 |1|0|1|0|1|0|0000|11|00|1|0|00000|1|0|1|1|0|00000|1|00| |_____|___|_|_|_|_|_|_|____|__|__|_|_|_____|_|_|_|_|_|_____|_|__|
In a scenario where a frame is received, low performance microcontrollers with inaccurate clock can correctly synchronize with transmitter during the frame initializer, and consequently each byte is received. The frame initializer is detected if 3 synchronizations occurred and if its duration is coherent with its expected duration. With a correct bit and synchronization pad ratio and timing configuration, the frame initializer is 100% reliable, false positives cannot occur if not because of externally induced interference.
A frame transmission can be optionally followed by a synchronous response by its recipient. This feature is available for both master-slave and multi-master. In multi-master configuration the maximum acceptable acknowledgement overall response time is equal to 1 byte transmission time.
Transmission Response ________ ______ ______ ______ ________ _____ |PREAMBLE| INIT || BYTE || BYTE | CRC COMPUTATION |PREAMBLE| ACK | |____ |------||------||------|-----------------|____ | | | | | || || | LATENCY | | | 6 | |____|___|______||______||______| |____|___|_____|
In master-slave configuration the maximum time dedicated to potential acknowledgement reception it is defined by the use case constraints like maximum packet length and latency or physical distance between devices.
The proposed communication mode is the result of years of testing and optimization for ASK/FSK radio transceivers and have been selected to be easily supported also by low quality hardware.
|MODE||Bit timing||Sync bit timing||Pad-bit ratio||Speed|
|1||512||328||0.64||202B/s - 1620Bb|
Binary timing durations are expressed in microseconds.
This document is automatically generated from the github repository. If you have noticed an error or an inconsistency, please report it opening an issue here