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 (1 modified, 0 added, 0 removed)
Details
- Page properties
-
- Content
-
... ... @@ -16,6 +16,7 @@ 16 16 * End Node traffic (from server UI) to shows end node activity in server. (Normaly possible) 17 17 * End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI) 18 18 19 + 19 19 (% style="color:blue" %)**1. End Device Join Screen shot, we can check:** 20 20 21 21 * If the device is sending join request to server? ... ... @@ -210,6 +210,8 @@ 210 210 * This packet must match the frequency of the RX1 or RX2 window. 211 211 * 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.** 212 212 214 + 215 + 213 213 == 5.2 See Debug Info == 214 214 215 215 ... ... @@ -323,6 +323,8 @@ 323 323 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. 324 324 * End Node traffic (from server UI) to shows end node activity in server. 325 325 329 + 330 + 326 326 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 327 327 328 328 ... ... @@ -439,23 +439,18 @@ 439 439 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 440 440 441 441 442 -* *Why thishappen:**447 +* If you are using US915, AU915 or AS923 frequencies.It is possible because: . 443 443 444 -For US915, AU915 or AS923 frequencies.It is possible because: . 445 - 446 446 When using the frequency mentioned above, the server sometimes adjusts the Data Rate (DR) of the node, because the end node has Adaptive Data Rate (ADR) Enabled. 447 447 448 -When the server adjusts endnodedatarate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to theend node,followingan additional 00 data packetto handle this MAC command response.451 +When the server adjusts your node rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the node,and the node will reply to the server after receiving the ADR packet, but the number of payload bytes exceeds the limit,so it will send a normal uplink packet, and an additional 00 data packet. 449 449 453 +Solution: Use the decoder to filter out this 00 packet. 450 450 451 - **Howto solve:**455 +Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]] 452 452 453 -Solution: Use the decoder to filter out this 0x00 packet. 454 454 455 -Some node decoders may not have the filter function, or you need decoders of other servers and formats. Please send an email to [[support@dragino.com>>mailto:support@dragino.com]] 456 456 457 - 458 - 459 459 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 460 460 461 461