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)
Details
- Page properties
-
- Author
-
... ... @@ -1,1 +1,1 @@ 1 -XWiki. Xiaoling1 +XWiki.Bei - Content
-
... ... @@ -214,8 +214,6 @@ 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 - 218 - 219 219 == 5.2 See Debug Info == 220 220 221 221 ... ... @@ -332,7 +332,6 @@ 332 332 * End Node traffic (from server UI) to shows end node activity in server. 333 333 334 334 335 - 336 336 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 337 337 338 338 ... ... @@ -451,7 +451,6 @@ 451 451 (% class="wikigeneratedid" %) 452 452 4)We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue 453 453 454 - 455 455 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 456 456 457 457