Last modified by Edwin Chen on 2025/01/29 20:30
<
From version < 29.3 >
edited by Xiaoling
on 2022/05/26 17:11
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
... ... @@ -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]]
26 +[[image:image-20220526163523-1.png]]
27 27  
28 28  Console Output from End device to see the transmit frequency
29 29  
... ... @@ -197,6 +197,7 @@
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  
200 +
200 200  == 5.2 See Debug Info ==
201 201  
202 202  (((
... ... @@ -297,10 +297,12 @@
297 297   Receive data
298 298   1:0012345678}}}
299 299  
301 +(% class="wikigeneratedid" %)
302 +​​​​​​​
300 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:**
306 +**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.
... ... @@ -338,32 +338,29 @@
338 338  
339 339  (% class="box infomessage" %)
340 340  (((
341 -**Change to ABP Mode: AT+NJM=0**
344 +Change to ABP Mode: AT+NJM=0
342 342  )))
343 343  
344 344  (% class="box infomessage" %)
345 345  (((
346 -**Change to fix frequency: AT+CHS=904900000**
349 +Change to fix frequency: AT+CHS=904900000
347 347  )))
348 348  
349 349  (% class="box infomessage" %)
350 350  (((
351 -**Change to fix DR: AT+DR=0**
354 +Change to fix DR: AT+DR=0
352 352  )))
353 353  
354 -[[image:image-20220526165525-16.png]]
357 +[[image:https://wiki.dragino.com/images/e/e6/Decrypt_a_LoRaWAN_Packet1.jpg||alt="Decrypt a LoRaWAN Packet1.jpg" height="607" width="558"]]
355 355  
356 -
357 357  2. In LG02 , configure to receive above message
358 358  
359 -[[image:image-20220526165612-17.png]]
361 +[[image:https://wiki.dragino.com/images/c/c3/Decrypt_a_LoRaWAN_Packet2.jpg||alt="Decrypt a LoRaWAN Packet2.jpg" height="337" width="558"]]
360 360  
361 -
362 362  In LG02 console, we can see the hex receive are:
363 363  
364 -[[image:image-20220526171112-21.png]]
365 +[[image:https://wiki.dragino.com/images/f/f1/Decrypt_a_LoRaWAN_Packet3.jpg||alt="Decrypt a LoRaWAN Packet3.jpg" height="179" width="558"]]
365 365  
366 -
367 367  3. Decode the info in web
368 368  
369 369  [[https:~~/~~/lorawan-packet-decoder-0ta6puiniaut.runkit.sh>>url:https://lorawan-packet-decoder-0ta6puiniaut.runkit.sh/]]
... ... @@ -378,7 +378,7 @@
378 378  
379 379  [[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]]
380 380  
381 -[[image:image-20220526171029-20.png]]
381 +[[image:https://wiki.dragino.com/images/7/77/Decrypt_a_LoRaWAN_Packet4.png||alt="Decrypt a LoRaWAN Packet4.png" height="390" width="558"]]
382 382  
383 383  (((
384 384   The FRMPayload is the device payload.
... ... @@ -389,7 +389,6 @@
389 389  
390 390  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.
391 391  
392 -
393 393  = 9. Why do I see a "MIC Mismatch" error message from the server? =
394 394  
395 395  (((
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

Applications

Navigation

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