Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.14 >
edited by Xiaoling
on 2022/07/13 15:24
To version < 32.5 >
edited by Xiaoling
on 2022/07/13 15:02
>
Change comment: There is no comment for this version

Summary

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

Applications

Navigation

Copyright ©2010-2024 Dragino Technology Co., LTD. All rights reserved
Dragino Wiki v2.0