Changes for page LoRaWAN Communication Debug
Last modified by Edwin Chen on 2025/01/29 20:30
Summary
-
Page properties (1 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 2 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,9 +1,12 @@ 1 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. ... ... @@ -194,8 +194,6 @@ 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 197 - 198 - 199 199 == 5.2 See Debug Info == 200 200 201 201 ((( ... ... @@ -337,32 +337,29 @@ 337 337 338 338 (% class="box infomessage" %) 339 339 ((( 340 - **Change to ABP Mode: AT+NJM=0**341 +Change to ABP Mode: AT+NJM=0 341 341 ))) 342 342 343 343 (% class="box infomessage" %) 344 344 ((( 345 - **Change to fix frequency: AT+CHS=904900000**346 +Change to fix frequency: AT+CHS=904900000 346 346 ))) 347 347 348 348 (% class="box infomessage" %) 349 349 ((( 350 - **Change to fix DR: AT+DR=0**351 +Change to fix DR: AT+DR=0 351 351 ))) 352 352 353 -[[image:image -20220526165525-16.png]]354 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]] 354 354 355 - 356 356 2. In LG02 , configure to receive above message 357 357 358 -[[image:image -20220526165612-17.png]]358 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]] 359 359 360 - 361 361 In LG02 console, we can see the hex receive are: 362 362 363 -[[image:image -20220526171112-21.png]]362 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]] 364 364 365 - 366 366 3. Decode the info in web 367 367 368 368 [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]] ... ... @@ -377,7 +377,7 @@ 377 377 378 378 [[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]] 379 379 380 -[[image:image -20220526171029-20.png]]378 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]] 381 381 382 382 ((( 383 383 The FRMPayload is the device payload. ... ... @@ -388,7 +388,6 @@ 388 388 389 389 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. 390 390 391 - 392 392 = 9. Why do I see a "MIC Mismatch" error message from the server? = 393 393 394 394 ((( ... ... @@ -441,62 +441,31 @@ 441 441 442 442 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 443 443 444 -((( 445 445 It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 446 -))) 447 447 448 -((( 449 449 AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 450 -))) 451 451 452 -((( 453 453 AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 454 -))) 455 455 456 -((( 457 457 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 458 -))) 459 459 460 -((( 461 461 AT+APPEUI=00 00 00 00 00 00 00 00 462 -))) 463 463 464 -((( 465 - 466 -))) 467 467 468 -((( 469 469 You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number. 470 -))) 471 471 472 -((( 473 473 You can rewrites the keys by running commands in AT Console 474 -))) 475 475 476 -((( 477 -**For example:** 478 -))) 456 +For example: 479 479 480 -((( 481 481 AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE 482 -))) 483 483 484 -((( 485 485 AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11 486 -))) 487 487 488 -((( 489 489 AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10 490 -))) 491 491 492 -((( 493 493 AT+APPEUI=2C 45 47 E3 24 12 23 24 494 -))) 495 495 496 -((( 497 497 (Any combination of 16 bit codes can be used) 498 -))) 499 499 500 500 501 -(% class="wikigeneratedid" %) 502 -
- 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