Summary

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

Details

Page properties

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
...	...	@@ -331,7 +331,6 @@
331	331	* End Node traffic (from server UI) to shows end node activity in server.
332	332
333	333
334		-
335	335	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
336	336
337	337
...	...	@@ -438,11 +438,18 @@
438	438
439	439	* (((
440	440	If a node is registered with multiple servers, it may also cause the "mic mismatch" error.
	439	+)))
441	441
	441	+(% class="wikigeneratedid" %)
	442	+3）Wrong Regional Parameters version selected
	443	+ We generally use versions above 1.0.2
442	442
443		-
444		-)))
	445	+(% class="wikigeneratedid" %)
	446	+[[image:image-20230322163227-1.png]]
445	445
	448	+(% class="wikigeneratedid" %)
	449	+4）We have had cases where it was automatically fixed the next day despite no manual changes, probably a server side issue
	450	+
446	446	= 10. Why i got the payload only with "0x00" or "AA~=~="? =
447	447
448	448