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,8 +71,6 @@ 71 71 ** Uplink channels 1-8 (RX1) 72 72 ** 923.2 - SF10BW125 (RX2) 73 73 74 - 75 - 76 76 === 3.1.3 AS923-2 === 77 77 78 78 * Default Uplink channel: ... ... @@ -85,8 +85,6 @@ 85 85 ** Uplink channels 1-8 (RX1) 86 86 ** 921.4 - SF10BW125 (RX2) 87 87 88 - 89 - 90 90 === 3.1.4 AS923-3 === 91 91 92 92 * Default Uplink channel: ... ... @@ -99,8 +99,6 @@ 99 99 ** Uplink channels 1-8 (RX1) 100 100 ** 916.6 - SF10BW125 (RX2) 101 101 102 - 103 - 104 104 === 3.1.5 AS923-4 === 105 105 106 106 * Countries : Israel ... ... @@ -113,8 +113,6 @@ 113 113 ** Uplink channels 1-8 (RX1) 114 114 ** 917.3 - SF10BW125 (RX2) 115 115 116 - 117 - 118 118 == 3.2 AU915-928(AU915) == 119 119 120 120 **Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2 ... ... @@ -140,29 +140,15 @@ 140 140 ** 927.5 - SF7BW500 to SF12BW500 141 141 ** 923.3 - SF12BW500(RX2 downlink only) 142 142 143 -((( 144 144 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. 145 -))) 146 146 147 - 148 -((( 149 149 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. 150 -))) 151 151 152 - 153 -((( 154 154 After Join success, the end node will switch to the correct sub band by: 155 -))) 156 156 157 -* ((( 158 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 159 -))) 160 -* ((( 161 -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) 162 162 163 - 164 -))) 165 - 166 166 == 3.3 CN470-510 (CN470) == 167 167 168 168 Used in China, Default use CHE=1 ... ... @@ -188,8 +188,6 @@ 188 188 ** 508.1 - SF7BW125 to SF12BW125 189 189 ** 505.3 - SF12BW125 (RX2 downlink only) 190 190 191 - 192 - 193 193 == 3.4 EU863-870 (EU868) == 194 194 195 195 * Uplink: ... ... @@ -256,8 +256,6 @@ 256 256 257 257 == 3.8 MA869 == 258 258 259 - Country: Morroco 260 - 261 261 * Uplink: 262 262 ** 869.1 - SF7BW125 to SF12BW125 263 263 ** 869.3 - SF7BW125 to SF12BW125 ... ... @@ -277,7 +277,6 @@ 277 277 278 278 Used in USA, Canada and South America. 279 279 280 - 281 281 === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. === 282 282 283 283 Default use CHE=2, Subband 2 ... ... @@ -305,27 +305,13 @@ 305 305 306 306 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 307 307 308 -((( 309 309 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. 310 -))) 311 311 312 -((( 313 - 314 -))) 315 - 316 -((( 317 317 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: 318 -))) 319 319 320 -* ((( 321 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 322 -))) 323 -* ((( 324 -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) 325 325 326 - 327 -))) 328 - 329 329 = 4. Frequency Bands for different server = 330 330 331 331 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]