Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 34 added, 0 removed)
  • image-20220526135125-7.png
  • image-20220526135316-8.png
  • image-20220526135349-9.png
  • image-20220526135428-10.png
  • image-20220526135528-11.png
  • image-20220526135601-12.png
  • image-20220526135654-13.png
  • image-20220526135734-14.png
  • image-20220526135845-15.png
  • image-20220526135940-16.png
  • image-20220526140015-17.png
  • image-20220526140044-18.png
  • image-20220526140132-19.png
  • image-20220526140205-20.png
  • image-20220526140251-21.png
  • image-20220526140347-22.png
  • image-20220526140420-23.png
  • image-20220526140452-24.png
  • image-20220526140708-25.png
  • image-20220526140856-26.png
  • image-20220526140936-27.png
  • image-20220526141021-28.png
  • image-20220526141052-29.png
  • image-20220526141116-30.png
  • image-20220526141149-31.png
  • image-20220526141236-32.png
  • image-20220526141308-33.png
  • image-20220526141350-34.png
  • image-20220526141612-36.png
  • image-20220526141739-37.png
  • image-20220526141823-38.png
  • image-20220526141917-39.png
  • image-20220526141956-40.png
  • image-20220526142033-41.png

Details

Page properties

Content

...	...	@@ -1,14 +1,18 @@
1		-**~ Contents：**
	1	+**~ Table of Contents：**
2	2
3	3	{{toc/}}
4	4
5	5
	6	+
6	6	= 1. The Things Network-V3 =
7	7
8		-== 1.1 Introduction ==
9	9
10		-=== 1.1.1 What is The Things Network ===
	10	+== 1.1  Introduction ==
11	11
	12	+
	13	+=== 1.1.1  What is The Things Network ===
	14	+
	15	+
12	12	(((
13	13	The Things Network is a global collaborative Internet of Things ecosystem that creates networks, devices and solutions using LoRaWAN.
14	14	)))
...	...	@@ -15,10 +15,14 @@
15	15
16	16	(((
17	17	The Things Network runs The Things Stack Community Edition, which is a crowdsourced, open and decentralized LoRaWAN network. This network is a great way to get started testing devices, applications, and integrations, and get familiar with LoRaWAN.
	22	+
	23	+
	24	+
18	18	)))
19	19
20		-=== 1.1.2 Login or crate an account ===
	27	+=== 1.1.2  Login or crate an account ===
21	21
	29	+
22	22	(((
23	23	[[Login or create an account>>url:https://console.cloud.thethings.network/]] to get started with The Things Network and start using The Things Stack Console.
24	24	)))
...	...	@@ -25,107 +25,148 @@
25	25
26	26	(((
27	27	Once you have an account,get started by following steps for adding Gateway,Device and Intergrations.
	36	+
	37	+
	38	+
28	28	)))
29	29
30		-=== 1.1.3 List the support products and Requirements ===
	41	+=== 1.1.3  List the support products and Requirements ===
31	31
	43	+
32	32	LoRaWAN Gateway model: Existing Gateway
33	33
34		-= 2. Gateway Registration for Semtech UDP =
35	35
36		-== 2.1 Primary LoRaWAN Server ==
37	37
	48	+= 2.  Gateway Registration for Semtech UDP =
	49	+
	50	+
	51	+== 2.1  Primary LoRaWAN Server ==
	52	+
	53	+
38	38	[[image:image-20220526134633-2.png||height="616" width="1323"]]
39	39
40	40	Register Gateway
41	41
42	42
	59	+
43	43	[[image:image-20220526134826-4.png]]
44	44
45	45	Put Gateway ID
46	46
47	47
	65	+
48	48	[[image:image-20220526134759-3.png]]
49	49
50	50	Choose Frequency Band
51	51
52	52
	71	+
53	53	[[image:image-20220526134919-5.png]]
54	54
55	55	Show Status
56	56
57		-== 2.2 Secondary LoRaWAN Server ==
58	58
59		-=== 2.2.1 Introduction ===
60	60
	78	+== 2.2  Secondary LoRaWAN Server ==
	79	+
	80	+
	81	+=== 2.2.1  Introduction ===
	82	+
	83	+
61	61	The Dragino gateway has supports the Secondary server settings.
62	62
63		-=== 2.2.2 Below list the support products and Requirements: ===
64	64
	87	+
	88	+=== 2.2.2  Below list the support products and Requirements: ===
	89	+
	90	+
65	65	(((
66		-~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
	92	+1.  LoRaWAN Gateway model:  [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
67	67	)))
68	68
69	69	(((
70		-2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
	96	+2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
71	71	)))
72	72
73		-=== 2.2.3 Example ===
74	74
75		-The following takes Helium as a Secondary LoRaWAN server as an example,
76	76
77		-=== 2.2.4 Step 1: Download and Install the helium gateway-rs ===
	101	+=== 2.2.3  Example ===
78	78
	103	+
	104	+The following takes Helium as a Secondary LoRaWAN server as an example
	105	+
	106	+
	107	+
	108	+=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
	109	+
	110	+
79	79	The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
80	80
81		-[[image:image-20220525093626-7.png]]
	113	+[[image:image-20220526135049-6.png]]
82	82
83	83	Download and Install gateway-rs
84	84
85		-=== 2.2.5 Step 2: Back to Semtech UDP page ===
86	86
	118	+
	119	+=== 2.2.5  Step 2: Back to Semtech UDP page ===
	120	+
	121	+
87	87	Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
88	88
89		-​​​​[[image:image-20220525093929-1.png]]
	124	+​​​​[[image:image-20220526135125-7.png]]
90	90
91	91	Configuration of helium
92	92
93		-= 3. Gateway Registration for Basics Station =
94	94
95		-== 3.1 Introduction ==
96	96
	130	+= 3.  Gateway Registration for Basics Station =
	131	+
	132	+
	133	+== 3.1  Introduction ==
	134	+
	135	+
97	97	(((
98	98	(((
99	99	The LoRa Basics™ Station protocol simplifies management of large scale LoRaWAN networks. LoRa Basics™ Station is the preferred way of connecting Gateways to The Things Stack. [[The LoRa Basics Station doc>>url:https://www.thethingsindustries.com/docs/gateways/lora-basics-station/]]
	139	+
	140	+
100	100	)))
101	101	)))
102	102
103	103	(((
104		-**Below list the support products and Requirements:**
	145	+(% style="color:blue" %)**Below list the support products and Requirements:**
105	105	)))
106	106
107	107	(((
108	108	(((
109		- ~1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
	150	+1. LoRaWAN Gateway model: [[LIG16>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/171-lig16.html]], [[LG308>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/140-lg308.html]], [[DLOS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/160-dlos8.html]] [[LPS8>>url:http://www.dragino.com/products/lora-lorawan-gateway/item/148-lps8.html]]
110	110	)))
111	111
112	112	(((
113	113	2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
	155	+
	156	+
	157	+
	158	+
114	114	)))
115	115	)))
116	116
117	117	(((
118		-**What do you need to prepare**
	163	+(% style="color:blue" %)**What do you need to prepare**
119	119	)))
120	120
121	121	(((
122	122	(((
123	123	A gateway that can access the internet normally
	169	+
	170	+
	171	+
124	124	)))
125	125	)))
126	126
127		-== 3.2 Step 1. Add Gateway ==
	175	+== 3.2  Step 1: Add Gateway ==
128	128
	177	+
129	129	(((
130	130	(((
131	131	The example for **EU**
...	...	@@ -141,92 +141,129 @@
141	141	(((
142	142	(((
143	143	Following picture is the successful added.
	193	+
	194	+
144	144	)))
145	145	)))
146	146
147		-[[image:image-20220525094010-2.png]]
	198	+[[image:image-20220526135316-8.png]]
148	148
149	149	Add Gateway
150	150
151		-== 3.3 Step 2. Create the API key ==
152	152
	203	+
	204	+== 3.3  Step 2: Create the API key ==
	205	+
	206	+
153	153	user need to create the CUPS API key and LNS API key.
154	154
155		-[[image:image-20220525094115-3.png]]
156	156
	210	+[[image:image-20220526135349-9.png]]
	211	+
157	157	Create CUPS API key
158	158
159	159
160		-[[image:image-20220525094146-4.png]]
161	161
	216	+[[image:image-20220526135428-10.png]]
	217	+
162	162	Create LNS API key
163	163
	220	+
164	164	(% style="color:red" %)**Note : Please copy the API key.**
165	165
166		-== 3.4 Step 3. Update the gateway setting ==
167	167
	224	+
	225	+== 3.4  Step 3: Update the gateway setting ==
	226	+
	227	+
168	168	In the LoRa Basics Station LNS Authentication Key field, paste the API key you generated in the previous step.
169	169
170		-[[image:image-20220525094220-5.png]]
171	171
	231	+[[image:image-20220526135528-11.png]]
	232	+
172	172	paste the API key
173	173
174		-== 3.5 Step 4. Access the gateway GUI ==
175	175
	236	+
	237	+== 3.5  Step 4: Access the gateway GUI ==
	238	+
	239	+
176	176	User need to update the API key and install the Certificate
177	177
178		-[[image:image-20220525094257-6.png]]
179	179
	243	+[[image:image-20220526135601-12.png]]
	244	+
180	180	Access the gateway GUI
181	181
182		-== 3.6 Step 5. Configure Station ==
183	183
	248	+
	249	+== 3.6  Step 5: Configure Station ==
	250	+
	251	+
184	184	User need to input Server URI, Server CUPS Key and LNS Key, as well as install CUPS certificate.
185	185
186		-**just to clarify.**
187	187
	255	+(% style="color:blue" %)**just to clarify:**
	256	+
188	188	(% class="box" %)
189	189	(((
190		- CUPS Server URI  ~-~-> Server Adress
191		- CUPS Authorization Key         ~-~-> Server CUPS API Key
192		- LNS Authorization Key  ~-~-> Server LNS API Key
193		- CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
	259	+ CUPS Server URI  ~-~->  Server Adress
	260	+ CUPS Authorization Key         ~-~->  Server CUPS API Key
	261	+ LNS Authorization Key  ~-~->  Server LNS API Key
	262	+ CUPS certificate  ~-~->  Server CA(user can use the button to install the certificate by default)
194	194	)))
195	195
196		-[[image:image-20220525094329-7.png]]
	265	+[[image:image-20220526135654-13.png]]
197	197
198	198	Congfigure Station
199	199
200		-== 3.7 Start Station ==
201	201
	270	+
	271	+== 3.7  Start Station ==
	272	+
	273	+
202	202	(((
203	203	When the user has finished the configuration,Please click Sace&Apply to start station to connect The Things Network.
	276	+
	277	+
	278	+
204	204	)))
205	205
206		-== 3.8 Siccessful Connection ==
	281	+== 3.8  Siccessful Connection ==
207	207
	283	+
208	208	If user completes the above steps,which will see live date in the TTN.
209	209
210		-[[image:image-20220525094409-8.png]]
211	211
	287	+[[image:image-20220526135734-14.png]]
	288	+
212	212	Station live date
213	213
214		-== 3.9 Trouble Shooting ==
215	215
	292	+
	293	+== 3.9  Trouble Shooting ==
	294	+
	295	+
216	216	User can check the station log in the logread/system log page.
217	217
218		-[[image:image-20220525090622-14.png]]
219	219
	299	+[[image:image-20220526135845-15.png]]
	300	+
220	220	Station Log
221	221
	303	+
	304	+
222	222	and recode the station log in the system/Recode log page.
223	223
224		-[[image:image-20220525090705-15.png]]
	307	+[[image:image-20220526135940-16.png]]
225	225
226	226	Recore Log
227	227
228		-= 4. Configure node connection to TTNv3 =
229	229
	312	+
	313	+= 4.  Configure node connection to TTNv3 =
	314	+
	315	+
230	230	(((
231	231	(((
232	232	Following is an example for how to join the TTN v3 LoRaWAN Network.
...	...	@@ -242,11 +242,15 @@
242	242	(((
243	243	(((
244	244	We take LES01 as an example.
	331	+
	332	+
	333	+
245	245	)))
246	246	)))
247	247
248		-== 4.1 Step1 ==
	337	+== 4.1  Step1 ==
249	249
	339	+
250	250	(((
251	251	(((
252	252	Create a device in TTN with the OTAA keys from LSE01.
...	...	@@ -265,44 +265,65 @@
265	265	)))
266	266	)))
267	267
268		-[[image:image-20220525090739-16.png]]
	358	+[[image:image-20220526140015-17.png]]
269	269
270		-[[image:image-20220525090833-17.png]]
	360	+[[image:image-20220526140044-18.png]]
271	271
272		-== 4.2 Step2 ==
273	273
	363	+
	364	+== 4.2  Step2 ==
	365	+
	366	+
274	274	(((
275	275	(((
276	276	There are all our nodes in the repository. Users can choose the corresponding brand, model, firmware version and frequency.The decoder and configuration information of the node are pre-configured.Users do not need to configure them.
	370	+
	371	+
277	277	)))
278	278	)))
279	279
280		-[[image:image-20220525090920-18.png]]
	375	+[[image:image-20220526140132-19.png]]
281	281
282		-== 4.3 Step3 ==
283	283
	378	+
	379	+== 4.3  Step3 ==
	380	+
	381	+
284	284	Add APP EUI in the application:
285	285
286		-[[image:image-20220525091022-19.png]]
287	287
288		-== 4.4 Step4 ==
	385	+[[image:image-20220526140205-20.png]]
289	289
	387	+
	388	+
	389	+== 4.4  Step4 ==
	390	+
	391	+
290	290	Add APP KEY and DEV EUI:
291	291
292		-[[image:image-20220525091128-20.png]]
293	293
294		-= 5. TTN V3 integrated into MQTT server =
	395	+[[image:image-20220526140251-21.png]]
295	295
296		-== 5.1 Introduction ==
297	297
	398	+
	399	+= 5.  TTN V3 integrated into MQTT server =
	400	+
	401	+
	402	+== 5.1  Introduction ==
	403	+
	404	+
298	298	(((
299	299	(((
300	300	The Application Server exposes an MQTT server to work with streaming events. In order to use the MQTT server you need to create a new API key, which will function as connection password. You can also use an existing API key, as long as it has the necessary rights granted.
	408	+
	409	+
	410	+
301	301	)))
302	302	)))
303	303
304		-== 5.2 Create device steps at MQTT ==
	414	+== 5.2  Create device steps at MQTT ==
305	305
	416	+
306	306	(((
307	307	(((
308	308	The user creates a new API KEY after creating a device on TTN V3.
...	...	@@ -318,16 +318,20 @@
318	318	(((
319	319	(((
320	320	Fill in Broker Address and Broker port.
	432	+
	433	+
321	321	)))
322	322	)))
323	323
324		-[[image:image-20220525091251-22.png]]
	437	+[[image:image-20220526140347-22.png]]
325	325
326	326	Fill in the username and password into MQTT.
327	327
328	328
329		-[[image:image-20220525091333-23.png]]
330	330
	443	+[[image:image-20220526140420-23.png]]
	444	+
	445	+
331	331	The Application Server publishes uplink traffic on the following topics:
332	332
333	333	(% class="box" %)
...	...	@@ -344,13 +344,18 @@
344	344	)))
345	345
346	346	(((
	462	+
	463	+
347	347	(((
348		-**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
	465	+(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
	466	+
	467	+
349	349	)))
350	350	)))
351	351
352		-[[image:image-20220525091430-24.png]]
	471	+[[image:image-20220526140452-24.png]]
353	353
	473	+
354	354	(((
355	355	(((
356	356	While you could subscribe to all of these topics separately, for the simplicity of this tutorial we use # to subscribe to all topics, i.e. to receive all uplink traffic.
...	...	@@ -357,7 +357,7 @@
357	357	)))
358	358	)))
359	359
360		-[[image:image-20220525091458-25.png]]
	480	+[[image:image-20220526140708-25.png]]
361	361
362	362	(((
363	363	(((
...	...	@@ -367,7 +367,11 @@
367	367
368	368	(((
369	369	(((
370		-**Note**: Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.
	490	+
	491	+
	492	+(% style="color:red" %)**Note**: **Remember that the format of this topic for The Things Stack Open Source deployment would be v3/{application id}/devices/{device id}/down/push.**
	493	+
	494	+
371	371	)))
372	372	)))
373	373
...	...	@@ -377,20 +377,27 @@
377	377	)))
378	378	)))
379	379
380		-[[image:image-20220525091618-27.png]]
	504	+[[image:image-20220526140856-26.png]]
381	381
382	382	(((
383	383	To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
	508	+
	509	+
384	384	)))
385	385
386	386	(((
387		-**Note**: Use this handy tool to convert hexadecimal to base64.
	513	+(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
	514	+
	515	+
388	388	)))
389	389
390		-[[image:image-20220525091702-28.png]]
	518	+[[image:image-20220526140936-27.png]]
391	391
392		-== 5.3 Send Downlink message ==
393	393
	521	+
	522	+== 5.3  Send Downlink message ==
	523	+
	524	+
394	394	(((
395	395	How to configure downlink in TTN V3?
396	396	)))
...	...	@@ -400,31 +400,40 @@
400	400	)))
401	401
402	402	(((
403		-Downlink command:01 00 00 5A
	534	+(% style="color:blue" %)**Downlink command: 01 00 00 5A**
	535	+
	536	+
404	404	)))
405	405
406		-[[image:image-20220525091752-29.png]]
	539	+[[image:image-20220526141021-28.png]]
407	407
408	408	downlink
409	409
	543	+
	544	+
410	410	After sending, you can view it in live data.
411	411
412		-[[image:image-20220525091816-30.png]]
	547	+[[image:image-20220526141052-29.png]]
413	413
414	414	downlink
415	415
	551	+
	552	+
416	416	(((
417	417	When downlink is successfully sent, the downlink information can be received on the serial port.
418	418	)))
419	419
420	420	(((
421		-**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
	558	+(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
	559	+
	560	+
422	422	)))
423	423
424		-[[image:image-20220525091855-31.png]]
	563	+[[image:image-20220526141116-30.png]]
425	425
426	426	downlink
427	427
	567	+
428	428	(((
429	429	(((
430	430	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
...	...	@@ -433,13 +433,13 @@
433	433
434	434	(((
435	435	(((
436		-If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
	576	+If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
437	437	)))
438	438	)))
439	439
440	440	(((
441	441	(((
442		-If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
	582	+If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
443	443	)))
444	444	)))
445	445
...	...	@@ -446,15 +446,20 @@
446	446	(((
447	447	(((
448	448	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
	589	+
	590	+
449	449	)))
450	450	)))
451	451
452		-[[image:image-20220525091925-32.png]]
	594	+[[image:image-20220526141149-31.png]]
453	453
454	454	downlink
455	455
456		-= 6. Request Remote Support =
457	457
	599	+
	600	+= 6.  Request Remote Support =
	601	+
	602	+
458	458	(((
459	459	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.
460	460	\\If problem not solve, and you need dragino remote support, please follow to this document: [[TTN Support instruction>>url:https://www.dragino.com/downloads/index.php?dir=&file=TTNv3_Support_Guide.pdf]](% style="color:red" %) **If user has checked below steps and still can't solve the problem, please send us (support @ dragino.com) the screenshots for each step to check. They include:**
...	...	@@ -466,39 +466,51 @@
466	466	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
467	467	* End Node Keys screen shot shows in end node and server. so we can check if the keys are correct. (In most case, we found keys doesn't match, especially APP EUI)
468	468
469		-**~1. End Device Join Screen shot, we can check:**
470	470
	615	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	616	+
471	471	* If the device is sending join request to server?
472	472	* What frequency the device is sending?
473	473
474		-[[image:image-20220525092012-33.png]]
475	475
	621	+[[image:image-20220526141308-33.png]]
	622	+
476	476	Console Output from End device to see the transmit frequency
477	477
478		-User can run **AT+CFG **command to print configuration information.
479	479
480		-* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
	626	+User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
481	481
482		-[[image:image-20220525092043-34.png]]
	628	+* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
483	483
	630	+
	631	+
	632	+[[image:image-20220526141612-36.png]]
	633	+
	634	+
484	484	Console Output from End device to see the transmit frequency
485	485
486		-**2. Gateway packet traffic in gateway web or ssh. we can check:**
487	487
	638	+
	639	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
	640	+
488	488	* (((
489	489	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
490	490	)))
491	491	* (((
492	492	If the gateway gets the Join Accept message from server and transmit it via LoRa?
	646	+
	647	+
	648	+
493	493	)))
494	494
495		-[[image:image-20220525092124-35.png]]
	651	+[[image:image-20220526141739-37.png]]
496	496
497	497	Console Output from Gateway to see packets between end node and server.
498	498
499	499
500		-**3. Gateway Traffic Page in LoRaWAN Server**
501	501
	657	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	658	+
502	502	* (((
503	503	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
504	504	)))
...	...	@@ -507,25 +507,32 @@
507	507	)))
508	508	* (((
509	509	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.
	667	+
	668	+
	669	+
510	510	)))
511	511
512		-[[image:image-20220525092157-36.png]]
	672	+[[image:image-20220526141823-38.png||height="501" width="1144"]]
513	513
514	514	The Traffic for the End node in the server, use TTNv3 as example
515	515
516	516
517		-[[image:image-20220525092231-37.png]]
518	518
	678	+[[image:image-20220526141917-39.png]]
	679	+
519	519	The Traffic for the End node in the server, use TTNv3 as example
520	520
521		-**4. Data Page in LoRaWAN server**
522	522
	683	+
	684	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
	685	+
523	523	(((
524	524	(((
525	525	(((
526	526	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.
527	527
528		-[[image:image-20220525092546-1.png]]
	691	+
	692	+[[image:image-20220526141956-40.png]]
529	529	)))
530	530	)))
531	531	)))
...	...	@@ -532,6 +532,8 @@
532	532
533	533	The data for the end device set in server
534	534
535		-[[image:image-20220525092430-40.png]]
536	536
	700	+
	701	+[[image:image-20220526142033-41.png]]
	702	+
537	537	Check if OTAA Keys match the keys in device

image-20220526135125-7.png

Author

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

Size

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

Content

image-20220526135316-8.png

Author

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

Size

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

Content

image-20220526135349-9.png

Author

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

Size

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

Content

image-20220526135428-10.png

Author

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

Size

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

Content

image-20220526135528-11.png

Author

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

Size

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

Content

image-20220526135601-12.png

Author

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

Size

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

Content

image-20220526135654-13.png

Author

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

Size

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

Content

image-20220526135734-14.png

Author

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

Size

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

Content

image-20220526135845-15.png

Author

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

Size

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

Content

image-20220526135940-16.png

Author

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

Size

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

Content

image-20220526140015-17.png

Author

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

Size

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

Content

image-20220526140044-18.png

Author

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

Size

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

Content

image-20220526140132-19.png

Author

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

Size

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

Content

image-20220526140205-20.png

Author

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

Size

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

Content

image-20220526140251-21.png

Author

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

Size

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

Content

image-20220526140347-22.png

Author

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

Size

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

Content

image-20220526140420-23.png

Author

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

Size

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

Content

image-20220526140452-24.png

Author

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

Size

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

Content

image-20220526140708-25.png

Author

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

Size

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

Content

image-20220526140856-26.png

Author

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

Size

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

Content

image-20220526140936-27.png

Author

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

Size

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

Content

image-20220526141021-28.png

Author

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

Size

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

Content

image-20220526141052-29.png

Author

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

Size

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

Content

image-20220526141116-30.png

Author

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

Size

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

Content

image-20220526141149-31.png

Author

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

Size

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

Content

image-20220526141236-32.png

Author

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

Size

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

Content

image-20220526141308-33.png

Author

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

Size

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

Content

image-20220526141350-34.png

Author

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

Size

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

Content

image-20220526141612-36.png

Author

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

Size

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

Content

image-20220526141739-37.png

Author

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

Size

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

Content

image-20220526141823-38.png

Author

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

Size

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

Content

image-20220526141917-39.png

Author

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

Size

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

Content

image-20220526141956-40.png

Author

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

Size

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

Content

image-20220526142033-41.png

Author

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

Size

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

Content