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)
Details
- Page properties
-
- Content
-
... ... @@ -16,10 +16,8 @@ 16 16 * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible) 17 17 * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI) 18 18 19 +**~1. End Device Join Screen shot, we can check:** 19 19 20 - 21 -(% style="color:blue" %)**1. End Device Join Screen shot, we can check:** 22 - 23 23 * If the device is sending join request to server? 24 24 * What frequency the device is sending? 25 25 ... ... @@ -28,7 +28,7 @@ 28 28 Console Output from End device to see the transmit frequency 29 29 30 30 31 - (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**29 +**2. Gateway packet traffic in gateway web or ssh. we can check:** 32 32 33 33 * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency) 34 34 * If the gateway gets the Join Accept message from server and transmit it via LoRa? ... ... @@ -38,7 +38,7 @@ 38 38 Console Output from Gateway to see packets between end node and server. 39 39 40 40 41 - (% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**39 +**3. Gateway Traffic Page in LoRaWAN Server** 42 42 43 43 * If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings. 44 44 * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device. ... ... @@ -49,7 +49,7 @@ 49 49 The Traffic for the End node in the server, use TTN as example 50 50 51 51 52 - (% style="color:blue" %)**4. Data Page in LoRaWAN server**50 +**4. Data Page in LoRaWAN server** 53 53 54 54 * If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node. 55 55 ... ... @@ -207,9 +207,6 @@ 207 207 * This packet must match the frequency of the RX1 or RX2 window. 208 208 * This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**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.** 209 209 210 - 211 - 212 - 213 213 == 5.2 See Debug Info == 214 214 215 215 ... ... @@ -354,7 +354,6 @@ 354 354 **Change to fix frequency: AT+CHS=904900000** 355 355 **Change to fix DR: AT+DR=0** 356 356 357 - 358 358 [[image:image-20220526165525-16.png]] 359 359 360 360 ... ... @@ -380,7 +380,6 @@ 380 380 381 381 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key) 382 382 383 - 384 384 [[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]] 385 385 386 386 [[image:image-20220526171029-20.png]] ... ... @@ -392,15 +392,13 @@ 392 392 393 393 = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware = 394 394 395 - 396 396 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. 397 397 398 398 399 399 = 9. Why do I see a "MIC Mismatch" error message from the server? = 400 400 401 - 402 402 ((( 403 -1) 394 +1)If the user receives a "MIC Mismatch" message after registering the node on the server. 404 404 ))) 405 405 406 406 ((( ... ... @@ -422,14 +422,11 @@ 422 422 * ((( 423 423 If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 424 424 425 - 426 - 427 427 428 428 ))) 429 429 430 430 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 431 431 432 - 433 433 * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 434 434 435 435 ((( ... ... @@ -446,14 +446,11 @@ 446 446 * ((( 447 447 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]] 448 448 449 - 450 - 451 451 452 452 ))) 453 453 454 454 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 455 455 456 - 457 457 ((( 458 458 It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 459 459 ))) ... ... @@ -484,8 +484,6 @@ 484 484 485 485 ((( 486 486 You can rewrites the keys by running commands in AT Console 487 - 488 - 489 489 ))) 490 490 491 491 (((