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,6 +1,14 @@ 1 1 (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %) 2 2 3 3 4 += Contents ~[[[hide>>http://8.211.40.43:8080/xwiki/bin/view/Main/End%20Device%20Frequency%20Band]]] = 5 + 6 +== Contents == 7 + 8 + ~[[[hide>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#]]] 9 + 10 +* [[1 Introduction>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#Introduction]] 11 + 4 4 {{toc/}} 5 5 6 6 = 1. Introduction = ... ... @@ -14,9 +14,7 @@ 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 17 -((( 18 18 For 005 LoRaWAN Stack: 19 -))) 20 20 21 21 * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop 22 22 * 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,13 +28,9 @@ 28 28 29 29 === 3.1.1 Notice for AS923 Frequency Bands === 30 30 31 -((( 32 32 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. 33 -))) 34 34 35 -((( 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. 37 -))) 38 38 39 39 40 40 ... ... @@ -126,26 +126,14 @@ 126 126 ** 927.5 - SF7BW500 to SF12BW500 127 127 ** 923.3 - SF12BW500(RX2 downlink only) 128 128 129 -((( 130 130 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. 131 -))) 132 132 133 - 134 -((( 135 135 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. 136 -))) 137 137 138 - 139 -((( 140 140 After Join success, the end node will switch to the correct sub band by: 141 -))) 142 142 143 -* ((( 144 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 145 -))) 146 -* ((( 147 -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 -))) 137 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band 138 +* 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 149 150 150 == 3.3 CN470-510 (CN470) == 151 151 ... ... @@ -284,24 +284,12 @@ 284 284 285 285 === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] === 286 286 287 -((( 288 288 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. 289 -))) 290 290 291 -((( 292 - 293 -))) 294 - 295 -((( 296 296 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: 297 -))) 298 298 299 -* ((( 300 -Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 301 -))) 302 -* ((( 303 -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) 304 -))) 281 +* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband 282 +* 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) 305 305 306 306 = 4. Frequency Bands for different server = 307 307