Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.3 >
edited by Xiaoling
on 2022/07/13 14:59
To version < 40.1 >
edited by Bei Jinggeng
on 2023/04/23 10:58
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -4,7 +4,7 @@
4 4  
5 5  
6 6  
7 -= 1. OTAA Join Process Debug =
7 += 1.(% style="display:none" %) (%%) OTAA Join Process Debug =
8 8  
9 9  
10 10  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
... ... @@ -11,24 +11,31 @@
11 11  \\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
12 12  
13 13  * End node console to show the Join freuqency and DR. (If possible)
14 +
14 14  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. (If possible)
16 +
15 15  * Gateway traffic (from server UI) to shows the data exchange between gateway and server. (Normaly possible)
18 +
16 16  * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible)
20 +
17 17  * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
18 18  
19 -**~1. End Device Join Screen shot, we can check:**
23 +(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
20 20  
21 21  * If the device is sending join request to server?
26 +
22 22  * What frequency the device is sending?
23 23  
24 -[[image:image-20220526164956-15.png]]
29 +[[image:image-20220526164956-15.png||height="591" width="1153"]]
25 25  
26 26  Console Output from End device to see the transmit frequency
27 27  
28 28  
29 -**2. Gateway packet traffic in gateway web or ssh. we can check:**
30 30  
35 +(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 +
31 31  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
38 +
32 32  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
33 33  
34 34  [[image:image-20220526163608-2.png]]
... ... @@ -36,10 +36,13 @@
36 36  Console Output from Gateway to see packets between end node and server.
37 37  
38 38  
39 -**3. Gateway Traffic Page in LoRaWAN Server**
40 40  
47 +(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
48 +
41 41  * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
50 +
42 42  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
52 +
43 43  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
44 44  
45 45  [[image:image-20220526163633-3.png]]
... ... @@ -47,8 +47,9 @@
47 47  The Traffic for the End node in the server, use TTN as example
48 48  
49 49  
50 -**4. Data Page in LoRaWAN server**
51 51  
61 +(% style="color:blue" %)**4. Data Page in LoRaWAN server**
62 +
52 52  * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
53 53  
54 54  [[image:image-20220526163704-4.png]]
... ... @@ -55,6 +55,7 @@
55 55  
56 56  The data for the end device set in server
57 57  
69 +
58 58  [[image:image-20220526163732-5.png]]
59 59  
60 60  Check if OTAA Keys match the keys in device
... ... @@ -101,6 +101,7 @@
101 101  
102 102  US915 Channels
103 103  
116 +
104 104  [[image:image-20220526163926-7.png]]
105 105  
106 106  AU915 Channels
... ... @@ -123,7 +123,7 @@
123 123  (((
124 124  TTN FREQUENCY PLAN
125 125  
126 -
139 +(% style="display:none" %) (%%)
127 127  )))
128 128  
129 129  (((
... ... @@ -130,6 +130,7 @@
130 130  In dragino end node, user can use AT+CHE command to set what frequencies set the end node will use. The default settings for Dragino end node are preconfigure for TTN server, so use 8~~15 channels, which is **AT+CHE=2**. (AT+CHE=1 for first 8 channels, AT+CHE=2 for second 8 channels.. etc, and AT+CHE=0 for all 72 channels. )
131 131  )))
132 132  
146 +(% style="display:none" %) (%%)
133 133  
134 134  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
135 135  
... ... @@ -136,17 +136,16 @@
136 136  
137 137  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
138 138  
139 -* **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
140 -* **Gateway** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
141 -* **LoRaWAN server** ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
153 +* (% style="color:blue" %)**End node** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
142 142  
155 +* (% style="color:blue" %)**Gateway** (%%) ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Gateway. this is the default settings for dragino sensors.
156 +
157 +* (% style="color:blue" %)**LoRaWAN server**  (%%) ~-~-> ChirpStack default installation and use Sub-band1, **enabled_uplink_channels=[0, 1, 2, 3, 4, 5, 6, 7]** in the file chirpstack-network-server.toml.
158 +
143 143  (((
144 144  When Sensor power on, it will use sub-band2 to join the network, the frequency matches the settings in gateway so all Join Request will be passed to the server for Join. Server will ask the sensor to change to Sub-band1 in the Join Accept downlink message. Sensor will change to sub-band1 for data upload. This cause the sensor and gateway have different frequencies so user see lost of most data or even no data.
145 145  )))
146 146  
147 -(((
148 -
149 -)))
150 150  
151 151  (((
152 152  Use Subband2 as a default subband cause the sensor to have problem to work with the LoRaWAN server which use other subband, and use need to access to the end node to change the subband by console. that is not user frendily,. So since Dragino LoRaWAN Stack version DLS-005(release on end of 2020), we have changed the device to use All Subbands for OTAA join, for example, device will use the first frequency in Sub-Band1 as firt OTAA join packet, then use the first frequency in Sub-Band 2 , then first frequency in sub-band 3, and so on. LoRaWAN server will normally provide the required subband in the OTAA accept process, so end node will know what subband it use after join. If LoRaWAN server doesn't provide subband info in OTAA join, end node will use the subband which join success as the working subband. So the new method cause a longer OTAA Join time but will be compatible with all LoRaWAN server. And new method won't affect the normal uplink after Join Success.
... ... @@ -161,18 +161,10 @@
161 161  )))
162 162  
163 163  (((
164 -
165 -)))
166 -
167 -(((
168 168  So in ABP mode, first check if the packet already arrive your gateway, if the packet arrive gatewat but didn't arrive server. Please check if this is the issue.
169 169  )))
170 170  
171 171  (((
172 -
173 -)))
174 -
175 -(((
176 176  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
177 177  )))
178 178  
... ... @@ -200,9 +200,13 @@
200 200  Below are the requirement for the End Device to receive the packets.
201 201  
202 202  * The End Device must open the receive windows: RX1 or RX2
208 +
203 203  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
210 +
204 204  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
212 +
205 205  * This packet must match the frequency of the RX1 or RX2 window.
214 +
206 206  * This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**This is the common fail point, because different lorawan server might use different RX2DR and they don't info End Node via ADR message so cause the mismatch. If this happen, user need to change the RX2DR to the right value in end node. In OTAA, LoRaWAN Server will send the RX2DR setting in Join Accept message so the end node will auto adjust. but ABP uplink doesn't support this auto change.**
207 207  
208 208  
... ... @@ -239,6 +239,7 @@
239 239  )))
240 240  
241 241  
251 +
242 242  (((
243 243  (% style="color:blue" %)**For LoRaWAN Gateway**
244 244  )))
... ... @@ -254,6 +254,7 @@
254 254  )))
255 255  
256 256  
267 +
257 257  (((
258 258  (% style="color:blue" %)**For End Node**
259 259  )))
... ... @@ -263,18 +263,14 @@
263 263  )))
264 264  
265 265  (((
266 -
267 -)))
277 +* (% style="color:#037691" %)**AT+RX2FQ=869525000**  (%%) **~-~-->**  The RX2 Window frequency
268 268  
269 -(((
270 -(% class="box infomessage" %)
271 -(((
272 -AT+RX2FQ=869525000     ~-~--> The RX2 Window frequency
273 -AT+RX2DR=3      ~-~--> The RX2 DataRate
274 -AT+RX1DL=1000   ~-~--> Receive Delay 1
275 -AT+RX2DL=2000   ~-~--> Receive Delay 2
279 +* (% style="color:#037691" %)**AT+RX2DR=3**          (%%) **~-~-->**  The RX2 DataRate
280 +
281 +* (% style="color:#037691" %)**AT+RX1DL=1000**       (%%) ** ~-~-->**  Receive Delay 1
282 +
283 +* (% style="color:#037691" %)**AT+RX2DL=2000**       (%%) **~-~--> ** Receive Delay 2
276 276  )))
277 -)))
278 278  
279 279  (((
280 280  (% style="color:blue" %)**when the device running, we can see below info:**
... ... @@ -290,6 +290,8 @@
290 290  
291 291  (((
292 292  
300 +
301 +
293 293  )))
294 294  
295 295  (((
... ... @@ -308,17 +308,23 @@
308 308   1:0012345678}}}
309 309  
310 310  
311 -== 5.3 If problem doesn’t solve ==
320 +== 5.3 If problem doesn't solve ==
312 312  
322 +
313 313  (% style="color:red" %)**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
314 314  
315 315  * End node console to show the transmit freuqency and DR.
326 +
316 316  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
328 +
317 317  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
330 +
318 318  * End Node traffic (from server UI) to shows end node activity in server.
319 319  
333 +
320 320  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
321 321  
336 +
322 322  (((
323 323  In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink.
324 324  )))
... ... @@ -344,20 +344,22 @@
344 344  
345 345  = 7. Decrypt a LoRaWAN Packet =
346 346  
347 -~1. LHT65 End device configure:
348 348  
349 -(% class="box infomessage" %)
350 -(((
351 -**Change to ABP Mode: AT+NJM=0**
352 -**Change to fix frequency: AT+CHS=904900000**
353 -**Change to fix DR: AT+DR=0**
354 -)))
363 +(% style="color:blue" %)**1. LHT65 End device configure:**
355 355  
365 +**Change to ABP Mode:  AT+NJM=0**
366 +
367 +**Change to fix frequency:  AT+CHS=904900000**
368 +
369 +**Change to fix DR:  AT+DR=0**
370 +
371 +
356 356  [[image:image-20220526165525-16.png]]
357 357  
358 358  
359 -2. In LG02 , configure to receive above message
360 360  
376 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
377 +
361 361  [[image:image-20220526165612-17.png]]
362 362  
363 363  
... ... @@ -366,8 +366,9 @@
366 366  [[image:image-20220526171112-21.png]]
367 367  
368 368  
369 -3. Decode the info in web
370 370  
387 +(% style="color:blue" %)**3. Decode the info in web**
388 +
371 371  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
372 372  
373 373  Need these three fields:
... ... @@ -378,6 +378,7 @@
378 378  
379 379  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
380 380  
399 +
381 381  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/?data=40c1190126800100024926272bf18bbb6341584e27e23245&nwkskey=00000000000000000000000000000111&appskey=00000000000000000000000000000111]]
382 382  
383 383  [[image:image-20220526171029-20.png]]
... ... @@ -389,13 +389,15 @@
389 389  
390 390  = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware =
391 391  
411 +
392 392  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
393 393  
394 394  
395 395  = 9. Why do I see a "MIC Mismatch" error message from the server? =
396 396  
417 +
397 397  (((
398 -1)If the user receives a "MIC Mismatch" message after registering the node on the server.
419 +1)  If the user receives a "MIC Mismatch" message after registering the node on the server.
399 399  )))
400 400  
401 401  (((
... ... @@ -416,33 +416,57 @@
416 416  
417 417  * (((
418 418  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
419 -
420 -
421 421  )))
422 422  
442 +(% class="wikigeneratedid" %)
443 +3）Wrong Regional Parameters version selected
444 + We generally use versions above 1.0.2
445 +
446 +(% class="wikigeneratedid" %)
447 +[[image:image-20230322163227-1.png]]
448 +
449 +(% class="wikigeneratedid" %)
450 +4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
451 +
452 +
423 423  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
424 424  
425 -* If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
426 426  
427 -(((
428 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
429 -)))
456 +(% style="color:blue" %)**Why this happen:**
430 430  
431 -(((
432 -When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
433 -)))
458 +For US915, AU915 or AS923 frequencies.It is possible because: .
434 434  
435 -* (((
436 -Solution: Use the decoder to filter out this 00 packet.
437 -)))
438 -* (((
439 -Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
460 +When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled.
440 440  
441 -
442 -)))
462 +1.
443 443  
464 +When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end node, and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit, so it will send a normal uplink packet, and following an additional 00 data packet to handle this MAC command response.
465 +
466 +2.
467 +
468 +The server downlinks a calibration time package
469 +This calibration time packet will exceed the byte limit, causing its payload to become 00
470 +
471 +(% style="color:blue" %)**How to solve:**
472 +
473 +Solution:
474 +
475 +~1. Use the decoder to filter out this 0x00 packet.
476 +
477 +2. Data rate changed from DR3 to DR5, increasing upload byte length
478 +AT+ADR=0
479 +AT+DR=3
480 +
481 +Downlink：
482 +
483 +[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
484 +
485 +Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]]
486 +
487 +
444 444  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
445 445  
490 +
446 446  (((
447 447  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
448 448  )))
... ... @@ -473,6 +473,8 @@
473 473  
474 474  (((
475 475  You can rewrites the keys by running commands in AT Console
521 +
522 +
476 476  )))
477 477  
478 478  (((
... ... @@ -506,6 +506,30 @@
506 506  Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
507 507  
508 508  
556 += 13. Why it takes longer time for OTAA joined in US915/CN470/AU915 band? =
509 509  
558 +
559 +In US915, AU915 or CN470 frequency band, there are 8 subbands, totally 72 channels. and LoRaWAN server normally use only one sub-band, for example Subband 2 in TTN. The gateway also configured to Subband 2 and cover eight channels in this subband. If the end node transfer data in Subband 2, it will reach to gateway and to the LoRaWAN server. If the end node transfer packets in other subbands, for example subband 1, the packet won't arrive both gateway or LoRaWAN server.
560 +
561 +
562 +In Dragino Sensors old version firmware (before early 2022), the subband is fixed the subband to 2 , but this cause a problem, the end node is hard to use in other subband and need program. So the new logic is as below:
563 +
564 +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:
565 +
566 +* (((
567 +Check what sub-band the LoRaWAN server ask from the OTAA Join Accept message and switch to that subband
568 +)))
569 +* (((
570 +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)
571 +)))
572 +
573 +This change will make the activation time a littler longer but make sure the device can be used in any subband.
574 +
575 +
576 +Below is a photo to show why it takes longer time for OTAA Join. We can see in 72 channels mode, why it takes more time to join success. If users want to have faster OTAA Join success, he can change default CHE to the subband he use.
577 +
578 +
579 +[[image:image-20221215223215-1.png||height="584" width="1280"]]
580 +
510 510  (% class="wikigeneratedid" %)
511 511  
image-20221215223215-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Edwin
Size
... ... @@ -1,0 +1,1 @@
1 +183.6 KB
Content
image-20230322163227-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Bei
Size
... ... @@ -1,0 +1,1 @@
1 +43.1 KB
Content

Applications

Navigation

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