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, 6 removed)
Details
- Page properties
-
- Content
-
... ... @@ -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-2022052616 4956-15.png]]26 +[[image:image-20220526163523-1.png]] 27 27 28 28 Console Output from End device to see the transmit frequency 29 29 ... ... @@ -197,6 +197,7 @@ 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 200 + 200 200 == 5.2 See Debug Info == 201 201 202 202 ((( ... ... @@ -300,7 +300,7 @@ 300 300 301 301 == 5.3 If problem doesn’t solve == 302 302 303 - (% 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:** 304 304 305 305 * End node console to show the transmit freuqency and DR. 306 306 * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server. ... ... @@ -307,6 +307,9 @@ 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 311 +(% class="wikigeneratedid" %) 312 + 313 + 310 310 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 311 311 312 312 ((( ... ... @@ -338,32 +338,29 @@ 338 338 339 339 (% class="box infomessage" %) 340 340 ((( 341 - **Change to ABP Mode: AT+NJM=0**345 +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**350 +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**355 +Change to fix DR: AT+DR=0 352 352 ))) 353 353 354 -[[image:image -20220526165525-16.png]]358 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]] 355 355 356 - 357 357 2. In LG02 , configure to receive above message 358 358 359 -[[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"]] 360 360 361 - 362 362 In LG02 console, we can see the hex receive are: 363 363 364 -[[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"]] 365 365 366 - 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: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"]] 382 382 383 383 ((( 384 384 The FRMPayload is the device payload. ... ... @@ -389,7 +389,6 @@ 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 392 - 393 393 = 9. Why do I see a "MIC Mismatch" error message from the server? = 394 394 395 395 ((( ... ... @@ -442,61 +442,32 @@ 442 442 443 443 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 444 444 445 -((( 446 446 It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 447 -))) 448 448 449 -((( 450 450 AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 451 -))) 452 452 453 -((( 454 454 AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 455 -))) 456 456 457 -((( 458 458 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 459 -))) 460 460 461 -((( 462 462 AT+APPEUI=00 00 00 00 00 00 00 00 463 -))) 464 464 465 -((( 466 - 467 -))) 468 468 469 -((( 470 470 You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number. 471 -))) 472 472 473 -((( 474 474 You can rewrites the keys by running commands in AT Console 475 -))) 476 476 477 -((( 478 -**For example:** 479 -))) 460 +For example: 480 480 481 -((( 482 482 AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE 483 -))) 484 484 485 -((( 486 486 AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11 487 -))) 488 488 489 -((( 490 490 AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10 491 -))) 492 492 493 -((( 494 494 AT+APPEUI=2C 45 47 E3 24 12 23 24 495 -))) 496 496 497 -((( 498 498 (Any combination of 16 bit codes can be used) 499 -))) 500 500 501 501 502 502 (% class="wikigeneratedid" %)
- 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