Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -1,9 +1,12 @@
1	1	**~ Contents:**
2	2
	3	+(((
	4	+
	5	+)))
	6	+
3	3	{{toc/}}
4	4
5	5
6		-
7	7	= 1. OTAA Join Process Debug =
8	8
9	9	These pages are useful to check what is wrong on the Join process. Below shows the four steps that we can check the Join Process.
...	...	@@ -182,7 +182,7 @@
182	182	Depends on Class A or Class C, the receive windows will be a little difference,
183	183	)))
184	184
185		-[[image:image-20220531161828-1.png]]
	188	+[[image:image-20220526164547-11.png]]
186	186
187	187	receive windows for Class A and Class C
188	188
...	...	@@ -194,7 +194,6 @@
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		-
198	198	== 5.2 See Debug Info ==
199	199
200	200	(((
...	...	@@ -305,7 +305,6 @@
305	305	* Gateway traffic (from server UI) to shows the data exchange between gateway and server.
306	306	* End Node traffic (from server UI) to shows end node activity in server.
307	307
308		-
309	309	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
310	310
311	311	(((
...	...	@@ -338,7 +338,15 @@
338	338	(% class="box infomessage" %)
339	339	(((
340	340	**Change to ABP Mode: AT+NJM=0**
	342	+)))
	343	+
	344	+(% class="box infomessage" %)
	345	+(((
341	341	**Change to fix frequency: AT+CHS=904900000**
	347	+)))
	348	+
	349	+(% class="box infomessage" %)
	350	+(((
342	342	**Change to fix DR: AT+DR=0**
343	343	)))
344	344
...	...	@@ -427,6 +427,7 @@
427	427	* (((
428	428	Some node decoders may not have filtering function, or you need decoders of other servers and formats. Please send an email to [[david.huang@dragino.cc>>mailto:david.huang@dragino.cc]]
429	429
	439	+
430	430
431	431	)))
432	432
...	...	@@ -486,15 +486,8 @@
486	486
487	487	(((
488	488	(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? =
492	492	)))
493	493
494	494
495		-Class C only refers to status after OTAA Join successfully. The OTAA Join Process will use Class A mode.
496		-
497		-
498		-
499	499	(% class="wikigeneratedid" %)
500	500

image-20220531161828-1.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-98.6 KB

Content