Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 52.1 >
edited by Mengting Qiu
on 2024/01/23 18:24
To version < 66.1 >
edited by Mengting Qiu
on 2024/01/29 16:37
>
Change comment: Uploaded new attachment "image-20240129163741-3.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,13 +25,11 @@
25 25  
26 26  * What frequency the device is sending?
27 27  
28 -[[image:image-20240123182345-1.png||height="605" width="946"]]
29 +[[image:image-20240129142147-2.png||height="736" width="964"]]
29 29  
30 -
31 31  Console Output from End device to see the transmit frequency.
32 32  
33 33  
34 -
35 35  (% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
36 36  
37 37  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
... ... @@ -38,12 +38,11 @@
38 38  
39 39  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
40 40  
41 -[[image:image-20220526163608-2.png]]
40 +[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
42 42  
43 43  Console Output from Gateway to see packets between end node and server.
44 44  
45 45  
46 -
47 47  (% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
48 48  
49 49  * Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
... ... @@ -52,22 +52,21 @@
52 52  
53 53  * 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.
54 54  
55 -[[image:image-20220526163633-3.png]]
53 +[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
56 56  
57 57  The Traffic for the End node in the server, use TTN as example.
58 58  
59 59  
60 -
61 61  (% style="color:blue" %)**4. Data Page in LoRaWAN server**
62 62  
63 63  * 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.
64 64  
65 -[[image:image-20240123150720-1.png||height="459" width="1182"]]
62 +[[image:image-20240129142557-3.png||height="488" width="1267"]]
66 66  
67 67  The data for the end device set in server
68 68  
69 69  
70 -[[image:image-20240123150943-2.png||height="556" width="1179"]]
67 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
71 71  
72 72  Check if OTAA Keys match the keys in device.
73 73  
... ... @@ -216,8 +216,6 @@
216 216  
217 217  * 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.**
218 218  
219 -== ==
220 -
221 221  == 5.2 See Debug Info ==
222 222  
223 223  
... ... @@ -231,23 +231,26 @@
231 231  
232 232  (((
233 233  Configure a downlink to the end device
229 +
230 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
234 234  )))
235 235  
236 -[[image:image-20240123163307-7.png||height="330" width="1125"]]
237 237  
238 238  (((
239 239  Set a downstream in TTN and see it is sent
240 240  )))
241 241  
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.**
242 242  
240 +
243 243  (((
244 -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.
245 245  )))
246 246  
247 -[[image:image-20220526164650-13.png]]
245 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
248 248  
249 249  (((
250 -Gateway Traffic can see this downstream info
248 +Gateway Traffic can see this downlink info
251 251  )))
252 252  
253 253  
... ... @@ -257,10 +257,10 @@
257 257  )))
258 258  
259 259  (((
260 -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:
261 261  )))
262 262  
263 -[[image:image-20220526164734-14.png]]
261 +[[image:image-20240129154321-9.png]]
264 264  
265 265  (((
266 266  Gateway Sent out this packet
... ... @@ -337,7 +337,7 @@
337 337  
338 338  
339 339  (((
340 -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.
341 341  )))
342 342  
343 343  (((
... ... @@ -452,7 +452,7 @@
452 452  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
453 453  
454 454  
455 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
453 += 10. Why I got the payload only with "0x00" or "AA~=~="? =
456 456  
457 457  
458 458  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -547,7 +547,7 @@
547 547  (Any combination of 16 bit codes can be used）
548 548  
549 549  
550 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
548 += 12. I set my device is LoRaWAN Class C mode, why I still see Class A after boot? =
551 551  )))
552 552  
553 553  
... ... @@ -579,5 +579,3 @@
579 579  
580 580  [[image:image-20221215223215-1.png||height="584" width="1280"]]
581 581  
582 -(% class="wikigeneratedid" %)
583 -
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

Applications

Navigation

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