Menu map

Every menu of the serial port as the MS2net reference station prints it, with the key of each item and the place where the setting is explained. How to connect and type is in Using the serial menu; the diagnostic menus are in Debug and tuning. Items marked serial only have no field in the panel.

SoluTOP MS2net v1.3.N
** Bluetooth SPP broadcasting as: MS2net-F8CE **
Menu: Main
1) Configure GNSS Receiver
2) Configure GNSS Messages
3) Configure Base
4) Configure Ports
5) Configure Logging
6) Configure WiFi
7) Configure Network
p) Configure User Profiles
r) Configure Radios
s) Configure System
f) Firmware upgrade
x) Exit

Key	Menu
`1`	GNSS
`2`	Messages
`3`	Base
`4`	Ports
`5`	Logging
`6`	WiFi networks
`7`	Network
`p`	Profiles
`r`	Radios
`s`	System
`f`	Firmware
`x`	closes the menu and stores the changes

Over a Bluetooth echo session the menu also shows b) Exit Bluetooth Echo mode (Remote access). With Bluetooth set to BLE the second line reads ** Bluetooth Low-Energy broadcasting as: … **.

GNSS

Menu: GNSS Receiver
1) Set measurement rate in Hz: 4.00000
2) Set measurement rate in seconds between measurements: 0.25000
    Note: The measurement rate is overridden to 1Hz when in Base mode.
3) Set dynamic model: Portable
4) Set Constellations
5) Toggle NTRIP Client: Enabled
6) Set Caster Address: caster.example.com
7) Set Caster Port: 2101
8) Set Caster User Name: user
9) Set Caster User Password: password
10) Set Mountpoint: MOUNTPOINT
11) Set Mountpoint PW: 
12) Toggle sending GGA Location to Caster: Enabled
13) Minimum elevation for a GNSS satellite to be used in fix (degrees): 10
14) Minimum satellite signal level for navigation (dBHz): 6
15) List the caster's mount points
x) Exit

Key	Panel field
`1`, `2`	Measurement Rate (the same value in Hz or in seconds)
`3`	Dynamic Model
`4`	Constellations, submenu below
`5` … `12`	NTRIP client: on/off, Caster Host, Port, User, User PW, Mount Point, Mount Point PW, Transmit GGA
`13`	Min SV Elevation
`14`	Min C/N0
`15`	the List button beside Mount Point (NTRIP client): asks the caster for its mount points

Items 6 to 12 and 15 appear only with the NTRIP client on; otherwise the two minimum values move up to 6 and 7. 15 uses the caster address, port, user and password set above and needs a WiFi network with Internet access: it prints one line per mount point (number, name, format, place), at most 40, or the reason it failed (Error: caster not reachable. Check the address and the port, Error: the caster refused the user name or the password…). The list is for reading: the chosen name is typed in 10. The serial menu accepts up to 20 Hz (the panel stops at 10) and does not accept 0 for the two minimum values.

Menu: Constellations
1) Constellation GPS: Enabled
2) Constellation SBAS: Enabled
3) Constellation Galileo: Enabled
4) Constellation BeiDou: Enabled
5) Constellation QZSS: Enabled
6) Constellation GLONASS: Enabled
x) Exit

Each number switches that system on or off; GPS and QZSS switch together, like the single GPS/QZSS box of the panel.

Item 3 prints the list of models and waits for a number; an empty line leaves the model as it is:

Enter the dynamic model to use: 
1) Portable
2) Stationary
3) Pedestrian
4) Automotive
5) Sea
6) Airborne 1g
7) Airborne 2g
8) Airborne 4g
9) Wrist

Messages

Menu: GNSS Messages
Active messages: 5
1) Set NMEA Messages
2) Set RTCM Messages
3) Set RXM Messages
4) Set NAV Messages
5) Set NAV2 Messages
6) Set NMEA NAV2 Messages
7) Set MON Messages
8) Set TIM Messages
9) Set PUBX Messages
10) Reset to Surveying Defaults (NMEAx5)
11) Reset to PPP Logging Defaults (NMEAx5 + RXMx2)
12) Turn off all messages
13) Turn on all messages
x) Exit

Key	Panel field
`1` … `9`	the same family in Message Rates
`10`	Surveying Rates
`11`	Logging Rates
`12`, `13`	serial only: every rate to 0, or every message on (tests only: far more data than the links can carry)
`x`	sends the rates to the GNSS module (`menuMessages: Messages successfully enabled`)

Active messages counts the messages with a rate other than 0. Each family lists its messages with the current rate:

Menu: Message NMEA_
1) Message UBX_NMEA_DTM: 0
2) Message UBX_NMEA_GBS: 0
3) Message UBX_NMEA_GGA: 1
4) Message UBX_NMEA_GLL: 0
5) Message UBX_NMEA_GNS: 0
6) Message UBX_NMEA_GRS: 0
7) Message UBX_NMEA_GSA: 1
8) Message UBX_NMEA_GST: 1
9) Message UBX_NMEA_GSV: 4
10) Message UBX_NMEA_RLM: 0
11) Message UBX_NMEA_RMC: 1
13) Message UBX_NMEA_VLW: 0
14) Message UBX_NMEA_VTG: 0
15) Message UBX_NMEA_ZDA: 0
x) Exit

Type the number of a message, then its rate: 0 off, 1 with every position, N once every N positions (up to 255). Missing numbers are messages the module does not support. The RTCM family (2) is the rover's RTCM output; the base rates are in Base RTCM.

Base

With a fixed position in geodetic coordinates and the NTRIP server off:

Menu: Base
Total Height Above Ellipsoid - Antenna Phase Center (HAE APC): 50.000mm
1) Toggle Base Mode: Fixed/Static Position
2) Toggle Coordinate System: Geodetic
3) Set Lat/Long/Altitude coordinates: 45.123456789, 12.345678901, 50.0000m
4) Set coordinate display format: DD.ddddddddd
5) Set Antenna Height: 0mm
6) Set Antenna Reference Point: 0.0mm
7) Toggle NTRIP Server: Disabled
8) Set RTCM Message Rates
x) Exit

Key	Panel field
`1`	Survey-In or Fixed
`2` (fixed)	ECEF or geodetic
`3` (fixed)	ECEF X/Y/Z, or Lat/Long/Altitude
`4` (fixed, geodetic)	serial only: display format of latitude and longitude
`5`, `6` (fixed, geodetic)	Antenna Height, Antenna Reference Point (geodetic)
`2`, `3` (survey-in)	Minimum observation time, Required Mean 3D Standard Deviation (Survey-In)
`4` (survey-in)	serial only: required initial positional accuracy (Survey-In)
`7`	NTRIP server
`8` … `14` (server on)	server 1 or 2, then its Caster Host, Port, User, User PW, Mountpoint, Mountpoint PW (NTRIP server)
`8` or `15`	Base RTCM
`9` or `16` (survey-in)	serial only: Select survey-in radio; stored, no effect in this firmware

With Survey-In, items 2 to 4 become the survey-in values and 5, 6 disappear; with the NTRIP server on, the RTCM rates move to 15. The Mean 3D Standard Deviation accepts 1.0 to 10.0 m here, up to 5.0 in the panel.

With Survey-In and the NTRIP server on (8 switches between server 1 and 2; the observation time accepts 60 to 600 s, the initial accuracy 0.1 to 10.0 m):

Menu: Base
1) Toggle Base Mode: Use Survey-In
2) Set minimum observation time: 60 seconds
3) Set required Mean 3D Standard Deviation: 5.000 meters
4) Set required initial positional accuracy before Survey-In: 1.000 meters
7) Toggle NTRIP Server: Enabled
8) Select NTRIP server index: 1
9) Set Caster Host / Address 1: caster.example.com
10) Set Caster Port 1: 2101
11) Set Caster User 1: user
12) Set Caster User PW 1: password
13) Set Mountpoint 1: MOUNTPOINT
14) Set Mountpoint PW 1: 
15) Set RTCM Message Rates
16) Select survey-in radio: Bluetooth
x) Exit

Latitude and longitude can be typed as 40.090335429, 40 05.4201257, 40-05.4201257, 4005.4201257 or 40 05 25.207544: the format is recognised, and must be the same for both. West and south are negative; the decimal separator is the point. The first line is the altitude of the antenna phase centre (typed altitude + antenna height + ARP offset), in metres despite the mm.

Coordinate display format

Menu: Coordinate Display Type
The coordinate type is autodetected during entry but can be changed here.
Current display format: DD.ddddddddd
1) DD.ddddddddd
2) DDMM.mmmmmmm
3) DD MM.mmmmmmm
4) DD-MM.mmmmmmm
5) DD°MM.mmmmmmm'
6) DDMMSS.ssssss
7) DD MM SS.ssssss
8) DD-MM-SS.ssssss
9) DD°MM'SS.ssssss"
10) DDMMSS
11) DD MM SS
12) DD-MM-SS
x) Exit

Base RTCM

Menu: GNSS Messages - Base RTCM
1) Set RTCM Messages for Base Mode
2) Reset to Defaults (1005/74/84/94/124 1Hz & 1230 0.1Hz)
3) Reset to Low Bandwidth Link (1074/84/94/124 0.5Hz & 1005/230 0.1Hz)
4) Reset to EU 868 MHz Radio (1074/94 1Hz, 1124 0.5Hz & 1005 0.1Hz)
5) Reset to MSM7 (1077/87/97/127 1Hz, 1005 1Hz & 1230 0.1Hz)
x) Exit

Key	Panel field
`1`	RTCM Rates: each message with its rate in seconds
`2`	Default Rates
`3`	Low Bandwidth
`4`	EU 868 MHz
`5`	MSM7: full-resolution observations, for links with bandwidth to spare (NTRIP, ESP-Now)

Item 1 lists the base messages; type the number, then the rate (0 off, up to 255):

Menu: Message RTCM-Base
1) Message UBX_RTCM_1005: 1
2) Message UBX_RTCM_1074: 1
3) Message UBX_RTCM_1077: 0
4) Message UBX_RTCM_1084: 1
5) Message UBX_RTCM_1087: 0
6) Message UBX_RTCM_1094: 1
7) Message UBX_RTCM_1097: 0
8) Message UBX_RTCM_1124: 1
9) Message UBX_RTCM_1127: 0
10) Message UBX_RTCM_1230: 10
11) Message UBX_RTCM_4072_0: 0
12) Message UBX_RTCM_4072_1: 0
x) Exit

Ports

Menu: Ports
1) Set serial baud rate for Radio Port: 57600 bps
Data Port (internal GNSS link, fixed): 230400 bps
3) GNSS UART2 UBX Protocol In: Disabled
x) Exit

Key	Panel field
`1`	LoRa Radio Baud Rate (sent to the module at once)
—	GNSS Serial Baud Rate, shown only
`3`	serial only: GNSS UART2 UBX Protocol In (Ports)

The radio port accepts the standard rates from 4800 to 921600 bps, or 0 to switch it off (Disabled); 3 takes effect at the next restart.

Logging

Menu: Logging
SD card size: 14.6 GB / Free space: 13.6 GB
Current log file name: /MS2_260929_131301.ubx
1) Log to microSD: Enabled
2) Set max logging time: 1440 minutes
3) Set max log length: 1440 minutes
4) Start new log
5) Log Antenna Reference Position from RTCM 1005/1006: Disabled
7) Write Marks_date.csv file to microSD: Disabled
8) Reset system if the SD card is detected but fails to initialize: Disabled
x) Exit

Every item, including the serial-only 7 and 8, is in the settings of MicroSD logging. Without a card the menu says No microSD card is detected; Buffer overruns: N means data could not be written in time.

Items 2 to 6 appear only with logging on, 4 only while a file is open, and 6) Set ARP logging interval: 10 seconds (1 to 600 s) only with 5 on.

WiFi networks

Menu: WiFi Networks
1) SSID 1: OfficeNetwork
2) Password 1: password
3) SSID 2: 
4) Password 2: 
5) SSID 3: 
6) Password 3: 
7) SSID 4: 
8) Password 4: 
a) Configure device via WiFi Access Point or connect to WiFi: WiFi
c) Captive Portal: Enabled
p) Maximum WiFi and ESP-Now transmit power: 11.0 dBm (radio now 11.00 dBm)
m) MDNS: Enabled
x) Exit

Key	Panel field
`1` … `8`	Networks, SSID and PW 1 to 4 (emptying an SSID erases its password)
`a`	Configure Mode
`p`	Max WiFi Power: each press moves to the next level down (19.5 to 2 dBm, then back to 19.5), applied at once; radio now is the power the radio reports, shown while the radio is on
`c`, `m`	serial only: Captive Portal, MDNS (WiFi)
`x`	restarts the WiFi if networks or mode changed

Network

Menu: Network

1) PVT Client: Disabled
4) PVT Server: Enabled
5) PVT Server Port: 2948
9) PVT Server RTCM Only (Base mode): Enabled
m) Remote config: Web page
k) Remote config password: (empty - remote config OFF)
6) PVT UDP Server: Disabled
8) Display server IP address: Enabled
r) WiFi max retry delay: 56s (level 4, range 1-7)
x) Exit

PVT is the menu's name for the station's data stream. The items under each service appear only when it is on.

Key	Panel field
`1` … `3`	TCP Client: on/off, host, port
`4`, `5`, `9`	TCP Server: on/off, port, RTCM only (Base mode)
`m`, `k`	Remote configuration: mode and password (the menu only says whether it is set)
`6`, `7`	UDP Server: on/off, port
`8`	serial only: Display server IP address (TCP/UDP)
`r`	serial only: WiFi max retry delay (WiFi)

8 appears with the TCP or the UDP server on.

Profiles

Menu: User Profiles
1) Select Profile1 <- Current
2) Select (Empty)
3) Select (Empty)
4) Select (Empty)
5) Select (Empty)
6) Select (Empty)
7) Select (Empty)
8) Select (Empty)
9) Edit profile name: Profile1
10) Set profile 'Profile1' to factory defaults
11) Delete a profile
x) Exit

With a safety copy available, one more item appears:

12) Bring back the safety copy of profile 1 ('Profile1')

Key	Panel field
`1` … `8`	Profile + Save
`9`	Profile name
`10`, `12`	Reset Profile, Undo change (Buttons)
`11`	serial only: Delete a profile (Profiles)
`x`	after `1`…`8`, `10` or `12`, restarts with `Rebooting to apply new profile settings. Goodbye!`

Radios

Menu: Radios
1) Select Radio Type: Internal ESP-Now
  Radio MAC: XX:XX:XX:XX:XX:XX
  No Paired Radios
2) Pair radios
3) Forget all radios
4) Disable GNSS module UART2 with ESP-NOW: No
5) Network key (the same on every station): (none - packets not signed)
6) Relay the corrections received (rover): Disabled
7) Gateway: send the NTRIP client's corrections (rover): Disabled
8) Send this station's UBX (NAV-PVT, RAWX, SFRBX): Disabled
9) Collect the UBX of the other stations on the microSD: Disabled
  Packets since start: 0 copies dropped, 0 rejected (wrong key or check), 0 old format accepted, 0 relayed
  Stations heard: none in the last minute
  This station announces itself as rover
x) Exit

With External only (radio off) only item 1 is shown. The Packets since start line counts the ESP-Now packets received since power-on: copies dropped (each packet is sent twice), rejected (wrong network key or failed check) and accepted in the old format of stations with an earlier firmware, plus the packets this station has sent again as a relay. Below it, Stations heard lists the ESP-Now stations heard in the last minute, one per line with ID, role, signal, age, time on, free memory, firmware and the relay each rover asks (see ESP-Now radio › Stations heard); on a relay or a gateway, a last line gives its state: This relay is repeating or This relay is quiet: no rover asks for it, This gateway is sending the caster's corrections or This gateway is quiet: another source is sending. From firmware 1.3.18, under each station that has a solution there is a line at <latitude>, <longitude>, <height> m, <solution> (3D, RTK float, RTK fix), and with items 8 or 9 on, or once the station has heard UBX data from others, the line UBX since start: N bytes sent (N frames not sent, N packets refused by the radio), N heard from others, N saved (N not) (ESP-Now radio › Counters). The last line says which role the station announces (This station announces itself as …). Developer builds add items 10 to 12. With radios paired, No Paired Radios becomes Paired Radios: followed by one MAC address per line.

Key	Panel field
`1`	Radio
`2`	pairing, like E-Pair in the button menu: `Scanning for other radio...` until `Pairing complete`, any key cancels (ESP-Now radio)
`3`	Forget All Radios, after `y`
`4`	serial only: Disable GNSS module UART2 with ESP-NOW, until the next rover or base start (ESP-Now radio)
`5`	Network key (ESP-Now radio): type it, or an empty line to remove it; the line shows only `(set)` or `(none - packets not signed)`
`6`	ESP-Now Relay: switches between `Enabled` and `Disabled`; works only in rover, and repeats only when a rover needs it
`7`	ESP-Now Gateway: switches between `Enabled` and `Disabled`; works only in rover with the NTRIP client on
`8`	Send UBX over ESP-Now: switches between `Enabled` and `Disabled`; sends the NAV-PVT, RXM-RAWX and RXM-SFRBX switched on in Messages
`9`	Collect UBX from ESP-Now: switches between `Enabled` and `Disabled`; saves on the microSD card one file per station and per day
`x`	restarts the radio with the new settings

Broadcast Override is in Debug Network (s → n → 2).

System

Menu: System
GNSS: Online - GNSS module firmware: (version)
Module unique chip ID: XXXXXXXXXX
SIV: 32, HPA (m): 0.485, Lat: 45.12345680, Lon: 12.34567890, Altitude (m): 50.0
Display: Online
Fuel Gauge: Online - Batt (100%) / Voltage: 4.19V
microSD: Online
Bluetooth (F8CE): Online
WiFi MAC Address: XX:XX:XX:XX:XX:XX
WiFi IP address: 192.168.1.50 RSSI: -79
System Uptime: 0 01:42:53.731 (Resets: 0)
Last reset: ESP_RST_SW
NTRIP Client Connecting - caster.example.com/MOUNTPOINT:2101 Last Uptime: 0 00:00:00.000 (Reconnects: 10)
Filtered by parser: 7 NMEA / 0 RTCM / 0 UBX
-----  Mode Switch  -----
B) Switch to Base mode
R) Switch to Rover mode
W) Switch to WiFi Config mode
-----  Settings  -----
b) Set Bluetooth Mode: Classic
c) Shutdown if not charging: Disabled
d) Debug software
e) Echo User Input: On
f) Display microSD Files
h) Debug hardware
n) Debug network
l) Power Saving
m) RTCM message statistics
o) Configure RTK operation
p) Configure periodic print messages
r) Reset all settings to default
z) Set time zone offset: 00:00:00
~) Setup button: Enabled
w) Start in WiFi Config at power on: Disabled
S) Shut down
x) Exit

The lines above Mode Switch are a read-only status report, refreshed each time the menu is shown: GNSS module state and chip ID; satellites, horizontal accuracy (m) and position; display, battery gauge and card; Bluetooth; WiFi MAC, IP and RSSI (dBm); uptime; Last reset (as Last restart in the panel); NTRIP client and server connections; messages discarded as damaged. If the internal sensor bus does not answer, the first line is I2C: Offline - Something is causing bus problems. Under Settings, f appears only with a working card, b marks with * a change not yet applied, and with a time set c reads c) Shutdown if not charging after: N seconds.

Key	Panel field
`B`, `R`	switch to base or rover as soon as the menu is closed, like the button menu; the mode started becomes the Startup Mode
`W`	Config mode, as soon as the menu is closed and with no restart
`b`	Bluetooth Protocol (Classic = SPP, BLE, Off; applied when the menu is closed)
`c`	serial only: Shutdown if not charging (System)
`d`, `h`, `n`, `o`, `p`	Debug Software, Debug Hardware, Debug Network, RTK Operation, Periodic Print Messages
`e`	serial only: the station repeats what is typed
`f`	serial only: lists the card files with date and size; see the File Manager
`l`	Power Saving, submenu below
`m`	RTCM messages: prints the table at that moment, example below
`r`	Factory Reset (System), after `y`; any other answer gives `Reset aborted`
`z`	serial only: time zone offset (System)
`~`	stored, no effect on MS2net: the button always works
`w`	Startup Mode WiFi Config: power on into Config mode, leave it to the last mode used
`S`	switches off at once, like holding the button

Menu: Power Saving
-----  Processor LEDs  -----
1) RGB Status LED: Enabled
2) Button Backlight LED: Enabled
-----  GNSS module LEDs  -----
3) Geofence and its LED (yellow): LED Enabled, geofence Off, 0 of 4 fences
4) PPS LED: Enabled
   Note: RTK LED (green) is hardware-controlled, requires HW mod to disable
-----  Display & Audio  -----
5) Display: On
6) Buzzer: Enabled (battery warnings always on)
9) RTK fix sound: Enabled (rover, needs the buzzer)
-----  Quick Options  -----
7) Disable ALL LEDs (power saving)
8) Enable ALL LEDs
x) Exit

Items 1, 2, 4 to 6 and 9 are switches of Power Saving, in the same order; 3 opens the Geofence menu, which holds the Geofence LED (yellow) switch and the fences; 7 and 8 switch the four LEDs off or on together. Each item acts at once.

m in a rover receiving corrections:

RTCM statistics: Rover, received by the GNSS module
  Type      Count   Age (s)  Errors
  1005        149         0       0
  1074        152         0       0
  1084        146         0       0
  1094        151         0       0
  1124        144         0       0
  1230         15         0       0
  Errors (CRC failed or frame rejected): 0

In a base the first line reads Base, sent by the station, before any RTCM No RTCM yet; Other types (table full): N appears when more than 16 types have been seen.

s → l → 3, with the geofence on and one fence set:

Menu: Geofence
The GNSS module checks the fences itself and drives the yellow LED
1) Geofence: Enabled
2) Geofence LED (yellow): Enabled
3) LED on: outside every fence
4) Confidence level: none
5) Fence 1: 45.650000000, 13.770000000, radius 50.00 m
6) Fence 2: Off
7) Fence 3: Off
8) Fence 4: Off
9) Clear all fences
State: inside, fence 1 inside
x) Exit

Key	Panel field
`1`	Enable Geofence
`2`	Geofence LED (yellow) of Power Saving
`3`	LED on: outside every fence, inside a fence
`4`	Confidence level: each press moves to the next value, `none` (= No check), 68%, 95%, 99.7%, 99.99%, 99.999%
`5` to `8`	Fence 1 to Fence 4: opens the fence, submenu below
`9`	serial only: clears the four fences

The State line appears with the geofence on and is read from the GNSS module each time the menu is shown: inside, outside or unknown (no position yet), overall and then fence by fence. With no fence that has a radius it reads State: no fence in use; if the module does not answer, State: GNSS module did not answer.

Menu: Geofence - Fence 1
Fence: 45.650000000, 13.770000000, radius 50.00 m
1) Use the current position as centre
2) Latitude (decimal degrees): 45.650000000
3) Longitude (decimal degrees): 13.770000000
4) Radius (m, 0 = fence off): 50.00
5) Clear this fence
x) Exit

Key	Panel field
`1`	serial only: the position of the station becomes the centre; a radius under 1 m becomes 50 m. Without a fix: `No position fix: the current position cannot be used`
`2`, `3`	Latitude (−90 to 90), Longitude (−180 to 180), in decimal degrees
`4`	Radius (m), 0 to 4,000,000; 0 turns the fence off
`5`	serial only: clears this fence (centre and radius back to 0)

A value out of range gives Error: value out of range and is not saved. Every change reaches the GNSS module at once.

Firmware

Menu: Update Firmware
Current firmware: v1.3.N
a) Automatic firmware updates: Disabled
c) Check for device firmware update
e) Allow Beta Firmware: Disabled
x) Exit

After a check that found a newer version, with automatic updates on and a firmware file on the microSD card:

Menu: Update Firmware
Current firmware: v1.3.N
a) Automatic firmware updates: Enabled
e) Allow Beta Firmware: Disabled
i) Automatic firmware check minutes: 1440
u) Update to new firmware: v1.3.N
1) Load SD file: MS2_Firmware_v1_3_N.bin
x) Exit

Key	Explained in
`a`, `i`	serial only: Automatic updates; `i` (minutes between checks, 1 to 999999) appears with `a` enabled
`c`	Check for New Firmware: answers `New version detected`, `No new firmware available` or an error. After a check with nothing newer the line reads `c) Check for device firmware update: Up to date`; after one that found a newer version the line is not shown (the key still works) and `u` appears
`e`	Allow Beta Firmware
`u`	Update to v…
`1`, `2`…	serial only: Load SD file, one item for each `MS2_Firmware…` file on the card; a file not newer than the running firmware asks for `y` first

Over a Bluetooth echo session the menu opens with Firmware update not available while configuration over Bluetooth is active, and c only repeats that message.