<
From version < 29.2 >
edited by Xiaoling
on 2022/05/26 17:11
To version < 30.3 >
edited by Xiaoling
on 2022/05/30 10:57
>
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.
... ... @@ -197,6 +197,8 @@
197 197  * This packet must match the frequency of the RX1 or RX2 window.
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  
197 +
198 +
200 200  == 5.2 See Debug Info ==
201 201  
202 202  (((
... ... @@ -307,6 +307,8 @@
307 307  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
308 308  * End Node traffic (from server UI) to shows end node activity in server.
309 309  
309 +
310 +
310 310  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
311 311  
312 312  (((
... ... @@ -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  (((
... ... @@ -441,31 +441,62 @@
441 441  
442 442  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443 443  
446 +(((
444 444  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
448 +)))
445 445  
450 +(((
446 446  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
452 +)))
447 447  
454 +(((
448 448  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
456 +)))
449 449  
458 +(((
450 450  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
460 +)))
451 451  
462 +(((
452 452  AT+APPEUI=00 00 00 00 00 00 00 00
464 +)))
453 453  
466 +(((
467 +
468 +)))
454 454  
470 +(((
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.
472 +)))
456 456  
474 +(((
457 457  You can rewrites the keys by running commands in AT Console
476 +)))
458 458  
459 -For example:
478 +(((
479 +**For example:**
480 +)))
460 460  
482 +(((
461 461  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
484 +)))
462 462  
486 +(((
463 463  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
488 +)))
464 464  
490 +(((
465 465  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
492 +)))
466 466  
494 +(((
467 467  AT+APPEUI=2C 45 47 E3 24 12 23 24
496 +)))
468 468  
498 +(((
469 469  (Any combination of 16 bit codes can be used)
500 +)))
470 470  
471 471  
503 +(% class="wikigeneratedid" %)
504 +
Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0