Summary

• Page properties (2 modified, 0 added, 0 removed)
• Attachments (0 modified, 5 added, 0 removed)
  • image-20240123150720-1.png
  • image-20240123150943-2.png
  • image-20240123151225-3.png
  • image-20240123161737-4.png
  • image-20240123161806-5.png

Details

Page properties

Author

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

Content

...	...	@@ -214,7 +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	218	== 5.2 See Debug Info ==
219	219
220	220
...	...	@@ -330,8 +330,6 @@
330	330
331	331	* End Node traffic (from server UI) to shows end node activity in server.
332	332
333		-
334		-
335	335	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
336	336
337	337
...	...	@@ -438,27 +438,50 @@
438	438
439	439	* (((
440	440	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
	438	+)))
441	441
	440	+(% class="wikigeneratedid" %)
	441	+3）Wrong Regional Parameters version selected
	442	+ We generally use versions above 1.0.2
442	442
443		-
444		-)))
	444	+(% class="wikigeneratedid" %)
	445	+[[image:image-20230322163227-1.png]]
445	445
	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	+
446	446	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
447	447
448	448
449		-(% style="color:blue" %)**Why this happen:**
	454	+(% style="color:blue" %)**Why sensor sends 0x00?**
450	450
451		-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.
452	452
453		-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**:
454	454
455		-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.
456	456
457	457
	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	+
458	458	(% style="color:blue" %)**How to solve:**
459	459
460		-Solution: Use the decoder to filter out this 0x00 packet.
	470	+Solution:
461	461
	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	+
462	462	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]]
463	463
464	464

image-20240123150720-1.png

Author

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

Size

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

Content

image-20240123150943-2.png

Author

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

Size

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

Content

image-20240123151225-3.png

Author

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

Size

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

Content

image-20240123161737-4.png

Author

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

Size

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

Content

image-20240123161806-5.png

Author

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

Size

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

Content