Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 4.18 >
edited by Xiaoling
on 2022/05/11 15:35
To version < 32.3 >
edited by Xiaoling
on 2022/07/13 14:59
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,10 +1,12 @@
1 -**~ Contents:**
1 +**~ Table of Contents:**
2 2  
3 3  {{toc/}}
4 4  
5 5  
6 +
6 6  = 1. OTAA Join Process Debug =
7 7  
9 +
8 8  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.
9 9  \\**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:**
10 10  
... ... @@ -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"]]
24 +[[image:image-20220526164956-15.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"]]
34 +[[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"]]
45 +[[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"]]
54 +[[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"]]
58 +[[image:image-20220526163732-5.png]]
57 57  
58 58  Check if OTAA Keys match the keys in device
59 59  
... ... @@ -60,6 +60,7 @@
60 60  
61 61  = 2. Notice of US915/CN470/AU915 Frequency band =
62 62  
65 +
63 63  (((
64 64  If user has problem to work with lorawan server in band US915/AU915/CN470, he can check:
65 65  )))
... ... @@ -94,18 +94,21 @@
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"]]
100 +[[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"]]
104 +[[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"]]
106 106  
109 +[[image:image-20220526163941-8.png]]
110 +
107 107  (((
108 108  CN470 Channels
113 +
114 +
109 109  )))
110 110  
111 111  (((
... ... @@ -112,10 +112,12 @@
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"]]
121 +[[image:image-20220526164052-9.png]]
116 116  
117 117  (((
118 118  TTN FREQUENCY PLAN
125 +
126 +
119 119  )))
120 120  
121 121  (((
... ... @@ -125,6 +125,7 @@
125 125  
126 126  = 3. Why i see data lost/unperiocially uplink data? Even the signal strength is good =
127 127  
136 +
128 128  In this case, we can check if the frequency band matches in End Node, Gateway and LoRaWAN server. A typical case is using US915 in ChirpStack server as below:
129 129  
130 130  * **End node** ~-~-> Use Sub-band2 (Channel 8,9,10,11,12,13,14,15) for Dragino Sensor. ADR is also enable, this is the default settings for dragino sensors.
... ... @@ -146,6 +146,7 @@
146 146  
147 147  = 4. Transmision on ABP Mode =
148 148  
158 +
149 149  (((
150 150  In ABP mode, there is a Frame Counter Checks. With this check enabled, the server will only accept the frame with a higher counter. If you reboot the device in ABP mode, the device will start from count 0, so you won't be able to see the frame update in server.
151 151  )))
... ... @@ -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]]
179 +[[image:image-20220526164508-10.png]]
170 170  
171 171  Disable Frame Counter Check in ABP Mode
172 172  
... ... @@ -175,6 +175,7 @@
175 175  
176 176  == 5.1 How it work ==
177 177  
188 +
178 178  LoRaWAN End node will open two receive windows to receive the downstream data. If the downstream packets arrive the end node at these receive windows, the end node will be able to get this packet and process it.
179 179  
180 180  (((
... ... @@ -181,10 +181,11 @@
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"]]
195 +[[image:image-20220531161828-1.png]]
185 185  
186 186  receive windows for Class A and Class C
187 187  
199 +
188 188  Below are the requirement for the End Device to receive the packets.
189 189  
190 190  * The End Device must open the receive windows: RX1 or RX2
... ... @@ -191,12 +191,14 @@
191 191  * The LoRaWAN server must send a downstream packet, and the gateway forward this downstream packet for this end node.
192 192  * This downstream packet must arrive to the end node while RX1 or RX2 is open.
193 193  * This packet must match the frequency of the RX1 or RX2 window.
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.**
206 +* 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.**
195 195  
208 +
196 196  == 5.2 See Debug Info ==
197 197  
211 +
198 198  (((
199 -**For LoRaWAN Server**
213 +(% style="color:blue" %)**For LoRaWAN Server**
200 200  )))
201 201  
202 202  (((
... ... @@ -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"]]
224 +[[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"]]
235 +[[image:image-20220526164650-13.png]]
222 222  
223 223  (((
224 224  Gateway Traffic can see this downstream info
... ... @@ -226,7 +226,7 @@
226 226  
227 227  
228 228  (((
229 -**For LoRaWAN Gateway**
243 +(% style="color:blue" %)**For LoRaWAN Gateway**
230 230  )))
231 231  
232 232  (((
... ... @@ -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"]]
250 +[[image:image-20220526164734-14.png]]
237 237  
238 238  (((
239 239  Gateway Sent out this packet
... ... @@ -241,7 +241,7 @@
241 241  
242 242  
243 243  (((
244 -**For End Node**
258 +(% style="color:blue" %)**For End Node**
245 245  )))
246 246  
247 247  (((
... ... @@ -263,7 +263,7 @@
263 263  )))
264 264  
265 265  (((
266 -**when the device running, we can see below info:**
280 +(% style="color:blue" %)**when the device running, we can see below info:**
267 267  )))
268 268  
269 269  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -279,7 +279,7 @@
279 279  )))
280 280  
281 281  (((
282 -**Another message:**
296 +(% style="color:blue" %)**Another message:**
283 283  )))
284 284  
285 285  {{{ [12502]***** UpLinkCounter= 0 *****
... ... @@ -293,9 +293,10 @@
293 293   Receive data
294 294   1:0012345678}}}
295 295  
310 +
296 296  == 5.3 If problem doesn’t solve ==
297 297  
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:**
313 +(% 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:**
299 299  
300 300  * End node console to show the transmit freuqency and DR.
301 301  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -333,29 +333,24 @@
333 333  
334 334  (% class="box infomessage" %)
335 335  (((
336 -Change to ABP Mode: AT+NJM=0
351 +**Change to ABP Mode: AT+NJM=0**
352 +**Change to fix frequency: AT+CHS=904900000**
353 +**Change to fix DR: AT+DR=0**
337 337  )))
338 338  
339 -(% class="box infomessage" %)
340 -(((
341 -Change to fix frequency: AT+CHS=904900000
342 -)))
356 +[[image:image-20220526165525-16.png]]
343 343  
344 -(% class="box infomessage" %)
345 -(((
346 -Change to fix DR: AT+DR=0
347 -)))
348 348  
349 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
350 -
351 351  2. In LG02 , configure to receive above message
352 352  
353 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
361 +[[image:image-20220526165612-17.png]]
354 354  
363 +
355 355  In LG02 console, we can see the hex receive are:
356 356  
357 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
366 +[[image:image-20220526171112-21.png]]
358 358  
368 +
359 359  3. Decode the info in web
360 360  
361 361  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -370,7 +370,7 @@
370 370  
371 371  [[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]]
372 372  
373 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
383 +[[image:image-20220526171029-20.png]]
374 374  
375 375  (((
376 376   The FRMPayload is the device payload.
... ... @@ -381,6 +381,7 @@
381 381  
382 382  Since firmware v1.8, LHT65 will send MAC command to request time, in the case if DR only support max 11 bytes, this MAC command will be bundled to a separate uplink payload with 0x00.
383 383  
394 +
384 384  = 9. Why do I see a "MIC Mismatch" error message from the server? =
385 385  
386 386  (((
... ... @@ -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.
419 +
420 +
408 408  )))
409 409  
410 410  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
... ... @@ -412,27 +412,87 @@
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.
428 +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,
432 +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  
435 +* (((
436 +Solution: Use the decoder to filter out this 00 packet.
437 +)))
438 +* (((
439 +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]]
440 +
441 +
442 +)))
443 +
444 += 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
445 +
422 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
447 +It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
424 424  )))
425 425  
426 426  (((
427 - uplink packet, and an additional 00 data packet.
451 +AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
428 428  )))
429 429  
430 -* (((
431 -Solution: Use the decoder to filter out this 00 packet.
454 +(((
455 +AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
432 432  )))
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
457 +
458 +(((
459 +AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
435 435  )))
436 436  
437 -(% class="wikigeneratedid" id="H" %)
462 +(((
463 +AT+APPEUI=00 00 00 00 00 00 00 00
464 +)))
465 +
466 +(((
438 438  
468 +)))
469 +
470 +(((
471 +You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
472 +)))
473 +
474 +(((
475 +You can rewrites the keys by running commands in AT Console
476 +)))
477 +
478 +(((
479 +**For example：**
480 +)))
481 +
482 +(((
483 +AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
484 +)))
485 +
486 +(((
487 +AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
488 +)))
489 +
490 +(((
491 +AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
492 +)))
493 +
494 +(((
495 +AT+APPEUI=2C 45 47 E3 24 12 23 24
496 +)))
497 +
498 +(((
499 +(Any combination of 16 bit codes can be used）
500 +
501 +
502 += 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
503 +)))
504 +
505 +
506 +Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
507 +
508 +
509 +
510 +(% class="wikigeneratedid" %)
511 +
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
image-20220526164956-15.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,0 +1,1 @@
1 +XWiki.Xiaoling
Size
... ... @@ -1,0 +1,1 @@
1 +98.6 KB
Content

Applications

Navigation

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