Summary

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

Details

Page properties

Content

...	...	@@ -123,22 +123,16 @@
123	123	== 3.2 Step 1. Add Gateway ==
124	124
125	125	(((
126		-(((
127	127	The example for **EU**
128	128	)))
129		-)))
130	130
131	131	(((
132		-(((
133	133	User can add your gateway into The Things Network V3 according to the previous step
134	134	)))
135		-)))
136	136
137	137	(((
138		-(((
139	139	Following picture is the successful added.
140	140	)))
141		-)))
142	142
143	143	[[image:https://wiki.dragino.com/images/thumb/5/5f/Add_gateway_1.1.png/600px-Add_gateway_1.1.png||height="397" width="600"]]
144	144
...	...	@@ -157,7 +157,7 @@
157	157
158	158	Create LNS API key
159	159
160		-(% style="color:red" %)**Note : Please copy the API key.**
	154	+**Note : Please copy the API key.**
161	161
162	162	== 3.4 Step 3. Update the gateway setting ==
163	163
...	...	@@ -181,13 +181,11 @@
181	181
182	182	**just to clarify.**
183	183
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		-)))
	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	+}}}
191	191
192	192	[[image:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png||height="321" width="600"]]
193	193
...	...	@@ -224,42 +224,30 @@
224	224	= 4. Configure node connection to TTNv3 =
225	225
226	226	(((
227		-(((
228	228	Following is an example for how to join the TTN v3 LoRaWAN Network.
229	229	)))
230		-)))
231	231
232	232	(((
233		-(((
234	234	The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
235	235	)))
236		-)))
237	237
238	238	(((
239		-(((
240	240	We take LES01 as an example.
241	241	)))
242		-)))
243	243
244	244	== 4.1 Step1 ==
245	245
246	246	(((
247		-(((
248	248	Create a device in TTN with the OTAA keys from LSE01.
249	249	)))
250		-)))
251	251
252	252	(((
253		-(((
254	254	Each LSE01 is shipped with a sticker with the default device EUI as below:
255	255	)))
256		-)))
257	257
258	258	(((
259		-(((
260	260	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
261	261	)))
262		-)))
263	263
264	264	[[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png||alt="TTNv3--01.png" height="277" width="600"]]
265	265
...	...	@@ -268,10 +268,8 @@
268	268	== 4.2 Step2 ==
269	269
270	270	(((
271		-(((
272	272	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.
273	273	)))
274		-)))
275	275
276	276	[[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png||alt="TTNv3--03.png" height="333" width="600"]]
277	277
...	...	@@ -292,30 +292,22 @@
292	292	== 5.1 Introduction ==
293	293
294	294	(((
295		-(((
296	296	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.
297	297	)))
298		-)))
299	299
300	300	== 5.2 Create device steps at MQTT ==
301	301
302	302	(((
303		-(((
304	304	The user creates a new API KEY after creating a device on TTN V3.
305	305	)))
306		-)))
307	307
308	308	(((
309		-(((
310	310	Then copy the password and open MQTT.fx.
311	311	)))
312		-)))
313	313
314	314	(((
315		-(((
316	316	Fill in Broker Address and Broker port.
317	317	)))
318		-)))
319	319
320	320	[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
321	321
...	...	@@ -326,9 +326,7 @@
326	326
327	327	The Application Server publishes uplink traffic on the following topics:
328	328
329		-(% class="box" %)
330		-(((
331		- v3/{application id}@{tenant id}/devices/{device id}/join
	299	+{{{ v3/{application id}@{tenant id}/devices/{device id}/join
332	332	v3/{application id}@{tenant id}/devices/{device id}/up
333	333	v3/{application id}@{tenant id}/devices/{device id}/down/queued
334	334	v3/{application id}@{tenant id}/devices/{device id}/down/sent
...	...	@@ -337,41 +337,31 @@
337	337	v3/{application id}@{tenant id}/devices/{device id}/down/failed
338	338	v3/{application id}@{tenant id}/devices/{device id}/service/data
339	339	v3/{application id}@{tenant id}/devices/{device id}/location/solved
340		-)))
	308	+}}}
341	341
342	342	(((
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}.
	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}.
345	345	)))
346		-)))
347	347
348	348	[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
349	349
350	350	(((
351		-(((
352	352	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.
353	353	)))
354		-)))
355	355
356	356	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
357	357
358	358	(((
359		-(((
360	360	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
361	361	)))
362		-)))
363	363
364	364	(((
365		-(((
366	366	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.
367	367	)))
368		-)))
369	369
370	370	(((
371		-(((
372	372	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
373	373	)))
374		-)))
375	375
376	376	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
377	377
...	...	@@ -454,6 +454,7 @@
454	454	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
455	455	* 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)
456	456
	415	+
457	457	**~1. End Device Join Screen shot, we can check:**
458	458
459	459	* If the device is sending join request to server?
...	...	@@ -483,15 +483,9 @@
483	483
484	484	**3. Gateway Traffic Page in LoRaWAN Server**
485	485
486		-* (((
487		-If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
488		-)))
489		-* (((
490		-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.
491		-)))
492		-* (((
493		-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.
494		-)))
	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.
495	495
496	496	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
497	497
...	...	@@ -505,10 +505,8 @@
505	505	**4. Data Page in LoRaWAN server**
506	506
507	507	* (((
508		-(((
509	509	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.
510	510	)))
511		-)))
512	512
513	513	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
514	514