Changes for page End Device Frequency Band

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

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -14,18 +14,22 @@
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 +
17 17  = 2. OTAA Join Behaviour =
18 18  
19 19  
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.
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 21  
22 22  (((
23 -Since 005 LoRaWAN Stack:
25 +For 005 LoRaWAN Stack:
24 24  )))
25 25  
26 26  * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
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
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
28 28  
31 +
32 +
29 29  = 3. Default Frequency Bands =
30 30  
31 31  == 3.1 AS923 ==
... ... @@ -71,6 +71,8 @@
71 71  ** Uplink channels 1-8 (RX1)
72 72  ** 923.2 - SF10BW125 (RX2)
73 73  
78 +
79 +
74 74  === 3.1.3 AS923-2 ===
75 75  
76 76  
... ... @@ -84,6 +84,7 @@
84 84  ** Uplink channels 1-8 (RX1)
85 85  ** 921.4 - SF10BW125 (RX2)
86 86  
93 +
87 87  === 3.1.4 AS923-3 ===
88 88  
89 89  
... ... @@ -97,6 +97,8 @@
97 97  ** Uplink channels 1-8 (RX1)
98 98  ** 916.6 - SF10BW125 (RX2)
99 99  
107 +
108 +
100 100  === 3.1.5 AS923-4 ===
101 101  
102 102  
... ... @@ -110,6 +110,8 @@
110 110  ** Uplink channels 1-8 (RX1)
111 111  ** 917.3 - SF10BW125 (RX2)
112 112  
122 +
123 +
113 113  == 3.2 AU915-928(AU915) ==
114 114  
115 115  
... ... @@ -186,6 +186,8 @@
186 186  ** 508.1 - SF7BW125 to SF12BW125
187 187  ** 505.3 - SF12BW125 (RX2 downlink only)
188 188  
200 +
201 +
189 189  == 3.4 EU863-870 (EU868) ==
190 190  
191 191  
... ... @@ -230,6 +230,8 @@
230 230  * 866.5850 - SF7BW125 to SF12BW125
231 231  * 866.7850 - SF7BW125 to SF12BW125
232 232  
246 +
247 +
233 233  == 3.6 KZ865 ==
234 234  
235 235  
... ... @@ -244,6 +244,8 @@
244 244  ** The RX1 receive window uses the same channel as the preceding uplink.
245 245  ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)​
246 246  
262 +
263 +
247 247  == 3.7 KR920-923 (KR920) ==
248 248  
249 249  
... ... @@ -265,6 +265,8 @@
265 265  ** Uplink channels 1-7(RX1)
266 266  ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
267 267  
285 +
286 +
268 268  == 3.8 MA869 ==
269 269  
270 270  
... ... @@ -285,6 +285,8 @@
285 285  ** Uplink channels 1-9 (RX1)
286 286  ** 869.525 - SF12BW125 (RX2 downlink only)
287 287  
307 +
308 +
288 288  == 3.9 US902-928 (US915) ==
289 289  
290 290  
... ... @@ -317,6 +317,8 @@
317 317  ** 927.5 - SF7BW500 to SF12BW500
318 318  ** 923.3 - SF12BW500(RX2 downlink only)
319 319  
341 +
342 +
320 320  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
321 321  
322 322  
... ... @@ -325,9 +325,13 @@
325 325  )))
326 326  
327 327  (((
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:
351 +
329 329  )))
330 330  
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 +
331 331  * (((
332 332  Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
333 333  )))
... ... @@ -344,30 +344,5 @@
344 344  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
345 345  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
346 346  
347 -= 5. Subband Related questiones in US915, AU915, CN470 bands. =
348 348  
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 -
373 373  

Applications

Navigation

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