Summary

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

Details

Page properties

Content

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