Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -215,7 +215,6 @@
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	217
218		-
219	219	== 5.2 See Debug Info ==
220	220
221	221
...	...	@@ -331,6 +331,7 @@
331	331
332	332	* End Node traffic (from server UI) to shows end node activity in server.
333	333
	333	+
334	334	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
335	335
336	336
...	...	@@ -437,11 +437,19 @@
437	437
438	438	* (((
439	439	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
	440	+)))
440	440
	442	+(% class="wikigeneratedid" %)
	443	+3）Wrong Regional Parameters version selected
	444	+ We generally use versions above 1.0.2
441	441
442		-
443		-)))
	446	+(% class="wikigeneratedid" %)
	447	+[[image:image-20230322163227-1.png]]
444	444
	449	+(% class="wikigeneratedid" %)
	450	+4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
	451	+
	452	+
445	445	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
446	446
447	447
...	...	@@ -451,13 +451,29 @@
451	451
452	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.
453	453
	462	+1.
	463	+
454	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.
455	455
	466	+2.
456	456
	468	+The server downlinks a calibration time package
	469	+This calibration time packet will exceed the byte limit, causing its payload to become 00
	470	+
457	457	(% style="color:blue" %)**How to solve:**
458	458
459		-Solution: Use the decoder to filter out this 0x00 packet.
	473	+Solution:
460	460
	475	+~1. Use the decoder to filter out this 0x00 packet.
	476	+
	477	+2. Data rate changed from DR3 to DR5, increasing upload byte length
	478	+AT+ADR=0
	479	+AT+DR=3
	480	+
	481	+Downlink：
	482	+
	483	+[[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]]
	484	+
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