Summary

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

Details

Page properties

Content

...	...	@@ -35,6 +35,7 @@
35	35
36	36	== 2.1 Primary LoRaWAN Server ==
37	37
	38	+[[image:https://wiki.dragino.com/images/thumb/0/0c/TTN_v3_Primary_001.png/600px-TTN_v3_Primary_001.png||height="296" width="600"]]
38	38
39	39	Register Gateway
40	40
...	...	@@ -61,13 +61,9 @@
61	61
62	62	=== 2.2.2 Below list the support products and Requirements: ===
63	63
64		-(((
65		-~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]]
66		-)))
	65	+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]]
67	67
68		-(((
69		-2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
70		-)))
	67	+1. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
71	71
72	72	=== 2.2.3 Example ===
73	73
...	...	@@ -295,30 +295,22 @@
295	295	== 5.1 Introduction ==
296	296
297	297	(((
298		-(((
299	299	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.
300	300	)))
301		-)))
302	302
303	303	== 5.2 Create device steps at MQTT ==
304	304
305	305	(((
306		-(((
307	307	The user creates a new API KEY after creating a device on TTN V3.
308	308	)))
309		-)))
310	310
311	311	(((
312		-(((
313	313	Then copy the password and open MQTT.fx.
314	314	)))
315		-)))
316	316
317	317	(((
318		-(((
319	319	Fill in Broker Address and Broker port.
320	320	)))
321		-)))
322	322
323	323	[[image:https://wiki.dragino.com/images/thumb/8/82/V3_MQTT1_.png/600px-V3_MQTT1_.png||alt="V3 MQTT1 .png" height="325" width="600"]]
324	324
...	...	@@ -329,9 +329,7 @@
329	329
330	330	The Application Server publishes uplink traffic on the following topics:
331	331
332		-(% class="box" %)
333		-(((
334		- v3/{application id}@{tenant id}/devices/{device id}/join
	321	+{{{ v3/{application id}@{tenant id}/devices/{device id}/join
335	335	v3/{application id}@{tenant id}/devices/{device id}/up
336	336	v3/{application id}@{tenant id}/devices/{device id}/down/queued
337	337	v3/{application id}@{tenant id}/devices/{device id}/down/sent
...	...	@@ -340,41 +340,31 @@
340	340	v3/{application id}@{tenant id}/devices/{device id}/down/failed
341	341	v3/{application id}@{tenant id}/devices/{device id}/service/data
342	342	v3/{application id}@{tenant id}/devices/{device id}/location/solved
343		-)))
	330	+}}}
344	344
345	345	(((
346		-(((
347		-**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
	333	+Note: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
348	348	)))
349		-)))
350	350
351	351	[[image:https://wiki.dragino.com/images/thumb/d/dc/V3_MQTT3.png/600px-V3_MQTT3.png||alt="V3 MQTT3.png" height="400" width="600"]]
352	352
353	353	(((
354		-(((
355	355	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.
356	356	)))
357		-)))
358	358
359	359	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT4.jpg/600px-V3_MQTT4.jpg||alt="V3 MQTT4.jpg" height="326" width="600"]]
360	360
361	361	(((
362		-(((
363	363	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
364	364	)))
365		-)))
366	366
367	367	(((
368		-(((
369		-**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.
	349	+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.
370	370	)))
371		-)))
372	372
373	373	(((
374		-(((
375	375	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
376	376	)))
377		-)))
378	378
379	379	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
380	380
...	...	@@ -383,7 +383,7 @@
383	383	)))
384	384
385	385	(((
386		-**Note**: Use this handy tool to convert hexadecimal to base64.
	363	+Note: Use this handy tool to convert hexadecimal to base64.
387	387	)))
388	388
389	389	[[image:https://wiki.dragino.com/images/thumb/9/9f/V3_MQTT6.png/600px-V3_MQTT6.png||alt="V3 MQTT6.png" height="313" width="600"]]
...	...	@@ -417,7 +417,7 @@
417	417	)))
418	418
419	419	(((
420		-**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
	397	+Note: If the downlink byte sent is longer, the number of bytes will be displayed.
421	421	)))
422	422
423	423	[[image:https://wiki.dragino.com/images/thumb/c/c9/Downlink_52.png/600px-Downlink_52.png||height="407" width="600"]]
...	...	@@ -425,28 +425,20 @@
425	425	downlink
426	426
427	427	(((
428		-(((
429	429	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
430	430	)))
431		-)))
432	432
433	433	(((
434		-(((
435		-If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
	409	+If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
436	436	)))
437		-)))
438	438
439	439	(((
440		-(((
441		-If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
	413	+If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
442	442	)))
443		-)))
444	444
445	445	(((
446		-(((
447	447	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
448	448	)))
449		-)))
450	450
451	451	[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png||height="127" width="600"]]
452	452
...	...	@@ -456,7 +456,7 @@
456	456
457	457	(((
458	458	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.
459		-\\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:**
	428	+\\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:
460	460	)))
461	461
462	462	* End node is connected to serial port to show the Join frequency and DR. (If possible)
...	...	@@ -474,9 +474,9 @@
474	474
475	475	Console Output from End device to see the transmit frequency
476	476
477		-User can run **AT+CFG **command to print configuration information.
	446	+User can run AT+CFG command to print configuration information.
478	478
479		-* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
	448	+* Is the device in OTAA mode or ABP mode? AT+NJM=1 (OTAA mode), AT+NJM=0 (ABP mode)
480	480
481	481	[[image:https://wiki.dragino.com/images/thumb/c/c5/LoRaWAN_Communication_Debug23.png/600px-LoRaWAN_Communication_Debug23.png||height="514" width="600"]]
482	482
...	...	@@ -484,12 +484,8 @@
484	484
485	485	**2. Gateway packet traffic in gateway web or ssh. we can check:**
486	486
487		-* (((
488		-If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
489		-)))
490		-* (((
491		-If the gateway gets the Join Accept message from server and transmit it via LoRa?
492		-)))
	456	+* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
	457	+* If the gateway gets the Join Accept message from server and transmit it via LoRa?
493	493
494	494	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
495	495
...	...	@@ -498,15 +498,9 @@
498	498
499	499	**3. Gateway Traffic Page in LoRaWAN Server**
500	500
501		-* (((
502		-If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
503		-)))
504		-* (((
505		-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.
506		-)))
507		-* (((
508		-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.
509		-)))
	466	+* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
	467	+* 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.
	468	+* 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.
510	510
511	511	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
512	512
...	...	@@ -520,12 +520,8 @@
520	520	**4. Data Page in LoRaWAN server**
521	521
522	522	* (((
523		-(((
524		-(((
525	525	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.
526	526	)))
527		-)))
528		-)))
529	529
530	530	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
531	531