Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 8 removed)
  • 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

Details

Page properties

Content

...	...	@@ -4,9 +4,8 @@
4	4
5	5
6	6
7		-= 1. Join process page check =
	7	+= 1.Join process page check =
8	8
9		-
10	10	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.
11	11	\\**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:**
12	12
...	...	@@ -26,11 +26,12 @@
26	26
27	27	* What frequency the device is sending?
28	28
29		-[[image:image-20240129142147-2.png||height="736" width="964"]]
	28	+[[image:image-20220526164956-15.png||height="591" width="1153"]]
30	30
31		-Console Output from End device to see the transmit frequency.
	30	+Console Output from End device to see the transmit frequency
32	32
33	33
	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,11 +37,12 @@
37	37
38	38	* If the gateway gets the Join Accept message from server and transmit it via LoRa?
39	39
40		-[[image:image-20240129151608-6.jpeg||height="725" width="1256"]]
	40	+[[image:image-20220526163608-2.png]]
41	41
42	42	Console Output from Gateway to see packets between end node and server.
43	43
44	44
	45	+
45	45	(% style="color:blue" %)**3. Gateway Live data in LoRaWAN Server**
46	46
47	47	* Does the gateway real-time data contain information about Join Request? If not, check the internet connection and gateway LoRaWAN server Settings.
...	...	@@ -50,21 +50,22 @@
50	50
51	51	* 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.
52	52
53		-[[image:image-20240129150821-5.jpeg||height="522" width="1264"]]
	54	+[[image:image-20220526163633-3.png]]
54	54
55	55	The Traffic for the End node in the server, use TTN as example.
56	56
57	57
	59	+
58	58	(% style="color:blue" %)**4. Data Page in LoRaWAN server**
59	59
60	60	* 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.
61	61
62		-[[image:image-20240129142557-3.png||height="488" width="1267"]]
	64	+[[image:image-20240123150720-1.png||height="459" width="1182"]]
63	63
64	64	The data for the end device set in server
65	65
66	66
67		-[[image:image-20240129142631-4.png||height="637" width="1256"]]
	69	+[[image:image-20240123150943-2.png||height="556" width="1179"]]
68	68
69	69	Check if OTAA Keys match the keys in device.
70	70
...	...	@@ -213,6 +213,8 @@
213	213
214	214	* 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.**
215	215
	218	+== ==
	219	+
216	216	== 5.2 See Debug Info ==
217	217
218	218
...	...	@@ -226,8 +226,6 @@
226	226
227	227	(((
228	228	Configure a downlink to the end device
229		-
230		-[[image:image-20240129152412-8.png||height="486" width="1206"]]
231	231	)))
232	232
233	233	[[image:image-20240123163307-7.png||height="330" width="1125"]]
...	...	@@ -238,10 +238,10 @@
238	238
239	239
240	240	(((
241		-This downstream info will then pass to the gateway downstream list. and the DR which is used (SF7BW500) in US915 is DR5.
	243	+This downstream info will then pass to the gateway downstream list. and include the DR which is used (SF9BW125) in EU868 is DR3
242	242	)))
243	243
244		-[[image:image-20240129152049-7.png||height="463" width="1166"]]
	246	+[[image:image-20220526164650-13.png]]
245	245
246	246	(((
247	247	Gateway Traffic can see this downstream info

image-20240129142110-1.png

Author

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

Size

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

Content

image-20240129142147-2.png

Author

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

Size

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

Content

image-20240129142557-3.png

Author

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

Size

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

Content

image-20240129142631-4.png

Author

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

Size

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

Content

image-20240129150821-5.jpeg

Author

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

Size

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

Content

image-20240129151608-6.jpeg

Author

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

Size

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

Content

image-20240129152049-7.png

Author

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

Size

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

Content

image-20240129152412-8.png

Author

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

Size

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

Content