Changes for page LoRaWAN Communication Debug
Last modified by Edwin Chen on 2025/01/29 20:30
Change comment:
There is no comment for this version
Summary
-
Page properties (2 modified, 0 added, 0 removed)
-
Attachments (0 modified, 0 added, 1 removed)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Bei1 +XWiki.Xiaoling - Content
-
... ... @@ -214,6 +214,7 @@ 214 214 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 217 == 5.2 See Debug Info == 218 218 219 219 ... ... @@ -330,6 +330,7 @@ 330 330 * End Node traffic (from server UI) to shows end node activity in server. 331 331 332 332 334 + 333 333 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 334 334 335 335 ... ... @@ -436,18 +436,11 @@ 436 436 437 437 * ((( 438 438 If a node is registered with multiple servers, it may also cause the "mic mismatch" error. 439 -))) 440 440 441 -(% class="wikigeneratedid" %) 442 -3)Wrong Regional Parameters version selected 443 - We generally use versions above 1.0.2 444 444 445 - (%class="wikigeneratedid" %)446 - [[image:image-20230322163227-1.png]]443 + 444 +))) 447 447 448 -(% class="wikigeneratedid" %) 449 -4)We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue 450 - 451 451 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 452 452 453 453
- image-20230322163227-1.png
-
- Author
-
... ... @@ -1,1 +1,0 @@ 1 -XWiki.Bei - Size
-
... ... @@ -1,1 +1,0 @@ 1 -43.1 KB - Content