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,5 +1,5 @@ 1 1 (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %) 2 - **Contents:**2 + 3 3 4 4 {{toc/}} 5 5 ... ... @@ -10,7 +10,6 @@ 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 13 - 14 14 = 2. OTAA Join Behaviour = 15 15 16 16 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. ... ... @@ -22,7 +22,6 @@ 22 22 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop 23 23 * 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 24 24 25 - 26 26 = 3. Default Frequency Bands = 27 27 28 28 ... ... @@ -39,6 +39,7 @@ 39 39 ))) 40 40 41 41 40 + 42 42 === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) === 43 43 44 44 * Default Uplink channel: ... ... @@ -66,7 +66,6 @@ 66 66 ** Uplink channels 1-8 (RX1) 67 67 ** 923.2 - SF10BW125 (RX2) 68 68 69 - 70 70 === 3.1.3 AS923-2 === 71 71 72 72 * Default Uplink channel: ... ... @@ -79,8 +79,6 @@ 79 79 ** Uplink channels 1-8 (RX1) 80 80 ** 921.4 - SF10BW125 (RX2) 81 81 82 - 83 - 84 84 === 3.1.4 AS923-3 === 85 85 86 86 * Default Uplink channel: ... ... @@ -93,8 +93,6 @@ 93 93 ** Uplink channels 1-8 (RX1) 94 94 ** 916.6 - SF10BW125 (RX2) 95 95 96 - 97 - 98 98 === 3.1.5 AS923-4 === 99 99 100 100 * Countries : Israel ... ... @@ -107,8 +107,6 @@ 107 107 ** Uplink channels 1-8 (RX1) 108 108 ** 917.3 - SF10BW125 (RX2) 109 109 110 - 111 - 112 112 == 3.2 AU915-928(AU915) == 113 113 114 114 **Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2 ... ... @@ -134,29 +134,15 @@ 134 134 ** 927.5 - SF7BW500 to SF12BW500 135 135 ** 923.3 - SF12BW500(RX2 downlink only) 136 136 137 -((( 138 138 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. 139 -))) 140 140 141 - 142 -((( 143 143 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. 144 -))) 145 145 146 - 147 -((( 148 148 After Join success, the end node will switch to the correct sub band by: 149 -))) 150 150 151 -* ((( 152 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 153 -))) 154 -* ((( 155 -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) 156 156 157 - 158 -))) 159 - 160 160 == 3.3 CN470-510 (CN470) == 161 161 162 162 Used in China, Default use CHE=1 ... ... @@ -182,8 +182,6 @@ 182 182 ** 508.1 - SF7BW125 to SF12BW125 183 183 ** 505.3 - SF12BW125 (RX2 downlink only) 184 184 185 - 186 - 187 187 == 3.4 EU863-870 (EU868) == 188 188 189 189 * Uplink: ... ... @@ -215,8 +215,6 @@ 215 215 ** Uplink channels 1-3 (RX1) 216 216 ** 866.550 - SF10BW125 (RX2) 217 217 218 - 219 - 220 220 == 3.6 KZ865 == 221 221 222 222 * Uplink ~-~- 125Khz , DR0 - DR5 ... ... @@ -230,8 +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 - 235 235 == 3.7 KR920-923 (KR920) == 236 236 237 237 * Default channel: ... ... @@ -252,12 +252,8 @@ 252 252 ** Uplink channels 1-7(RX1) 253 253 ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 254 254 255 - 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 ... ... @@ -273,12 +273,10 @@ 273 273 ** Uplink channels 1-9 (RX1) 274 274 ** 869.525 - SF12BW125 (RX2 downlink only) 275 275 276 - 277 277 == 3.9 US902-928 (US915) == 278 278 279 279 Used in USA, Canada and South America. 280 280 281 - 282 282 === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. === 283 283 284 284 Default use CHE=2, Subband 2 ... ... @@ -304,31 +304,15 @@ 304 304 ** 927.5 - SF7BW500 to SF12BW500 305 305 ** 923.3 - SF12BW500(RX2 downlink only) 306 306 307 - 308 - 309 309 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 310 310 311 -((( 312 312 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. 313 -))) 314 314 315 -((( 316 - 317 -))) 318 - 319 -((( 320 320 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: 321 -))) 322 322 323 -* ((( 324 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 325 -))) 326 -* ((( 327 -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) 328 328 329 - 330 -))) 331 - 332 332 = 4. Frequency Bands for different server = 333 333 334 334 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]