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,8 +1,11 @@ 1 1 (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %) 2 - 2 + **Contents：** 3 3 4 4 {{toc/}} 5 5 6 + 7 + 8 + 6 6 = 1. Introduction = 7 7 8 8 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. ... ... @@ -10,15 +10,19 @@ 10 10 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]] 11 11 * 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]] 12 12 16 + 13 13 = 2. OTAA Join Behaviour = 14 14 15 15 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. 16 16 21 +((( 17 17 For 005 LoRaWAN Stack: 23 +))) 18 18 19 19 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop 20 20 * 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 21 21 28 + 22 22 = 3. Default Frequency Bands = 23 23 24 24 ... ... @@ -26,12 +26,15 @@ 26 26 27 27 === 3.1.1 Notice for AS923 Frequency Bands === 28 28 36 +((( 29 29 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. 38 +))) 30 30 40 +((( 31 31 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. 42 +))) 32 32 33 33 34 - 35 35 === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) === 36 36 37 37 * Default Uplink channel: ... ... @@ -59,6 +59,7 @@ 59 59 ** Uplink channels 1-8 (RX1) 60 60 ** 923.2 - SF10BW125 (RX2) 61 61 72 + 62 62 === 3.1.3 AS923-2 === 63 63 64 64 * Default Uplink channel: ... ... @@ -120,15 +120,29 @@ 120 120 ** 927.5 - SF7BW500 to SF12BW500 121 121 ** 923.3 - SF12BW500(RX2 downlink only) 122 122 134 +((( 123 123 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 +))) 124 124 138 + 139 +((( 125 125 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 +))) 126 126 143 + 144 +((( 127 127 After Join success, the end node will switch to the correct sub band by: 146 +))) 128 128 129 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 130 -* 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) 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) 131 131 154 + 155 +))) 156 + 132 132 == 3.3 CN470-510 (CN470) == 133 133 134 134 Used in China, Default use CHE=1 ... ... @@ -154,6 +154,7 @@ 154 154 ** 508.1 - SF7BW125 to SF12BW125 155 155 ** 505.3 - SF12BW125 (RX2 downlink only) 156 156 182 + 157 157 == 3.4 EU863-870 (EU868) == 158 158 159 159 * Uplink: ... ... @@ -185,6 +185,7 @@ 185 185 ** Uplink channels 1-3 (RX1) 186 186 ** 866.550 - SF10BW125 (RX2) 187 187 214 + 188 188 == 3.6 KZ865 == 189 189 190 190 * Uplink ~-~- 125Khz , DR0 - DR5 ... ... @@ -198,6 +198,7 @@ 198 198 ** The RX1 receive window uses the same channel as the preceding uplink. 199 199 ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz) 200 200 228 + 201 201 == 3.7 KR920-923 (KR920) == 202 202 203 203 * Default channel: ... ... @@ -218,8 +218,11 @@ 218 218 ** Uplink channels 1-7(RX1) 219 219 ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 220 220 249 + 221 221 == 3.8 MA869 == 222 222 252 + Country: Morroco 253 + 223 223 * Uplink: 224 224 ** 869.1 - SF7BW125 to SF12BW125 225 225 ** 869.3 - SF7BW125 to SF12BW125 ... ... @@ -235,10 +235,12 @@ 235 235 ** Uplink channels 1-9 (RX1) 236 236 ** 869.525 - SF12BW125 (RX2 downlink only) 237 237 269 + 238 238 == 3.9 US902-928 (US915) == 239 239 240 240 Used in USA, Canada and South America. 241 241 274 + 242 242 === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. === 243 243 244 244 Default use CHE=2, Subband 2 ... ... @@ -264,15 +264,30 @@ 264 264 ** 927.5 - SF7BW500 to SF12BW500 265 265 ** 923.3 - SF12BW500(RX2 downlink only) 266 266 300 + 267 267 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 268 268 303 +((( 269 269 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 +))) 270 270 307 +((( 308 + 309 +))) 310 + 311 +((( 271 271 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 +))) 272 272 273 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 274 -* 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) 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) 275 275 321 + 322 +))) 323 + 276 276 = 4. Frequency Bands for different server = 277 277 278 278 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]