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