Skip to Content
Last modified by Xiaoling on 2025/05/05 08:51
From version 39.2
edited by Xiaoling
on 2023/03/23 17:08
Change comment: There is no comment for this version
To version 38.1
edited by Bei Jinggeng
on 2023/03/22 16:32
Change comment: Uploaded new attachment "image-20230322163227-1.png", version {1}

Summary

Details

Page properties
Author
... ... @@ -1,1 +1,1 @@
1 -XWiki.Xiaoling
1 +XWiki.Bei
Content
... ... @@ -215,7 +215,6 @@
215 215  * 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.**
216 216  
217 217  
218 -
219 219  == 5.2 See Debug Info ==
220 220  
221 221  
... ... @@ -439,19 +439,11 @@
439 439  
440 440  * (((
441 441  If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
442 -)))
443 443  
444 -(% class="wikigeneratedid" %)
445 -3）Wrong Regional Parameters version selected
446 - We generally use versions above 1.0.2
447 447  
448 -(% class="wikigeneratedid" %)
449 -[[image:image-20230322163227-1.png]]
443 +
444 +)))
450 450  
451 -(% class="wikigeneratedid" %)
452 -4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
453 -
454 -
455 455  = 10. Why i got the payload only with "0x00" or "AA~=~="? =
456 456  
457 457