Summary

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

Details

Page properties

Content

...	...	@@ -224,30 +224,42 @@
224	224	= 4. Configure node connection to TTNv3 =
225	225
226	226	(((
	227	+(((
227	227	Following is an example for how to join the TTN v3 LoRaWAN Network.
228	228	)))
	230	+)))
229	229
230	230	(((
	233	+(((
231	231	The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
232	232	)))
	236	+)))
233	233
234	234	(((
	239	+(((
235	235	We take LES01 as an example.
236	236	)))
	242	+)))
237	237
238	238	== 4.1 Step1 ==
239	239
240	240	(((
	247	+(((
241	241	Create a device in TTN with the OTAA keys from LSE01.
242	242	)))
	250	+)))
243	243
244	244	(((
	253	+(((
245	245	Each LSE01 is shipped with a sticker with the default device EUI as below:
246	246	)))
	256	+)))
247	247
248	248	(((
	259	+(((
249	249	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
250	250	)))
	262	+)))
251	251
252	252	[[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png||alt="TTNv3--01.png" height="277" width="600"]]
253	253
...	...	@@ -256,8 +256,10 @@
256	256	== 4.2 Step2 ==
257	257
258	258	(((
	271	+(((
259	259	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.
260	260	)))
	274	+)))
261	261
262	262	[[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png||alt="TTNv3--03.png" height="333" width="600"]]
263	263
...	...	@@ -278,22 +278,30 @@
278	278	== 5.1 Introduction ==
279	279
280	280	(((
	295	+(((
281	281	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.
282	282	)))
	298	+)))
283	283
284	284	== 5.2 Create device steps at MQTT ==
285	285
286	286	(((
	303	+(((
287	287	The user creates a new API KEY after creating a device on TTN V3.
288	288	)))
	306	+)))
289	289
290	290	(((
	309	+(((
291	291	Then copy the password and open MQTT.fx.
292	292	)))
	312	+)))
293	293
294	294	(((
	315	+(((
295	295	Fill in Broker Address and Broker port.
296	296	)))
	318	+)))
297	297
298	298	[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
299	299
...	...	@@ -304,7 +304,9 @@
304	304
305	305	The Application Server publishes uplink traffic on the following topics:
306	306
307		-{{{ v3/{application id}@{tenant id}/devices/{device id}/join
	329	+(% class="box" %)
	330	+(((
	331	+ v3/{application id}@{tenant id}/devices/{device id}/join
308	308	v3/{application id}@{tenant id}/devices/{device id}/up
309	309	v3/{application id}@{tenant id}/devices/{device id}/down/queued
310	310	v3/{application id}@{tenant id}/devices/{device id}/down/sent
...	...	@@ -313,31 +313,41 @@
313	313	v3/{application id}@{tenant id}/devices/{device id}/down/failed
314	314	v3/{application id}@{tenant id}/devices/{device id}/service/data
315	315	v3/{application id}@{tenant id}/devices/{device id}/location/solved
316		-}}}
	340	+)))
317	317
318	318	(((
319		-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}.
320	320	)))
	346	+)))
321	321
322	322	[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
323	323
324	324	(((
	351	+(((
325	325	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.
326	326	)))
	354	+)))
327	327
328	328	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
329	329
330	330	(((
	359	+(((
331	331	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
332	332	)))
	362	+)))
333	333
334	334	(((
	365	+(((
335	335	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.
336	336	)))
	368	+)))
337	337
338	338	(((
	371	+(((
339	339	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
340	340	)))
	374	+)))
341	341
342	342	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
343	343
...	...	@@ -388,20 +388,28 @@
388	388	downlink
389	389
390	390	(((
	425	+(((
391	391	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
392	392	)))
	428	+)))
393	393
394	394	(((
	431	+(((
395	395	If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
396	396	)))
	434	+)))
397	397
398	398	(((
	437	+(((
399	399	If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
400	400	)))
	440	+)))
401	401
402	402	(((
	443	+(((
403	403	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
404	404	)))
	446	+)))
405	405
406	406	[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png||height="127" width="600"]]
407	407
...	...	@@ -411,7 +411,7 @@
411	411
412	412	(((
413	413	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.
414		-\\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:**
415	415	)))
416	416
417	417	* End node is connected to serial port to show the Join frequency and DR. (If possible)
...	...	@@ -439,8 +439,12 @@
439	439
440	440	**2. Gateway packet traffic in gateway web or ssh. we can check:**
441	441
442		-* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
443		-* 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	+)))
444	444
445	445	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
446	446
...	...	@@ -449,9 +449,15 @@
449	449
450	450	**3. Gateway Traffic Page in LoRaWAN Server**
451	451
452		-* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
453		-* 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.
454		-* 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	+)))
455	455
456	456	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
457	457
...	...	@@ -465,8 +465,10 @@
465	465	**4. Data Page in LoRaWAN server**
466	466
467	467	* (((
	520	+(((
468	468	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.
469	469	)))
	523	+)))
470	470
471	471	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
472	472