Changes for page End Device Frequency Band

Last modified by Edwin Chen on 2024/10/21 20:35
<
From version < 3.4 >
edited by Xiaoling
on 2022/05/10 14:31
To version < 11.7 >
edited by Xiaoling
on 2022/06/01 11:46
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,16 +1,11 @@
1 1  (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
2 -
2 + **Contents：**
3 3  
4 -= Contents ~[[[hide>>http://8.211.40.43:8080/xwiki/bin/view/Main/End%20Device%20Frequency%20Band]]] =
4 +{{toc/}}
5 5  
6 -== Contents ==
7 7  
8 - ~[[[hide>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#]]]
9 9  
10 -* [[1 Introduction>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#Introduction]]
11 11  
12 -{{toc/}}
13 -
14 14  = 1. Introduction =
15 15  
16 16  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.
... ... @@ -18,15 +18,21 @@
18 18  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
19 19  * 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]]
20 20  
16 +
17 +
21 21  = 2. OTAA Join Behaviour =
22 22  
23 23  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.
24 24  
22 +(((
25 25  For 005 LoRaWAN Stack:
24 +)))
26 26  
27 27  * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
28 28  * 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
29 29  
29 +
30 +
30 30  = 3. Default Frequency Bands =
31 31  
32 32  
... ... @@ -34,12 +34,15 @@
34 34  
35 35  === 3.1.1 Notice for AS923 Frequency Bands ===
36 36  
38 +(((
37 37  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.
40 +)))
38 38  
42 +(((
39 39  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.
44 +)))
40 40  
41 41  
42 -
43 43  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
44 44  
45 45  * Default Uplink channel:
... ... @@ -67,6 +67,8 @@
67 67  ** Uplink channels 1-8 (RX1)
68 68  ** 923.2 - SF10BW125 (RX2)
69 69  
74 +
75 +
70 70  === 3.1.3 AS923-2 ===
71 71  
72 72  * Default Uplink channel:
... ... @@ -128,15 +128,29 @@
128 128  ** 927.5 - SF7BW500 to SF12BW500
129 129  ** 923.3 - SF12BW500(RX2 downlink only)
130 130  
137 +(((
131 131  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 +)))
132 132  
141 +
142 +(((
133 133  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 +)))
134 134  
146 +
147 +(((
135 135  After Join success, the end node will switch to the correct sub band by:
149 +)))
136 136  
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)
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)
139 139  
157 +
158 +)))
159 +
140 140  == 3.3 CN470-510 (CN470) ==
141 141  
142 142  Used in China, Default use CHE=1
... ... @@ -228,6 +228,8 @@
228 228  
229 229  == 3.8 MA869 ==
230 230  
251 + Country: Morroco
252 +
231 231  * Uplink:
232 232  ** 869.1 - SF7BW125 to SF12BW125
233 233  ** 869.3 - SF7BW125 to SF12BW125
... ... @@ -247,6 +247,7 @@
247 247  
248 248  Used in USA, Canada and South America.
249 249  
272 +
250 250  === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
251 251  
252 252  Default use CHE=2, Subband 2
... ... @@ -274,13 +274,27 @@
274 274  
275 275  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
276 276  
300 +(((
277 277  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.
302 +)))
278 278  
304 +(((
305 +
306 +)))
307 +
308 +(((
279 279  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:
310 +)))
280 280  
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)
312 +* (((
313 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
314 +)))
315 +* (((
316 +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)
283 283  
318 +
319 +)))
320 +
284 284  = 4. Frequency Bands for different server =
285 285  
286 286  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]

Applications

Navigation

Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0