Summary

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

Details

Page properties

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.
...	...	@@ -194,8 +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		-
199	199	== 5.2 See Debug Info ==
200	200
201	201	(((
...	...	@@ -306,8 +306,6 @@
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
309		-
310		-
311	311	= 6. Downlink Issue ~-~- Packet REJECTED, unsupported frequency =
312	312
313	313	(((
...	...	@@ -437,6 +437,7 @@
437	437	* (((
438	438	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]]
439	439
	439	+
440	440
441	441	)))
442	442

image-20220531161828-1.png

Author

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

Size

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

Content