Changes for page End Device Frequency Band

Last modified by Edwin Chen on 2024/10/21 20:35
<
From version < 13.1 >
edited by Edwin Chen
on 2022/12/13 22:49
To version < 18.1
edited by Edwin Chen
on 2024/10/21 20:35
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -14,28 +14,23 @@
14 14  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
15 15  * Frequency Bands vs Country List : Page 11 of [[LoRaWAN Regional Parameters RP2-1.0.3>>url:https://resources.lora-alliance.org/technical-specifications/rp2-1-0-3-lorawan-regional-parameters]]
16 16  
17 -
18 -
19 19  = 2. OTAA Join Behaviour =
20 20  
19 +Since 005 LoRaWAN stack: One device boot or reset, it will
21 21  
22 -For 005 LoRaWAN stack: to save battery, once boot, device will make first make 200 tries for OTAA Join, the time period of two Join Requests will depends on the DR and the airtime requirement. After this 200 Join finish, device will send a join request every 20 minutes. If device reboot, it will do above loop again.
21 +* First make 200 Join Requestes for OTAA Join, the interval of two Join Requests will depends on the DR and the airtime requirement.
22 +* After 200 Join Requestes, if end node still not join successful, to save battery life, it will keep sending join request at the default uplink interval ( 20 minutes) .
23 +* If device reboot, it will do above loop again.
23 23  
24 -(((
25 -For 005 LoRaWAN Stack:
26 -)))
25 +Since 005 LoRaWAN Stack:
27 27  
28 -* EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
29 -* US915 and AU915 OTAA Join procedure,. End node by default will use all 72 channels to join and it will be set to use the proper sub-band after Join success
27 +* **EU868 OTAA Join DR Logic**. SF7->SF8->SF9->SF10->SF11->SF12; Each SF will make 3 attempts and then loop
28 +* **US915 and AU915 OTAA Join procedure**,. End node by default will use all 72 channels (All sub-bands) to join and it will be set to use the proper sub-band after Join success
30 30  
31 -
32 -
33 33  = 3. Default Frequency Bands =
34 34  
35 -
36 36  == 3.1 AS923 ==
37 37  
38 -
39 39  === 3.1.1 Notice for AS923 Frequency Bands ===
40 40  
41 41  
... ... @@ -48,7 +48,6 @@
48 48  )))
49 49  
50 50  
51 -
52 52  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
53 53  
54 54  
... ... @@ -78,8 +78,6 @@
78 78  ** Uplink channels 1-8 (RX1)
79 79  ** 923.2 - SF10BW125 (RX2)
80 80  
81 -
82 -
83 83  === 3.1.3 AS923-2 ===
84 84  
85 85  
... ... @@ -93,8 +93,6 @@
93 93  ** Uplink channels 1-8 (RX1)
94 94  ** 921.4 - SF10BW125 (RX2)
95 95  
96 -
97 -
98 98  === 3.1.4 AS923-3 ===
99 99  
100 100  
... ... @@ -108,8 +108,6 @@
108 108  ** Uplink channels 1-8 (RX1)
109 109  ** 916.6 - SF10BW125 (RX2)
110 110  
111 -
112 -
113 113  === 3.1.5 AS923-4 ===
114 114  
115 115  
... ... @@ -123,8 +123,6 @@
123 123  ** Uplink channels 1-8 (RX1)
124 124  ** 917.3 - SF10BW125 (RX2)
125 125  
126 -
127 -
128 128  == 3.2 AU915-928(AU915) ==
129 129  
130 130  
... ... @@ -169,10 +169,9 @@
169 169  Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
170 170  )))
171 171  * (((
172 -Use the Join successful sub-band if the server doesn’t include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
158 +Use the Join successful sub-band if the server doesn't include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
173 173  
174 174  
175 -
176 176  
177 177  )))
178 178  
... ... @@ -202,8 +202,6 @@
202 202  ** 508.1 - SF7BW125 to SF12BW125
203 203  ** 505.3 - SF12BW125 (RX2 downlink only)
204 204  
205 -
206 -
207 207  == 3.4 EU863-870 (EU868) ==
208 208  
209 209  
... ... @@ -225,7 +225,6 @@
225 225  OTAA RX2DR is set to DR0, SF12BW125 since 2021,Mar for Dragino Devices.
226 226  
227 227  
228 -
229 229  == 3.5 IN865-867 (IN865) ==
230 230  
231 231  
... ... @@ -238,7 +238,6 @@
238 238  ** Uplink channels 1-3 (RX1)
239 239  ** 866.550 - SF10BW125 (RX2)
240 240  
241 -
242 242  Gateway has below eight channels in IN865 bands.
243 243  
244 244  * 865.0625 - SF7BW125 to SF12BW125
... ... @@ -250,7 +250,6 @@
250 250  * 866.5850 - SF7BW125 to SF12BW125
251 251  * 866.7850 - SF7BW125 to SF12BW125
252 252  
253 -
254 254  == 3.6 KZ865 ==
255 255  
256 256  
... ... @@ -265,8 +265,6 @@
265 265  ** The RX1 receive window uses the same channel as the preceding uplink.
266 266  ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)​
267 267  
268 -
269 -
270 270  == 3.7 KR920-923 (KR920) ==
271 271  
272 272  
... ... @@ -288,8 +288,6 @@
288 288  ** Uplink channels 1-7(RX1)
289 289  ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
290 290  
291 -
292 -
293 293  == 3.8 MA869 ==
294 294  
295 295  
... ... @@ -310,8 +310,6 @@
310 310  ** Uplink channels 1-9 (RX1)
311 311  ** 869.525 - SF12BW125 (RX2 downlink only)
312 312  
313 -
314 -
315 315  == 3.9 US902-928 (US915) ==
316 316  
317 317  
... ... @@ -318,7 +318,6 @@
318 318  Used in USA, Canada and South America.
319 319  
320 320  
321 -
322 322  === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
323 323  
324 324  
... ... @@ -345,8 +345,6 @@
345 345  ** 927.5 - SF7BW500 to SF12BW500
346 346  ** 923.3 - SF12BW500(RX2 downlink only)
347 347  
348 -
349 -
350 350  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
351 351  
352 352  
... ... @@ -355,13 +355,9 @@
355 355  )))
356 356  
357 357  (((
358 -
329 +So since **Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]**, we have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join. In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
359 359  )))
360 360  
361 -(((
362 -So since **Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]**, we have improved this, the end node will use frequency 1 from sub-band1, then frequency 1 from sub-band2, then frequency 1 from sub-band3, etc to process the OTAA join, In this case, In this case, the end node can support LoRaWAN servers with different subbands. To make sure the end node will only transmit the proper sub-band after OTAA Joined successfully, the end node will:
363 -)))
364 -
365 365  * (((
366 366  Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
367 367  )))
... ... @@ -369,7 +369,6 @@
369 369  Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include)
370 370  
371 371  
372 -
373 373  
374 374  )))
375 375  
... ... @@ -378,3 +378,39 @@
378 378  
379 379  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
380 380  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
347 +
348 +
349 += 5. Subband Related questiones in US915, AU915, CN470 bands. =
350 +
351 +
352 +Frequency band US915, AU915 and CN470 supports totally 72 frequency in 8 sub-bands, Normally Gateway only support 8 channels ( one subband). So how does the gateway and end nodes work in such frequency?
353 +
354 +
355 +== 5.1 Set Subband in Gateway. ==
356 +
357 +
358 +* If Gateway choose (% style="color:blue" %)**Semtech UDP packet**(%%) forwarder to Connect to LoRaWAN server. User need to manually set the match Subband in the gateway web UI.
359 +
360 +* If Gateway choose (% style="color:blue" %)**Basic Station Mode**(%%) to connect to the LoRaWAN server. User can set the subband in the Server side and gateway will the correct subband from server. no need to set this in gateway. AWS-IoT, TTN, ChirpStack all supports Basic Station Connection.
361 +
362 +== 5.2 Set Subband in End Node ==
363 +
364 +
365 +* In early End Node firmware, it is pre-set to subband 2 , user need to manually set to proper subband if they don;t use subband 2.
366 +
367 +* In new end node firmware , it supports all sub-bands, and will swtich to the proper subband after OTAA join. So user can use the end node with all sub-band.
368 +
369 +Reference: [[How it affects the OTAA Join when end node is set to support all subbands>>http://wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H13.WhyittakeslongertimeforOTAAjoinedinUS9152FCN4702FAU915band3F]]?
370 +
371 +
372 += 6. Data Rate and TXP auto-adjust logic. =
373 +
374 +In below cases the sensor end node will auto-adjust. (ADR must set to 1)
375 +
376 +* Auto-just according to the server ADR request change downlink command.
377 +* If there is no adr_req_ack arrive the sensor end node for more than 64 uplinks, end node will set the output to maximum power (AT+TXP=0).
378 +* If there is no adr_req_ack arrive the sensor end node for more than 96 uplinks, end node will reduce the Data Rate by 1.
379 +
380 +
381 +
382 +

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0