You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/menu_system.md
+6-6Lines changed: 6 additions & 6 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -33,8 +33,8 @@ In order of appearance:
33
33
* GNSS status including receiver type and firmware version
34
34
* Unique ID assigned to the GNSS receiver
35
35
* GNSS information including SIV, HPA, Lat/Lon/Alt
36
-
* Battery information (if available)
37
-
* Bluetooth MAC (ending) and status
36
+
* Battery information (if supported)
37
+
* Bluetooth MAC (ending) and radio status
38
38
* WiFi MAC (full)
39
39
* System Uptime
40
40
* NTRIP Client/Server uptime (if enabled)
@@ -47,14 +47,14 @@ In order of appearance:
47
47
48
48
*System Menu Options serial menu*
49
49
50
-
The device can be in Rover, Base, or WiFi Config mode. The select mode will be entered once the user exits the menu system.
50
+
The device can be in Rover, Base, or WiFi Config mode. The selected mode will be entered once the user exits the menu system.
51
51
52
52
***B, R, W, or S** - Change the mode the device is in.
53
53
54
54
***R**over - This is the default mode. The device transmits its NMEA and other messages (if enabled) over Bluetooth. It can receive corrections over Bluetooth (or other transport methods such as NTRIP Client) to achieve RTK Fix.
55
55
***B**ase - The device will reconfigure for base mode. It will begin transmitting corrections over Bluetooth, WiFi (NTRIP Server, TCP, etc), or other (ESP-Now, external radio if compatible, etc).
56
56
***W**iFi Config - The device will shut down GNSS operations and begin broadcasting as a WiFi Access Point (or will attempt to connect to local WiFi). Once started, the device can be connected to over WiFi for configuration.
57
-
***S**hut Down - If available, the device will immediately shut down.
57
+
***S**hut Down - If supported, the device will immediately shut down.
58
58
59
59
## Settings
60
60
@@ -66,13 +66,13 @@ The device can be in Rover, Base, or WiFi Config mode. The select mode will be e
66
66
67
67
***b** - Change the Bluetooth protocol. By default, the RTK device begins dual broadcasting over Bluetooth Classic SPP (Serial Port Profile) **and** Bluetooth Low-Energy (BLE). The following options are available: *Dual*, *Classic*, *BLE*, or *Off*. Bluetooth v2.0 SPP (Serial Port Profile) is supported by nearly all data collectors and Android tablets. BLE is used for configuration and to be compatible with Apple iOS-based devices. Additionally, the Bluetooth radio can be turned off.
68
68
69
-
***c** - By default, a device will continue to operate until the battery (if available) is exhausted. If desired, a timeout can be entered: If no charging is detected, the device will power off once this amount of time has expired.
69
+
***c** - On devices that support it, a device will continue to operate until the battery is exhausted. If desired, a timeout can be entered: If no charging is detected, the device will power off once this amount of time has expired.
70
70
71
71
***d** - Enters the [Debug Software menu](menu_debug_software.md) that is for advanced users.
72
72
73
73
***e** - Controls the printing of local characters (also known as 'echoing').
74
74
75
-
***f** - If supported, show any files on the microSD card (if present).
75
+
***f** - On devices that support it, show any files on the microSD card (if present).
76
76
77
77
***h** - Enters the [Debug Hardware menu](menu_debug_hardware.md) that is for advanced users.

7
+
8
+
*Tilt Compensation menu*
9
+
10
+
On devices that support it, tilt compensation can be configured.
11
+
12
+
***1** - By default, tilt compensation is enabled but can be disabled if desired.
13
+
14
+
***2** - The pole length must be set accurately to enter tilt compensation mode. The default is 1.8 meters but may be altered.
15
+
16
+
## Entering Tilt Compensation Mode
17
+
18
+
To use Tilt Compensation, the device must first have Tilt Compensation enabled (by shaking), then once the IMU has calculated its position on the end of the pole, Tile Compensation will be active.
19
+
20
+
During Tilt Compensation, all outgoing NMEA messages are modified to output the location *of the tip of the pole*. The Data Collector software will not be aware that the position of the GNSS receiver position is being modified.
21
+
22
+
Tilt compensation mode can be entered using the following steps:
23
+
24
+
1) The device must be in Rover mode.
25
+
2) The device must achieve an RTK Fix.
26
+
3) The pole length must be accurately configured. By default, this is 1.8 meters.
27
+
4) Once the above requirements are met, the device must be shaken. This is normally a strong up/down vertical motion. However, if it is more comfortable, the device can be positioned horizontally over the shoulder and shaken with a strong forward/backward motion.
28
+
5) On devices that support it, the device will emit a chirp once Tilt Mode is started.
29
+
6) Place the tip of the device on the ground. Move the head of the device back and forth up to ~30 degrees of tilt. Repeat on the opposite axis.
30
+
7) On devices that support it, the device will emit a long chirp once Tilt Mode is active.
0 commit comments