Summary

• Page properties (1 modified, 0 added, 0 removed)

Details

Page properties

Content

...	...	@@ -16,7 +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	20	(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
21	21
22	22	* If the device is sending join request to server?
...	...	@@ -211,8 +211,6 @@
211	211	* This packet must match the frequency of the RX1 or RX2 window.
212	212	* 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.**
213	213
214		-
215		-
216	216	== 5.2 See Debug Info ==
217	217
218	218
...	...	@@ -326,8 +326,6 @@
326	326	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
327	327	* End Node traffic (from server UI) to shows end node activity in server.
328	328
329		-
330		-
331	331	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
332	332
333	333
...	...	@@ -444,18 +444,23 @@
444	444	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
445	445
446	446
447		-* If you are using US915, AU915 or AS923 frequencies.It is possible because: .
	442	+**Why this happen:**
448	448
	444	+For US915, AU915 or AS923 frequencies.It is possible because: .
	445	+
449	449	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.
450	450
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.
	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.
452	452
453		-Solution: Use the decoder to filter out this 00 packet.
454	454
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]]
	451	+**How to solve:**
456	456
	453	+Solution: Use the decoder to filter out this 0x00 packet.
457	457
	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]]
458	458
	457	+
	458	+
459	459	= 11. Why my Dev EUI and APP EUI is 0x000000000000, how to solve? =
460	460
461	461