Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 28.1 >
edited by Xiaoling
on 2022/05/26 17:10
To version < 31.3 >
edited by Xiaoling
on 2022/06/01 13:38
>
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.
... ... @@ -185,7 +185,7 @@
185 185  Depends on Class A or Class C, the receive windows will be a little difference,
186 186  )))
187 187  
188 -[[image:image-20220526164547-11.png]]
185 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
... ... @@ -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  (((
... ... @@ -338,29 +338,32 @@
338 338  
339 339  (% class="box infomessage" %)
340 340  (((
341 -Change to ABP Mode: AT+NJM=0
340 +**Change to ABP Mode: AT+NJM=0**
342 342  )))
343 343  
344 344  (% class="box infomessage" %)
345 345  (((
346 -Change to fix frequency: AT+CHS=904900000
345 +**Change to fix frequency: AT+CHS=904900000**
347 347  )))
348 348  
349 349  (% class="box infomessage" %)
350 350  (((
351 -Change to fix DR: AT+DR=0
350 +**Change to fix DR: AT+DR=0**
352 352  )))
353 353  
354 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
353 +[[image:image-20220526165525-16.png]]
355 355  
355 +
356 356  2. In LG02 , configure to receive above message
357 357  
358 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
358 +[[image:image-20220526165612-17.png]]
359 359  
360 +
360 360  In LG02 console, we can see the hex receive are:
361 361  
362 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
363 +[[image:image-20220526171112-21.png]]
363 363  
365 +
364 364  3. Decode the info in web
365 365  
366 366  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -375,7 +375,7 @@
375 375  
376 376  [[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]]
377 377  
378 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
380 +[[image:image-20220526171029-20.png]]
379 379  
380 380  (((
381 381   The FRMPayload is the device payload.
... ... @@ -386,6 +386,7 @@
386 386  
387 387  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.
388 388  
391 +
389 389  = 9. Why do I see a "MIC Mismatch" error message from the server? =
390 390  
391 391  (((
... ... @@ -432,37 +432,67 @@
432 432  * (((
433 433  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]]
434 434  
435 -
436 436  
437 437  )))
438 438  
439 439  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
440 440  
443 +(((
441 441  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
445 +)))
442 442  
447 +(((
443 443  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449 +)))
444 444  
451 +(((
445 445  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
453 +)))
446 446  
455 +(((
447 447  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
457 +)))
448 448  
459 +(((
449 449  AT+APPEUI=00 00 00 00 00 00 00 00
461 +)))
450 450  
463 +(((
464 +
465 +)))
451 451  
467 +(((
452 452  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
469 +)))
453 453  
471 +(((
454 454  You can rewrites the keys by running commands in AT Console
473 +)))
455 455  
456 -For example：
475 +(((
476 +**For example：**
477 +)))
457 457  
479 +(((
458 458  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
481 +)))
459 459  
483 +(((
460 460  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
485 +)))
461 461  
487 +(((
462 462  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
489 +)))
463 463  
491 +(((
464 464  AT+APPEUI=2C 45 47 E3 24 12 23 24
493 +)))
465 465  
495 +(((
466 466  (Any combination of 16 bit codes can be used）
497 +)))
467 467  
468 468  
500 +(% class="wikigeneratedid" %)
501 +
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content

Applications

Navigation

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