Summary

• Page properties (1 modified, 0 added, 0 removed)
• Attachments (0 modified, 0 added, 2 removed)
  • image-20240903100736-3.png
  • image-20240903100832-4.png

Details

Page properties

Content

...	...	@@ -928,11 +928,6 @@
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		-
936	936	The following are three related AT commands that introduce GPS functions.
937	937
938	938	* **Turn on/off GPS**
...	...	@@ -949,6 +949,7 @@
949	949
950	950	Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
951	951
	947	+
952	952	* **Set GNSS open time**
953	953
954	954	Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
...	...	@@ -963,6 +963,7 @@
963	963
964	964	Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
965	965
	962	+
966	966	* **Set GPS positioning interval**
967	967
968	968	Feature: Set GPS positioning interval (unit: hour).
...	...	@@ -982,43 +982,13 @@
982	982	Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
983	983
984	984
985		-=== 6.5.2 GPS workflow ===
	982	+Indoor GPS signal is very weak, outdoor positioning is generally recommended.
986	986
987	987
988		-The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
989	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	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	993
994		- So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
995	995
996		-2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
997	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	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-20240903100736-3.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-250.8 KB

Content

image-20240903100832-4.png

Author

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

Size

...	...	@@ -1,1 +1,0 @@
1		-181.5 KB

Content