Summary

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

Details

Page properties

Author

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

Content

...	...	@@ -4,8 +4,9 @@
4	4
5	5
6	6
7		-= 1.Join process page check =
	7	+= 1. Join process page check =
8	8
	9	+
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.
10	10	\\**If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the sceenshots for each step to check. They include:**
11	11
...	...	@@ -25,12 +25,11 @@
25	25
26	26	* What frequency the device is sending?
27	27
28		-[[image:image-20220526164956-15.png||height="591" width="1153"]]
	29	+[[image:image-20240123182345-1.png||height="605" width="946"]]
29	29
30		-Console Output from End device to see the transmit frequency
	31	+Console Output from End device to see the transmit frequency.
31	31
32	32
33		-
34	34	(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
35	35
36	36	* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
...	...	@@ -42,7 +42,6 @@
42	42	Console Output from Gateway to see packets between end node and server.
43	43
44	44
45		-
46	46	(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
47	47
48	48	* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
...	...	@@ -56,7 +56,6 @@
56	56	The Traffic for the End node in the server, use TTN as example.
57	57
58	58
59		-
60	60	(% style="color:blue" %)**4. Data Page in LoRaWAN server**
61	61
62	62	* If this data page shows the Join Request message from the end node? If not, most properly you have wrong settings in the keys. Keys in the server doesn't match the keys in End Node.
...	...	@@ -215,7 +215,6 @@
215	215
216	216	* This packet must match the DataRate of RX1(RX1DR) or RX2 (RX2DR). (% style="color:red" %)**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.**
217	217
218		-== ==
219	219
220	220	== 5.2 See Debug Info ==
221	221