Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 32.1 >
edited by Edwin Chen
on 2022/06/10 19:32
To version < 22.1 >
edited by Xiaoling
on 2022/05/26 16:47
>
Change comment: Uploaded new attachment "image-20220526164734-14.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Edwin
1 +XWiki.Xiaoling
Content
... ... @@ -1,9 +1,12 @@
1 1  **~ Contents:**
2 2  
3 +(((
4 +
5 +)))
6 +
3 3  {{toc/}}
4 4  
5 5  
6 -
7 7  = 1. OTAA Join Process Debug =
8 8  
9 9  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.
... ... @@ -20,7 +20,7 @@
20 20  * If the device is sending join request to server?
21 21  * What frequency the device is sending?
22 22  
23 -[[image:image-20220526164956-15.png]]
26 +[[image:image-20220526163523-1.png]]
24 24  
25 25  Console Output from End device to see the transmit frequency
26 26  
... ... @@ -182,7 +182,7 @@
182 182  Depends on Class A or Class C, the receive windows will be a little difference,
183 183  )))
184 184  
185 -[[image:image-20220531161828-1.png]]
188 +[[image:image-20220526164547-11.png]]
186 186  
187 187  receive windows for Class A and Class C
188 188  
... ... @@ -194,7 +194,6 @@
194 194  * This packet must match the frequency of the RX1 or RX2 window.
195 195  * 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.**
196 196  
197 -
198 198  == 5.2 See Debug Info ==
199 199  
200 200  (((
... ... @@ -209,7 +209,7 @@
209 209  Configure a downstream to the end device
210 210  )))
211 211  
212 -[[image:image-20220526164623-12.png]]
214 +[[image:https://wiki.dragino.com/images/thumb/8/82/Downstream_debug_1.png/600px-Downstream_debug_1.png||height="217" width="600"]]
213 213  
214 214  (((
215 215  Set a downstream in TTN and see it is sent
... ... @@ -220,7 +220,7 @@
220 220  This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
221 221  )))
222 222  
223 -[[image:image-20220526164650-13.png]]
225 +[[image:https://wiki.dragino.com/images/thumb/d/dc/Downstream_debug_2.png/600px-Downstream_debug_2.png||height="245" width="600"]]
224 224  
225 225  (((
226 226  Gateway Traffic can see this downstream info
... ... @@ -235,7 +235,7 @@
235 235  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:
236 236  )))
237 237  
238 -[[image:image-20220526164734-14.png]]
240 +[[image:https://wiki.dragino.com/images/thumb/2/21/Downstream_debug_3.png/600px-Downstream_debug_3.png||height="195" width="600"]]
239 239  
240 240  (((
241 241  Gateway Sent out this packet
... ... @@ -295,10 +295,9 @@
295 295   Receive data
296 296   1:0012345678}}}
297 297  
298 -
299 299  == 5.3 If problem doesn’t solve ==
300 300  
301 -(% 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:**
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 302  
303 303  * End node console to show the transmit freuqency and DR.
304 304  * Gateway (from gateway UI) traffic to show the packet got from end node and receive from Server.
... ... @@ -305,7 +305,6 @@
305 305  * Gateway traffic (from server UI) to shows the data exchange between gateway and server.
306 306  * End Node traffic (from server UI) to shows end node activity in server.
307 307  
308 -
309 309  = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310 310  
311 311  (((
... ... @@ -337,24 +337,29 @@
337 337  
338 338  (% class="box infomessage" %)
339 339  (((
340 -**Change to ABP Mode: AT+NJM=0**
341 -**Change to fix frequency: AT+CHS=904900000**
342 -**Change to fix DR: AT+DR=0**
340 +Change to ABP Mode: AT+NJM=0
343 343  )))
344 344  
345 -[[image:image-20220526165525-16.png]]
343 +(% class="box infomessage" %)
344 +(((
345 +Change to fix frequency: AT+CHS=904900000
346 +)))
346 346  
348 +(% class="box infomessage" %)
349 +(((
350 +Change to fix DR: AT+DR=0
351 +)))
347 347  
353 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
354 +
348 348  2. In LG02 , configure to receive above message
349 349  
350 -[[image:image-20220526165612-17.png]]
357 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
351 351  
352 -
353 353  In LG02 console, we can see the hex receive are:
354 354  
355 -[[image:image-20220526171112-21.png]]
361 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
356 356  
357 -
358 358  3. Decode the info in web
359 359  
360 360  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -369,7 +369,7 @@
369 369  
370 370  [[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]]
371 371  
372 -[[image:image-20220526171029-20.png]]
377 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
373 373  
374 374  (((
375 375   The FRMPayload is the device payload.
... ... @@ -380,7 +380,6 @@
380 380  
381 381  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.
382 382  
383 -
384 384  = 9. Why do I see a "MIC Mismatch" error message from the server? =
385 385  
386 386  (((
... ... @@ -427,74 +427,37 @@
427 427  * (((
428 428  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]]
429 429  
434 +
430 430  
431 431  )))
432 432  
433 433  = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
434 434  
435 -(((
436 436  It is possible the keys is erased during upgrading of firmware. and the console output shows below after AT+CFG
437 -)))
438 438  
439 -(((
440 440  AT+APPKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
441 -)))
442 442  
443 -(((
444 444  AT+NWKSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
445 -)))
446 446  
447 -(((
448 448  AT+APPSKEY=00 00 00 00 00 00 00 00 00 00 00 00 00 00 00 00
449 -)))
450 450  
451 -(((
452 452  AT+APPEUI=00 00 00 00 00 00 00 00
453 -)))
454 454  
455 -(((
456 -
457 -)))
458 458  
459 -(((
460 460  You can get the keys from the box sticker or send mail to Dragino Support to check keys with the provided SN number.
461 -)))
462 462  
463 -(((
464 464  You can rewrites the keys by running commands in AT Console
465 -)))
466 466  
467 -(((
468 -**For example：**
469 -)))
455 +For example：
470 470  
471 -(((
472 472  AT+APPKEY=85 41 47 20 45 58 28 14 16 82 A0 F0 80 0D DD EE
473 -)))
474 474  
475 -(((
476 476  AT+NWKSKEY=AA CC B0 20 30 45 37 32 14 1E 14 93 E2 3B 20 11
477 -)))
478 478  
479 -(((
480 480  AT+APPSKEY=11 23 02 20 30 20 30 60 80 20 20 30 30 20 10 10
481 -)))
482 482  
483 -(((
484 484  AT+APPEUI=2C 45 47 E3 24 12 23 24
485 -)))
486 486  
487 -(((
488 488  (Any combination of 16 bit codes can be used）
489 489  
490 490  
491 -= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
492 -)))
493 -
494 -
495 -Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
496 -
497 -
498 -
499 -(% class="wikigeneratedid" %)
500 -
image-20220526164956-15.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -634.4 KB
Content
image-20220526165525-16.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -185.4 KB
Content
image-20220526165612-17.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -116.5 KB
Content
image-20220526165855-18.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.7 KB
Content
image-20220526170151-19.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.4 KB
Content
image-20220526171029-20.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -70.6 KB
Content
image-20220526171112-21.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -183.8 KB
Content
image-20220531161828-1.png
Author
... ... @@ -1,1 +1,0 @@
1 -XWiki.Xiaoling
Size
... ... @@ -1,1 +1,0 @@
1 -98.6 KB
Content

Applications

Navigation

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