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,8 +302,9 @@ 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 + 307 307 (% 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:** 308 308 309 309 * End node console to show the transmit freuqency and DR. ... ... @@ -311,8 +311,11 @@ 311 311 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. 312 312 * End Node traffic (from server UI) to shows end node activity in server. 313 313 315 + 316 + 314 314 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 315 315 319 + 316 316 ((( 317 317 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. 318 318 ))) ... ... @@ -338,19 +338,17 @@ 338 338 339 339 = 7. Decrypt a LoRaWAN Packet = 340 340 341 -~1. LHT65 End device configure: 342 342 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 -))) 346 +(% style="color:blue" %)**1. LHT65 End device configure:** 349 349 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 + 350 350 [[image:image-20220526165525-16.png]] 351 351 352 352 353 -2. In LG02 , configure to receive above message 355 +(% style="color:blue" %)**2. In LG02 , configure to receive above message** 354 354 355 355 [[image:image-20220526165612-17.png]] 356 356 ... ... @@ -360,7 +360,7 @@ 360 360 [[image:image-20220526171112-21.png]] 361 361 362 362 363 -3. Decode the info in web 365 +(% style="color:blue" %)**3. Decode the info in web** 364 364 365 365 [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]] 366 366 ... ... @@ -372,6 +372,7 @@ 372 372 373 373 AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key) 374 374 377 + 375 375 [[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]] 376 376 377 377 [[image:image-20220526171029-20.png]] ... ... @@ -383,13 +383,15 @@ 383 383 384 384 = 8. Why i see uplink 0x00 periodcally on the LHT65 v1.8 firmware = 385 385 389 + 386 386 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. 387 387 388 388 389 389 = 9. Why do I see a "MIC Mismatch" error message from the server? = 390 390 395 + 391 391 ((( 392 -1)If the user receives a "MIC Mismatch" message after registering the node on the server. 397 +1) If the user receives a "MIC Mismatch" message after registering the node on the server. 393 393 ))) 394 394 395 395 ((( ... ... @@ -411,11 +411,14 @@ 411 411 * ((( 412 412 If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 413 413 419 + 420 + 414 414 415 415 ))) 416 416 417 417 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 418 418 426 + 419 419 * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon. 420 420 421 421 ((( ... ... @@ -432,11 +432,14 @@ 432 432 * ((( 433 433 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]] 434 434 443 + 444 + 435 435 436 436 ))) 437 437 438 438 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 439 439 450 + 440 440 ((( 441 441 It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG 442 442 ))) ... ... @@ -467,6 +467,8 @@ 467 467 468 468 ((( 469 469 You can rewrites the keys by running commands in AT Console 481 + 482 + 470 470 ))) 471 471 472 472 (((