Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.2 >
edited by Xiaoling
on 2022/07/13 14:44
To version < 22.3 >
edited by Xiaoling
on 2022/05/26 16:48
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,12 @@
1 -**~ Table of Contents:**
1 +**~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. OTAA Join Process Debug =
8 8  
9 9  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.
... ... @@ -20,7 +20,7 @@
20 20  * If the device is sending join request to server?
21 21  * What frequency the device is sending?
22 22  
23 -[[image:image-20220526164956-15.png]]
26 +[[image:image-20220526163523-1.png]]
24 24  
25 25  Console Output from End device to see the transmit frequency
26 26  
... ... @@ -182,7 +182,7 @@
182 182  Depends on Class A or Class C, the receive windows will be a little difference,
183 183  )))
184 184  
185 -[[image:image-20220531161828-1.png]]
188 +[[image:image-20220526164547-11.png]]
186 186  
187 187  receive windows for Class A and Class C
188 188  
... ... @@ -194,6 +194,7 @@
194 194  * This packet must match the frequency of the RX1 or RX2 window.
195 195  * This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **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.**
196 196  
200 +
197 197  == 5.2 See Debug Info ==
198 198  
199 199  (((
... ... @@ -297,7 +297,7 @@
297 297  
298 298  == 5.3 If problem doesn’t solve ==
299 299  
300 -(% 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:**
304 +**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:**
301 301  
302 302  * End node console to show the transmit freuqency and DR.
303 303  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -304,6 +304,9 @@
304 304  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
305 305  * End Node traffic (from server UI) to shows end node activity in server.
306 306  
311 +(% class="wikigeneratedid" %)
312 +​​​​​​​
313 +
307 307  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
308 308  
309 309  (((
... ... @@ -335,24 +335,29 @@
335 335  
336 336  (% class="box infomessage" %)
337 337  (((
338 -**Change to ABP Mode: AT+NJM=0**
339 -**Change to fix frequency: AT+CHS=904900000**
340 -**Change to fix DR: AT+DR=0**
345 +Change to ABP Mode: AT+NJM=0
341 341  )))
342 342  
343 -[[image:image-20220526165525-16.png]]
348 +(% class="box infomessage" %)
349 +(((
350 +Change to fix frequency: AT+CHS=904900000
351 +)))
344 344  
353 +(% class="box infomessage" %)
354 +(((
355 +Change to fix DR: AT+DR=0
356 +)))
345 345  
358 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
359 +
346 346  2. In LG02 , configure to receive above message
347 347  
348 -[[image:image-20220526165612-17.png]]
362 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
349 349  
350 -
351 351  In LG02 console, we can see the hex receive are:
352 352  
353 -[[image:image-20220526171112-21.png]]
366 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
354 354  
355 -
356 356  3. Decode the info in web
357 357  
358 358  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -367,7 +367,7 @@
367 367  
368 368  [[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]]
369 369  
370 -[[image:image-20220526171029-20.png]]
382 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
371 371  
372 372  (((
373 373   The FRMPayload is the device payload.
... ... @@ -378,7 +378,6 @@
378 378  
379 379  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.
380 380  
381 -
382 382  = 9. Why do I see a "MIC Mismatch" error message from the server? =
383 383  
384 384  (((
... ... @@ -425,74 +425,39 @@
425 425  * (((
426 426  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]]
427 427  
439 +
428 428  
429 429  )))
430 430  
431 431  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
432 432  
433 -(((
434 434  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
435 -)))
436 436  
437 -(((
438 438  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
439 -)))
440 440  
441 -(((
442 442  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
443 -)))
444 444  
445 -(((
446 446  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447 -)))
448 448  
449 -(((
450 450  AT+APPEUI=00 00 00 00 00 00 00 00
451 -)))
452 452  
453 -(((
454 -
455 -)))
456 456  
457 -(((
458 458  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
459 -)))
460 460  
461 -(((
462 462  You can rewrites the keys by running commands in AT Console
463 -)))
464 464  
465 -(((
466 -**For example：**
467 -)))
460 +For example：
468 468  
469 -(((
470 470  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
471 -)))
472 472  
473 -(((
474 474  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
475 -)))
476 476  
477 -(((
478 478  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
479 -)))
480 480  
481 -(((
482 482  AT+APPEUI=2C 45 47 E3 24 12 23 24
483 -)))
484 484  
485 -(((
486 486  (Any combination of 16 bit codes can be used）
487 487  
488 488  
489 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
490 -)))
491 -
492 -
493 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
494 -
495 -
496 -
497 497  (% class="wikigeneratedid" %)
498 498  
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content

Applications

Navigation

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