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	(((
...	...	@@ -306,6 +306,7 @@
306	306	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
307	307	* End Node traffic (from server UI) to shows end node activity in server.
308	308
	308	+
309	309	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310	310
311	311	(((
...	...	@@ -338,15 +338,7 @@
338	338	(% class="box infomessage" %)
339	339	(((
340	340	**Change to ABP Mode: AT+NJM=0**
341		-)))
342		-
343		-(% class="box infomessage" %)
344		-(((
345	345	**Change to fix frequency: AT+CHS=904900000**
346		-)))
347		-
348		-(% class="box infomessage" %)
349		-(((
350	350	**Change to fix DR: AT+DR=0**
351	351	)))
352	352
...	...	@@ -494,8 +494,15 @@
494	494
495	495	(((
496	496	(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? =
497	497	)))
498	498
499	499
	495	+Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
	496	+
	497	+
	498	+
500	500	(% class="wikigeneratedid" %)
501	501