Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 4.13 >
edited by Xiaoling
on 2022/05/11 15:28
To version < 22.2 >
edited by Xiaoling
on 2022/05/26 16:48
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,5 +1,9 @@
1 1  **~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
... ... @@ -19,7 +19,7 @@
19 19  * If the device is sending join request to server?
20 20  * What frequency the device is sending?
21 21  
22 -[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
26 +[[image:image-20220526163523-1.png]]
23 23  
24 24  Console Output from End device to see the transmit frequency
25 25  
... ... @@ -29,7 +29,7 @@
29 29  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
30 30  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
31 31  
32 -[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
36 +[[image:image-20220526163608-2.png]]
33 33  
34 34  Console Output from Gateway to see packets between end node and server.
35 35  
... ... @@ -40,7 +40,7 @@
40 40  * If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
41 41  * 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.
42 42  
43 -[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
47 +[[image:image-20220526163633-3.png]]
44 44  
45 45  The Traffic for the End node in the server, use TTN as example
46 46  
... ... @@ -49,11 +49,11 @@
49 49  
50 50  * 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.
51 51  
52 -[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
56 +[[image:image-20220526163704-4.png]]
53 53  
54 54  The data for the end device set in server
55 55  
56 -[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
60 +[[image:image-20220526163732-5.png]]
57 57  
58 58  Check if OTAA Keys match the keys in device
59 59  
... ... @@ -94,15 +94,15 @@
94 94  Here are the freuqency tables for these bands as reference:
95 95  )))
96 96  
97 -[[image:https://wiki.dragino.com/images/thumb/3/3f/US915_FRE_BAND-1.png/600px-US915_FRE_BAND-1.png||height="170" width="600"]]
101 +[[image:image-20220526163801-6.png]]
98 98  
99 99  US915 Channels
100 100  
101 -[[image:https://wiki.dragino.com/images/thumb/8/8a/AU915_FRE_BAND-1.png/600px-AU915_FRE_BAND-1.png||height="167" width="600"]]
105 +[[image:image-20220526163926-7.png]]
102 102  
103 103  AU915 Channels
104 104  
105 -[[image:https://wiki.dragino.com/images/thumb/3/3a/CN470_FRE_BAND-1.png/600px-CN470_FRE_BAND-1.png||height="205" width="600"]]
109 +[[image:image-20220526163941-8.png]]
106 106  
107 107  (((
108 108  CN470 Channels
... ... @@ -112,7 +112,7 @@
112 112  If we look at the [[TTN network server frequency plan>>url:https://www.thethingsnetwork.org/docs/lorawan/frequency-plans.html]], we can see the US915 frequency band use the channel 8~~15.So the End Node must work at the same frequency in US915 8~~15 channels for TTN server.
113 113  )))
114 114  
115 -[[image:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
119 +[[image:image-20220526164052-9.png]]
116 116  
117 117  (((
118 118  TTN FREQUENCY PLAN
... ... @@ -166,7 +166,7 @@
166 166  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
167 167  )))
168 168  
169 -[[~[~[image:https://wiki.dragino.com/images/thumb/1/19/ABP_Issue-1.jpg/600px-ABP_Issue-1.jpg~|~|height="340" width="600"~]~]>>url:https://wiki.dragino.com/index.php/File:ABP_Issue-1.jpg]]
173 +[[image:image-20220526164508-10.png]]
170 170  
171 171  Disable Frame Counter Check in ABP Mode
172 172  
... ... @@ -181,7 +181,7 @@
181 181  Depends on Class A or Class C, the receive windows will be a little difference,
182 182  )))
183 183  
184 -[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
188 +[[image:image-20220526164547-11.png]]
185 185  
186 186  receive windows for Class A and Class C
187 187  
... ... @@ -193,6 +193,7 @@
193 193  * This packet must match the frequency of the RX1 or RX2 window.
194 194  * This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **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.**
195 195  
200 +
196 196  == 5.2 See Debug Info ==
197 197  
198 198  (((
... ... @@ -207,7 +207,7 @@
207 207  Configure a downstream to the end device
208 208  )))
209 209  
210 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
215 +[[image:image-20220526164623-12.png]]
211 211  
212 212  (((
213 213  Set a downstream in TTN and see it is sent
... ... @@ -218,7 +218,7 @@
218 218  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
219 219  )))
220 220  
221 -[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
226 +[[image:image-20220526164650-13.png]]
222 222  
223 223  (((
224 224  Gateway Traffic can see this downstream info
... ... @@ -233,7 +233,7 @@
233 233  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:
234 234  )))
235 235  
236 -[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
241 +[[image:image-20220526164734-14.png]]
237 237  
238 238  (((
239 239  Gateway Sent out this packet
... ... @@ -293,6 +293,9 @@
293 293   Receive data
294 294   1:0012345678}}}
295 295  
301 +(% class="wikigeneratedid" %)
302 +​​​​​​​
303 +
296 296  == 5.3 If problem doesn’t solve ==
297 297  
298 298  **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:**
... ... @@ -405,6 +405,8 @@
405 405  
406 406  * (((
407 407  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
416 +
417 +
408 408  )))
409 409  
410 410  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
... ... @@ -412,27 +412,52 @@
412 412  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
413 413  
414 414  (((
415 - When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
425 +When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
416 416  )))
417 417  
418 418  (((
419 - When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,
429 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet.
420 420  )))
421 421  
422 -(((
423 - and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,
424 -)))
425 -
426 -(((
427 - so it will send a normal uplink packet, and an additional 00 data packet.
428 -)))
429 -
430 430  * (((
431 431  Solution: Use the decoder to filter out this 00 packet.
432 432  )))
433 433  * (((
434 -Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to david.huang@dragino.cc
436 +Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
437 +
438 +
439 +
435 435  )))
436 436  
437 -(% class="wikigeneratedid" id="H" %)
442 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
443 +
444 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
445 +
446 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
447 +
448 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449 +
450 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
451 +
452 +AT+APPEUI=00 00 00 00 00 00 00 00
453 +
454 +
455 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
456 +
457 +You can rewrites the keys by running commands in AT Console
458 +
459 +For example：
460 +
461 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
462 +
463 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
464 +
465 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
466 +
467 +AT+APPEUI=2C 45 47 E3 24 12 23 24
468 +
469 +(Any combination of 16 bit codes can be used）
470 +
471 +
472 +(% class="wikigeneratedid" %)
438 438  
image-20220526163523-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +120.3 KB
Content

Applications

Navigation

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