...
Number of events since last counter update message transmission | Elapsed time since last counter update message transmission, seconds |
|---|---|
0 | 3600 |
1 | 60 |
2 | 40 |
X | 0xFFF - not used |
X | 0xFFF - not used |
There is also a feature that allows you to set only used(defined) records of the policy table. So, for example, if you send just 2 bytes they will be interpreted as 1 record of the table and other records will be set as not used.
For example, for fast demonstration or debugging, you can configure a high data rate and no minimum delay between counter update messages even if there is just 1 message. To do it:
send 15 to port 52(No ADR, Data Rate DR5, unconfirmed message without repetitions)
send 10 00 to port 53( no minimum delay between counter update messages for 1 event)
Another example, if you need to perform a connectivity test, you can set Data Rate to a target value or to minimum(DR0) and set a record in the policy table with a number of events equal to 0, and elapsed time set to target transmission period, for example:
send 11 to port 52(No ADR, Data Rate DR1, unconfirmed message without repetitions)
send 00 64 to port 53( messages will be sent every 100 seconds even without any new events)
It is important to remember, that minimum delay between LoRaWAN messages including Counter Update messages is also defined by LoRaWAN specifications(like duty cycle limitations in EU868 region) and Car Counter abides by these limitations. In the case of low data rates, delays caused by duty cycle limitations can be significant(for example, about 100 s for DR0).
4.3.3 Heartbeat frequency
...