Changes for page End Device Frequency Band

Last modified by Edwin Chen on 2024/10/21 20:35
<
From version < 3.5 >
edited by Xiaoling
on 2022/05/10 15:33
To version < 15.1 >
edited by Edwin Chen
on 2023/10/22 21:56
>
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,39 +1,53 @@
1 1  (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
2 -
2 + **Table of** **Contents：**
3 3  
4 4  {{toc/}}
5 5  
6 +
7 +
8 +
6 6  = 1. Introduction =
7 7  
11 +
8 8  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.
9 9  
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  
17 +
13 13  = 2. OTAA Join Behaviour =
14 14  
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 -For 005 LoRaWAN Stack:
21 +Since 005 LoRaWAN stack: to save battery, once boot, device will 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.
18 18  
23 +(((
24 +Since 005 LoRaWAN Stack:
25 +)))
26 +
19 19  * EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
20 20  * 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
21 21  
30 +
22 22  = 3. Default Frequency Bands =
23 23  
24 -
25 25  == 3.1 AS923 ==
26 26  
27 27  === 3.1.1 Notice for AS923 Frequency Bands ===
28 28  
37 +
38 +(((
29 29  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 +)))
30 30  
42 +(((
31 31  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 +)))
32 32  
33 33  
34 -
35 35  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
36 36  
49 +
50 +* **Countries**: Malaysia,
37 37  * Default Uplink channel:
38 38  ** 923.2 - SF7BW125 to SF10BW125
39 39  ** 923.4 - SF7BW125 to SF10BW125
... ... @@ -59,8 +59,10 @@
59 59  ** Uplink channels 1-8 (RX1)
60 60  ** 923.2 - SF10BW125 (RX2)
61 61  
76 +
62 62  === 3.1.3 AS923-2 ===
63 63  
79 +
64 64  * Default Uplink channel:
65 65  ** 921.4 - SF7BW125 to SF10BW125
66 66  ** 921.6 - SF7BW125 to SF10BW125
... ... @@ -71,8 +71,10 @@
71 71  ** Uplink channels 1-8 (RX1)
72 72  ** 921.4 - SF10BW125 (RX2)
73 73  
90 +
74 74  === 3.1.4 AS923-3 ===
75 75  
93 +
76 76  * Default Uplink channel:
77 77  ** 916.6 - SF7BW125 to SF10BW125
78 78  ** 916.8 - SF7BW125 to SF10BW125
... ... @@ -83,8 +83,10 @@
83 83  ** Uplink channels 1-8 (RX1)
84 84  ** 916.6 - SF10BW125 (RX2)
85 85  
104 +
86 86  === 3.1.5 AS923-4 ===
87 87  
107 +
88 88  * Countries : Israel
89 89  * Default Uplink channel:
90 90  ** 917.3 - SF7BW125 to SF10BW125
... ... @@ -95,8 +95,10 @@
95 95  ** Uplink channels 1-8 (RX1)
96 96  ** 917.3 - SF10BW125 (RX2)
97 97  
118 +
98 98  == 3.2 AU915-928(AU915) ==
99 99  
121 +
100 100  **Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2
101 101  
102 102  * Uplink:
... ... @@ -120,17 +120,33 @@
120 120  ** 927.5 - SF7BW500 to SF12BW500
121 121  ** 923.3 - SF12BW500(RX2 downlink only)
122 122  
145 +(((
123 123  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.
147 +)))
124 124  
149 +
150 +(((
125 125  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.
152 +)))
126 126  
154 +
155 +(((
127 127  After Join success, the end node will switch to the correct sub band by:
157 +)))
128 128  
129 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
130 -* 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)
159 +* (((
160 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
161 +)))
162 +* (((
163 +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)
131 131  
165 +
166 +
167 +)))
168 +
132 132  == 3.3 CN470-510 (CN470) ==
133 133  
171 +
134 134  Used in China, Default use CHE=1
135 135  
136 136  * Uplink:
... ... @@ -154,8 +154,10 @@
154 154  ** 508.1 - SF7BW125 to SF12BW125
155 155  ** 505.3 - SF12BW125 (RX2 downlink only)
156 156  
195 +
157 157  == 3.4 EU863-870 (EU868) ==
158 158  
198 +
159 159  * Uplink:
160 160  ** 868.1 - SF7BW125 to SF12BW125
161 161  ** 868.3 - SF7BW125 to SF12BW125 and SF7BW250
... ... @@ -176,6 +176,7 @@
176 176  
177 177  == 3.5 IN865-867 (IN865) ==
178 178  
219 +
179 179  * Uplink:
180 180  ** 865.0625 - SF7BW125 to SF12BW125
181 181  ** 865.4025 - SF7BW125 to SF12BW125
... ... @@ -185,8 +185,21 @@
185 185  ** Uplink channels 1-3 (RX1)
186 186  ** 866.550 - SF10BW125 (RX2)
187 187  
229 +Gateway has below eight channels in IN865 bands.
230 +
231 +* 865.0625 - SF7BW125 to SF12BW125
232 +* 865.4025 - SF7BW125 to SF12BW125
233 +* 865.6025 - SF7BW125 to SF12BW125
234 +* 865.9850 - SF7BW125 to SF12BW125
235 +* 866.1850 - SF7BW125 to SF12BW125
236 +* 866.3850 - SF7BW125 to SF12BW125
237 +* 866.5850 - SF7BW125 to SF12BW125
238 +* 866.7850 - SF7BW125 to SF12BW125
239 +
240 +
188 188  == 3.6 KZ865 ==
189 189  
243 +
190 190  * Uplink ~-~- 125Khz , DR0 - DR5
191 191  ** 865.1
192 192  ** 865.2
... ... @@ -198,8 +198,10 @@
198 198  ** The RX1 receive window uses the same channel as the preceding uplink.
199 199  ** The RX2 receive window uses a fixed frequency and data rate. The default parameters are 866.7MHz / DR0 (SF12, 125 kHz)​
200 200  
255 +
201 201  == 3.7 KR920-923 (KR920) ==
202 202  
258 +
203 203  * Default channel:
204 204  ** 922.1 - SF7BW125 to SF12BW125
205 205  ** 922.3 - SF7BW125 to SF12BW125
... ... @@ -218,8 +218,12 @@
218 218  ** Uplink channels 1-7(RX1)
219 219  ** 921.9 - SF12BW125 (RX2 downlink only; SF12BW125 might be changed to SF9BW125)
220 220  
277 +
221 221  == 3.8 MA869 ==
222 222  
280 +
281 + Country: Morroco
282 +
223 223  * Uplink:
224 224  ** 869.1 - SF7BW125 to SF12BW125
225 225  ** 869.3 - SF7BW125 to SF12BW125
... ... @@ -235,12 +235,16 @@
235 235  ** Uplink channels 1-9 (RX1)
236 236  ** 869.525 - SF12BW125 (RX2 downlink only)
237 237  
298 +
238 238  == 3.9 US902-928 (US915) ==
239 239  
301 +
240 240  Used in USA, Canada and South America.
241 241  
304 +
242 242  === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
243 243  
307 +
244 244  Default use CHE=2, Subband 2
245 245  
246 246  * Uplink:
... ... @@ -264,16 +264,60 @@
264 264  ** 927.5 - SF7BW500 to SF12BW500
265 265  ** 923.3 - SF12BW500(RX2 downlink only)
266 266  
331 +
267 267  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
268 268  
334 +
335 +(((
269 269  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.
337 +)))
270 270  
339 +(((
271 271  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:
341 +)))
272 272  
273 -* Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
274 -* 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)
343 +* (((
344 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
345 +)))
346 +* (((
347 +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)
275 275  
349 +
350 +
351 +)))
352 +
276 276  = 4. Frequency Bands for different server =
277 277  
355 +
278 278  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
279 279  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
358 +
359 +
360 += 5. Subband Related questiones in US915, AU915, CN470 bands. =
361 +
362 +
363 +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?
364 +
365 +
366 +== 5.1 Set Subband in Gateway. ==
367 +
368 +
369 +* 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.
370 +
371 +* 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.
372 +
373 +
374 +== 5.2 Set Subband in End Node ==
375 +
376 +
377 +* 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.
378 +
379 +* 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.
380 +
381 +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]]?
382 +
383 +
384 +
385 +
386 +
387 +

Applications

Navigation

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