Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 10 added, 0 removed)
  • image-20240123182345-1.png
  • image-20240129142110-1.png
  • image-20240129142147-2.png
  • image-20240129142557-3.png
  • image-20240129142631-4.png
  • image-20240129150821-5.jpeg
  • image-20240129151608-6.jpeg
  • image-20240129152049-7.png
  • image-20240129152412-8.png
  • image-20240129154321-9.png

Details

Page properties

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-20240129142147-2.png||height="736" width="964"]]
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)
...	...	@@ -37,12 +37,11 @@
37	37
38	38	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
39	39
40		-[[image:image-20220526163608-2.png]]
	40	+[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
41	41
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.
...	...	@@ -51,22 +51,21 @@
51	51
52	52	* If the Join Accept message are in correct frequency? If you set the server to use US915 band, and your end node and gateway is EU868, you will see the Join Accept message are in US915 band so no possible to Join success.
53	53
54		-[[image:image-20220526163633-3.png]]
	53	+[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
55	55
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.
63	63
64		-[[image:image-20240123150720-1.png||height="459" width="1182"]]
	62	+[[image:image-20240129142557-3.png||height="488" width="1267"]]
65	65
66	66	The data for the end device set in server
67	67
68	68
69		-[[image:image-20240123150943-2.png||height="556" width="1179"]]
	67	+[[image:image-20240129142631-4.png||height="637" width="1256"]]
70	70
71	71	Check if OTAA Keys match the keys in device.
72	72
...	...	@@ -215,8 +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		-
220	220	== 5.2 See Debug Info ==
221	221
222	222
...	...	@@ -230,6 +230,8 @@
230	230
231	231	(((
232	232	Configure a downlink to the end device
	229	+
	230	+[[image:image-20240129152412-8.png||height="486" width="1206"]]
233	233	)))
234	234
235	235	[[image:image-20240123163307-7.png||height="330" width="1125"]]
...	...	@@ -240,10 +240,10 @@
240	240
241	241
242	242	(((
243		-This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
	241	+This downstream info will then pass to the gateway downstream list. and the DR which is used (SF7BW500) in US915 is DR5.
244	244	)))
245	245
246		-[[image:image-20220526164650-13.png]]
	244	+[[image:image-20240129152049-7.png||height="463" width="1166"]]
247	247
248	248	(((
249	249	Gateway Traffic can see this downstream info

image-20240123182345-1.png

Author

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

Size

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

Content

image-20240129142110-1.png

Author

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

Size

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

Content

image-20240129142147-2.png

Author

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

Size

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

Content

image-20240129142557-3.png

Author

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

Size

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

Content

image-20240129142631-4.png

Author

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

Size

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

Content

image-20240129150821-5.jpeg

Author

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

Size

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

Content

image-20240129151608-6.jpeg

Author

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

Size

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

Content

image-20240129152049-7.png

Author

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

Size

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

Content

image-20240129152412-8.png

Author

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

Size

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

Content

image-20240129154321-9.png

Author

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

Size

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

Content