Summary

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

Details

Page properties

Content

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