Summary

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

Details

Page properties

Content

...	...	@@ -333,9 +333,8 @@
333	333	)))
334	334	)))
335	335
336		-== 4.1  Step1 ==
	336	+== 4.1 Step1 ==
337	337
338		-
339	339	(((
340	340	(((
341	341	Create a device in TTN with the OTAA keys from LSE01.
...	...	@@ -359,15 +359,11 @@
359	359	[[image:image-20220526140044-18.png]]
360	360
361	361
	361	+== 4.2 Step2 ==
362	362
363		-== 4.2  Step2 ==
364		-
365		-
366	366	(((
367	367	(((
368	368	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.
369		-
370		-
371	371	)))
372	372	)))
373	373
...	...	@@ -374,45 +374,34 @@
374	374	[[image:image-20220526140132-19.png]]
375	375
376	376
	372	+== 4.3 Step3 ==
377	377
378		-== 4.3  Step3 ==
379		-
380		-
381	381	Add APP EUI in the application:
382	382
383		-
384	384	[[image:image-20220526140205-20.png]]
385	385
386	386
	379	+== 4.4 Step4 ==
387	387
388		-== 4.4  Step4 ==
389		-
390		-
391	391	Add APP KEY and DEV EUI:
392	392
393		-
394	394	[[image:image-20220526140251-21.png]]
395	395
396	396
	386	+= 5. TTN V3 integrated into MQTT server =
397	397
398		-= 5.  TTN V3 integrated into MQTT server =
	388	+== 5.1 Introduction ==
399	399
400		-
401		-== 5.1  Introduction ==
402		-
403		-
404	404	(((
405	405	(((
406	406	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.
407	407
408		-
409	409
410	410	)))
411	411	)))
412	412
413		-== 5.2  Create device steps at MQTT ==
	398	+== 5.2 Create device steps at MQTT ==
414	414
415		-
416	416	(((
417	417	(((
418	418	The user creates a new API KEY after creating a device on TTN V3.
...	...	@@ -428,8 +428,6 @@
428	428	(((
429	429	(((
430	430	Fill in Broker Address and Broker port.
431		-
432		-
433	433	)))
434	434	)))
435	435
...	...	@@ -438,10 +438,8 @@
438	438	Fill in the username and password into MQTT.
439	439
440	440
441		-
442	442	[[image:image-20220526140420-23.png]]
443	443
444		-
445	445	The Application Server publishes uplink traffic on the following topics:
446	446
447	447	(% class="box" %)
...	...	@@ -458,18 +458,13 @@
458	458	)))
459	459
460	460	(((
461		-
462		-
463	463	(((
464		-(% style="color:red" %)**Note**: **Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.**
465		-
466		-
	442	+**Note**: Remember that the format of these topics for The Things Stack Open Source would contain {application id} instead of {application id}@{tenant id}.
467	467	)))
468	468	)))
469	469
470	470	[[image:image-20220526140452-24.png]]
471	471
472		-
473	473	(((
474	474	(((
475	475	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.
...	...	@@ -486,11 +486,7 @@
486	486
487	487	(((
488	488	(((
489		-
490		-
491		-(% style="color:red" %)**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.**
492		-
493		-
	464	+**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.
494	494	)))
495	495	)))
496	496
...	...	@@ -504,23 +504,17 @@
504	504
505	505	(((
506	506	To send an unconfirmed downlink message to the device dev1 in application app1 in tenant tenant1 with the hexadecimal payload BE EF on FPort 15 with normal priority, use the topic v3/app1@tenant1/devices/dev1/down/push with the following contents:
507		-
508		-
509	509	)))
510	510
511	511	(((
512		-(% style="color:red" %)**Note**: **Use this handy tool to convert hexadecimal to base64.**
513		-
514		-
	481	+**Note**: Use this handy tool to convert hexadecimal to base64.
515	515	)))
516	516
517	517	[[image:image-20220526140936-27.png]]
518	518
519	519
	487	+== 5.3 Send Downlink message ==
520	520
521		-== 5.3  Send Downlink message ==
522		-
523		-
524	524	(((
525	525	How to configure downlink in TTN V3?
526	526	)))
...	...	@@ -530,9 +530,7 @@
530	530	)))
531	531
532	532	(((
533		-(% style="color:blue" %)**Downlink command: 01 00 00 5A**
534		-
535		-
	498	+Downlink command:01 00 00 5A
536	536	)))
537	537
538	538	[[image:image-20220526141021-28.png]]
...	...	@@ -540,7 +540,6 @@
540	540	downlink
541	541
542	542
543		-
544	544	After sending, you can view it in live data.
545	545
546	546	[[image:image-20220526141052-29.png]]
...	...	@@ -548,15 +548,12 @@
548	548	downlink
549	549
550	550
551		-
552	552	(((
553	553	When downlink is successfully sent, the downlink information can be received on the serial port.
554	554	)))
555	555
556	556	(((
557		-(% style="color:red" %)**Note**:** If the downlink byte sent is longer, the number of bytes will be displayed.**
558		-
559		-
	518	+**Note**: If the downlink byte sent is longer, the number of bytes will be displayed.
560	560	)))
561	561
562	562	[[image:image-20220526141116-30.png]]
...	...	@@ -572,13 +572,13 @@
572	572
573	573	(((
574	574	(((
575		-If the equipment uses (% style="color:blue" %)**CLASS A**(%%). You can set (% style="color:red" %)**AT+RPL=2** (%%)or send the downlink command: (% style="color:red" %)**2102**
	534	+If the equipment uses CLASS A. You can set **AT+RPL=2** or send the downlink command: **2102**
576	576	)))
577	577	)))
578	578
579	579	(((
580	580	(((
581		-If the equipment uses (% style="color:blue" %)**CLASS C**(%%). You can set** (% style="color:red" %)AT+RPL=4(%%)** or send the downlink command: (% style="color:red" %)**2104**
	540	+If the equipment uses CLASS C. You can set** AT+RPL=4** or send the downlink command: **2104**
582	582	)))
583	583	)))
584	584
...	...	@@ -585,8 +585,6 @@
585	585	(((
586	586	(((
587	587	When the device successfully receives the downlink, the server will receive a confirmation packet of 00.
588		-
589		-
590	590	)))
591	591	)))
592	592
...	...	@@ -595,10 +595,8 @@
595	595	downlink
596	596
597	597
	555	+= 6. Request Remote Support =
598	598
599		-= 6.  Request Remote Support =
600		-
601		-
602	602	(((
603	603	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.
604	604	\\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:**
...	...	@@ -610,24 +610,19 @@
610	610	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
611	611	* 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)
612	612
	568	+**~1. End Device Join Screen shot, we can check:**
613	613
614		-(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
615		-
616	616	* If the device is sending join request to server?
617	617	* What frequency the device is sending?
618	618
619		-
620	620	[[image:image-20220526141308-33.png]]
621	621
622	622	Console Output from End device to see the transmit frequency
623	623
	577	+User can run **AT+CFG **command to print configuration information.
624	624
625		-User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
	579	+* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
626	626
627		-* Is the device in OTAA mode or ABP mode? (% style="color:red" %)**AT+NJM=1** (%%)(OTAA mode), (% style="color:red" %)**AT+NJM=0**(%%) (ABP mode)
628		-
629		-
630		-
631	631	[[image:image-20220526141612-36.png]]
632	632
633	633
...	...	@@ -634,17 +634,13 @@
634	634	Console Output from End device to see the transmit frequency
635	635
636	636
	587	+**2. Gateway packet traffic in gateway web or ssh. we can check:**
637	637
638		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
639		-
640	640	* (((
641	641	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
642	642	)))
643	643	* (((
644	644	If the gateway gets the Join Accept message from server and transmit it via LoRa?
645		-
646		-
647		-
648	648	)))
649	649
650	650	[[image:image-20220526141739-37.png]]
...	...	@@ -652,9 +652,8 @@
652	652	Console Output from Gateway to see packets between end node and server.
653	653
654	654
	601	+**3. Gateway Traffic Page in LoRaWAN Server**
655	655
656		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
657		-
658	658	* (((
659	659	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
660	660	)))
...	...	@@ -663,9 +663,6 @@
663	663	)))
664	664	* (((
665	665	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.
666		-
667		-
668		-
669	669	)))
670	670
671	671	[[image:image-20220526141823-38.png||height="501" width="1144"]]
...	...	@@ -673,21 +673,18 @@
673	673	The Traffic for the End node in the server, use TTNv3 as example
674	674
675	675
676		-
677	677	[[image:image-20220526141917-39.png]]
678	678
679	679	The Traffic for the End node in the server, use TTNv3 as example
680	680
681	681
	623	+**4. Data Page in LoRaWAN server**
682	682
683		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
684		-
685	685	(((
686	686	(((
687	687	(((
688	688	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.
689	689
690		-
691	691	[[image:image-20220526141956-40.png]]
692	692	)))
693	693	)))
...	...	@@ -696,7 +696,6 @@
696	696	The data for the end device set in server
697	697
698	698
699		-
700	700	[[image:image-20220526142033-41.png]]
701	701
702	702	Check if OTAA Keys match the keys in device