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
...	...	@@ -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,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
	612	+**~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
	621	+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.
	623	+* 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
	631	+**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
	645	+**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
	667	+**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