Document

LoRaWAN® Specification v1.0.3

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

Contents of this Issue

Navigation

Page 29 of 71

LoRaWAN 1.0.3 Specification ©2018 LoRa™ Alliance Page 30 of 72 The authors reserve the right to change specifications without notice. Uplink frequency exists The uplink frequency is not defined for this channel , the downlink frequency can only be set for a channel that already has a valid uplink frequency The uplink frequency of the channel is valid Table 11: DlChannelAns status bits signification 832 If either of those 2 bits equals 0, the command did not succeed and the RX1 slot channel 833 frequency has not been updated. 834 835 836 5.7 Setting delay between TX and RX (RXTimingSetupReq, 837 RXTimingSetupAns) 838 The RXTimingSetupReq command allows configuring the delay between the end of the TX 839 uplink and the opening of the first reception slot. The second reception slot opens one second 840 after the first reception slot. 841 Size (bytes) 1 RXTimingSetupReq Payload Settings 842 The delay (Delay) field specifies the delay. The field is split in two 4-bit indexes: 843 Bits 7:4 3:0 Settings RFU Del 844 The delay is expressed in seconds. Del 0 is mapped on 1 s. 845 Del Delay [s] 0 1 1 1 2 2 3 3 .. .. 15 15 Table 12: Del mapping table 846 847 An end device answers RXTimingSetupReq with RXTimingSetupAns with no payload. 848 The RXTimingSetupAns command should be added in the FOpt field of all uplinks until a 849 class A downlink is received by the end-device. This guarantees that even in presence of 850 uplink packet loss, the network is always aware of the downlink parameters used by the end- 851 device. 852 853 5.8 End-device transmission parameters (TxParamSetupReq, 854 TxParamSetupAns) 855 This MAC command only needs to be implemented for compliance in certain regulatory 856 regions. Please refer to the "LoRaWAN physical layer definitions" document. 857

Articles in this issue

view archives of Document - LoRaWAN® Specification v1.0.3