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,7 +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 17 = 2. OTAA Join Behaviour = 18 18 19 19 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. ... ... @@ -25,7 +25,6 @@ 25 25 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop 26 26 * 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 27 28 - 29 29 = 3. Default Frequency Bands = 30 30 31 31 ... ... @@ -42,6 +42,7 @@ 42 42 ))) 43 43 44 44 40 + 45 45 === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) === 46 46 47 47 * Default Uplink channel: ... ... @@ -69,7 +69,6 @@ 69 69 ** Uplink channels 1-8 (RX1) 70 70 ** 923.2 - SF10BW125 (RX2) 71 71 72 - 73 73 === 3.1.3 AS923-2 === 74 74 75 75 * Default Uplink channel: ... ... @@ -131,29 +131,15 @@ 131 131 ** 927.5 - SF7BW500 to SF12BW500 132 132 ** 923.3 - SF12BW500(RX2 downlink only) 133 133 134 -((( 135 135 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. 136 -))) 137 137 138 - 139 -((( 140 140 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. 141 -))) 142 142 143 - 144 -((( 145 145 After Join success, the end node will switch to the correct sub band by: 146 -))) 147 147 148 -* ((( 149 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 150 -))) 151 -* ((( 152 -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) 153 153 154 - 155 -))) 156 - 157 157 == 3.3 CN470-510 (CN470) == 158 158 159 159 Used in China, Default use CHE=1 ... ... @@ -179,7 +179,6 @@ 179 179 ** 508.1 - SF7BW125 to SF12BW125 180 180 ** 505.3 - SF12BW125 (RX2 downlink only) 181 181 182 - 183 183 == 3.4 EU863-870 (EU868) == 184 184 185 185 * Uplink: ... ... @@ -211,7 +211,6 @@ 211 211 ** Uplink channels 1-3 (RX1) 212 212 ** 866.550 - SF10BW125 (RX2) 213 213 214 - 215 215 == 3.6 KZ865 == 216 216 217 217 * Uplink ~-~- 125Khz , DR0 - DR5 ... ... @@ -225,7 +225,6 @@ 225 225 ** The RX1 receive window uses the same channel as the preceding uplink. 226 226 ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz) 227 227 228 - 229 229 == 3.7 KR920-923 (KR920) == 230 230 231 231 * Default channel: ... ... @@ -246,11 +246,8 @@ 246 246 ** Uplink channels 1-7(RX1) 247 247 ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 248 248 249 - 250 250 == 3.8 MA869 == 251 251 252 - Country: Morroco 253 - 254 254 * Uplink: 255 255 ** 869.1 - SF7BW125 to SF12BW125 256 256 ** 869.3 - SF7BW125 to SF12BW125 ... ... @@ -266,12 +266,10 @@ 266 266 ** Uplink channels 1-9 (RX1) 267 267 ** 869.525 - SF12BW125 (RX2 downlink only) 268 268 269 - 270 270 == 3.9 US902-928 (US915) == 271 271 272 272 Used in USA, Canada and South America. 273 273 274 - 275 275 === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. === 276 276 277 277 Default use CHE=2, Subband 2 ... ... @@ -297,30 +297,15 @@ 297 297 ** 927.5 - SF7BW500 to SF12BW500 298 298 ** 923.3 - SF12BW500(RX2 downlink only) 299 299 300 - 301 301 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 302 302 303 -((( 304 304 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. 305 -))) 306 306 307 -((( 308 - 309 -))) 310 - 311 -((( 312 312 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: 313 -))) 314 314 315 -* ((( 316 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 317 -))) 318 -* ((( 319 -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) 320 320 321 - 322 -))) 323 - 324 324 = 4. Frequency Bands for different server = 325 325 326 326 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]