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
...	...	@@ -108,9 +108,8 @@
108	108	=== 2.2.4  Step 1: Download and Install the helium gateway-rs ===
109	109
110	110
111		-The users is needing to download and install the helium gateway-rs then click the button of (% style="color:blue" %)**Save&Apply.**
	110	+The users is needing to download and install the helium gateway-rs then click the button of Save&Apply
112	112
113		-
114	114	[[image:image-20220526135049-6.png]]
115	115
116	116	Download and Install gateway-rs
...	...	@@ -122,7 +122,6 @@
122	122
123	123	Back to the page of Semtech UDP check the secondary server settings and click the button of Save&Apply
124	124
125		-
126	126	​​​​[[image:image-20220526135125-7.png]]
127	127
128	128	Configuration of helium
...	...	@@ -149,12 +149,14 @@
149	149
150	150	(((
151	151	(((
152		-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]]
	149	+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]]
153	153	)))
154	154
155	155	(((
156		- 2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
	153	+ 2. Firmware version since :[[lgw~~-~~-build-v5.4.1640315898>>url:https://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LPS8/Firmware/Release/]]
157	157
	155	+
	156	+
158	158
159	159	)))
160	160	)))
...	...	@@ -599,7 +599,6 @@
599	599
600	600	= 6.  Request Remote Support =
601	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,7 +611,7 @@
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
614		-(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	612	+**~1. End Device Join Screen shot, we can check:**
615	615
616	616	* If the device is sending join request to server?
617	617	* What frequency the device is sending?
...	...	@@ -620,12 +620,10 @@
620	620
621	621	Console Output from End device to see the transmit frequency
622	622
	621	+User can run **AT+CFG **command to print configuration information.
623	623
624		-User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
	623	+* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
625	625
626		-* 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)
627		-
628		-
629	629	[[image:image-20220526141612-36.png]]
630	630
631	631
...	...	@@ -632,17 +632,13 @@
632	632	Console Output from End device to see the transmit frequency
633	633
634	634
	631	+**2. Gateway packet traffic in gateway web or ssh. we can check:**
635	635
636		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
637		-
638	638	* (((
639	639	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
640	640	)))
641	641	* (((
642	642	If the gateway gets the Join Accept message from server and transmit it via LoRa?
643		-
644		-
645		-
646	646	)))
647	647
648	648	[[image:image-20220526141739-37.png]]
...	...	@@ -650,9 +650,8 @@
650	650	Console Output from Gateway to see packets between end node and server.
651	651
652	652
	645	+**3. Gateway Traffic Page in LoRaWAN Server**
653	653
654		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
655		-
656	656	* (((
657	657	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
658	658	)))
...	...	@@ -661,9 +661,6 @@
661	661	)))
662	662	* (((
663	663	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.
664		-
665		-
666		-
667	667	)))
668	668
669	669	[[image:image-20220526141823-38.png||height="501" width="1144"]]
...	...	@@ -671,21 +671,18 @@
671	671	The Traffic for the End node in the server, use TTNv3 as example
672	672
673	673
674		-
675	675	[[image:image-20220526141917-39.png]]
676	676
677	677	The Traffic for the End node in the server, use TTNv3 as example
678	678
679	679
	667	+**4. Data Page in LoRaWAN server**
680	680
681		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
682		-
683	683	(((
684	684	(((
685	685	(((
686	686	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.
687	687
688		-
689	689	[[image:image-20220526141956-40.png]]
690	690	)))
691	691	)))
...	...	@@ -694,7 +694,6 @@
694	694	The data for the end device set in server
695	695
696	696
697		-
698	698	[[image:image-20220526142033-41.png]]
699	699
700	700	Check if OTAA Keys match the keys in device