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
-
... ... @@ -302,9 +302,8 @@ 302 302 1:0012345678}}} 303 303 304 304 305 -== 5.3 If problem doesn 't solve ==305 +== 5.3 If problem doesn’t solve == 306 306 307 - 308 308 (% 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:** 309 309 310 310 * End node console to show the transmit freuqency and DR. ... ... @@ -312,12 +312,8 @@ 312 312 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. 313 313 * End Node traffic (from server UI) to shows end node activity in server. 314 314 315 - 316 - 317 - 318 318 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 319 319 320 - 321 321 ((( 322 322 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. 323 323 ))) ... ... @@ -343,18 +343,19 @@ 343 343 344 344 = 7. Decrypt a LoRaWAN Packet = 345 345 341 +~1. LHT65 End device configure: 346 346 347 -(% style="color:blue" %)**1. LHT65 End device configure:** 343 +(% class="box infomessage" %) 344 +((( 345 +**Change to ABP Mode: AT+NJM=0** 346 +**Change to fix frequency: AT+CHS=904900000** 347 +**Change to fix DR: AT+DR=0** 348 +))) 348 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 - 353 - 354 354 [[image:image-20220526165525-16.png]] 355 355 356 356 357 - (% style="color:blue" %)**2. In LG02 , configure to receive above message**353 +2. In LG02 , configure to receive above message 358 358 359 359 [[image:image-20220526165612-17.png]] 360 360 ... ... @@ -364,7 +364,7 @@ 364 364 [[image:image-20220526171112-21.png]] 365 365 366 366 367 - (% style="color:blue" %)**3. Decode the info in web**363 +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/]] 370 370 ... ... @@ -376,7 +376,6 @@ 376 376 377 377 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key) 378 378 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 382 [[image:image-20220526171029-20.png]] ... ... @@ -388,15 +388,13 @@ 388 388 389 389 = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware = 390 390 391 - 392 392 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. 393 393 394 394 395 395 = 9. Why do I see a "MIC Mismatch" error message from the server? = 396 396 397 - 398 398 ((( 399 -1) 392 +1)If the user receives a "MIC Mismatch" message after registering the node on the server. 400 400 ))) 401 401 402 402 ((( ... ... @@ -418,14 +418,11 @@ 418 418 * ((( 419 419 If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 420 420 421 - 422 - 423 423 424 424 ))) 425 425 426 426 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 427 427 428 - 429 429 * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 430 430 431 431 ((( ... ... @@ -442,14 +442,11 @@ 442 442 * ((( 443 443 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]] 444 444 445 - 446 - 447 447 448 448 ))) 449 449 450 450 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 451 451 452 - 453 453 ((( 454 454 It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 455 455 ))) ... ... @@ -480,8 +480,6 @@ 480 480 481 481 ((( 482 482 You can rewrites the keys by running commands in AT Console 483 - 484 - 485 485 ))) 486 486 487 487 (((