Issue link: https://read.uberflip.com/i/1428395
LoRaWAN ® L2 1.0.4 Specification © 2020 LoRa Alliance ® Page 39 of 90 The authors reserve the right to change specifications without notice. 5.7 Setting Delay between TX and RX (RXTimingSetupReq, 1221 RXTimingSetupAns) 1222 End-devices and Network Servers SHALL implement these commands. 1223 A Network Server can use the RXTimingSetupReq command to configure the delay between 1224 the end of the TX uplink transmission and the opening of RX1. RX2 always opens 1s after 1225 RX1 [RP002]. 1226 1227 Size (octets) 1 RXTimingSetupReq payload RxTimingSettings Table 43: RXTimingSetupReq payload format 1228 1229 1230 The RxTimingSettings field specifies the delay. The field is split in two 4-bit indexes: 1231 1232 Bits 7:4 3:0 RxTimingSettings RFU Del Table 44: RxTiminingSettings field format 1233 1234 1235 The delay is expressed in seconds. Del 0 is mapped to 1s. 1236 1237 Del Delay [s] 0 1 1 1 2 2 3 3 … … 15 15 Table 45: Del mapping 1238 1239 1240 An end-device SHALL answer RXTimingSetupReq with RXTimingSetupAns , which has no 1241 payload. 1242 The RXTimingSetupAns command SHALL be added to the FOpts field (if FPort is either 1243 missing or greater than 0) or to the FRMPayload field (if FPort=0) of all uplinks until a 1244 Class A downlink is received by the end-device. This guarantees that, even in the case of an 1245 uplink frame loss, the Network is always aware of the downlink parameters used by the end- 1246 device. 1247 1248 1249