Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 51.1 >
edited by Mengting Qiu
on 2024/01/23 18:23
To version < 73.1 >
edited by Mengting Qiu
on 2024/01/29 17:38
>
Change comment: Uploaded new attachment "image-20240129173810-9.png", version {1}

Summary

Details

Page properties
Content
... ... @@ -4,8 +4,9 @@
4 4  
5 5  
6 6  
7 -= 1.Join process page check =
7 += 1. Join process page check =
8 8  
9 +
9 9  These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
10 10  \\**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:**
11 11  
... ... @@ -25,12 +25,11 @@
25 25  
26 26  * What frequency the device is sending?
27 27  
28 -[[image:image-20220526164956-15.png||height="591" width="1153"]]
29 +[[image:image-20240129142147-2.png||height="736" width="964"]]
29 29  
30 -Console Output from End device to see the transmit frequency
31 +Console Output from End device to see the transmit frequency.
31 31  
32 32  
33 -
34 34  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
35 35  
36 36  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
... ... @@ -37,12 +37,11 @@
37 37  
38 38  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
39 39  
40 -[[image:image-20220526163608-2.png]]
40 +[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
41 41  
42 42  Console Output from Gateway to see packets between end node and server.
43 43  
44 44  
45 -
46 46  (% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
47 47  
48 48  * Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
... ... @@ -51,22 +51,21 @@
51 51  
52 52  * 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.
53 53  
54 -[[image:image-20220526163633-3.png]]
53 +[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
55 55  
56 56  The Traffic for the End node in the server, use TTN as example.
57 57  
58 58  
59 -
60 60  (% style="color:blue" %)**4. Data Page in LoRaWAN server**
61 61  
62 62  * 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.
63 63  
64 -[[image:image-20240123150720-1.png||height="459" width="1182"]]
62 +[[image:image-20240129142557-3.png||height="488" width="1267"]]
65 65  
66 66  The data for the end device set in server
67 67  
68 68  
69 -[[image:image-20240123150943-2.png||height="556" width="1179"]]
67 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
70 70  
71 71  Check if OTAA Keys match the keys in device.
72 72  
... ... @@ -215,8 +215,6 @@
215 215  
216 216  * 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.**
217 217  
218 -== ==
219 -
220 220  == 5.2 See Debug Info ==
221 221  
222 222  
... ... @@ -230,23 +230,26 @@
230 230  
231 231  (((
232 232  Configure a downlink to the end device
229 +
230 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
233 233  )))
234 234  
235 -[[image:image-20240123163307-7.png||height="330" width="1125"]]
236 236  
237 237  (((
238 238  Set a downstream in TTN and see it is sent
239 239  )))
240 240  
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.**
241 241  
240 +
242 242  (((
243 -This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
242 +This downlink info will then pass to the gateway downlink list. and the DR which is used (SF7BW500) in US915 is DR5.
244 244  )))
245 245  
246 -[[image:image-20220526164650-13.png]]
245 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
247 247  
248 248  (((
249 -Gateway Traffic can see this downstream info
248 +Gateway Traffic can see this downlink info
250 250  )))
251 251  
252 252  
... ... @@ -256,10 +256,10 @@
256 256  )))
257 257  
258 258  (((
259 -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:
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:
260 260  )))
261 261  
262 -[[image:image-20220526164734-14.png]]
261 +[[image:image-20240129154321-9.png]]
263 263  
264 264  (((
265 265  Gateway Sent out this packet
... ... @@ -336,7 +336,7 @@
336 336  
337 337  
338 338  (((
339 -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.
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.
340 340  )))
341 341  
342 342  (((
... ... @@ -361,45 +361,47 @@
361 361  = 7. Decrypt a LoRaWAN Packet =
362 362  
363 363  
364 -(% style="color:blue" %)**1. LHT65 End device configure:**
363 +(% style="color:blue" %)**1. LHT65N End device configure:**
365 365  
366 366  **Change to ABP Mode:  AT+NJM=0**
367 367  
368 -**Change to fix frequency:  AT+CHS=904900000**
367 +**Change to fix frequency:  ​​​​AT+CHE=1**
369 369  
370 -**Change to fix DR:  AT+DR=0**
371 371  
370 +**AT+CFG(Print configuration):**
372 372  
373 -[[image:image-20220526165525-16.png]]
372 +[[image:image-20240129163714-2.png]][[image:image-20240129163741-3.png]]
374 374  
375 375  
376 376  
377 -(% style="color:blue" %)**2. In LG02 , configure to receive above message**
376 +**Configuration: **
378 378  
379 -[[image:image-20220526165612-17.png]]
378 +[[image:image-20240129164219-4.png||height="612" width="440"]]
380 380  
381 381  
382 -In LG02 console, we can see the hex receive are:
383 383  
384 -[[image:image-20220526171112-21.png]]
382 +(% style="color:blue" %)**2. In LPS8-v2, configure to receive above message**
385 385  
384 +[[image:image-20240129164326-5.png||height="506" width="1114"]]
386 386  
387 387  
388 -(% style="color:blue" %)**3. Decode the info in web**
387 +In LPS8-v2 console, we can see the Base64 receive are:
389 389  
390 -[[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
389 +[[image:image-20240129170137-6.png||height="459" width="1116"]]
391 391  
392 -Need these three fields:
393 393  
394 -LoRa packet hex format: 40c1190126800100024926272bf18bbb6341584e27e23245 (from LG02)
395 395  
396 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End node Network Session Key)
393 +(% style="color:blue" %)**3. Decode the info **
397 397  
398 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 01 11 (End Node App Session Key)
395 +Need these three fields:
399 399  
397 +LoRa packet Base64 format:  QP~/~/~/~/+AFQACZv8Hjmc8gFTAkhMzU+75 (from LPS8-v2)
400 400  
401 -[[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]]
399 +AT+NWKSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF (End node Network Session Key)
402 402  
401 +AT+APPSKEY=FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF FF (End Node App Session Key)
402 +
403 +
403 403  [[image:image-20220526171029-20.png]]
404 404  
405 405  (((
... ... @@ -451,7 +451,7 @@
451 451  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
452 452  
453 453  
454 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
455 += 10. Why I got the payload only with "0x00" or "AA~=~="? =
455 455  
456 456  
457 457  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -546,7 +546,7 @@
546 546  (Any combination of 16 bit codes can be used）
547 547  
548 548  
549 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
550 += 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
550 550  )))
551 551  
552 552  
... ... @@ -577,6 +577,3 @@
577 577  
578 578  
579 579  [[image:image-20221215223215-1.png||height="584" width="1280"]]
580 -
581 -(% class="wikigeneratedid" %)
582 -
image-20240129142110-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +126.9 KB
Content
image-20240129142147-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +116.1 KB
Content
image-20240129142557-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +125.7 KB
Content
image-20240129142631-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +189.0 KB
Content
image-20240129150821-5.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +129.2 KB
Content
image-20240129151608-6.jpeg
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +318.1 KB
Content
image-20240129152049-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +148.3 KB
Content
image-20240129152412-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +133.6 KB
Content
image-20240129154321-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +99.5 KB
Content
image-20240129163533-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +23.0 KB
Content
image-20240129163714-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129163741-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +36.5 KB
Content
image-20240129164219-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +30.3 KB
Content
image-20240129164326-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +80.8 KB
Content
image-20240129170137-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +115.2 KB
Content
image-20240129170603-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +39.2 KB
Content
image-20240129172956-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +54.2 KB
Content
image-20240129173810-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.ting
Size
... ... @@ -1,0 +1,1 @@
1 +74.1 KB
Content

Applications

Navigation

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