Summary

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

Details

Page properties

Author

...	...	@@ -1,1 +1,1 @@
1		-XWiki.Xiaoling
	1	+XWiki.Edwin

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
...	...	@@ -331,8 +331,6 @@
331	331
332	332	* End Node traffic (from server UI) to shows end node activity in server.
333	333
334		-
335		-
336	336	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
337	337
338	338
...	...	@@ -455,19 +455,34 @@
455	455	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
456	456
457	457
458		-(% style="color:blue" %)**Why this happen:**
	454	+(% style="color:blue" %)**Why sensor sends 0x00?**
459	459
460		-For US915, AU915 or AS923 frequencies.It is possible because: .
	456	+For US915, AU915 or AS923 frequencies, the max payload lenght is 11 bytes for DR0. Some times sensor needs to send MAC command to server, because the payload is 11 bytes, The MAC command + Payload will exceed 11 bytes and LoRaWAN server will ignore the uplink. In this case, Sensor will send two uplinks together: one uplink is the payload without MAC command, another uplink is **0x00 payload + MAC Command.**  For the second uplink, in the server side, it will shows the payload is 0x00. Normally, there are several case this will happen.
461	461
462		-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.
	458	+**Possible Case 1**:
463	463
464		-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.
	460	+Sensor has ADR=1 enable and sensor need to reply server MAC command (ADR request) while sensor has DR=0.
465	465
466	466
	463	+**Possible Case 2:**
	464	+
	465	+For the sensor which has Datalog Feature enable, the sensor will send TimeRequest MAC Command to sync the time. This Time Request will be sent once Sensor Join Network and Every 10 days. While they send such command with DR=0, sensor will send this command with 0x00 payload.
	466	+
	467	+
467	467	(% style="color:blue" %)**How to solve:**
468	468
469		-Solution: Use the decoder to filter out this 0x00 packet.
	470	+Solution:
470	470
	472	+~1. Use the decoder to filter out this 0x00 packet. (**Recommand**)
	473	+
	474	+2. Data rate changed from DR3 to DR5, increasing upload byte length
	475	+AT+ADR=0
	476	+AT+DR=3
	477	+
	478	+Downlink：
	479	+
	480	+[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/#H7.4DataRate]]
	481	+
471	471	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]]
472	472
473	473