<
From version < 12.4 >
edited by Xiaoling
on 2022/07/13 11:31
To version < 14.2 >
edited by Xiaoling
on 2023/02/02 15:37
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -16,7 +16,6 @@
16 16  
17 17  
18 18  
19 -
20 20  = 2. OTAA Join Behaviour =
21 21  
22 22  
... ... @@ -31,13 +31,10 @@
31 31  
32 32  
33 33  
34 -
35 35  = 3. Default Frequency Bands =
36 36  
37 -
38 38  == 3.1 AS923 ==
39 39  
40 -
41 41  === 3.1.1 Notice for AS923 Frequency Bands ===
42 42  
43 43  
... ... @@ -50,7 +50,6 @@
50 50  )))
51 51  
52 52  
53 -
54 54  === 3.1.2 AS920-923 & AS923-925 : AS923-1 (AS923) ===
55 55  
56 56  
... ... @@ -82,7 +82,6 @@
82 82  
83 83  
84 84  
85 -
86 86  === 3.1.3 AS923-2 ===
87 87  
88 88  
... ... @@ -98,7 +98,6 @@
98 98  
99 99  
100 100  
101 -
102 102  === 3.1.4 AS923-3 ===
103 103  
104 104  
... ... @@ -114,7 +114,6 @@
114 114  
115 115  
116 116  
117 -
118 118  === 3.1.5 AS923-4 ===
119 119  
120 120  
... ... @@ -130,7 +130,6 @@
130 130  
131 131  
132 132  
133 -
134 134  == 3.2 AU915-928(AU915) ==
135 135  
136 136  
... ... @@ -157,7 +157,6 @@
157 157  ** 927.5 - SF7BW500 to SF12BW500
158 158  ** 923.3 - SF12BW500(RX2 downlink only)
159 159  
160 -
161 161  (((
162 162  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.
163 163  )))
... ... @@ -176,10 +176,9 @@
176 176  Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that sub-band
177 177  )))
178 178  * (((
179 -Use the Join successful sub-band if the server doesnt include sub-band info in the OTAA Join Accept message ( TTN v2 doesn't include)
169 +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)
180 180  
181 181  
182 -
183 183  
184 184  )))
185 185  
... ... @@ -211,7 +211,6 @@
211 211  
212 212  
213 213  
214 -
215 215  == 3.4 EU863-870 (EU868) ==
216 216  
217 217  
... ... @@ -233,7 +233,6 @@
233 233  OTAA RX2DR is set to DR0, SF12BW125 since 2021,Mar for Dragino Devices.
234 234  
235 235  
236 -
237 237  == 3.5 IN865-867 (IN865) ==
238 238  
239 239  
... ... @@ -246,9 +246,19 @@
246 246  ** Uplink channels 1-3 (RX1)
247 247  ** 866.550 - SF10BW125 (RX2)
248 248  
236 +Gateway has below eight channels in IN865 bands.
249 249  
238 +* 865.0625 - SF7BW125 to SF12BW125
239 +* 865.4025 - SF7BW125 to SF12BW125
240 +* 865.6025 - SF7BW125 to SF12BW125
241 +* 865.9850 - SF7BW125 to SF12BW125
242 +* 866.1850 - SF7BW125 to SF12BW125
243 +* 866.3850 - SF7BW125 to SF12BW125
244 +* 866.5850 - SF7BW125 to SF12BW125
245 +* 866.7850 - SF7BW125 to SF12BW125
250 250  
251 251  
248 +
252 252  == 3.6 KZ865 ==
253 253  
254 254  
... ... @@ -265,7 +265,6 @@
265 265  
266 266  
267 267  
268 -
269 269  == 3.7 KR920-923 (KR920) ==
270 270  
271 271  
... ... @@ -289,7 +289,6 @@
289 289  
290 290  
291 291  
292 -
293 293  == 3.8 MA869 ==
294 294  
295 295  
... ... @@ -312,7 +312,6 @@
312 312  
313 313  
314 314  
315 -
316 316  == 3.9 US902-928 (US915) ==
317 317  
318 318  
... ... @@ -319,7 +319,6 @@
319 319  Used in USA, Canada and South America.
320 320  
321 321  
322 -
323 323  === 3.9.1 Before [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]]. ===
324 324  
325 325  
... ... @@ -348,7 +348,6 @@
348 348  
349 349  
350 350  
351 -
352 352  === 3.9.2 Latest firmware, Since [[Dragino DLS-005 LoRaWAN Stack>>url:https://www.dragino.com/downloads/downloads/LoRa_End_Node/DR-LWS/changelog]] ===
353 353  
354 354  
... ... @@ -357,10 +357,6 @@
357 357  )))
358 358  
359 359  (((
360 -
361 -)))
362 -
363 -(((
364 364  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:
365 365  )))
366 366  
... ... @@ -371,7 +371,6 @@
371 371  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)
372 372  
373 373  
374 -
375 375  
376 376  )))
377 377  
... ... @@ -380,3 +380,35 @@
380 380  
381 381  * TTN Frequency Band Settings: [[https:~~/~~/www.thethingsnetwork.org/docs/lorawan/frequency-plans.html>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]]
382 382  * Loriot [[https:~~/~~/docs.loriot.io/display/LNS/Regional+Frequency+Plans>>url:https://docs.loriot.io/display/LNS/Regional+Frequency+Plans]]
370 +
371 +
372 +
373 += 5. Subband Related questiones in US915, AU915, CN470 bands. =
374 +
375 +
376 +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?
377 +
378 +
379 +== 5.1 Set Subband in Gateway. ==
380 +
381 +
382 +* 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.
383 +
384 +* 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.
385 +
386 +
387 +
388 +== 5.2 Set Subband in End Node ==
389 +
390 +
391 +* 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.
392 +
393 +* 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.
394 +
395 +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]]?
396 +
397 +
398 +
399 +
400 +
401 +
Copyright ©2010-2022 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0