Summary

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

Details

Page properties

Content

...	...	@@ -1,4 +1,4 @@
1		-**~ Table of Contents:**
	1	+**~ Contents:**
2	2
3	3	{{toc/}}
4	4
...	...	@@ -194,6 +194,7 @@
194	194	* This packet must match the frequency of the RX1 or RX2 window.
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	197	== 5.2 See Debug Info ==
198	198
199	199	(((
...	...	@@ -304,6 +304,7 @@
304	304	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
305	305	* End Node traffic (from server UI) to shows end node activity in server.
306	306
	308	+
307	307	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
308	308
309	309	(((
...	...	@@ -336,7 +336,15 @@
336	336	(% class="box infomessage" %)
337	337	(((
338	338	**Change to ABP Mode: AT+NJM=0**
	341	+)))
	342	+
	343	+(% class="box infomessage" %)
	344	+(((
339	339	**Change to fix frequency: AT+CHS=904900000**
	346	+)))
	347	+
	348	+(% class="box infomessage" %)
	349	+(((
340	340	**Change to fix DR: AT+DR=0**
341	341	)))
342	342
...	...	@@ -484,15 +484,8 @@
484	484
485	485	(((
486	486	(Any combination of 16 bit codes can be used）
487		-
488		-
489		-= 12. I set my device is LoRaWAN Class C mode, why i still see Class A after boot? =
490	490	)))
491	491
492	492
493		-Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
494		-
495		-
496		-
497	497	(% class="wikigeneratedid" %)
498	498