Issue link: https://read.uberflip.com/i/1428386
LoRaWAN Specification ©2016 LoRa™ Alliance Page 71 of 91 The authors reserve the right to change specifications without notice. DrRange is the data rate range allowed on this channel. This byte is split in two 4-bit 1 indexes. 2 3 Bits 7:4 3:0 DrRange Max data rate Min data rate 4 Following the convention defined in the "Physical layer" section of the Class A specification, 5 the "Min data rate" subfield designates the lowest data rate allowed on this channel. For 6 example 0 designates DR0 / 125 kHz in the EU physical layer. Similarly "Max data rate" 7 designates the highest data rate. For example in the EU spec, DrRange = 0x77 means that 8 only 50 kbps GFSK is allowed on a channel and DrRange = 0x50 means that DR0 / 125 kHz 9 to DR5 / 125 kHz are supported. 10 Upon reception of this command the end-device answers with a PingSlotFreqAns 11 message. The MAC payload of this message contains the following information: 12 13 Size (bytes) 1 pingSlotFreqAns Payload Status The Status bits have the following meaning: 14 Bits 7:2 1 0 Status RFU Data rate range ok Channel frequency ok 15 Bit = 0 Bit = 1 Data rate range ok The designated data rate range exceeds the ones currently defined for this end device, the previous range is kept The data rate range is compatible with the possibilities of the end device Channel frequency ok The device cannot use this frequency, the previous ping frequency is kept The device is able to use this frequency. 15.4 BeaconTimingReq 16 This command is sent by the end-device to request the next beacon timing and channel. 17 This MAC command has no payload. The BeaconTimingReq & BeaconTimingAns 18 mechanism is only meant to accelerate the initial beacon search to lower the end-device 19 energy requirement. 20 The network may answer only a limited number of requests per a given time period. An end- 21 device must not expect that BeaconTimingReq is answered immediately with a 22 BeaconTimingAns. Class A end-devices wanting to switch to Class B should not transmit 23 more than one BeaconTimingReq per hour. 24 End-devices requiring a fast beacon lock must implement an autonomous beacon finding 25 algorithm. 26
