Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 2 removed)
  • image-20240903094214-1.png
  • image-20240903094457-2.png

Details

Page properties

Content

...	...	@@ -900,6 +900,8 @@
900	900
901	901	[[http:~~/~~/wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/>>http://wiki.dragino.com/xwiki/bin/view/Main/End%20Device%20AT%20Commands%20and%20Downlink%20Command/]]
902	902
	903	+
	904	+​
903	903
904	904	== 6.4 What if the signal is good but the domain name resolution fails? ==
905	905
...	...	@@ -906,8 +906,6 @@
906	906
907	907	If the domain name resolution fails, first check whether the domain name is correct, users can use their own website domain name resolution tool to verify the domain name.
908	908
909		-[[image:image-20240827150705-6.png||height="489" width="687"]]
910		-
911	911	If the domain name is correct, but the domain name cannot be resolved, the user can turn off the domain name resolution function(AT+GDNS=1) and use the domain name communication directly.
912	912
913	913	* Set the DNS
...	...	@@ -916,109 +916,17 @@
916	916
917	917	**AT+GDNS=0**  ~/~/Default. Automatically resolves the domain name and uses the resolved IP to communicate.
918	918
919		-**AT+GDNS=1    **~/~/Disabling Domain name resolution. Use the domain name directly to communicate.
	919	+**AT+GDNS=1  **~/~/Disabling Domain name resolution. Use the domain name directly to communicate.
920	920
921	921	(% style="color:red" %)**Note: For -CB products, with the exception of AT+PRO=2,5, all protocols and payload formats support direct domain communication.**
922	922
923	923	Example:
924	924
925		-[[image:image-20240827150121-5.png||height="476" width="680"]][[image:image-20240827145055-4.png||height="484" width="678"]]
926	926
927	927
928		-== 6.5 GPS debugging ==
929	929
930	930
931		-Indoor GPS signal is very weak, outdoor positioning is generally recommended.
932	932
933		-=== 6.5.1 GPS commands ===
934	934
935	935
936		-The following are three related AT commands that introduce GPS functions.
937		-
938		-* **Turn on/off GPS**
939		-
940		-(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GPS **
941		-
942		-**Ex1:  **AT+GPS=0  ~/~/ Turn off GPS
943		-
944		-**Ex2:  **AT+GPS=1  ~/~/ Turn on GPS
945		-
946		-(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x11(%%)**
947		-
948		-Format: Command Code (0x11) followed by 1 byte.
949		-
950		-Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
951		-
952		-* **Set GNSS open time**
953		-
954		-Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
955		-
956		-(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GNSST**
957		-
958		-Example: AT+GNSST=30  ~/~/ Set the GPS positioning time to 30 seconds
959		-
960		-(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x10(%%)**
961		-
962		-Format: Command Code (0x10) followed by 2 bytes.
963		-
964		-Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
965		-
966		-* **Set GPS positioning interval**
967		-
968		-Feature: Set GPS positioning interval (unit: hour).
969		-
970		-When GPS is enabled, the node automatically locates and uplinks each time it passes **GTDC time** after activation.
971		-
972		-(% style="color:blue" %)**AT Command: **(% style="color:#037691" %)**AT+GTDC**
973		-
974		-Example: AT+GTDC=24  ~/~/ Set the GPS positioning interval to 24h.
975		-
976		-(% style="color:blue" %)**Downlink command:**(%%)** (% style="color:#037691" %)0x12(%%)**
977		-
978		-Format: Command Code (0x12) followed by 3 bytes.
979		-
980		-Example: 24 hours:  24(D)=0x18(H)
981		-
982		- Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
983		-
984		-
985		-=== 6.5.2 GPS workflow ===
986		-
987		-
988		-The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
989		-
990		-~1. When activate the node, the node will turn on the GNSS, if the GPS signal is good, the node will print and upload the position information with the first data packet immediately.
991		-
992		- If the signal is not good, it may take the whole (% style="color:#037691" %)**GNSST**(%%) time but still can not search the latitude and longitude information, at this time the node uploads the latitude and longitude all to 0.
993		-
994		- So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
995		-
996		-2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
997		-
998		- The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
999		-
1000		- Only when the node is activated or every (% style="color:#037691" %)**GTDC**(%%) time is reached, the node turns on the GNSS and we can observe the GPS search information through the serial assistant or Bluetooth tool.
1001		-
1002		-
1003		-=== 6.5.3 GPS debugging methods ===
1004		-
1005		-
1006		-In summary, we can deduce the method of debugging GPS:
1007		-
1008		-* **Check whether the GPS antenna is loose**.
1009		-
1010		-If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
1011		-
1012		-[[image:image-20240903094214-1.png||height="340" width="461"]]
1013		-
1014		-* **Use the AT+GNSST command to extend the positioning time.**
1015		-
1016		-The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
1017		-
1018		-If the location fails, users can extend the location time.
1019		-
1020		-
1021		-
1022		-
1023		-
1024	1024

image-20240903094214-1.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.ting

Size

...	...	@@ -1,1 +1,0 @@
1		-4.5 MB

Content

image-20240903094457-2.png

Author

...	...	@@ -1,1 +1,0 @@
1		-XWiki.ting

Size

...	...	@@ -1,1 +1,0 @@
1		-2.6 MB

Content