Issue link: https://read.uberflip.com/i/1428377
LoRaWAN Specification ©2015 LoRa™ Alliance Page 50 of 82 The authors reserve the right to change specifications without notice. 8:15 Not defined Table 34 : EU433 maximum payload size (not repeater compatible) 1 2 7.4.7 EU433 Receive windows 3 The RX1 receive window uses the same channel than the preceding uplink. The data rate is 4 a function of the uplink data rate and the RX1DROffset as given by the following table. The 5 allowed values for RX1DROffset are in the [0:5] range. Values in the range [6:7] are 6 reserved for future use. 7 8 RX1DROffset 0 1 2 3 4 5 Upstream data rate Downstream data rate in RX1 slot DR0 DR0 DR0 DR0 DR0 DR0 DR0 DR1 DR1 DR0 DR0 DR0 DR0 DR0 DR2 DR2 DR1 DR0 DR0 DR0 DR0 DR3 DR3 DR2 DR1 DR0 DR0 DR0 DR4 DR4 DR3 DR2 DR1 DR0 DR0 DR5 DR5 DR4 DR3 DR2 DR1 DR0 DR6 DR6 DR5 DR4 DR3 DR2 DR1 DR7 DR7 DR6 DR5 DR4 DR3 DR2 9 10 11 The RX2 receive window uses a fixed frequency and data rate. The default parameters are 12 434.665MHz / DR0 (SF12 , 125kHz) 13 7.4.8 EU433 Default Settings 14 The following parameters are recommended values for the EU863-870Mhz band. 15 RECEIVE_DELAY1 1 s 16 RECEIVE_DELAY2 2 s (must be RECEIVE_DELAY1 + 1s) 17 JOIN_ACCEPT_DELAY1 5 s 18 JOIN_ACCEPT_DELAY2 6 s 19 MAX_FCNT_GAP 16384 20 ADR_ACK_LIMIT 64 21 ADR_ACK_DELAY 32 22 ACK_TIMEOUT 2 +/- 1 s (random delay between 1 and 3 seconds) 23 24 If the actual parameter values implemented in the end-device are different from those default 25 values (for example the end-device uses a longer RECEIVE_DELAY1 & 2 latency) , those 26 parameters must be communicated to the network server using an out-of-band channel 27 during the end-device commissioning process. The network server may not accept 28 parameters different from those default values. 29
