Changes for page End Device Frequency Band

Last modified by Edwin Chen on 2024/10/21 20:35
<
From version < 13.4 >
edited by Xiaoling
on 2022/12/14 09:24
To version < 16.1 >
edited by Edwin Chen
on 2023/12/07 09:47
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -14,22 +14,18 @@
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  
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.
20 +Since 005 LoRaWAN stack: to save battery, once boot, device will 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.
23 23  
24 24  (((
25 -For 005 LoRaWAN Stack:
23 +Since 005 LoRaWAN Stack:
26 26  )))
27 27  
28 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 +* 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 35  == 3.1 AS923 ==
... ... @@ -75,8 +75,6 @@
75 75  ** Uplink channels 1-8 (RX1)
76 76  ** 923.2 - SF10BW125 (RX2)
77 77  
78 -
79 -
80 80  === 3.1.3 AS923-2 ===
81 81  
82 82  
... ... @@ -90,7 +90,6 @@
90 90  ** Uplink channels 1-8 (RX1)
91 91  ** 921.4 - SF10BW125 (RX2)
92 92  
93 -
94 94  === 3.1.4 AS923-3 ===
95 95  
96 96  
... ... @@ -104,8 +104,6 @@
104 104  ** Uplink channels 1-8 (RX1)
105 105  ** 916.6 - SF10BW125 (RX2)
106 106  
107 -
108 -
109 109  === 3.1.5 AS923-4 ===
110 110  
111 111  
... ... @@ -119,8 +119,6 @@
119 119  ** Uplink channels 1-8 (RX1)
120 120  ** 917.3 - SF10BW125 (RX2)
121 121  
122 -
123 -
124 124  == 3.2 AU915-928(AU915) ==
125 125  
126 126  
... ... @@ -197,8 +197,6 @@
197 197  ** 508.1 - SF7BW125 to SF12BW125
198 198  ** 505.3 - SF12BW125 (RX2 downlink only)
199 199  
200 -
201 -
202 202  == 3.4 EU863-870 (EU868) ==
203 203  
204 204  
... ... @@ -243,8 +243,6 @@
243 243  * 866.5850 - SF7BW125 to SF12BW125
244 244  * 866.7850 - SF7BW125 to SF12BW125
245 245  
246 -
247 -
248 248  == 3.6 KZ865 ==
249 249  
250 250  
... ... @@ -259,8 +259,6 @@
259 259  ** The RX1 receive window uses the same channel as the preceding uplink.
260 260  ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)​
261 261  
262 -
263 -
264 264  == 3.7 KR920-923 (KR920) ==
265 265  
266 266  
... ... @@ -282,8 +282,6 @@
282 282  ** Uplink channels 1-7(RX1)
283 283  ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
284 284  
285 -
286 -
287 287  == 3.8 MA869 ==
288 288  
289 289  
... ... @@ -304,8 +304,6 @@
304 304  ** Uplink channels 1-9 (RX1)
305 305  ** 869.525 - SF12BW125 (RX2 downlink only)
306 306  
307 -
308 -
309 309  == 3.9 US902-928 (US915) ==
310 310  
311 311  
... ... @@ -338,8 +338,6 @@
338 338  ** 927.5 - SF7BW500 to SF12BW500
339 339  ** 923.3 - SF12BW500(RX2 downlink only)
340 340  
341 -
342 -
343 343  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
344 344  
345 345  
... ... @@ -348,13 +348,9 @@
348 348  )))
349 349  
350 350  (((
351 -
328 +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:
352 352  )))
353 353  
354 -(((
355 -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:
356 -)))
357 -
358 358  * (((
359 359  Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
360 360  )))
... ... @@ -371,5 +371,30 @@
371 371  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
372 372  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
373 373  
347 += 5. Subband Related questiones in US915, AU915, CN470 bands. =
374 374  
349 +
350 +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?
351 +
352 +
353 +== 5.1 Set Subband in Gateway. ==
354 +
355 +
356 +* 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.
357 +
358 +* 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.
359 +
360 +== 5.2 Set Subband in End Node ==
361 +
362 +
363 +* 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.
364 +
365 +* 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.
366 +
367 +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]]?
368 +
369 +
370 +
371 +
372 +
375 375  

Applications

Navigation

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