Changes for page LoRaWAN Communication Debug
Last modified by Edwin Chen on 2025/01/29 20:30
Summary
-
Page properties (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -1,12 +1,9 @@ 1 1 **~ Contents:** 2 2 3 -((( 4 - 5 -))) 6 - 7 7 {{toc/}} 8 8 9 9 6 + 10 10 = 1. OTAA Join Process Debug = 11 11 12 12 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. ... ... @@ -197,6 +197,8 @@ 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 197 + 198 + 200 200 == 5.2 See Debug Info == 201 201 202 202 ((( ... ... @@ -307,6 +307,8 @@ 307 307 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. 308 308 * End Node traffic (from server UI) to shows end node activity in server. 309 309 309 + 310 + 310 310 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 311 311 312 312 (((