Summary

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

Details

Page properties

Content

...	...	@@ -928,14 +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		-[[image:image-20240903100832-4.png||height="268" width="580"]]
934		-
935		-
936		-=== 6.5.1 GPS commands ===
937		-
938		-
939	939	The following are three related AT commands that introduce GPS functions.
940	940
941	941	* **Turn on/off GPS**
...	...	@@ -952,6 +952,7 @@
952	952
953	953	Example:  Downlink Payload: **11 01   **~/~/ AT+GPS=1
954	954
	947	+
955	955	* **Set GNSS open time**
956	956
957	957	Extend the time to turn on GNSS. The automatic GPS location time is extended when the node is activated.
...	...	@@ -966,6 +966,7 @@
966	966
967	967	Example:  Downlink Payload: **10 00 1E    **~/~/ AT+GNSST=30
968	968
	962	+
969	969	* **Set GPS positioning interval**
970	970
971	971	Feature: Set GPS positioning interval (unit: hour).
...	...	@@ -985,43 +985,13 @@
985	985	Downlink Payload: **12 00 00 18   **~/~/ AT+GTDC=24
986	986
987	987
988		-=== 6.5.2 GPS workflow ===
	982	+Indoor GPS signal is very weak, outdoor positioning is generally recommended.
989	989
990	990
991		-The whole working process after the GPS function is enabled((% style="color:#037691" %)**AT+GPS=1**(%%)) is as follows:
992	992
993		-~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.
994	994
995		- 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.
996	996
997		- So if there is a failure of positioning, the user can extend the (% style="color:#037691" %)**GNSST**(%%) time appropriately.
998	998
999		-2. Each TDC time node is not repositioned and the positioning interval is determined by the AT+GTDC time.
1000	1000
1001		- The latitude and longitude payload uplinked at each TDC time is the GPS positioning information from the previous (% style="color:#037691" %)**GTDC**(%%) time.
1002	1002
1003		- 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.
1004		-
1005		-
1006		-=== 6.5.3 GPS debugging methods ===
1007		-
1008		-
1009		-In summary, we can deduce the method of debugging GPS:
1010		-
1011		-* **Check whether the GPS antenna is loose**.
1012		-
1013		-If the GPS antenna is loose, the GPS signal is weak, and the positioning fails.
1014		-
1015		-[[image:image-20240903094214-1.png||height="340" width="461"]]
1016		-
1017		-* **Use the AT+GNSST command to extend the positioning time.**
1018		-
1019		-The default AT+GNSST=30, that is, the default positioning time is 30 seconds.
1020		-
1021		-If the location fails, users can extend the location time.
1022		-
1023		-
1024		-
1025		-
1026		-
1027	1027

image-20240903094457-2.png

Author

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

Size

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

Content

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

image-20240903102327-5.png

Author

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

Size

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

Content