Changes for page End Device Frequency Band

Last modified by Edwin Chen on 2024/10/21 20:35
<
From version < 13.2 >
edited by Xiaoling
on 2022/12/14 09:21
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -14,20 +14,19 @@
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 18  = 2. OTAA Join Behaviour =
19 19  
19 +Since 005 LoRaWAN stack: One device boot or reset, it will
20 20  
21 -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.
22 22  
23 -(((
24 -For 005 LoRaWAN Stack:
25 -)))
25 +Since 005 LoRaWAN Stack:
26 26  
27 -* EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
28 -* 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
29 29  
30 -
31 31  = 3. Default Frequency Bands =
32 32  
33 33  == 3.1 AS923 ==
... ... @@ -73,7 +73,6 @@
73 73  ** Uplink channels 1-8 (RX1)
74 74  ** 923.2 - SF10BW125 (RX2)
75 75  
76 -
77 77  === 3.1.3 AS923-2 ===
78 78  
79 79  
... ... @@ -87,7 +87,6 @@
87 87  ** Uplink channels 1-8 (RX1)
88 88  ** 921.4 - SF10BW125 (RX2)
89 89  
90 -
91 91  === 3.1.4 AS923-3 ===
92 92  
93 93  
... ... @@ -101,7 +101,6 @@
101 101  ** Uplink channels 1-8 (RX1)
102 102  ** 916.6 - SF10BW125 (RX2)
103 103  
104 -
105 105  === 3.1.5 AS923-4 ===
106 106  
107 107  
... ... @@ -115,7 +115,6 @@
115 115  ** Uplink channels 1-8 (RX1)
116 116  ** 917.3 - SF10BW125 (RX2)
117 117  
118 -
119 119  == 3.2 AU915-928(AU915) ==
120 120  
121 121  
... ... @@ -160,7 +160,7 @@
160 160  Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
161 161  )))
162 162  * (((
163 -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)
164 164  
165 165  
166 166  
... ... @@ -192,7 +192,6 @@
192 192  ** 508.1 - SF7BW125 to SF12BW125
193 193  ** 505.3 - SF12BW125 (RX2 downlink only)
194 194  
195 -
196 196  == 3.4 EU863-870 (EU868) ==
197 197  
198 198  
... ... @@ -237,7 +237,6 @@
237 237  * 866.5850 - SF7BW125 to SF12BW125
238 238  * 866.7850 - SF7BW125 to SF12BW125
239 239  
240 -
241 241  == 3.6 KZ865 ==
242 242  
243 243  
... ... @@ -252,7 +252,6 @@
252 252  ** The RX1 receive window uses the same channel as the preceding uplink.
253 253  ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)​
254 254  
255 -
256 256  == 3.7 KR920-923 (KR920) ==
257 257  
258 258  
... ... @@ -274,7 +274,6 @@
274 274  ** Uplink channels 1-7(RX1)
275 275  ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
276 276  
277 -
278 278  == 3.8 MA869 ==
279 279  
280 280  
... ... @@ -295,7 +295,6 @@
295 295  ** Uplink channels 1-9 (RX1)
296 296  ** 869.525 - SF12BW125 (RX2 downlink only)
297 297  
298 -
299 299  == 3.9 US902-928 (US915) ==
300 300  
301 301  
... ... @@ -328,7 +328,6 @@
328 328  ** 927.5 - SF7BW500 to SF12BW500
329 329  ** 923.3 - SF12BW500(RX2 downlink only)
330 330  
331 -
332 332  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
333 333  
334 334  
... ... @@ -337,13 +337,9 @@
337 337  )))
338 338  
339 339  (((
340 -
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:
341 341  )))
342 342  
343 -(((
344 -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:
345 -)))
346 -
347 347  * (((
348 348  Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
349 349  )))
... ... @@ -359,3 +359,39 @@
359 359  
360 360  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
361 361  * 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