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, 4 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,5 +1,9 @@ 1 1 **~ Contents:** 2 2 3 +((( 4 + 5 +))) 6 + 3 3 {{toc/}} 4 4 5 5 ... ... @@ -19,7 +19,7 @@ 19 19 * If the device is sending join request to server? 20 20 * What frequency the device is sending? 21 21 22 -[[image: https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]26 +[[image:image-20220526163523-1.png]] 23 23 24 24 Console Output from End device to see the transmit frequency 25 25 ... ... @@ -29,7 +29,7 @@ 29 29 * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency) 30 30 * If the gateway gets the Join Accept message from server and transmit it via LoRa? 31 31 32 -[[image: https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]36 +[[image:image-20220526163608-2.png]] 33 33 34 34 Console Output from Gateway to see packets between end node and server. 35 35 ... ... @@ -405,6 +405,8 @@ 405 405 406 406 * ((( 407 407 If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 412 + 413 + 408 408 ))) 409 409 410 410 = 10. Why i got the payload only with "0x00" or "AA~=~="? = ... ... @@ -423,8 +423,39 @@ 423 423 Solution: Use the decoder to filter out this 00 packet. 424 424 ))) 425 425 * ((( 426 -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 427 -))) 432 +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]] 428 428 429 - (% class="wikigeneratedid" id="H" %)434 + 430 430 436 +))) 437 + 438 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 439 + 440 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 441 + 442 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 443 + 444 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 445 + 446 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 447 + 448 +AT+APPEUI=00 00 00 00 00 00 00 00 449 + 450 + 451 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number. 452 + 453 +You can rewrites the keys by running commands in AT Console 454 + 455 +For example： 456 + 457 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE 458 + 459 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11 460 + 461 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10 462 + 463 +AT+APPEUI=2C 45 47 E3 24 12 23 24 464 + 465 +(Any combination of 16 bit codes can be used） 466 + 467 +
- image-20220526163523-1.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +633.8 KB - Content
- image-20220526163608-2.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +116.4 KB - Content
- image-20220526163633-3.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +65.6 KB - Content
- image-20220526163704-4.png
-
- Author
-
... ... @@ -1,0 +1,1 @@ 1 +XWiki.Xiaoling - Size
-
... ... @@ -1,0 +1,1 @@ 1 +78.8 KB - Content