Issue link: https://read.uberflip.com/i/1428362
LoRaWAN 1.0.2 Regional Parameters ©2017 LoRa Alliance™ Page 32 of 55 The authors reserve the right to change specifications without notice. the Class A specification Table 40 : AU915-928 beacon settings 844 The downstream channel used for a given beacon is: 845 Channel = [ ( _ _ ) ] 8 846 whereby beacon_time is the integer value of the 4 bytes "Time" field of the beacon 847 frame 848 whereby beacon_period is the periodicity of beacons , 128 seconds 849 whereby floor(x) designates rounding to the integer immediately inferior or equal to x 850 851 Example: the first beacon will be transmitted on 923.3Mhz , the second 852 on 923.9MHz, the 9 th beacon will be on 923.3Mhz again. 853 854 855 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 856 857 The beacon frame content is: 858 Size (bytes) 3 4 2 7 1 2 BCNPayload RFU Time CRC GwSpecific RFU CRC 859 2.5.9 AU915-928 Default Settings 860 The following parameters are recommended values for the AU915-928 band. 861 RECEIVE_DELAY1 1 s 862 RECEIVE_DELAY2 2 s (must be RECEIVE_DELAY1 + 1s) 863 JOIN_ACCEPT_DELAY1 5 s 864 JOIN_ACCEPT_DELAY2 6 s 865 MAX_FCNT_GAP 16384 866 ADR_ACK_LIMIT 64 867 ADR_ACK_DELAY 32 868 ACK_TIMEOUT 2 +/- 1 s (random delay between 1 and 3 seconds) 869 If the actual parameter values implemented in the end-device are different from those default 870 values (for example the end-device uses a longer RECEIVE_DELAY1 & 2 latency), those 871 parameters must be communicated to the network server using an out-of-band channel 872 during the end-device commissioning process. The network server may not accept 873 parameters different from those default values. 874 875