Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -195,7 +195,6 @@
195	195	* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). **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.**
196	196
197	197
198		-
199	199	== 5.2 See Debug Info ==
200	200
201	201	(((
...	...	@@ -307,7 +307,6 @@
307	307	* End Node traffic (from server UI) to shows end node activity in server.
308	308
309	309
310		-
311	311	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
312	312
313	313	(((
...	...	@@ -340,15 +340,7 @@
340	340	(% class="box infomessage" %)
341	341	(((
342	342	**Change to ABP Mode: AT+NJM=0**
343		-)))
344		-
345		-(% class="box infomessage" %)
346		-(((
347	347	**Change to fix frequency: AT+CHS=904900000**
348		-)))
349		-
350		-(% class="box infomessage" %)
351		-(((
352	352	**Change to fix DR: AT+DR=0**
353	353	)))
354	354
...	...	@@ -496,8 +496,15 @@
496	496
497	497	(((
498	498	(Any combination of 16 bit codes can be used）
	489	+
	490	+
	491	+= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
499	499	)))
500	500
501	501
	495	+Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
	496	+
	497	+
	498	+
502	502	(% class="wikigeneratedid" %)
503	503