Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 2 added, 0 removed)
  • image-20230322163227-1.png
  • image-20240123150720-1.png

Details

Page properties

Author

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

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
...	...	@@ -437,27 +437,50 @@
437	437
438	438	* (((
439	439	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
	438	+)))
440	440
	440	+(% class="wikigeneratedid" %)
	441	+3）Wrong Regional Parameters version selected
	442	+ We generally use versions above 1.0.2
441	441
442		-
443		-)))
	444	+(% class="wikigeneratedid" %)
	445	+[[image:image-20230322163227-1.png]]
444	444
	447	+(% class="wikigeneratedid" %)
	448	+4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
	449	+
	450	+
445	445	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
446	446
447	447
448		-(% style="color:blue" %)**Why this happen:**
	454	+(% style="color:blue" %)**Why sensor sends 0x00?**
449	449
450		-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.
451	451
452		-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**:
453	453
454		-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.
455	455
456	456
	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	+
457	457	(% style="color:blue" %)**How to solve:**
458	458
459		-Solution: Use the decoder to filter out this 0x00 packet.
	470	+Solution:
460	460
	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	+
461	461	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]]
462	462
463	463

image-20230322163227-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.Bei

Size

...	...	@@ -1,0 +1,1 @@
	1	+43.1 KB

Content

image-20240123150720-1.png

Author

...	...	@@ -1,0 +1,1 @@
	1	+XWiki.ting

Size

...	...	@@ -1,0 +1,1 @@
	1	+119.9 KB

Content