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
-
... ... @@ -1,11 +1,8 @@ 1 1 (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %) 2 - **Contents：**2 + 3 3 4 4 {{toc/}} 5 5 6 - 7 - 8 - 9 9 = 1. Introduction = 10 10 11 11 This page list the default frequency band for Dragino End Devices. The frequency bands are base on TTN Frequency Bands. User can modify upgrade firmware to support different frequency band or use AT Command to change the sub band in some frequency bands. ... ... @@ -13,8 +13,6 @@ 13 13 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]] 14 14 * 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]] 15 15 16 - 17 - 18 18 = 2. OTAA Join Behaviour = 19 19 20 20 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. ... ... @@ -26,8 +26,6 @@ 26 26 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop 27 27 * 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 29 - 30 - 31 31 = 3. Default Frequency Bands = 32 32 33 33 ... ... @@ -44,6 +44,7 @@ 44 44 ))) 45 45 46 46 40 + 47 47 === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) === 48 48 49 49 * Default Uplink channel: ... ... @@ -71,7 +71,6 @@ 71 71 ** Uplink channels 1-8 (RX1) 72 72 ** 923.2 - SF10BW125 (RX2) 73 73 74 - 75 75 === 3.1.3 AS923-2 === 76 76 77 77 * Default Uplink channel: ... ... @@ -84,7 +84,6 @@ 84 84 ** Uplink channels 1-8 (RX1) 85 85 ** 921.4 - SF10BW125 (RX2) 86 86 87 - 88 88 === 3.1.4 AS923-3 === 89 89 90 90 * Default Uplink channel: ... ... @@ -97,7 +97,6 @@ 97 97 ** Uplink channels 1-8 (RX1) 98 98 ** 916.6 - SF10BW125 (RX2) 99 99 100 - 101 101 === 3.1.5 AS923-4 === 102 102 103 103 * Countries : Israel ... ... @@ -110,7 +110,6 @@ 110 110 ** Uplink channels 1-8 (RX1) 111 111 ** 917.3 - SF10BW125 (RX2) 112 112 113 - 114 114 == 3.2 AU915-928(AU915) == 115 115 116 116 **Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2 ... ... @@ -136,29 +136,15 @@ 136 136 ** 927.5 - SF7BW500 to SF12BW500 137 137 ** 923.3 - SF12BW500(RX2 downlink only) 138 138 139 -((( 140 140 There is a issue if the end node is fixed at sub-band2. The sensor won't be able to register to other sub-band and can only works for the LoRaWAN server use sub-band2 , such as TTN. To solve this, user need to use a USB-TTL adapter to connect to the end node to manually set the sub-band which is very inconvinient. 141 -))) 142 142 143 - 144 -((( 145 145 So since **Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]**, To make sure the end node supports all sub band by default. In the OTAA Join process, 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. 146 -))) 147 147 148 - 149 -((( 150 150 After Join success, the end node will switch to the correct sub band by: 151 -))) 152 152 153 -* ((( 154 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 155 -))) 156 -* ((( 157 -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) 135 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 136 +* 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 158 159 - 160 -))) 161 - 162 162 == 3.3 CN470-510 (CN470) == 163 163 164 164 Used in China, Default use CHE=1 ... ... @@ -184,7 +184,6 @@ 184 184 ** 508.1 - SF7BW125 to SF12BW125 185 185 ** 505.3 - SF12BW125 (RX2 downlink only) 186 186 187 - 188 188 == 3.4 EU863-870 (EU868) == 189 189 190 190 * Uplink: ... ... @@ -216,7 +216,6 @@ 216 216 ** Uplink channels 1-3 (RX1) 217 217 ** 866.550 - SF10BW125 (RX2) 218 218 219 - 220 220 == 3.6 KZ865 == 221 221 222 222 * Uplink ~-~- 125Khz , DR0 - DR5 ... ... @@ -230,7 +230,6 @@ 230 230 ** The RX1 receive window uses the same channel as the preceding uplink. 231 231 ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz) 232 232 233 - 234 234 == 3.7 KR920-923 (KR920) == 235 235 236 236 * Default channel: ... ... @@ -251,11 +251,8 @@ 251 251 ** Uplink channels 1-7(RX1) 252 252 ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 253 253 254 - 255 255 == 3.8 MA869 == 256 256 257 - Country: Morroco 258 - 259 259 * Uplink: 260 260 ** 869.1 - SF7BW125 to SF12BW125 261 261 ** 869.3 - SF7BW125 to SF12BW125 ... ... @@ -271,12 +271,10 @@ 271 271 ** Uplink channels 1-9 (RX1) 272 272 ** 869.525 - SF12BW125 (RX2 downlink only) 273 273 274 - 275 275 == 3.9 US902-928 (US915) == 276 276 277 277 Used in USA, Canada and South America. 278 278 279 - 280 280 === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. === 281 281 282 282 Default use CHE=2, Subband 2 ... ... @@ -304,27 +304,13 @@ 304 304 305 305 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 306 306 307 -((( 308 308 There is an issue if the end node is fixed at sub-band2. The sensor won't be able to register to other sub-band and can only work for the LoRaWAN server use sub-band2 , such as TTN. To solve this, the user needs to use a USB-TTL adapter to connect to the end node to manually set the sub-band which is very inconvenient. 309 -))) 310 310 311 -((( 312 - 313 -))) 314 - 315 -((( 316 316 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: 317 -))) 318 318 319 -* ((( 320 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 321 -))) 322 -* ((( 323 -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) 279 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 280 +* 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) 324 324 325 - 326 -))) 327 - 328 328 = 4. Frequency Bands for different server = 329 329 330 330 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]