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: ... ... @@ -78,7 +78,6 @@ 78 78 ** Uplink channels 1-8 (RX1) 79 79 ** 921.4 - SF10BW125 (RX2) 80 80 81 - 82 82 === 3.1.4 AS923-3 === 83 83 84 84 * Default Uplink channel: ... ... @@ -91,7 +91,6 @@ 91 91 ** Uplink channels 1-8 (RX1) 92 92 ** 916.6 - SF10BW125 (RX2) 93 93 94 - 95 95 === 3.1.5 AS923-4 === 96 96 97 97 * Countries : Israel ... ... @@ -104,7 +104,6 @@ 104 104 ** Uplink channels 1-8 (RX1) 105 105 ** 917.3 - SF10BW125 (RX2) 106 106 107 - 108 108 == 3.2 AU915-928(AU915) == 109 109 110 110 **Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2 ... ... @@ -130,29 +130,15 @@ 130 130 ** 927.5 - SF7BW500 to SF12BW500 131 131 ** 923.3 - SF12BW500(RX2 downlink only) 132 132 133 -((( 134 134 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. 135 -))) 136 136 137 - 138 -((( 139 139 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. 140 -))) 141 141 142 - 143 -((( 144 144 After Join success, the end node will switch to the correct sub band by: 145 -))) 146 146 147 -* ((( 148 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 149 -))) 150 -* ((( 151 -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) 152 152 153 - 154 -))) 155 - 156 156 == 3.3 CN470-510 (CN470) == 157 157 158 158 Used in China, Default use CHE=1 ... ... @@ -178,7 +178,6 @@ 178 178 ** 508.1 - SF7BW125 to SF12BW125 179 179 ** 505.3 - SF12BW125 (RX2 downlink only) 180 180 181 - 182 182 == 3.4 EU863-870 (EU868) == 183 183 184 184 * Uplink: ... ... @@ -210,7 +210,6 @@ 210 210 ** Uplink channels 1-3 (RX1) 211 211 ** 866.550 - SF10BW125 (RX2) 212 212 213 - 214 214 == 3.6 KZ865 == 215 215 216 216 * Uplink ~-~- 125Khz , DR0 - DR5 ... ... @@ -224,7 +224,6 @@ 224 224 ** The RX1 receive window uses the same channel as the preceding uplink. 225 225 ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz) 226 226 227 - 228 228 == 3.7 KR920-923 (KR920) == 229 229 230 230 * Default channel: ... ... @@ -245,11 +245,8 @@ 245 245 ** Uplink channels 1-7(RX1) 246 246 ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125) 247 247 248 - 249 249 == 3.8 MA869 == 250 250 251 - Country: Morroco 252 - 253 253 * Uplink: 254 254 ** 869.1 - SF7BW125 to SF12BW125 255 255 ** 869.3 - SF7BW125 to SF12BW125 ... ... @@ -269,7 +269,6 @@ 269 269 270 270 Used in USA, Canada and South America. 271 271 272 - 273 273 === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. === 274 274 275 275 Default use CHE=2, Subband 2 ... ... @@ -295,30 +295,15 @@ 295 295 ** 927.5 - SF7BW500 to SF12BW500 296 296 ** 923.3 - SF12BW500(RX2 downlink only) 297 297 298 - 299 299 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 300 300 301 -((( 302 302 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. 303 -))) 304 304 305 -((( 306 - 307 -))) 308 - 309 -((( 310 310 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: 311 -))) 312 312 313 -* ((( 314 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 315 -))) 316 -* ((( 317 -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) 318 318 319 - 320 -))) 321 - 322 322 = 4. Frequency Bands for different server = 323 323 324 324 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]