...
The first calibration initiates the join process. The Join procedure follows the Over-the-Air Activation (OTAA) described in the LoRaWAN Specification 1.0.2. Activation By Personalization (ABP) is not supported.
After powering up the car counter device, it will try to join a LoRaWAN Network by sending the join request message. In case the join request is not answered, the sensor will retry as soon as possible, according to transmission time limitations, up to 4 additional times (5 attempts in total). After the 5th unsuccessful attempt, the sensor will wait with exponentially increasing intervals (see chapter 3.2) and repeat the process 5 more times.
If the Join request message is not answered with a Join Accept message, the sensor retries, according to the following sequence:
...
Attempt | DataRate |
|---|---|
1 | Configured DR or default(DR2) |
2 | Configured DR or default(DR2) |
3 | DR2 |
4 | DR1 |
5 | DR0 |
In case the Join accept message is received after attempts 3, 4, or 5(so the first 2 using configured datarate failed), and the sensor restores the configured DataRate to the default value (DR2)'s configured datarate(DR2 by default) is higher than the data rate used in the attempt, the configured datarate will be changed to DR2, DR1, or DR0 accordingly. This behavior assumes that the configured DataRate does not allow communication with the Gateway.
...
1 (1 byte) to calibrate the device,
2 (1 byte) to reboot the device,
3 (1 byte) to put the device into the initial energy-saving mode (the device sleeps until the next calibration with no detection and no LoRaWAN messages).
5. Changelog
0.6.7 4 January 2023
Features:
The way configured datarate is changed if attempts to join the network using this datarate fail is changed to avoid sensors being able to connect but not send messages later
Known issues and limitations:
None at the moment.
0.1.0 28 June 2021
Features:
...