Document

LoRaWAN® Regional Parameters v1.0.3revA

Issue link: https://read.uberflip.com/i/1428359

Contents of this Issue

Navigation

Page 41 of 70

LoRaWAN 1.0.3 Regional Parameters ©2018 LoRa™ Alliance Page 42 of 71 The authors reserve the right to change specifications without notice. • whereby beacon_time is the integer value of the 4 bytes "Time" field of the beacon 990 frame 991 • whereby beacon_period is the periodicity of beacons , 128 seconds 992 • whereby floor(x) designates rounding to the integer immediately inferior or equal to x 993 994 Example: the first beacon will be transmitted on 923.3Mhz , the second 995 on 923.9MHz, the 9 th beacon will be on 923.3Mhz again. 996 997 998 Beacon channel nb Frequency [MHz] 0 923.3 1 923.9 2 924.5 3 925.1 4 925.7 5 926.3 6 926.9 7 927.5 999 1000 The beacon frame content is: 1001 Size (bytes) 3 4 2 7 1 2 BCNPayload RFU Time CRC GwSpecific RFU CRC 1002 2.6.9 AU915-928 Default Settings 1003 The following parameters are recommended values for the AU915-928 band. 1004 RECEIVE_DELAY1 1 s 1005 RECEIVE_DELAY2 2 s (MUST be RECEIVE_DELAY1 + 1s) 1006 JOIN_ACCEPT_DELAY1 5 s 1007 JOIN_ACCEPT_DELAY2 6 s 1008 MAX_FCNT_GAP 16384 1009 ADR_ACK_LIMIT 64 1010 ADR_ACK_DELAY 32 1011 ACK_TIMEOUT 2 +/- 1 s (random delay between 1 and 3 seconds) 1012 If the actual parameter values implemented in the end-device are different from those default 1013 values (for example the end-device uses a longer RECEIVE_DELAY1 & 2 latency), those 1014 parameters MUST be communicated to the network server using an out-of-band channel 1015 during the end-device commissioning process. The network server may not accept 1016 parameters different from those default values. 1017 1018

Articles in this issue

view archives of Document - LoRaWAN® Regional Parameters v1.0.3revA