Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 53.1 >
edited by Mengting Qiu
on 2024/01/29 14:21
To version < 63.1 >
edited by Mengting Qiu
on 2024/01/29 15:50
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -26,7 +26,7 @@
26 26  
27 27  * What frequency the device is sending?
28 28  
29 -[[image:image-20240123182345-1.png||height="605" width="946"]]
29 +[[image:image-20240129142147-2.png||height="736" width="964"]]
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-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  
... ... @@ -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-20220526163633-3.png]]
53 +[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
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-20240123150720-1.png||height="459" width="1182"]]
62 +[[image:image-20240129142557-3.png||height="488" width="1267"]]
63 63  
64 64  The data for the end device set in server
65 65  
66 66  
67 -[[image:image-20240123150943-2.png||height="556" width="1179"]]
67 +[[image:image-20240129142631-4.png||height="637" width="1256"]]
68 68  
69 69  Check if OTAA Keys match the keys in device.
70 70  
... ... @@ -213,7 +213,6 @@
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 -
217 217  == 5.2 See Debug Info ==
218 218  
219 219  
... ... @@ -227,23 +227,26 @@
227 227  
228 228  (((
229 229  Configure a downlink to the end device
229 +
230 +[[image:image-20240129152412-8.png||height="486" width="1206"]]
230 230  )))
231 231  
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.**
238 238  
240 +
239 239  (((
240 -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.
241 241  )))
242 242  
243 -[[image:image-20220526164650-13.png]]
245 +[[image:image-20240129152049-7.png||height="463" width="1166"]]
244 244  
245 245  (((
246 -Gateway Traffic can see this downstream info
248 +Gateway Traffic can see this downlink info
247 247  )))
248 248  
249 249  
... ... @@ -253,10 +253,10 @@
253 253  )))
254 254  
255 255  (((
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:
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:
257 257  )))
258 258  
259 -[[image:image-20220526164734-14.png]]
261 +[[image:image-20240129154321-9.png]]
260 260  
261 261  (((
262 262  Gateway Sent out this packet
... ... @@ -333,7 +333,7 @@
333 333  
334 334  
335 335  (((
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.
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.
337 337  )))
338 338  
339 339  (((
... ... @@ -448,7 +448,7 @@
448 448  4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
449 449  
450 450  
451 -= 10. Why i got the payload only with "0x00" or "AA~=~="? =
453 += 10. Why I got the payload only with "0x00" or "AA~=~="? =
452 452  
453 453  
454 454  (% style="color:blue" %)**Why sensor sends 0x00?**
... ... @@ -543,7 +543,7 @@
543 543  (Any combination of 16 bit codes can be used）
544 544  
545 545  
546 -= 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? =
547 547  )))
548 548  
549 549  
... ... @@ -575,5 +575,3 @@
575 575  
576 576  [[image:image-20221215223215-1.png||height="584" width="1280"]]
577 577  
578 -(% class="wikigeneratedid" %)
579 -
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

Applications

Navigation

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