End Device sees data rate degradation when sending unconfirmed uplinks after gateway outage #1071
-
I've been doing some fault tolerance testing on my end devices, and one test has been to see what happens when the only gateway in view suffers an outage (e.g. loss of power or backhaul). I have some devices sending debug data every 10 seconds at SF7, and these devices consistently start degrading data rate after the gateway outage occurs. No other MLME or MCPS commands are being used, just unconfirmed uplinks. It seems that the data rate degrades one level for each 32 uplinks, so DR5, DR4, DR3 etc. Device ADR and Server ADR are enabled, but there is no ADR activity in the network server logs (Loriot) because there is no gateway in view that could be receiving the packets. Network server shows no uplinks after gateway outage. This seems contrary to my understanding of how LoRa works. Why would the device be aware of gateway outage when only sending unconfirmed uplinks? |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
The described behavior is according to LoRaWAN specification. Please read LoRaWAN 1.0.4 specification chapter "4.3.1.1 Adaptive data-rate control in frame header (ADR, ADRACKReq in FCtrl)" At the end of the chapter you will see an example table describing the expected behavior. After By setting the |
Beta Was this translation helpful? Give feedback.
-
This is the expected behaviour. At least one message reception every 32 messages sent, if not, the datarate is lowered. |
Beta Was this translation helpful? Give feedback.
The described behavior is according to LoRaWAN specification.
Please read LoRaWAN 1.0.4 specification chapter "4.3.1.1 Adaptive data-rate control in frame header (ADR, ADRACKReq in FCtrl)"
Please also note that this behavior exists since LoRaWAN 1.0.0 specification.
At the end of the chapter you will see an example table describing the expected behavior.
After
ADR_ACK_LIMIT
up links the end-device sets theADRACKReq
bit on frameFCtrl
field.By setting the
ADRACKReq
bit to 1 the end-device is requesting the network server to execute a down link.In case a down link is received the
ADRACKCnt
is reset to 0 and the process re-starts.In case a down link is not received the end-device will l…