Summary

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

Details

Page properties

Content

...	...	@@ -1,5 +1,6 @@
1		-**Contents：**
	1	+**~ Contents：**
2	2
	3	+{{toc/}}
3	3
4	4
5	5	= 1. The Things Network-V3 =
...	...	@@ -90,38 +90,54 @@
90	90	== 3.1 Introduction ==
91	91
92	92	(((
	94	+(((
93	93	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/]]
94	94	)))
	97	+)))
95	95
	99	+(((
96	96	**Below list the support products and Requirements:**
	101	+)))
97	97
98		-1. (((
99		-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]]
	103	+(((
	104	+(((
	105	+ ~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]]
100	100	)))
101	101
102		-1. (((
103		-Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
	108	+(((
	109	+ 2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
104	104	)))
	111	+)))
105	105
	113	+(((
106	106	**What do you need to prepare**
	115	+)))
107	107
108	108	(((
	118	+(((
109	109	A gateway that can access the internet normally
110	110	)))
	121	+)))
111	111
112	112	== 3.2 Step 1. Add Gateway ==
113	113
114	114	(((
	126	+(((
115	115	The example for **EU**
116	116	)))
	129	+)))
117	117
118	118	(((
	132	+(((
119	119	User can add your gateway into The Things Network V3 according to the previous step
120	120	)))
	135	+)))
121	121
122	122	(((
	138	+(((
123	123	Following picture is the successful added.
124	124	)))
	141	+)))
125	125
126	126	[[image:https://wiki.dragino.com/images/thumb/5/5f/Add_gateway_1.1.png/600px-Add_gateway_1.1.png||height="397" width="600"]]
127	127
...	...	@@ -140,7 +140,7 @@
140	140
141	141	Create LNS API key
142	142
143		-**Note : Please copy the API key.**
	160	+(% style="color:red" %)**Note : Please copy the API key.**
144	144
145	145	== 3.4 Step 3. Update the gateway setting ==
146	146
...	...	@@ -164,11 +164,13 @@
164	164
165	165	**just to clarify.**
166	166
167		-{{{ CUPS Server URI --> Server Adress
168		- CUPS Authorization Key --> Server CUPS API Key
169		- LNS Authorization Key --> Server LNS API Key
170		- CUPS certificate --> Server CA(user can use the button to install the certificate by default)
171		-}}}
	184	+(% class="box" %)
	185	+(((
	186	+ CUPS Server URI  ~-~-> Server Adress
	187	+ CUPS Authorization Key         ~-~-> Server CUPS API Key
	188	+ LNS Authorization Key  ~-~-> Server LNS API Key
	189	+ CUPS certificate  ~-~-> Server CA(user can use the button to install the certificate by default)
	190	+)))
172	172
173	173	[[image:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png||height="321" width="600"]]
174	174
...	...	@@ -205,30 +205,42 @@
205	205	= 4. Configure node connection to TTNv3 =
206	206
207	207	(((
	227	+(((
208	208	Following is an example for how to join the TTN v3 LoRaWAN Network.
209	209	)))
	230	+)))
210	210
211	211	(((
	233	+(((
212	212	The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
213	213	)))
	236	+)))
214	214
215	215	(((
	239	+(((
216	216	We take LES01 as an example.
217	217	)))
	242	+)))
218	218
219	219	== 4.1 Step1 ==
220	220
221	221	(((
	247	+(((
222	222	Create a device in TTN with the OTAA keys from LSE01.
223	223	)))
	250	+)))
224	224
225	225	(((
	253	+(((
226	226	Each LSE01 is shipped with a sticker with the default device EUI as below:
227	227	)))
	256	+)))
228	228
229	229	(((
	259	+(((
230	230	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
231	231	)))
	262	+)))
232	232
233	233	[[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png||alt="TTNv3--01.png" height="277" width="600"]]
234	234
...	...	@@ -237,8 +237,10 @@
237	237	== 4.2 Step2 ==
238	238
239	239	(((
	271	+(((
240	240	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.
241	241	)))
	274	+)))
242	242
243	243	[[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png||alt="TTNv3--03.png" height="333" width="600"]]
244	244
...	...	@@ -259,22 +259,30 @@
259	259	== 5.1 Introduction ==
260	260
261	261	(((
	295	+(((
262	262	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.
263	263	)))
	298	+)))
264	264
265	265	== 5.2 Create device steps at MQTT ==
266	266
267	267	(((
	303	+(((
268	268	The user creates a new API KEY after creating a device on TTN V3.
269	269	)))
	306	+)))
270	270
271	271	(((
	309	+(((
272	272	Then copy the password and open MQTT.fx.
273	273	)))
	312	+)))
274	274
275	275	(((
	315	+(((
276	276	Fill in Broker Address and Broker port.
277	277	)))
	318	+)))
278	278
279	279	[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
280	280
...	...	@@ -285,7 +285,9 @@
285	285
286	286	The Application Server publishes uplink traffic on the following topics:
287	287
288		-{{{ v3/{application id}@{tenant id}/devices/{device id}/join
	329	+(% class="box" %)
	330	+(((
	331	+ v3/{application id}@{tenant id}/devices/{device id}/join
289	289	v3/{application id}@{tenant id}/devices/{device id}/up
290	290	v3/{application id}@{tenant id}/devices/{device id}/down/queued
291	291	v3/{application id}@{tenant id}/devices/{device id}/down/sent
...	...	@@ -294,31 +294,41 @@
294	294	v3/{application id}@{tenant id}/devices/{device id}/down/failed
295	295	v3/{application id}@{tenant id}/devices/{device id}/service/data
296	296	v3/{application id}@{tenant id}/devices/{device id}/location/solved
297		-}}}
	340	+)))
298	298
299	299	(((
300		-Note: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
	343	+(((
	344	+**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
301	301	)))
	346	+)))
302	302
303	303	[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
304	304
305	305	(((
	351	+(((
306	306	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.
307	307	)))
	354	+)))
308	308
309	309	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
310	310
311	311	(((
	359	+(((
312	312	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
313	313	)))
	362	+)))
314	314
315	315	(((
	365	+(((
316	316	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.
317	317	)))
	368	+)))
318	318
319	319	(((
	371	+(((
320	320	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
321	321	)))
	374	+)))
322	322
323	323	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
324	324
...	...	@@ -369,20 +369,28 @@
369	369	downlink
370	370
371	371	(((
	425	+(((
372	372	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
373	373	)))
	428	+)))
374	374
375	375	(((
	431	+(((
376	376	If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
377	377	)))
	434	+)))
378	378
379	379	(((
	437	+(((
380	380	If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
381	381	)))
	440	+)))
382	382
383	383	(((
	443	+(((
384	384	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
385	385	)))
	446	+)))
386	386
387	387	[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png||height="127" width="600"]]
388	388
...	...	@@ -392,7 +392,7 @@
392	392
393	393	(((
394	394	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.
395		-\\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]] 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:
	456	+\\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:**
396	396	)))
397	397
398	398	* End node is connected to serial port to show the Join frequency and DR. (If possible)
...	...	@@ -401,7 +401,6 @@
401	401	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
402	402	* 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)
403	403
404		-
405	405	**~1. End Device Join Screen shot, we can check:**
406	406
407	407	* If the device is sending join request to server?
...	...	@@ -421,8 +421,12 @@
421	421
422	422	**2. Gateway packet traffic in gateway web or ssh. we can check:**
423	423
424		-* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
425		-* If the gateway gets the Join Accept message from server and transmit it via LoRa?
	484	+* (((
	485	+If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
	486	+)))
	487	+* (((
	488	+If the gateway gets the Join Accept message from server and transmit it via LoRa?
	489	+)))
426	426
427	427	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
428	428
...	...	@@ -431,9 +431,15 @@
431	431
432	432	**3. Gateway Traffic Page in LoRaWAN Server**
433	433
434		-* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
435		-* If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
436		-* 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.
	498	+* (((
	499	+If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	500	+)))
	501	+* (((
	502	+If the server send back a Join Accept for the Join Request? if not, check if the keys from the device match the keys you put in the server, or try to choose a different server route for this end device.
	503	+)))
	504	+* (((
	505	+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.
	506	+)))
437	437
438	438	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
439	439
...	...	@@ -447,8 +447,10 @@
447	447	**4. Data Page in LoRaWAN server**
448	448
449	449	* (((
	520	+(((
450	450	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.
451	451	)))
	523	+)))
452	452
453	453	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
454	454