Summary

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

Details

Page properties

Content

...	...	@@ -356,16 +356,22 @@
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	+(((
359	359	Downlinks can be scheduled by publishing the message to the topic v3/{application id}@{tenant id}/devices/{device id}/down/push.
360	360	)))
	362	+)))
361	361
362	362	(((
	365	+(((
363	363	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.
364	364	)))
	368	+)))
365	365
366	366	(((
	371	+(((
367	367	Instead of /push, you can also use /replace to replace the downlink queue. Replacing with an empty array clears the downlink queue. Example:
368	368	)))
	374	+)))
369	369
370	370	[[image:https://wiki.dragino.com/images/thumb/e/e8/V3_MQTT5.png/600px-V3_MQTT5.png||alt="V3 MQTT5.png" height="289" width="600"]]
371	371
...	...	@@ -416,20 +416,28 @@
416	416	downlink
417	417
418	418	(((
	425	+(((
419	419	If you want to get a successful reply to send downlink in TTN v3. You need to set the response level.
420	420	)))
	428	+)))
421	421
422	422	(((
	431	+(((
423	423	If the equipment uses CLASS A. You can set AT+RPL=2 or send the downlink command: 2102
424	424	)))
	434	+)))
425	425
426	426	(((
	437	+(((
427	427	If the equipment uses CLASS C. You can set AT+RPL=4 or send the downlink command: 2104
428	428	)))
	440	+)))
429	429
430	430	(((
	443	+(((
431	431	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
432	432	)))
	446	+)))
433	433
434	434	[[image:https://wiki.dragino.com/images/thumb/d/d9/Downlink_54.png/600px-Downlink_54.png||height="127" width="600"]]
435	435
...	...	@@ -439,7 +439,7 @@
439	439
440	440	(((
441	441	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.
442		-\\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:**
443	443	)))
444	444
445	445	* End node is connected to serial port to show the Join frequency and DR. (If possible)
...	...	@@ -467,8 +467,12 @@
467	467
468	468	**2. Gateway packet traffic in gateway web or ssh. we can check:**
469	469
470		-* If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
471		-* 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	+)))
472	472
473	473	[[image:https://wiki.dragino.com/images/thumb/1/1c/OTAA_Join-2.png/600px-OTAA_Join-2.png||height="325" width="600"]]
474	474
...	...	@@ -477,9 +477,15 @@
477	477
478	478	**3. Gateway Traffic Page in LoRaWAN Server**
479	479
480		-* If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
481		-* 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.
482		-* 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	+)))
483	483
484	484	[[image:https://wiki.dragino.com/images/thumb/d/da/LoRaWAN_Communication_Debug22.png/600px-LoRaWAN_Communication_Debug22.png||height="268" width="600"]]
485	485
...	...	@@ -493,8 +493,10 @@
493	493	**4. Data Page in LoRaWAN server**
494	494
495	495	* (((
	520	+(((
496	496	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.
497	497	)))
	523	+)))
498	498
499	499	[[image:https://wiki.dragino.com/images/thumb/9/99/LoRaWAN_Communication_Debug4.png/600px-LoRaWAN_Communication_Debug4.png||height="222" width="600"]]
500	500