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, 9 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 ... ... @@ -211,7 +211,7 @@ 211 211 Configure a downstream to the end device 212 212 ))) 213 213 214 -[[image:image -20220526164623-12.png]]214 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]] 215 215 216 216 ((( 217 217 Set a downstream in TTN and see it is sent ... ... @@ -222,7 +222,7 @@ 222 222 This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3 223 223 ))) 224 224 225 -[[image:image -20220526164650-13.png]]225 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]] 226 226 227 227 ((( 228 228 Gateway Traffic can see this downstream info ... ... @@ -237,7 +237,7 @@ 237 237 When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below: 238 238 ))) 239 239 240 -[[image:image -20220526164734-14.png]]240 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]] 241 241 242 242 ((( 243 243 Gateway Sent out this packet ... ... @@ -297,10 +297,9 @@ 297 297 Receive data 298 298 1:0012345678}}} 299 299 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:**302 +**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. ... ... @@ -338,32 +338,29 @@ 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:image -20220526165525-16.png]]353 +[[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]]357 +[[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]]361 +[[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]]377 +[[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,62 +442,31 @@ 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 -))) 455 +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 -(% class="wikigeneratedid" %) 503 -
- image-20220526164650-13.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -45.0 KB - Content
- image-20220526164734-14.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -120.3 KB - Content
- image-20220526164956-15.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Xiaoling - Size
-
... ... @@ -1,1 +1,0 @@ 1 -634.4 KB - Content
- 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