Summary

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

Details

Page properties

Content

...	...	@@ -928,6 +928,11 @@
928	928	== 6.5 GPS debugging ==
929	929
930	930
	931	+Indoor GPS signal is very weak, outdoor positioning is generally recommended.
	932	+
	933	+=== 6.5.1 GPS commands ===
	934	+
	935	+
931	931	The following are three related AT commands that introduce GPS functions.
932	932
933	933	* **Turn on/off GPS**
...	...	@@ -944,7 +944,6 @@
944	944
945	945	Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
946	946
947		-
948	948	* **Set GNSS open time**
949	949
950	950	Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
...	...	@@ -959,7 +959,6 @@
959	959
960	960	Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
961	961
962		-
963	963	* **Set GPS positioning interval**
964	964
965	965	Feature: Set GPS positioning interval (unit: hour).
...	...	@@ -979,13 +979,43 @@
979	979	Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
980	980
981	981
982		-Indoor GPS signal is very weak, outdoor positioning is generally recommended.
	985	+=== 6.5.2 GPS workflow ===
983	983
984	984
	988	+The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
985	985
	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.
986	986
	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.
987	987
	994	+ So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
988	988
	996	+2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
989	989
	998	+ The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
990	990
	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	+
991	991

image-20240903094214-1.png

Author

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

Size

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

Content

image-20240903094457-2.png

Author

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

Size

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

Content