Changes for page End Device Frequency Band
Last modified by Edwin Chen on 2024/10/21 20:35
Change comment:
There is no comment for this version
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -15,13 +15,14 @@ 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 21 - Since005 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. 22 22 23 23 ((( 24 - Since005 LoRaWAN Stack:25 +For 005 LoRaWAN Stack: 25 25 ))) 26 26 27 27 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop ... ... @@ -28,10 +28,13 @@ 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 35 + 33 33 == 3.1 AS923 == 34 34 38 + 35 35 === 3.1.1 Notice for AS923 Frequency Bands === 36 36 37 37 ... ... @@ -44,6 +44,7 @@ 44 44 ))) 45 45 46 46 51 + 47 47 === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) === 48 48 49 49 ... ... @@ -74,6 +74,7 @@ 74 74 ** 923.2 - SF10BW125 (RX2) 75 75 76 76 82 + 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 97 + 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 112 + 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 127 + 119 119 == 3.2 AU915-928(AU915) == 120 120 121 121 ... ... @@ -160,9 +160,10 @@ 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)172 +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 175 + 166 166 167 167 ))) 168 168 ... ... @@ -193,6 +193,7 @@ 193 193 ** 505.3 - SF12BW125 (RX2 downlink only) 194 194 195 195 206 + 196 196 == 3.4 EU863-870 (EU868) == 197 197 198 198 ... ... @@ -214,6 +214,7 @@ 214 214 OTAA RX2DR is set to DR0, SF12BW125 since 2021,Mar for Dragino Devices. 215 215 216 216 228 + 217 217 == 3.5 IN865-867 (IN865) == 218 218 219 219 ... ... @@ -226,6 +226,7 @@ 226 226 ** Uplink channels 1-3 (RX1) 227 227 ** 866.550 - SF10BW125 (RX2) 228 228 241 + 229 229 Gateway has below eight channels in IN865 bands. 230 230 231 231 * 865.0625 - SF7BW125 to SF12BW125 ... ... @@ -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 269 + 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 292 + 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 314 + 299 299 == 3.9 US902-928 (US915) == 300 300 301 301 ... ... @@ -302,6 +302,7 @@ 302 302 Used in USA, Canada and South America. 303 303 304 304 321 + 305 305 === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. === 306 306 307 307 ... ... @@ -329,6 +329,7 @@ 329 329 ** 923.3 - SF12BW500(RX2 downlink only) 330 330 331 331 349 + 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,6 +337,10 @@ 337 337 ))) 338 338 339 339 ((( 358 + 359 +))) 360 + 361 +((( 340 340 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: 341 341 ))) 342 342 ... ... @@ -347,6 +347,7 @@ 347 347 Use the Join successful sub-band if the server doesn't include subband info in the OTAA Join Accept message ( TTN v2 doesn't include) 348 348 349 349 372 + 350 350 351 351 ))) 352 352 ... ... @@ -355,33 +355,3 @@ 355 355 356 356 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]] 357 357 * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]] 358 - 359 - 360 -= 5. Subband Related questiones in US915, AU915, CN470 bands. = 361 - 362 - 363 -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? 364 - 365 - 366 -== 5.1 Set Subband in Gateway. == 367 - 368 - 369 -* 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. 370 - 371 -* 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. 372 - 373 - 374 -== 5.2 Set Subband in End Node == 375 - 376 - 377 -* 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. 378 - 379 -* 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. 380 - 381 -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]]? 382 - 383 - 384 - 385 - 386 - 387 -