Summary

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

Details

Page properties

Content

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