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
-
... ... @@ -314,9 +314,9 @@ 314 314 315 315 316 316 317 + 317 317 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 318 318 319 - 320 320 ((( 321 321 In LoRaWAN, the gatewat will use the frequency specify by the server to transmit a packet as downlink purpose. Each Frequency band has different downlink frequency. and the gateway has a frequency range limited to transmit downlink. 322 322 ))) ... ... @@ -342,17 +342,19 @@ 342 342 343 343 = 7. Decrypt a LoRaWAN Packet = 344 344 345 +~1. LHT65 End device configure: 345 345 346 -(% style="color:blue" %)**1. LHT65 End device configure:** 347 +(% class="box infomessage" %) 348 +((( 349 +**Change to ABP Mode: AT+NJM=0** 350 +**Change to fix frequency: AT+CHS=904900000** 351 +**Change to fix DR: AT+DR=0** 352 +))) 347 347 348 -**Change to ABP Mode: AT+NJM=0** 349 -**Change to fix frequency: AT+CHS=904900000** 350 -**Change to fix DR: AT+DR=0** 351 - 352 352 [[image:image-20220526165525-16.png]] 353 353 354 354 355 - (% style="color:blue" %)**2. In LG02 , configure to receive above message**357 +2. In LG02 , configure to receive above message 356 356 357 357 [[image:image-20220526165612-17.png]] 358 358 ... ... @@ -362,7 +362,7 @@ 362 362 [[image:image-20220526171112-21.png]] 363 363 364 364 365 - (% style="color:blue" %)**3. Decode the info in web**367 +3. Decode the info in web 366 366 367 367 [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]] 368 368 ... ... @@ -374,7 +374,6 @@ 374 374 375 375 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key) 376 376 377 - 378 378 [[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]] 379 379 380 380 [[image:image-20220526171029-20.png]] ... ... @@ -386,15 +386,13 @@ 386 386 387 387 = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware = 388 388 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 392 393 393 = 9. Why do I see a "MIC Mismatch" error message from the server? = 394 394 395 - 396 396 ((( 397 -1) 396 +1)If the user receives a "MIC Mismatch" message after registering the node on the server. 398 398 ))) 399 399 400 400 ((( ... ... @@ -416,14 +416,11 @@ 416 416 * ((( 417 417 If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 418 418 419 - 420 - 421 421 422 422 ))) 423 423 424 424 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 425 425 426 - 427 427 * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 428 428 429 429 ((( ... ... @@ -440,14 +440,11 @@ 440 440 * ((( 441 441 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]] 442 442 443 - 444 - 445 445 446 446 ))) 447 447 448 448 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 449 449 450 - 451 451 ((( 452 452 It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 453 453 ))) ... ... @@ -478,8 +478,6 @@ 478 478 479 479 ((( 480 480 You can rewrites the keys by running commands in AT Console 481 - 482 - 483 483 ))) 484 484 485 485 (((