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

Summary

Details

Page properties
Content
... ... @@ -1,9 +1,5 @@
1 1  **~ Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
... ... @@ -23,7 +23,7 @@
23 23  * If the device is sending join request to server?
24 24  * What frequency the device is sending?
25 25  
26 -[[image:image-20220526164956-15.png]]
22 +[[image:https://wiki.dragino.com/images/thumb/0/0f/OTAA_Join-1.jpg/600px-OTAA_Join-1.jpg||height="316" width="600"]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -33,7 +33,7 @@
33 33  * If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
34 34  * If the gateway gets the Join Accept message from server and transmit it via LoRa?
35 35  
36 -[[image:image-20220526163608-2.png]]
32 +[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
37 37  
38 38  Console Output from Gateway to see packets between end node and server.
39 39  
... ... @@ -44,7 +44,7 @@
44 44  * 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.
45 45  * 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.
46 46  
47 -[[image:image-20220526163633-3.png]]
43 +[[image:https://wiki.dragino.com/images/thumb/5/5c/OTAA_Join-3.png/600px-OTAA_Join-3.png||height="301" width="600"]]
48 48  
49 49  The Traffic for the End node in the server, use TTN as example
50 50  
... ... @@ -53,11 +53,11 @@
53 53  
54 54  * 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.
55 55  
56 -[[image:image-20220526163704-4.png]]
52 +[[image:https://wiki.dragino.com/images/thumb/e/ec/OTAA_Join-4.png/600px-OTAA_Join-4.png||height="181" width="600"]]
57 57  
58 58  The data for the end device set in server
59 59  
60 -[[image:image-20220526163732-5.png]]
56 +[[image:https://wiki.dragino.com/images/thumb/b/b1/OTAA_Join-5.png/600px-OTAA_Join-5.png||height="166" width="600"]]
61 61  
62 62  Check if OTAA Keys match the keys in device
63 63  
... ... @@ -98,15 +98,15 @@
98 98  Here are the freuqency tables for these bands as reference:
99 99  )))
100 100  
101 -[[image:image-20220526163801-6.png]]
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"]]
102 102  
103 103  US915 Channels
104 104  
105 -[[image:image-20220526163926-7.png]]
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"]]
106 106  
107 107  AU915 Channels
108 108  
109 -[[image:image-20220526163941-8.png]]
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"]]
110 110  
111 111  (((
112 112  CN470 Channels
... ... @@ -116,7 +116,7 @@
116 116  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.
117 117  )))
118 118  
119 -[[image:image-20220526164052-9.png]]
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"]]
120 120  
121 121  (((
122 122  TTN FREQUENCY PLAN
... ... @@ -170,7 +170,7 @@
170 170  To solve this, disable the Frame Counter Check will solve this issue , or reset the frame counter in the device page.
171 171  )))
172 172  
173 -[[image:image-20220526164508-10.png]]
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]]
174 174  
175 175  Disable Frame Counter Check in ABP Mode
176 176  
... ... @@ -185,7 +185,7 @@
185 185  Depends on Class A or Class C, the receive windows will be a little difference,
186 186  )))
187 187  
188 -[[image:image-20220526164547-11.png]]
184 +[[image:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
... ... @@ -211,7 +211,7 @@
211 211  Configure a downstream to the end device
212 212  )))
213 213  
214 -[[image:image-20220526164623-12.png]]
210 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
215 215  
216 216  (((
217 217  Set a downstream in TTN and see it is sent
... ... @@ -222,7 +222,7 @@
222 222  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
223 223  )))
224 224  
225 -[[image:image-20220526164650-13.png]]
221 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
226 226  
227 227  (((
228 228  Gateway Traffic can see this downstream info
... ... @@ -237,7 +237,7 @@
237 237  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:
238 238  )))
239 239  
240 -[[image:image-20220526164734-14.png]]
236 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
241 241  
242 242  (((
243 243  Gateway Sent out this packet
... ... @@ -297,10 +297,9 @@
297 297   Receive data
298 298   1:0012345678}}}
299 299  
300 -
301 301  == 5.3 If problem doesn’t solve ==
302 302  
303 -(% style="color:red" %)**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:**
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:**
304 304  
305 305  * End node console to show the transmit freuqency and DR.
306 306  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -410,8 +410,6 @@
410 410  
411 411  * (((
412 412  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
413 -
414 -
415 415  )))
416 416  
417 417  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
... ... @@ -419,50 +419,27 @@
419 419  * If you are using US915, AU915 and AS923 frequencies.This is normal phenomenon.
420 420  
421 421  (((
422 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
415 + When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate.
423 423  )))
424 424  
425 425  (((
426 -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.
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,
427 427  )))
428 428  
422 +(((
423 + 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
424 +)))
425 +
426 +(((
427 + uplink packet, and an additional 00 data packet.
428 +)))
429 +
429 429  * (((
430 430  Solution: Use the decoder to filter out this 00 packet.
431 431  )))
432 432  * (((
433 -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]]
434 -
435 -
436 -
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
437 437  )))
438 438  
439 -= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
440 -
441 -It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
442 -
443 -AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
444 -
445 -AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
446 -
447 -AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
448 -
449 -AT+APPEUI=00 00 00 00 00 00 00 00
450 -
451 -
452 -You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
453 -
454 -You can rewrites the keys by running commands in AT Console
455 -
456 -For example：
457 -
458 -AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
459 -
460 -AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
461 -
462 -AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
463 -
464 -AT+APPEUI=2C 45 47 E3 24 12 23 24
465 -
466 -(Any combination of 16 bit codes can be used）
467 -
468 -
437 +(% class="wikigeneratedid" id="H" %)
438 +
image-20220526163523-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -633.8 KB
Content
image-20220526163608-2.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.4 KB
Content
image-20220526163633-3.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -65.6 KB
Content
image-20220526163704-4.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -78.8 KB
Content
image-20220526163732-5.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -18.5 KB
Content
image-20220526163801-6.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.3 KB
Content
image-20220526163926-7.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -19.4 KB
Content
image-20220526163941-8.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -27.9 KB
Content
image-20220526164052-9.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -59.3 KB
Content
image-20220526164508-10.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -50.2 KB
Content
image-20220526164547-11.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.9 KB
Content
image-20220526164623-12.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -22.2 KB
Content
image-20220526164650-13.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -45.0 KB
Content
image-20220526164734-14.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -120.3 KB
Content
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content

Applications

Navigation

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