Summary

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

Details

Page properties

Content

...	...	@@ -91,38 +91,54 @@
91	91	== 3.1 Introduction ==
92	92
93	93	(((
	94	+(((
94	94	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/]]
95	95	)))
	97	+)))
96	96
	99	+(((
97	97	**Below list the support products and Requirements:**
	101	+)))
98	98
99		-1. (((
100		-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]]
101	101	)))
102	102
103		-1. (((
104		-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/]]
105	105	)))
	111	+)))
106	106
	113	+(((
107	107	**What do you need to prepare**
	115	+)))
108	108
109	109	(((
	118	+(((
110	110	A gateway that can access the internet normally
111	111	)))
	121	+)))
112	112
113	113	== 3.2 Step 1. Add Gateway ==
114	114
115	115	(((
	126	+(((
116	116	The example for **EU**
117	117	)))
	129	+)))
118	118
119	119	(((
	132	+(((
120	120	User can add your gateway into The Things Network V3 according to the previous step
121	121	)))
	135	+)))
122	122
123	123	(((
	138	+(((
124	124	Following picture is the successful added.
125	125	)))
	141	+)))
126	126
127	127	[[image:https://wiki.dragino.com/images/thumb/5/5f/Add_gateway_1.1.png/600px-Add_gateway_1.1.png||height="397" width="600"]]
128	128
...	...	@@ -141,7 +141,7 @@
141	141
142	142	Create LNS API key
143	143
144		-**Note : Please copy the API key.**
	160	+(% style="color:red" %)**Note : Please copy the API key.**
145	145
146	146	== 3.4 Step 3. Update the gateway setting ==
147	147
...	...	@@ -165,11 +165,13 @@
165	165
166	166	**just to clarify.**
167	167
168		-{{{ CUPS Server URI --> Server Adress
169		- CUPS Authorization Key --> Server CUPS API Key
170		- LNS Authorization Key --> Server LNS API Key
171		- CUPS certificate --> Server CA(user can use the button to install the certificate by default)
172		-}}}
	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	+)))
173	173
174	174	[[image:https://wiki.dragino.com/images/thumb/8/8c/Confiure_station_cao.png/600px-Confiure_station_cao.png||height="321" width="600"]]
175	175
...	...	@@ -206,30 +206,42 @@
206	206	= 4. Configure node connection to TTNv3 =
207	207
208	208	(((
	227	+(((
209	209	Following is an example for how to join the TTN v3 LoRaWAN Network.
210	210	)))
	230	+)))
211	211
212	212	(((
	233	+(((
213	213	The gateway is already set up to connect to the TTN network, so we now need to configure the TTNv3 server.
214	214	)))
	236	+)))
215	215
216	216	(((
	239	+(((
217	217	We take LES01 as an example.
218	218	)))
	242	+)))
219	219
220	220	== 4.1 Step1 ==
221	221
222	222	(((
	247	+(((
223	223	Create a device in TTN with the OTAA keys from LSE01.
224	224	)))
	250	+)))
225	225
226	226	(((
	253	+(((
227	227	Each LSE01 is shipped with a sticker with the default device EUI as below:
228	228	)))
	256	+)))
229	229
230	230	(((
	259	+(((
231	231	You can enter this key in the LoRaWAN Server portal. Below is TTN screen shot:
232	232	)))
	262	+)))
233	233
234	234	[[image:https://wiki.dragino.com/images/thumb/c/c7/TTNv3--01.png/600px-TTNv3--01.png||alt="TTNv3--01.png" height="277" width="600"]]
235	235
...	...	@@ -238,8 +238,10 @@
238	238	== 4.2 Step2 ==
239	239
240	240	(((
	271	+(((
241	241	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.
242	242	)))
	274	+)))
243	243
244	244	[[image:https://wiki.dragino.com/images/thumb/f/fc/TTNv3--03.png/600px-TTNv3--03.png||alt="TTNv3--03.png" height="333" width="600"]]
245	245
...	...	@@ -260,22 +260,30 @@
260	260	== 5.1 Introduction ==
261	261
262	262	(((
	295	+(((
263	263	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.
264	264	)))
	298	+)))
265	265
266	266	== 5.2 Create device steps at MQTT ==
267	267
268	268	(((
	303	+(((
269	269	The user creates a new API KEY after creating a device on TTN V3.
270	270	)))
	306	+)))
271	271
272	272	(((
	309	+(((
273	273	Then copy the password and open MQTT.fx.
274	274	)))
	312	+)))
275	275
276	276	(((
	315	+(((
277	277	Fill in Broker Address and Broker port.
278	278	)))
	318	+)))
279	279
280	280	[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
281	281
...	...	@@ -286,7 +286,9 @@
286	286
287	287	The Application Server publishes uplink traffic on the following topics:
288	288
289		-{{{ v3/{application id}@{tenant id}/devices/{device id}/join
	329	+(% class="box" %)
	330	+(((
	331	+ v3/{application id}@{tenant id}/devices/{device id}/join
290	290	v3/{application id}@{tenant id}/devices/{device id}/up
291	291	v3/{application id}@{tenant id}/devices/{device id}/down/queued
292	292	v3/{application id}@{tenant id}/devices/{device id}/down/sent
...	...	@@ -295,31 +295,41 @@
295	295	v3/{application id}@{tenant id}/devices/{device id}/down/failed
296	296	v3/{application id}@{tenant id}/devices/{device id}/service/data
297	297	v3/{application id}@{tenant id}/devices/{device id}/location/solved
298		-}}}
	340	+)))
299	299
300	300	(((
301		-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}.
302	302	)))
	346	+)))
303	303
304	304	[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
305	305
306	306	(((
	351	+(((
307	307	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.
308	308	)))
	354	+)))
309	309
310	310	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
311	311
312	312	(((
	359	+(((
313	313	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
314	314	)))
	362	+)))
315	315
316	316	(((
	365	+(((
317	317	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.
318	318	)))
	368	+)))
319	319
320	320	(((
	371	+(((
321	321	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
322	322	)))
	374	+)))
323	323
324	324	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
325	325
...	...	@@ -393,7 +393,7 @@
393	393
394	394	(((
395	395	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.
396		-\\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:
	448	+\\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:**
397	397	)))
398	398
399	399	* End node is connected to serial port to show the Join frequency and DR. (If possible)
...	...	@@ -402,7 +402,6 @@
402	402	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
403	403	* 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)
404	404
405		-
406	406	**~1. End Device Join Screen shot, we can check:**
407	407
408	408	* If the device is sending join request to server?
...	...	@@ -422,8 +422,12 @@
422	422
423	423	**2. Gateway packet traffic in gateway web or ssh. we can check:**
424	424
425		-* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
426		-* If the gateway gets the Join Accept message from server and transmit it via LoRa?
	476	+* (((
	477	+If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
	478	+)))
	479	+* (((
	480	+If the gateway gets the Join Accept message from server and transmit it via LoRa?
	481	+)))
427	427
428	428	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
429	429
...	...	@@ -432,9 +432,15 @@
432	432
433	433	**3. Gateway Traffic Page in LoRaWAN Server**
434	434
435		-* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
436		-* 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.
437		-* 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.
	490	+* (((
	491	+If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	492	+)))
	493	+* (((
	494	+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.
	495	+)))
	496	+* (((
	497	+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	+)))
438	438
439	439	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
440	440
...	...	@@ -448,8 +448,10 @@
448	448	**4. Data Page in LoRaWAN server**
449	449
450	450	* (((
	512	+(((
451	451	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.
452	452	)))
	515	+)))
453	453
454	454	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
455	455