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,6 @@ 1 1 (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %) 2 - 2 + **Contents：** 3 3 4 -(% class="wikigeneratedid" id="HContents" %) 5 -Contents 6 - 7 - ~[[[hide>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#]]] 8 - 9 9 {{toc/}} 10 10 11 11 = 1. Introduction = ... ... @@ -15,15 +15,21 @@ 15 15 * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]] 16 16 * 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]] 17 17 13 + 14 + 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 19 +((( 22 22 For 005 LoRaWAN Stack: 21 +))) 23 23 24 24 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop 25 25 * 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 26 26 26 + 27 + 27 27 = 3. Default Frequency Bands = 28 28 29 29 ... ... @@ -31,9 +31,13 @@ 31 31 32 32 === 3.1.1 Notice for AS923 Frequency Bands === 33 33 35 +((( 34 34 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. 37 +))) 35 35 39 +((( 36 36 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. 41 +))) 37 37 38 38 39 39 ... ... @@ -64,6 +64,8 @@ 64 64 ** Uplink channels 1-8 (RX1) 65 65 ** 923.2 - SF10BW125 (RX2) 66 66 72 + 73 + 67 67 === 3.1.3 AS923-2 === 68 68 69 69 * Default Uplink channel: ... ... @@ -125,14 +125,26 @@ 125 125 ** 927.5 - SF7BW500 to SF12BW500 126 126 ** 923.3 - SF12BW500(RX2 downlink only) 127 127 135 +((( 128 128 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. 137 +))) 129 129 139 + 140 +((( 130 130 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. 142 +))) 131 131 144 + 145 +((( 132 132 After Join success, the end node will switch to the correct sub band by: 147 +))) 133 133 134 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 135 -* 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) 149 +* ((( 150 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 151 +))) 152 +* ((( 153 +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) 154 +))) 136 136 137 137 == 3.3 CN470-510 (CN470) == 138 138 ... ... @@ -225,6 +225,8 @@ 225 225 226 226 == 3.8 MA869 == 227 227 247 + Country: Morroco 248 + 228 228 * Uplink: 229 229 ** 869.1 - SF7BW125 to SF12BW125 230 230 ** 869.3 - SF7BW125 to SF12BW125 ... ... @@ -271,12 +271,24 @@ 271 271 272 272 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 273 273 295 +((( 274 274 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. 297 +))) 275 275 299 +((( 300 + 301 +))) 302 + 303 +((( 276 276 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: 305 +))) 277 277 278 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 279 -* 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) 307 +* ((( 308 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 309 +))) 310 +* ((( 311 +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) 312 +))) 280 280 281 281 = 4. Frequency Bands for different server = 282 282