Changes for page End Device Frequency Band
Last modified by Edwin Chen on 2024/10/21 20:35
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -15,6 +15,7 @@ 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 17 18 + 18 18 = 2. OTAA Join Behaviour = 19 19 20 20 ... ... @@ -28,6 +28,7 @@ 28 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 29 29 30 30 32 + 31 31 = 3. Default Frequency Bands = 32 32 33 33 == 3.1 AS923 == ... ... @@ -74,6 +74,7 @@ 74 74 ** 923.2 - SF10BW125 (RX2) 75 75 76 76 79 + 77 77 === 3.1.3 AS923-2 === 78 78 79 79 ... ... @@ -88,6 +88,7 @@ 88 88 ** 921.4 - SF10BW125 (RX2) 89 89 90 90 94 + 91 91 === 3.1.4 AS923-3 === 92 92 93 93 ... ... @@ -102,6 +102,7 @@ 102 102 ** 916.6 - SF10BW125 (RX2) 103 103 104 104 109 + 105 105 === 3.1.5 AS923-4 === 106 106 107 107 ... ... @@ -116,6 +116,7 @@ 116 116 ** 917.3 - SF10BW125 (RX2) 117 117 118 118 124 + 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)169 +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 ... ... @@ -193,6 +193,7 @@ 193 193 ** 505.3 - SF12BW125 (RX2 downlink only) 194 194 195 195 202 + 196 196 == 3.4 EU863-870 (EU868) == 197 197 198 198 ... ... @@ -238,6 +238,7 @@ 238 238 * 866.7850 - SF7BW125 to SF12BW125 239 239 240 240 248 + 241 241 == 3.6 KZ865 == 242 242 243 243 ... ... @@ -253,6 +253,7 @@ 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 255 264 + 256 256 == 3.7 KR920-923 (KR920) == 257 257 258 258 ... ... @@ -275,6 +275,7 @@ 275 275 ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 276 276 277 277 287 + 278 278 == 3.8 MA869 == 279 279 280 280 ... ... @@ -296,6 +296,7 @@ 296 296 ** 869.525 - SF12BW125 (RX2 downlink only) 297 297 298 298 309 + 299 299 == 3.9 US902-928 (US915) == 300 300 301 301 ... ... @@ -329,6 +329,7 @@ 329 329 ** 923.3 - SF12BW500(RX2 downlink only) 330 330 331 331 343 + 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,10 +337,6 @@ 337 337 ))) 338 338 339 339 ((( 340 - 341 -))) 342 - 343 -((( 344 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 345 ))) 346 346 ... ... @@ -359,3 +359,35 @@ 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]] 370 + 371 + 372 + 373 += 5. Subband Related questiones in US915, AU915, CN470 bands. = 374 + 375 + 376 +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? 377 + 378 + 379 +== 5.1 Set Subband in Gateway. == 380 + 381 + 382 +* 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. 383 + 384 +* 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. 385 + 386 + 387 + 388 +== 5.2 Set Subband in End Node == 389 + 390 + 391 +* 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. 392 + 393 +* 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. 394 + 395 +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]]? 396 + 397 + 398 + 399 + 400 + 401 +