Changes for page End Device Frequency Band

Last modified by Edwin Chen on 2024/10/21 20:35
<
From version < 3.1 >
edited by Xiaoling
on 2022/05/10 14:17
To version < 17.1 >
edited by Edwin Chen
on 2024/02/15 00:10
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Edwin
Content
... ... @@ -1,15 +1,14 @@
1 1  (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
2 -
2 + **Table of** **Contents：**
3 3  
4 -(% class="wikigeneratedid" id="HContents" %)
5 -Contents
4 +{{toc/}}
6 6  
7 - ~[[[hide>>url:https://wiki.dragino.com/index.php/End_Device_Frequency_Band#]]]
8 8  
9 -{{toc/}}
10 10  
8 +
11 11  = 1. Introduction =
12 12  
11 +
13 13  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.
14 14  
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]]
... ... @@ -17,28 +17,37 @@
17 17  
18 18  = 2. OTAA Join Behaviour =
19 19  
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.
19 +Since 005 LoRaWAN stack: One device boot or reset, it will
21 21  
22 -For 005 LoRaWAN Stack:
21 +* First make 200 Join Requestes for OTAA Join, the interval of two Join Requests will depends on the DR and the airtime requirement.
22 +* After 200 Join Requestes, if end node still not join successful, to save battery life, it will keep sending join request at the default uplink interval ( 20 minutes) .
23 +* If device reboot, it will do above loop again.
23 23  
24 -* EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
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
25 +Since 005 LoRaWAN Stack:
26 26  
27 +* **EU868 OTAA Join DR Logic**. SF7->SF8->SF9->SF10->SF11->SF12; Each SF will make 3 attempts and then loop
28 +* **US915 and AU915 OTAA Join procedure**,. End node by default will use all 72 channels (All sub-bands) to join and it will be set to use the proper sub-band after Join success
29 +
27 27  = 3. Default Frequency Bands =
28 28  
29 -
30 30  == 3.1 AS923 ==
31 31  
32 32  === 3.1.1 Notice for AS923 Frequency Bands ===
33 33  
36 +
37 +(((
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.
39 +)))
35 35  
41 +(((
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.
43 +)))
37 37  
38 38  
39 -
40 40  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
41 41  
48 +
49 +* **Countries**: Malaysia,
42 42  * Default Uplink channel:
43 43  ** 923.2 - SF7BW125 to SF10BW125
44 44  ** 923.4 - SF7BW125 to SF10BW125
... ... @@ -66,6 +66,7 @@
66 66  
67 67  === 3.1.3 AS923-2 ===
68 68  
77 +
69 69  * Default Uplink channel:
70 70  ** 921.4 - SF7BW125 to SF10BW125
71 71  ** 921.6 - SF7BW125 to SF10BW125
... ... @@ -78,6 +78,7 @@
78 78  
79 79  === 3.1.4 AS923-3 ===
80 80  
90 +
81 81  * Default Uplink channel:
82 82  ** 916.6 - SF7BW125 to SF10BW125
83 83  ** 916.8 - SF7BW125 to SF10BW125
... ... @@ -90,6 +90,7 @@
90 90  
91 91  === 3.1.5 AS923-4 ===
92 92  
103 +
93 93  * Countries : Israel
94 94  * Default Uplink channel:
95 95  ** 917.3 - SF7BW125 to SF10BW125
... ... @@ -102,6 +102,7 @@
102 102  
103 103  == 3.2 AU915-928(AU915) ==
104 104  
116 +
105 105  **Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2
106 106  
107 107  * Uplink:
... ... @@ -125,17 +125,33 @@
125 125  ** 927.5 - SF7BW500 to SF12BW500
126 126  ** 923.3 - SF12BW500(RX2 downlink only)
127 127  
140 +(((
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.
142 +)))
129 129  
144 +
145 +(((
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.
147 +)))
131 131  
149 +
150 +(((
132 132  After Join success, the end node will switch to the correct sub band by:
152 +)))
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)
154 +* (((
155 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
156 +)))
157 +* (((
158 +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)
136 136  
160 +
161 +
162 +)))
163 +
137 137  == 3.3 CN470-510 (CN470) ==
138 138  
166 +
139 139  Used in China, Default use CHE=1
140 140  
141 141  * Uplink:
... ... @@ -161,6 +161,7 @@
161 161  
162 162  == 3.4 EU863-870 (EU868) ==
163 163  
192 +
164 164  * Uplink:
165 165  ** 868.1 - SF7BW125 to SF12BW125
166 166  ** 868.3 - SF7BW125 to SF12BW125 and SF7BW250
... ... @@ -181,6 +181,7 @@
181 181  
182 182  == 3.5 IN865-867 (IN865) ==
183 183  
213 +
184 184  * Uplink:
185 185  ** 865.0625 - SF7BW125 to SF12BW125
186 186  ** 865.4025 - SF7BW125 to SF12BW125
... ... @@ -190,8 +190,20 @@
190 190  ** Uplink channels 1-3 (RX1)
191 191  ** 866.550 - SF10BW125 (RX2)
192 192  
223 +Gateway has below eight channels in IN865 bands.
224 +
225 +* 865.0625 - SF7BW125 to SF12BW125
226 +* 865.4025 - SF7BW125 to SF12BW125
227 +* 865.6025 - SF7BW125 to SF12BW125
228 +* 865.9850 - SF7BW125 to SF12BW125
229 +* 866.1850 - SF7BW125 to SF12BW125
230 +* 866.3850 - SF7BW125 to SF12BW125
231 +* 866.5850 - SF7BW125 to SF12BW125
232 +* 866.7850 - SF7BW125 to SF12BW125
233 +
193 193  == 3.6 KZ865 ==
194 194  
236 +
195 195  * Uplink ~-~- 125Khz , DR0 - DR5
196 196  ** 865.1
197 197  ** 865.2
... ... @@ -205,6 +205,7 @@
205 205  
206 206  == 3.7 KR920-923 (KR920) ==
207 207  
250 +
208 208  * Default channel:
209 209  ** 922.1 - SF7BW125 to SF12BW125
210 210  ** 922.3 - SF7BW125 to SF12BW125
... ... @@ -225,6 +225,9 @@
225 225  
226 226  == 3.8 MA869 ==
227 227  
271 +
272 + Country: Morroco
273 +
228 228  * Uplink:
229 229  ** 869.1 - SF7BW125 to SF12BW125
230 230  ** 869.3 - SF7BW125 to SF12BW125
... ... @@ -242,10 +242,13 @@
242 242  
243 243  == 3.9 US902-928 (US915) ==
244 244  
291 +
245 245  Used in USA, Canada and South America.
246 246  
294 +
247 247  === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
248 248  
297 +
249 249  Default use CHE=2, Subband 2
250 250  
251 251  * Uplink:
... ... @@ -271,14 +271,55 @@
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  
323 +
324 +(((
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.
326 +)))
275 275  
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:
328 +(((
329 +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, 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:
330 +)))
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)
332 +* (((
333 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
334 +)))
335 +* (((
336 +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)
280 280  
338 +
339 +
340 +)))
341 +
281 281  = 4. Frequency Bands for different server =
282 282  
344 +
283 283  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
284 284  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
347 +
348 += 5. Subband Related questiones in US915, AU915, CN470 bands. =
349 +
350 +
351 +Frequency band US915, AU915 and CN470 supports totally 72 frequency in 8 sub-bands, Normally Gateway only support 8 channels ( one subband). So how does the gateway and end nodes work in such frequency?
352 +
353 +
354 +== 5.1 Set Subband in Gateway. ==
355 +
356 +
357 +* If Gateway choose (% style="color:blue" %)**Semtech UDP packet**(%%) forwarder to Connect to LoRaWAN server. User need to manually set the match Subband in the gateway web UI.
358 +
359 +* If Gateway choose (% style="color:blue" %)**Basic Station Mode**(%%) to connect to the LoRaWAN server. User can set the subband in the Server side and gateway will the correct subband from server. no need to set this in gateway. AWS-IoT, TTN, ChirpStack all supports Basic Station Connection.
360 +
361 +== 5.2 Set Subband in End Node ==
362 +
363 +
364 +* In early End Node firmware, it is pre-set to subband 2 , user need to manually set to proper subband if they don;t use subband 2.
365 +
366 +* In new end node firmware , it supports all sub-bands, and will swtich to the proper subband after OTAA join. So user can use the end node with all sub-band.
367 +
368 +Reference: [[How it affects the OTAA Join when end node is set to support all subbands>>http://wiki.dragino.com/xwiki/bin/view/Main/LoRaWAN%20Communication%20Debug/#H13.WhyittakeslongertimeforOTAAjoinedinUS9152FCN4702FAU915band3F]]?
369 +
370 +
371 +
372 +
373 +
374 +

Applications

Navigation

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