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
...	...	@@ -110,7 +110,6 @@
110	110
111	111	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
...	...	@@ -600,7 +600,6 @@
600	600
601	601	= 6.  Request Remote Support =
602	602
603		-
604	604	(((
605	605	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.
606	606	\\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:**
...	...	@@ -612,24 +612,19 @@
612	612	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
613	613	* 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)
614	614
	612	+**~1. End Device Join Screen shot, we can check:**
615	615
616		-(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
617		-
618	618	* If the device is sending join request to server?
619	619	* What frequency the device is sending?
620	620
621		-
622	622	[[image:image-20220526141308-33.png]]
623	623
624	624	Console Output from End device to see the transmit frequency
625	625
	621	+User can run **AT+CFG **command to print configuration information.
626	626
627		-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)
628	628
629		-* 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)
630		-
631		-
632		-
633	633	[[image:image-20220526141612-36.png]]
634	634
635	635
...	...	@@ -636,17 +636,13 @@
636	636	Console Output from End device to see the transmit frequency
637	637
638	638
	631	+**2. Gateway packet traffic in gateway web or ssh. we can check:**
639	639
640		-(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
641		-
642	642	* (((
643	643	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
644	644	)))
645	645	* (((
646	646	If the gateway gets the Join Accept message from server and transmit it via LoRa?
647		-
648		-
649		-
650	650	)))
651	651
652	652	[[image:image-20220526141739-37.png]]
...	...	@@ -654,9 +654,8 @@
654	654	Console Output from Gateway to see packets between end node and server.
655	655
656	656
	645	+**3. Gateway Traffic Page in LoRaWAN Server**
657	657
658		-(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
659		-
660	660	* (((
661	661	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
662	662	)))
...	...	@@ -665,9 +665,6 @@
665	665	)))
666	666	* (((
667	667	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.
668		-
669		-
670		-
671	671	)))
672	672
673	673	[[image:image-20220526141823-38.png||height="501" width="1144"]]
...	...	@@ -675,21 +675,18 @@
675	675	The Traffic for the End node in the server, use TTNv3 as example
676	676
677	677
678		-
679	679	[[image:image-20220526141917-39.png]]
680	680
681	681	The Traffic for the End node in the server, use TTNv3 as example
682	682
683	683
	667	+**4. Data Page in LoRaWAN server**
684	684
685		-(% style="color:blue" %)**4. Data Page in LoRaWAN server**
686		-
687	687	(((
688	688	(((
689	689	(((
690	690	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.
691	691
692		-
693	693	[[image:image-20220526141956-40.png]]
694	694	)))
695	695	)))
...	...	@@ -698,7 +698,6 @@
698	698	The data for the end device set in server
699	699
700	700
701		-
702	702	[[image:image-20220526142033-41.png]]
703	703
704	704	Check if OTAA Keys match the keys in device