Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 81.1 >
edited by Mengting Qiu
on 2024/01/29 19:03
To version < 56.1 >
edited by Mengting Qiu
on 2024/01/29 14:26
>
Change comment: Uploaded new attachment "image-20240129142631-4.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -26,7 +26,7 @@
26 26  
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20240129142147-2.png||height="736" width="964"]]
29 +[[image:image-20240123182345-1.png||height="605" width="946"]]
30 30  
31 31  Console Output from End device to see the transmit frequency.
32 32  
... ... @@ -37,7 +37,7 @@
37 37  
38 38  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
39 39  
40 -[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
40 +[[image:image-20220526163608-2.png]]
41 41  
42 42  Console Output from Gateway to see packets between end node and server.
43 43  
... ... @@ -50,7 +50,7 @@
50 50  
51 51  * If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
52 52  
53 -[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
53 +[[image:image-20220526163633-3.png]]
54 54  
55 55  The Traffic for the End node in the server, use TTN as example.
56 56  
... ... @@ -59,12 +59,12 @@
59 59  
60 60  * 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.
61 61  
62 -[[image:image-20240129142557-3.png||height="488" width="1267"]]
62 +[[image:image-20240123150720-1.png||height="459" width="1182"]]
63 63  
64 64  The data for the end device set in server
65 65  
66 66  
67 -[[image:image-20240129142631-4.png||height="637" width="1256"]]
67 +[[image:image-20240123150943-2.png||height="556" width="1179"]]
68 68  
69 69  Check if OTAA Keys match the keys in device.
70 70  
... ... @@ -213,6 +213,7 @@
213 213  
214 214  * 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.**
215 215  
216 +
216 216  == 5.2 See Debug Info ==
217 217  
218 218  
... ... @@ -226,26 +226,23 @@
226 226  
227 227  (((
228 228  Configure a downlink to the end device
229 -
230 -[[image:image-20240129152412-8.png||height="486" width="1206"]]
231 231  )))
232 232  
232 +[[image:image-20240123163307-7.png||height="330" width="1125"]]
233 233  
234 234  (((
235 235  Set a downstream in TTN and see it is sent
236 236  )))
237 237  
238 -(% style="color:red" %)**Note: After the downlink command is successfully sent from the platform to the node, the downlink command is executed only after the platform receives the next uplink package from the node.**
239 239  
240 -
241 241  (((
242 -This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
240 +This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
243 243  )))
244 244  
245 -[[image:image-20240129152049-7.png||height="463" width="1166"]]
243 +[[image:image-20220526164650-13.png]]
246 246  
247 247  (((
248 -Gateway Traffic can see this downlink info
246 +Gateway Traffic can see this downstream info
249 249  )))
250 250  
251 251  
... ... @@ -255,10 +255,10 @@
255 255  )))
256 256  
257 257  (((
258 -When the downlink packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragino Gateway, this can be checked by running "logread -f" in the SSH console. and see below:
256 +When the downstream packet appear on the traffic of Gateway page. The LoRaWAN gateway can get it from LoRaWAN server and transmit it. In Dragion Gateway, this can be checked by runinng "logread -f" in the SSH console. and see below:
259 259  )))
260 260  
261 -[[image:image-20240129154321-9.png]]
259 +[[image:image-20220526164734-14.png]]
262 262  
263 263  (((
264 264  Gateway Sent out this packet
... ... @@ -335,7 +335,7 @@
335 335  
336 336  
337 337  (((
338 -In LoRaWAN, the gateway 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.
336 +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.
339 339  )))
340 340  
341 341  (((
... ... @@ -360,67 +360,52 @@
360 360  = 7. Decrypt a LoRaWAN Packet =
361 361  
362 362  
363 -(% style="color:blue" %)**1. LHT65N End device configure:**
361 +(% style="color:blue" %)**1. LHT65 End device configure:**
364 364  
365 365  **Change to ABP Mode:  AT+NJM=0**
366 366  
367 -**Change to fix frequency:  ​​​​AT+CHE=1**
365 +**Change to fix frequency:  AT+CHS=904900000**
368 368  
367 +**Change to fix DR:  AT+DR=0**
369 369  
370 -**AT+CFG(Print configuration):**
371 371  
372 -[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
370 +[[image:image-20220526165525-16.png]]
373 373  
374 374  
375 375  
376 -**Configuration: **
374 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
377 377  
378 -[[image:image-20240129164219-4.png||height="612" width="440"]]
376 +[[image:image-20220526165612-17.png]]
379 379  
380 380  
379 +In LG02 console, we can see the hex receive are:
381 381  
382 -(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
381 +[[image:image-20220526171112-21.png]]
383 383  
384 -[[image:image-20240129164326-5.png||height="506" width="1114"]]
385 385  
386 386  
387 -In LPS8-v2 console, we can see the Base64 receive are:
385 +(% style="color:blue" %)**3. Decode the info in web**
388 388  
389 -[[image:image-20240129170137-6.png||height="459" width="1116"]]
387 +[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
390 390  
389 +Need these three fields:
391 391  
391 +LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
392 392  
393 -(% style="color:blue" %)**3. Decode the info in SecureCRT**
393 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
394 394  
395 -[[SecureCRT - The rock-solid Telnet and SSH client for Windows, Mac, and Linux (vandyke.com)>>url:https://www.vandyke.com/products/securecrt/]]
395 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
396 396  
397 -LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 (from LPS8-v2)
398 398  
399 -Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
398 +[[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]]
400 400  
400 +[[image:image-20220526171029-20.png]]
401 401  
402 -**Step1: In the SecureCRT access gateway control interface, enter the command to download the parsing package: npm install lora-packet.**
402 +(((
403 + The FRMPayload is the device payload.
404 +)))
403 403  
404 -[[image:image-20240129173810-9.png||height="389" width="1070"]]
405 405  
406 -[[image:image-20240129173932-10.png||height="350" width="1084"]]
407 -
408 -[[image:image-20240129174125-11.png||height="338" width="1078"]]
409 -
410 -
411 -**Step2: Parse the raw data from the gateway.**
412 -
413 -[[image:image-20240129174948-14.png]]
414 -
415 -
416 -[[image:image-20240129175037-15.png||height="619" width="1144"]]
417 -
418 -
419 -
420 -
421 -
422 -
423 -
424 424  = 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
425 425  
426 426  
... ... @@ -465,7 +465,7 @@
465 465  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
466 466  
467 467  
468 -= 10. Why I got the payload only with "0x00" or "AA~=~="? =
451 += 10. Why i got the payload only with "0x00" or "AA~=~="? =
469 469  
470 470  
471 471  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -560,7 +560,7 @@
560 560  (Any combination of 16 bit codes can be used）
561 561  
562 562  
563 -= 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
546 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
564 564  )))
565 565  
566 566  
... ... @@ -591,3 +591,6 @@
591 591  
592 592  
593 593  [[image:image-20221215223215-1.png||height="584" width="1280"]]
577 +
578 +(% class="wikigeneratedid" %)
579 +
image-20240129150821-5.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -129.2 KB
Content
image-20240129151608-6.jpeg
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -318.1 KB
Content
image-20240129152049-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -148.3 KB
Content
image-20240129152412-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -74.1 KB
Content
image-20240129173932-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -73.6 KB
Content
image-20240129174125-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -77.0 KB
Content
image-20240129174549-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.6 KB
Content
image-20240129174717-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.6 KB
Content
image-20240129174948-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.1 KB
Content
image-20240129175037-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -85.8 KB
Content
image-20240129190344-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content

Applications

Navigation

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