Summary

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

Details

Page properties

Content

...	...	@@ -84,15 +84,16 @@
84	84	The Dragino gateway has supports the Secondary server settings.
85	85
86	86
	87	+
87	87	=== 2.2.2  Below list the support products and Requirements: ===
88	88
89	89
90	90	(((
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]]
	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]]
92	92	)))
93	93
94	94	(((
95		-2. Firmware version since :[[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
	96	+2.  Firmware version since :  [[lgw~~-~~-build-v5.4.1644658774>>url:http://www.dragino.com/downloads/index.php?dir=LoRa_Gateway/LIG16/Firmware/Release/]]
96	96	)))
97	97
98	98
...	...	@@ -598,6 +598,7 @@
598	598
599	599	= 6.  Request Remote Support =
600	600
	602	+
601	601	(((
602	602	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.
603	603	\\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:**
...	...	@@ -609,19 +609,24 @@
609	609	* End Node traffic (from server UI) to shows end node activity in server. (Normally possible)
610	610	* 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)
611	611
612		-**~1. End Device Join Screen shot, we can check:**
613	613
	615	+(% style="color:blue" %)**1. End Device Join Screen shot, we can check:**
	616	+
614	614	* If the device is sending join request to server?
615	615	* What frequency the device is sending?
616	616
	620	+
617	617	[[image:image-20220526141308-33.png]]
618	618
619	619	Console Output from End device to see the transmit frequency
620	620
621		-User can run **AT+CFG **command to print configuration information.
622	622
623		-* Is the device in OTAA mode or ABP mode? **AT+NJM=1** (OTAA mode), **AT+NJM=0** (ABP mode)
	626	+User can run (% style="color:blue" %)**AT+CFG **(%%)command to print configuration information.
624	624
	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	+
625	625	[[image:image-20220526141612-36.png]]
626	626
627	627
...	...	@@ -628,13 +628,17 @@
628	628	Console Output from End device to see the transmit frequency
629	629
630	630
631		-**2. Gateway packet traffic in gateway web or ssh. we can check:**
632	632
	639	+(% style="color:blue" %)**2. Gateway packet traffic in gateway web or ssh. we can check:**
	640	+
633	633	* (((
634	634	If the gateway receive the Join request packet from sensor? (If this fail, check if the gateway and sensor works on the match frequency)
635	635	)))
636	636	* (((
637	637	If the gateway gets the Join Accept message from server and transmit it via LoRa?
	646	+
	647	+
	648	+
638	638	)))
639	639
640	640	[[image:image-20220526141739-37.png]]
...	...	@@ -642,8 +642,9 @@
642	642	Console Output from Gateway to see packets between end node and server.
643	643
644	644
645		-**3. Gateway Traffic Page in LoRaWAN Server**
646	646
	657	+(% style="color:blue" %)**3. Gateway Traffic Page in LoRaWAN Server**
	658	+
647	647	* (((
648	648	If the Join Request packet arrive the gateway traffic in server? If not, check the internet connection and gateway LoRaWAN server settings.
649	649	)))
...	...	@@ -652,6 +652,9 @@
652	652	)))
653	653	* (((
654	654	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	+
655	655	)))
656	656
657	657	[[image:image-20220526141823-38.png||height="501" width="1144"]]
...	...	@@ -659,18 +659,21 @@
659	659	The Traffic for the End node in the server, use TTNv3 as example
660	660
661	661
	677	+
662	662	[[image:image-20220526141917-39.png]]
663	663
664	664	The Traffic for the End node in the server, use TTNv3 as example
665	665
666	666
667		-**4. Data Page in LoRaWAN server**
668	668
	684	+(% style="color:blue" %)**4. Data Page in LoRaWAN server**
	685	+
669	669	(((
670	670	(((
671	671	(((
672	672	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.
673	673
	691	+
674	674	[[image:image-20220526141956-40.png]]
675	675	)))
676	676	)))
...	...	@@ -679,6 +679,7 @@
679	679	The data for the end device set in server
680	680
681	681
	700	+
682	682	[[image:image-20220526142033-41.png]]
683	683
684	684	Check if OTAA Keys match the keys in device