Summary

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

Details

Page properties

Content

...	...	@@ -123,16 +123,22 @@
123	123	== 3.2 Step 1. Add Gateway ==
124	124
125	125	(((
	126	+(((
126	126	The example for **EU**
127	127	)))
	129	+)))
128	128
129	129	(((
	132	+(((
130	130	User can add your gateway into The Things Network V3 according to the previous step
131	131	)))
	135	+)))
132	132
133	133	(((
	138	+(((
134	134	Following picture is the successful added.
135	135	)))
	141	+)))
136	136
137	137	[[image:https://wiki.dragino.com/images/thumb/5/5f/Add_gateway_1.1.png/600px-Add_gateway_1.1.png||height="397" width="600"]]
138	138
...	...	@@ -151,7 +151,7 @@
151	151
152	152	Create LNS API key
153	153
154		-**Note : Please copy the API key.**
	160	+(% style="color:red" %)**Note : Please copy the API key.**
155	155
156	156	== 3.4 Step 3. Update the gateway setting ==
157	157
...	...	@@ -175,11 +175,13 @@
175	175
176	176	**just to clarify.**
177	177
178		-{{{ CUPS Server URI --> Server Adress
179		- CUPS Authorization Key --> Server CUPS API Key
180		- LNS Authorization Key --> Server LNS API Key
181		- CUPS certificate --> Server CA(user can use the button to install the certificate by default)
182		-}}}
	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	+)))
183	183
184	184	[[image:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png||height="321" width="600"]]
185	185
...	...	@@ -216,30 +216,42 @@
216	216	= 4. Configure node connection to TTNv3 =
217	217
218	218	(((
	227	+(((
219	219	Following is an example for how to join the TTN v3 LoRaWAN Network.
220	220	)))
	230	+)))
221	221
222	222	(((
	233	+(((
223	223	The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
224	224	)))
	236	+)))
225	225
226	226	(((
	239	+(((
227	227	We take LES01 as an example.
228	228	)))
	242	+)))
229	229
230	230	== 4.1 Step1 ==
231	231
232	232	(((
	247	+(((
233	233	Create a device in TTN with the OTAA keys from LSE01.
234	234	)))
	250	+)))
235	235
236	236	(((
	253	+(((
237	237	Each LSE01 is shipped with a sticker with the default device EUI as below:
238	238	)))
	256	+)))
239	239
240	240	(((
	259	+(((
241	241	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
242	242	)))
	262	+)))
243	243
244	244	[[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png||alt="TTNv3--01.png" height="277" width="600"]]
245	245
...	...	@@ -248,8 +248,10 @@
248	248	== 4.2 Step2 ==
249	249
250	250	(((
	271	+(((
251	251	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.
252	252	)))
	274	+)))
253	253
254	254	[[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png||alt="TTNv3--03.png" height="333" width="600"]]
255	255
...	...	@@ -270,22 +270,30 @@
270	270	== 5.1 Introduction ==
271	271
272	272	(((
	295	+(((
273	273	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.
274	274	)))
	298	+)))
275	275
276	276	== 5.2 Create device steps at MQTT ==
277	277
278	278	(((
	303	+(((
279	279	The user creates a new API KEY after creating a device on TTN V3.
280	280	)))
	306	+)))
281	281
282	282	(((
	309	+(((
283	283	Then copy the password and open MQTT.fx.
284	284	)))
	312	+)))
285	285
286	286	(((
	315	+(((
287	287	Fill in Broker Address and Broker port.
288	288	)))
	318	+)))
289	289
290	290	[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
291	291
...	...	@@ -296,7 +296,9 @@
296	296
297	297	The Application Server publishes uplink traffic on the following topics:
298	298
299		-{{{ v3/{application id}@{tenant id}/devices/{device id}/join
	329	+(% class="box" %)
	330	+(((
	331	+ v3/{application id}@{tenant id}/devices/{device id}/join
300	300	v3/{application id}@{tenant id}/devices/{device id}/up
301	301	v3/{application id}@{tenant id}/devices/{device id}/down/queued
302	302	v3/{application id}@{tenant id}/devices/{device id}/down/sent
...	...	@@ -305,31 +305,41 @@
305	305	v3/{application id}@{tenant id}/devices/{device id}/down/failed
306	306	v3/{application id}@{tenant id}/devices/{device id}/service/data
307	307	v3/{application id}@{tenant id}/devices/{device id}/location/solved
308		-}}}
	340	+)))
309	309
310	310	(((
311		-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}.
312	312	)))
	346	+)))
313	313
314	314	[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
315	315
316	316	(((
	351	+(((
317	317	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.
318	318	)))
	354	+)))
319	319
320	320	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
321	321
322	322	(((
	359	+(((
323	323	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
324	324	)))
	362	+)))
325	325
326	326	(((
	365	+(((
327	327	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.
328	328	)))
	368	+)))
329	329
330	330	(((
	371	+(((
331	331	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
332	332	)))
	374	+)))
333	333
334	334	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
335	335
...	...	@@ -380,20 +380,28 @@
380	380	downlink
381	381
382	382	(((
	425	+(((
383	383	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
384	384	)))
	428	+)))
385	385
386	386	(((
	431	+(((
387	387	If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
388	388	)))
	434	+)))
389	389
390	390	(((
	437	+(((
391	391	If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
392	392	)))
	440	+)))
393	393
394	394	(((
	443	+(((
395	395	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
396	396	)))
	446	+)))
397	397
398	398	[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png||height="127" width="600"]]
399	399
...	...	@@ -403,7 +403,7 @@
403	403
404	404	(((
405	405	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.
406		-\\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:**
407	407	)))
408	408
409	409	* End node is connected to serial port to show the Join frequency and DR. (If possible)
...	...	@@ -412,7 +412,6 @@
412	412	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
413	413	* 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)
414	414
415		-
416	416	**~1. End Device Join Screen shot, we can check:**
417	417
418	418	* If the device is sending join request to server?
...	...	@@ -432,8 +432,12 @@
432	432
433	433	**2. Gateway packet traffic in gateway web or ssh. we can check:**
434	434
435		-* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
436		-* 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	+)))
437	437
438	438	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
439	439
...	...	@@ -442,9 +442,15 @@
442	442
443	443	**3. Gateway Traffic Page in LoRaWAN Server**
444	444
445		-* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
446		-* 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.
447		-* 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	+)))
448	448
449	449	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
450	450
...	...	@@ -458,8 +458,10 @@
458	458	**4. Data Page in LoRaWAN server**
459	459
460	460	* (((
	520	+(((
461	461	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.
462	462	)))
	523	+)))
463	463
464	464	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
465	465