Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 22.2 >
edited by Xiaoling
on 2022/05/26 16:48
To version < 30.4 >
edited by Xiaoling
on 2022/05/30 10:58
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,9 @@
1 1  **~ Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
6 +
10 10  = 1. OTAA Join Process Debug =
11 11  
12 12  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.
... ... @@ -23,7 +23,7 @@
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526163523-1.png]]
23 +[[image:image-20220526164956-15.png]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -198,6 +198,7 @@
198 198  * 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.**
199 199  
200 200  
198 +
201 201  == 5.2 See Debug Info ==
202 202  
203 203  (((
... ... @@ -298,12 +298,10 @@
298 298   Receive data
299 299   1:0012345678}}}
300 300  
301 -(% class="wikigeneratedid" %)
302 -​​​​​​​
303 303  
304 304  == 5.3 If problem doesn’t solve ==
305 305  
306 -**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:**
302 +(% 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:**
307 307  
308 308  * End node console to show the transmit freuqency and DR.
309 309  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -310,6 +310,8 @@
310 310  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
311 311  * End Node traffic (from server UI) to shows end node activity in server.
312 312  
309 +
310 +
313 313  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
314 314  
315 315  (((
... ... @@ -341,29 +341,32 @@
341 341  
342 342  (% class="box infomessage" %)
343 343  (((
344 -Change to ABP Mode: AT+NJM=0
342 +**Change to ABP Mode: AT+NJM=0**
345 345  )))
346 346  
347 347  (% class="box infomessage" %)
348 348  (((
349 -Change to fix frequency: AT+CHS=904900000
347 +**Change to fix frequency: AT+CHS=904900000**
350 350  )))
351 351  
352 352  (% class="box infomessage" %)
353 353  (((
354 -Change to fix DR: AT+DR=0
352 +**Change to fix DR: AT+DR=0**
355 355  )))
356 356  
357 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
355 +[[image:image-20220526165525-16.png]]
358 358  
357 +
359 359  2. In LG02 , configure to receive above message
360 360  
361 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
360 +[[image:image-20220526165612-17.png]]
362 362  
362 +
363 363  In LG02 console, we can see the hex receive are:
364 364  
365 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
365 +[[image:image-20220526171112-21.png]]
366 366  
367 +
367 367  3. Decode the info in web
368 368  
369 369  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -378,7 +378,7 @@
378 378  
379 379  [[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]]
380 380  
381 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
382 +[[image:image-20220526171029-20.png]]
382 382  
383 383  (((
384 384   The FRMPayload is the device payload.
... ... @@ -389,6 +389,7 @@
389 389  
390 390  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.
391 391  
393 +
392 392  = 9. Why do I see a "MIC Mismatch" error message from the server? =
393 393  
394 394  (((
... ... @@ -435,38 +435,66 @@
435 435  * (((
436 436  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]]
437 437  
438 -
439 439  
440 440  )))
441 441  
442 442  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443 443  
445 +(((
444 444  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
447 +)))
445 445  
449 +(((
446 446  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
451 +)))
447 447  
453 +(((
448 448  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
455 +)))
449 449  
457 +(((
450 450  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
459 +)))
451 451  
461 +(((
452 452  AT+APPEUI=00 00 00 00 00 00 00 00
463 +)))
453 453  
465 +(((
466 +
467 +)))
454 454  
469 +(((
455 455  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
471 +)))
456 456  
473 +(((
457 457  You can rewrites the keys by running commands in AT Console
475 +)))
458 458  
459 -For example：
477 +(((
478 +**For example：**
479 +)))
460 460  
481 +(((
461 461  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
483 +)))
462 462  
485 +(((
463 463  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
487 +)))
464 464  
489 +(((
465 465  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
491 +)))
466 466  
493 +(((
467 467  AT+APPEUI=2C 45 47 E3 24 12 23 24
495 +)))
468 468  
497 +(((
469 469  (Any combination of 16 bit codes can be used）
499 +)))
470 470  
471 471  
472 472  (% class="wikigeneratedid" %)
image-20220526164956-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content

Applications

Navigation

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