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,12 @@ 1 1 (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %) 2 - **Contents：**2 + 3 3 4 - {{toc/}}4 += Contents： = 5 5 6 + ~[[[hide>>url:https://http://8.211.40.43:8080/xwiki/bin/view/Main/End%20Device%20Frequency%20Band]]] 6 6 8 +{{toc/}} 7 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,21 +13,15 @@ 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. 21 21 22 -((( 23 23 For 005 LoRaWAN Stack: 24 -))) 25 25 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 ... ... @@ -35,15 +35,12 @@ 35 35 36 36 === 3.1.1 Notice for AS923 Frequency Bands === 37 37 38 -((( 39 39 Since [[RP002-1.0.1LoRaWAN Regional Parameters>>url:https://lora-alliance.org/sites/default/files/2020-02/rp_2-1.0.1.pdf]], AS923 include three different default settings for different countries: AS923-1, AS923-2 and AS923-3. 40 -))) 41 41 42 -((( 43 43 AS923-1 use the same default uplink frequency as previous AS923 firmware. AS923-2 and AS923-3 are new with different default uplink frequency. User need to know exactly the frequency bands from the LoRaWAN server and choose the right firmware version for the end node. 44 -))) 45 45 46 46 38 + 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: ... ... @@ -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) 133 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 134 +* 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 ... ... @@ -250,8 +250,6 @@ 250 250 251 251 == 3.8 MA869 == 252 252 253 - Country: Morroco 254 - 255 255 * Uplink: 256 256 ** 869.1 - SF7BW125 to SF12BW125 257 257 ** 869.3 - SF7BW125 to SF12BW125 ... ... @@ -271,7 +271,6 @@ 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 ... ... @@ -299,27 +299,13 @@ 299 299 300 300 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 301 301 302 -((( 303 303 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. 304 -))) 305 305 306 -((( 307 - 308 -))) 309 - 310 -((( 311 311 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: 312 -))) 313 313 314 -* ((( 315 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 316 -))) 317 -* ((( 318 -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) 277 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 278 +* 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) 319 319 320 - 321 -))) 322 - 323 323 = 4. Frequency Bands for different server = 324 324 325 325 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]