Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 92.1
edited by Edwin Chen
on 2025/01/29 20:30
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
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.ting
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  
... ... @@ -193,13 +193,7 @@
193 193  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
194 194  
195 195  (((
196 -Depends on Class A or Class C, the receive windows will be a little difference. The main difference between Class A and Class C:
197 -
198 -* **Class A** : Suitable for Battery powered end node. Class A will save a lot of power but it can only receive downlink after each uplink
199 -* **Class C**: End node can receive downlink immediately but have higher power consumption.
200 -
201 -
202 -
196 +Depends on Class A or Class C, the receive windows will be a little difference.
203 203  )))
204 204  
205 205  [[image:image-20220531161828-1.png]]
... ... @@ -219,6 +219,7 @@
219 219  
220 220  * 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.**
221 221  
216 +
222 222  == 5.2 See Debug Info ==
223 223  
224 224  
... ... @@ -232,26 +232,23 @@
232 232  
233 233  (((
234 234  Configure a downlink to the end device
235 -
236 -[[image:image-20240129152412-8.png||height="486" width="1206"]]
237 237  )))
238 238  
232 +[[image:image-20240123163307-7.png||height="330" width="1125"]]
239 239  
240 240  (((
241 241  Set a downstream in TTN and see it is sent
242 242  )))
243 243  
244 -(% 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.**
245 245  
246 -
247 247  (((
248 -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
249 249  )))
250 250  
251 -[[image:image-20240129152049-7.png||height="463" width="1166"]]
243 +[[image:image-20220526164650-13.png]]
252 252  
253 253  (((
254 -Gateway Traffic can see this downlink info
246 +Gateway Traffic can see this downstream info
255 255  )))
256 256  
257 257  
... ... @@ -261,10 +261,10 @@
261 261  )))
262 262  
263 263  (((
264 -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:
265 265  )))
266 266  
267 -[[image:image-20240129154321-9.png]]
259 +[[image:image-20220526164734-14.png]]
268 268  
269 269  (((
270 270  Gateway Sent out this packet
... ... @@ -341,7 +341,7 @@
341 341  
342 342  
343 343  (((
344 -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.
345 345  )))
346 346  
347 347  (((
... ... @@ -366,73 +366,52 @@
366 366  = 7. Decrypt a LoRaWAN Packet =
367 367  
368 368  
369 -(% style="color:blue" %)**1. LHT65N End device configure:**
361 +(% style="color:blue" %)**1. LHT65 End device configure:**
370 370  
371 371  **Change to ABP Mode:  AT+NJM=0**
372 372  
373 -**Change to fix frequency:  ​​​​AT+CHE=1**
365 +**Change to fix frequency:  AT+CHS=904900000**
374 374  
367 +**Change to fix DR:  AT+DR=0**
375 375  
376 -**AT+CFG(Print configuration):**
377 377  
378 -[[image:image-20240129170603-7.png||height="697" width="545"]][[image:image-20240129163741-3.png||height="694" width="565"]]
370 +[[image:image-20220526165525-16.png]]
379 379  
380 380  
381 381  
382 -**Configuration: **
374 +(% style="color:blue" %)**2. In LG02 , configure to receive above message**
383 383  
384 -[[image:image-20240129164219-4.png||height="612" width="440"]]
376 +[[image:image-20220526165612-17.png]]
385 385  
386 386  
379 +In LG02 console, we can see the hex receive are:
387 387  
388 -(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
381 +[[image:image-20220526171112-21.png]]
389 389  
390 -[[image:image-20240129164326-5.png||height="506" width="1114"]]
391 391  
392 392  
393 -In LPS8-v2 console, we can see the Base64 receive are:
385 +(% style="color:blue" %)**3. Decode the info in web**
394 394  
395 -[[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/]]
396 396  
389 +Need these three fields:
397 397  
391 +LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
398 398  
399 -(% style="color:blue" %)**3. Decode the info in CMD(Command prompt window)**
393 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
400 400  
401 -LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 **(from LPS8-v2)**
395 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
402 402  
403 -Then the instructions and format parsed in SecureCRT are:  ./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75
404 404  
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]]
405 405  
406 -**Step1: Open CMD, Enter the gateway IP and port.(ssh root@gateway IP -p 22)**
400 +[[image:image-20220526171029-20.png]]
407 407  
408 -[[image:image-20240129190752-17.png||height="338" width="901"]]
402 +(((
403 + The FRMPayload is the device payload.
404 +)))
409 409  
410 -[[image:image-20240129191937-21.png||height="450" width="901"]]
411 411  
412 -
413 -**Step2: Enter the command to download the LoRa parsing package.(npm install lora-packet)**
414 -
415 -[[image:image-20240129192239-22.png||height="416" width="902"]]
416 -
417 -[[image:image-20240129192549-23.png||height="459" width="898"]]
418 -
419 -
420 -**Step3: Parse the gateway raw payload.(./node_modules/.bin/lora-packet-decode ~-~-base64 QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75)**
421 -
422 -
423 -
424 -
425 -[[image:image-20240129192908-24.png||height="477" width="907"]]
426 -
427 -
428 -[[image:image-20240129192954-25.png||height="485" width="916"]]
429 -
430 -
431 -
432 -
433 -
434 -
435 -
436 436  = 8. Why I see uplink 0x00 periodically on the LHT65 v1.8 firmware =
437 437  
438 438  
... ... @@ -477,7 +477,7 @@
477 477  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
478 478  
479 479  
480 -= 10. Why I got the payload only with "0x00" or "AA~=~="? =
451 += 10. Why i got the payload only with "0x00" or "AA~=~="? =
481 481  
482 482  
483 483  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -572,7 +572,7 @@
572 572  (Any combination of 16 bit codes can be used）
573 573  
574 574  
575 -= 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? =
576 576  )))
577 577  
578 578  
... ... @@ -603,3 +603,6 @@
603 603  
604 604  
605 605  [[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
image-20240129190752-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -39.9 KB
Content
image-20240129190840-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -17.2 KB
Content
image-20240129191130-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -81.7 KB
Content
image-20240129191315-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -50.0 KB
Content
image-20240129191937-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -71.8 KB
Content
image-20240129192239-22.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -77.5 KB
Content
image-20240129192549-23.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -59.5 KB
Content
image-20240129192908-24.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -101.7 KB
Content
image-20240129192954-25.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.ting
Size
... ... @@ -1,1 +1,0 @@
1 -62.4 KB
Content

Applications

Navigation

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