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.Edwin - Content
-
... ... @@ -16,8 +16,6 @@ 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 - 20 - 21 21 (% style="color:blue" %)**1. End Device Join Screen shot, we can check:** 22 22 23 23 * If the device is sending join request to server? ... ... @@ -212,9 +212,6 @@ 212 212 * This packet must match the frequency of the RX1 or RX2 window. 213 213 * 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.** 214 214 215 - 216 - 217 - 218 218 == 5.2 See Debug Info == 219 219 220 220 ... ... @@ -328,9 +328,6 @@ 328 328 * Gateway traffic (from server UI) to shows the data exchange between gateway and server. 329 329 * End Node traffic (from server UI) to shows end node activity in server. 330 330 331 - 332 - 333 - 334 334 = 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency = 335 335 336 336 ... ... @@ -447,27 +447,23 @@ 447 447 = 10. Why i got the payload only with "0x00" or "AA~=~="? = 448 448 449 449 450 -* Ifyouare using US915, AU915 and AS923 frequencies.Thisis normalphenomenon.442 +**Why this happen:** 451 451 452 -((( 453 -When using the frequency mentioned above, the server sometimes adjusts the rate of the node, because the node defaults to the adaptive rate. 454 -))) 444 +For US915, AU915 or AS923 frequencies.It is possible because: . 455 455 456 -((( 457 -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. 458 -))) 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. 459 459 460 -* ((( 461 -Solution: Use the decoder to filter out this 00 packet. 462 -))) 463 -* ((( 464 -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]] 448 +When the server adjusts end node data rate to 0, the maximum payload length is 11 bytes. The server sometimes sends an ADR packet to the end 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 following an additional 00 data packet to handle this MAC command response. 465 465 466 466 451 +**How to solve:** 467 467 468 - 469 -))) 453 +Solution: Use the decoder to filter out this 0x00 packet. 470 470 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 + 457 + 458 + 471 471 = 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? = 472 472 473 473