Changes for page End Device Frequency Band
Last modified by Edwin Chen on 2024/10/21 20:35
<
edited by Edwin Chen
on 2024/10/21 20:35
on 2024/10/21 20:35
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Edwin - Content
-
... ... @@ -14,22 +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 - 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 loop29 -* 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 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,8 +90,6 @@ 90 90 ** Uplink channels 1-8 (RX1) 91 91 ** 921.4 - SF10BW125 (RX2) 92 92 93 - 94 - 95 95 === 3.1.4 AS923-3 === 96 96 97 97 ... ... @@ -105,8 +105,6 @@ 105 105 ** Uplink channels 1-8 (RX1) 106 106 ** 916.6 - SF10BW125 (RX2) 107 107 108 - 109 - 110 110 === 3.1.5 AS923-4 === 111 111 112 112 ... ... @@ -120,8 +120,6 @@ 120 120 ** Uplink channels 1-8 (RX1) 121 121 ** 917.3 - SF10BW125 (RX2) 122 122 123 - 124 - 125 125 == 3.2 AU915-928(AU915) == 126 126 127 127 ... ... @@ -198,8 +198,6 @@ 198 198 ** 508.1 - SF7BW125 to SF12BW125 199 199 ** 505.3 - SF12BW125 (RX2 downlink only) 200 200 201 - 202 - 203 203 == 3.4 EU863-870 (EU868) == 204 204 205 205 ... ... @@ -244,8 +244,6 @@ 244 244 * 866.5850 - SF7BW125 to SF12BW125 245 245 * 866.7850 - SF7BW125 to SF12BW125 246 246 247 - 248 - 249 249 == 3.6 KZ865 == 250 250 251 251 ... ... @@ -260,8 +260,6 @@ 260 260 ** The RX1 receive window uses the same channel as the preceding uplink. 261 261 ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz) 262 262 263 - 264 - 265 265 == 3.7 KR920-923 (KR920) == 266 266 267 267 ... ... @@ -283,8 +283,6 @@ 283 283 ** Uplink channels 1-7(RX1) 284 284 ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 285 285 286 - 287 - 288 288 == 3.8 MA869 == 289 289 290 290 ... ... @@ -305,8 +305,6 @@ 305 305 ** Uplink channels 1-9 (RX1) 306 306 ** 869.525 - SF12BW125 (RX2 downlink only) 307 307 308 - 309 - 310 310 == 3.9 US902-928 (US915) == 311 311 312 312 ... ... @@ -339,8 +339,6 @@ 339 339 ** 927.5 - SF7BW500 to SF12BW500 340 340 ** 923.3 - SF12BW500(RX2 downlink only) 341 341 342 - 343 - 344 344 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 345 345 346 346 ... ... @@ -349,13 +349,9 @@ 349 349 ))) 350 350 351 351 ((( 352 - 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: 353 353 ))) 354 354 355 -((( 356 -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: 357 -))) 358 - 359 359 * ((( 360 360 Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 361 361 ))) ... ... @@ -372,4 +372,38 @@ 372 372 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]] 373 373 * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]] 374 374 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 + 375 375