Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 14.2 >
edited by Xiaoling
on 2022/05/26 16:38
To version < 31.3 >
edited by Xiaoling
on 2022/06/01 13:38
>
Change comment: There is no comment for this version

Summary

Details

Page properties
Content
... ... @@ -1,12 +1,9 @@
1 1  **~ Contents:**
2 2  
3 -(((
4 -
5 -)))
6 -
7 7  {{toc/}}
8 8  
9 9  
6 +
10 10  = 1. OTAA Join Process Debug =
11 11  
12 12  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.
... ... @@ -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-20220526163523-1.png]]
23 +[[image:image-20220526164956-15.png]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -102,11 +102,11 @@
102 102  
103 103  US915 Channels
104 104  
105 -[[image:https://wiki.dragino.com/images/8/8a/AU915_FRE_BAND-1.png]]
102 +[[image:image-20220526163926-7.png]]
106 106  
107 107  AU915 Channels
108 108  
109 -[[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 +[[image:image-20220526163941-8.png]]
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:https://wiki.dragino.com/images/thumb/9/9a/US915_FRE_BAND-2.png/600px-US915_FRE_BAND-2.png||height="288" width="600"]]
116 +[[image:image-20220526164052-9.png]]
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: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]]
170 +[[image:image-20220526164508-10.png]]
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:https://wiki.dragino.com/images/thumb/1/1a/Downstream_LoRaWAN-1.png/600px-Downstream_LoRaWAN-1.png||height="590" width="600"]]
185 +[[image:image-20220531161828-1.png]]
189 189  
190 190  receive windows for Class A and Class C
191 191  
... ... @@ -197,6 +197,8 @@
197 197  * This packet must match the frequency of the RX1 or RX2 window.
198 198  * 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.**
199 199  
197 +
198 +
200 200  == 5.2 See Debug Info ==
201 201  
202 202  (((
... ... @@ -211,7 +211,7 @@
211 211  Configure a downstream to the end device
212 212  )))
213 213  
214 -[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
213 +[[image:image-20220526164623-12.png]]
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:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
224 +[[image:image-20220526164650-13.png]]
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:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
239 +[[image:image-20220526164734-14.png]]
241 241  
242 242  (((
243 243  Gateway Sent out this packet
... ... @@ -297,9 +297,10 @@
297 297   Receive data
298 298   1:0012345678}}}
299 299  
299 +
300 300  == 5.3 If problem doesn’t solve ==
301 301  
302 -**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:**
302 +(% 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:**
303 303  
304 304  * End node console to show the transmit freuqency and DR.
305 305  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -337,29 +337,32 @@
337 337  
338 338  (% class="box infomessage" %)
339 339  (((
340 -Change to ABP Mode: AT+NJM=0
340 +**Change to ABP Mode: AT+NJM=0**
341 341  )))
342 342  
343 343  (% class="box infomessage" %)
344 344  (((
345 -Change to fix frequency: AT+CHS=904900000
345 +**Change to fix frequency: AT+CHS=904900000**
346 346  )))
347 347  
348 348  (% class="box infomessage" %)
349 349  (((
350 -Change to fix DR: AT+DR=0
350 +**Change to fix DR: AT+DR=0**
351 351  )))
352 352  
353 -[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
353 +[[image:image-20220526165525-16.png]]
354 354  
355 +
355 355  2. In LG02 , configure to receive above message
356 356  
357 -[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
358 +[[image:image-20220526165612-17.png]]
358 358  
360 +
359 359  In LG02 console, we can see the hex receive are:
360 360  
361 -[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
363 +[[image:image-20220526171112-21.png]]
362 362  
365 +
363 363  3. Decode the info in web
364 364  
365 365  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -374,7 +374,7 @@
374 374  
375 375  [[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]]
376 376  
377 -[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
380 +[[image:image-20220526171029-20.png]]
378 378  
379 379  (((
380 380   The FRMPayload is the device payload.
... ... @@ -385,6 +385,7 @@
385 385  
386 386  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.
387 387  
391 +
388 388  = 9. Why do I see a "MIC Mismatch" error message from the server? =
389 389  
390 390  (((
... ... @@ -431,38 +431,66 @@
431 431  * (((
432 432  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]]
433 433  
434 -
435 435  
436 436  )))
437 437  
438 438  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
439 439  
443 +(((
440 440  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
445 +)))
441 441  
447 +(((
442 442  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449 +)))
443 443  
451 +(((
444 444  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
453 +)))
445 445  
455 +(((
446 446  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
457 +)))
447 447  
459 +(((
448 448  AT+APPEUI=00 00 00 00 00 00 00 00
461 +)))
449 449  
463 +(((
464 +
465 +)))
450 450  
467 +(((
451 451  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
469 +)))
452 452  
471 +(((
453 453  You can rewrites the keys by running commands in AT Console
473 +)))
454 454  
455 -For example：
475 +(((
476 +**For example：**
477 +)))
456 456  
479 +(((
457 457  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
481 +)))
458 458  
483 +(((
459 459  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
485 +)))
460 460  
487 +(((
461 461  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
489 +)))
462 462  
491 +(((
463 463  AT+APPEUI=2C 45 47 E3 24 12 23 24
493 +)))
464 464  
495 +(((
465 465  (Any combination of 16 bit codes can be used）
497 +)))
466 466  
467 467  
468 468  (% class="wikigeneratedid" %)
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