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 < 18.1
edited by Edwin Chen
on 2024/10/21 20:35
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,18 +1,14 @@
1 1  (% class="wikigeneratedid" id="HEndDeviceFrequencyBand" %)
2 -
2 + **Table of** **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  
11 +
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.
17 17  
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]]
... ... @@ -20,28 +20,37 @@
20 20  
21 21  = 2. OTAA Join Behaviour =
22 22  
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.
19 +Since 005 LoRaWAN stack: One device boot or reset, it will
24 24  
25 -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.
26 26  
27 -* EU868 OTAA Join DR select. SF7->SF8->SF9->SF10->SF11->SF12; Each 3 attempts and then loop
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
25 +Since 005 LoRaWAN Stack:
29 29  
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 +
30 30  = 3. Default Frequency Bands =
31 31  
32 -
33 33  == 3.1 AS923 ==
34 34  
35 35  === 3.1.1 Notice for AS923 Frequency Bands ===
36 36  
36 +
37 +(((
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.
39 +)))
38 38  
41 +(((
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.
43 +)))
40 40  
41 41  
42 -
43 43  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
44 44  
48 +
49 +* **Countries**: Malaysia,
45 45  * Default Uplink channel:
46 46  ** 923.2 - SF7BW125 to SF10BW125
47 47  ** 923.4 - SF7BW125 to SF10BW125
... ... @@ -69,6 +69,7 @@
69 69  
70 70  === 3.1.3 AS923-2 ===
71 71  
77 +
72 72  * Default Uplink channel:
73 73  ** 921.4 - SF7BW125 to SF10BW125
74 74  ** 921.6 - SF7BW125 to SF10BW125
... ... @@ -81,6 +81,7 @@
81 81  
82 82  === 3.1.4 AS923-3 ===
83 83  
90 +
84 84  * Default Uplink channel:
85 85  ** 916.6 - SF7BW125 to SF10BW125
86 86  ** 916.8 - SF7BW125 to SF10BW125
... ... @@ -93,6 +93,7 @@
93 93  
94 94  === 3.1.5 AS923-4 ===
95 95  
103 +
96 96  * Countries : Israel
97 97  * Default Uplink channel:
98 98  ** 917.3 - SF7BW125 to SF10BW125
... ... @@ -105,6 +105,7 @@
105 105  
106 106  == 3.2 AU915-928(AU915) ==
107 107  
116 +
108 108  **Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]** , Default use CHE=2
109 109  
110 110  * Uplink:
... ... @@ -128,17 +128,33 @@
128 128  ** 927.5 - SF7BW500 to SF12BW500
129 129  ** 923.3 - SF12BW500(RX2 downlink only)
130 130  
140 +(((
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.
142 +)))
132 132  
144 +
145 +(((
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.
147 +)))
134 134  
149 +
150 +(((
135 135  After Join success, the end node will switch to the correct sub band by:
152 +)))
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)
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)
139 139  
160 +
161 +
162 +)))
163 +
140 140  == 3.3 CN470-510 (CN470) ==
141 141  
166 +
142 142  Used in China, Default use CHE=1
143 143  
144 144  * Uplink:
... ... @@ -164,6 +164,7 @@
164 164  
165 165  == 3.4 EU863-870 (EU868) ==
166 166  
192 +
167 167  * Uplink:
168 168  ** 868.1 - SF7BW125 to SF12BW125
169 169  ** 868.3 - SF7BW125 to SF12BW125 and SF7BW250
... ... @@ -184,6 +184,7 @@
184 184  
185 185  == 3.5 IN865-867 (IN865) ==
186 186  
213 +
187 187  * Uplink:
188 188  ** 865.0625 - SF7BW125 to SF12BW125
189 189  ** 865.4025 - SF7BW125 to SF12BW125
... ... @@ -193,8 +193,20 @@
193 193  ** Uplink channels 1-3 (RX1)
194 194  ** 866.550 - SF10BW125 (RX2)
195 195  
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 +
196 196  == 3.6 KZ865 ==
197 197  
236 +
198 198  * Uplink ~-~- 125Khz , DR0 - DR5
199 199  ** 865.1
200 200  ** 865.2
... ... @@ -208,6 +208,7 @@
208 208  
209 209  == 3.7 KR920-923 (KR920) ==
210 210  
250 +
211 211  * Default channel:
212 212  ** 922.1 - SF7BW125 to SF12BW125
213 213  ** 922.3 - SF7BW125 to SF12BW125
... ... @@ -228,6 +228,9 @@
228 228  
229 229  == 3.8 MA869 ==
230 230  
271 +
272 + Country: Morroco
273 +
231 231  * Uplink:
232 232  ** 869.1 - SF7BW125 to SF12BW125
233 233  ** 869.3 - SF7BW125 to SF12BW125
... ... @@ -245,10 +245,13 @@
245 245  
246 246  == 3.9 US902-928 (US915) ==
247 247  
291 +
248 248  Used in USA, Canada and South America.
249 249  
294 +
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  
297 +
252 252  Default use CHE=2, Subband 2
253 253  
254 254  * Uplink:
... ... @@ -274,14 +274,63 @@
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  
323 +
324 +(((
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.
326 +)))
278 278  
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:
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 +)))
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)
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)
283 283  
338 +
339 +
340 +)))
341 +
284 284  = 4. Frequency Bands for different server =
285 285  
344 +
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]]
287 287  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
347 +
348 +
349 += 5. Subband Related questiones in US915, AU915, CN470 bands. =
350 +
351 +
352 +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?
353 +
354 +
355 +== 5.1 Set Subband in Gateway. ==
356 +
357 +
358 +* 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.
359 +
360 +* 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.
361 +
362 +== 5.2 Set Subband in End Node ==
363 +
364 +
365 +* 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.
366 +
367 +* 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.
368 +
369 +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]]?
370 +
371 +
372 += 6. Data Rate and TXP auto-adjust logic. =
373 +
374 +In below cases the sensor end node will auto-adjust. (ADR must set to 1)
375 +
376 +* Auto-just according to the server ADR request change downlink command.
377 +* If there is no adr_req_ack arrive the sensor end node for more than 64 uplinks, end node will set the output to maximum power (AT+TXP=0).
378 +* If there is no adr_req_ack arrive the sensor end node for more than 96 uplinks, end node will reduce the Data Rate by 1.
379 +
380 +
381 +
382 +

Applications

Navigation

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