Data

The data page is used to configure outgoing and incoming data. Using this page, it is possible to configure a data stream going to an external logging device. Data can be sent over ethernet (UDP) or by using the RS232 protocol.

Sensor specification

If an RS-232 port is not present in the housing of the system, the data lines are embedded in the Lemo-connector and a specific cable/box may be necessary to access the RS-232 port.

Data over ethernet

Entry	Description
Stream data over UPD	Enable/disable the datastream
Ip address	The address where to send the data
Port	The address where top send the data
Data included in the stream	Configure which messages are included in the data stream (see JSON sensor documentation for a descript of the data)

RS232 port

Entry

Description

Mode

Output: Stream data: Send the sensor data in the JSON format over RS-232
This setting will add the configuration of the included messages in the data stream (see JSON sensor documentation for a descript of the data)

Output: Medusa NMEA strings: Send the sensor data in the Medusa NMEA protocol over RS-232
This setting will add the configuration of the included sensors in the data stream, and the channels to sum option (see Medusa NMEA protocol documentation for the description of the data).

Output: GPS and total counts strings: Send the GPS and total counts data in a single line over RS-232
Format: #Sensordata, Unix-Timestamp, Lat, Lon, Total-Counts\n
Example: #Sensordata,1596015020973,53.2110364,6.612181,375

Input: RTCM GPS corrections: These corrections will be passed to the GPS and enable RTK precision. The Received RTCM Data will show the message type and in brackets the count if these messages.
Input: NMEA strings: This option will listen for GGA NMEA messages and will parse these for latitude and longitude. Other messages than the GGA string will be ignored.
Input: CSV formatted data: a CSV array streamed to the RS-232 port will be stored in a CSV_external JSON data entry in the project.
Input: JSON formatted data: a JSON formatted string streamed to the RS-232 port will be stored in a JSON_external JSON data entry in the project.
Input: text data: Text streamed to the RS-232 port will be stored in a TXT_external JSON data entry in the project.

Baud rate

The baud rate of the RS-232 connection

Show incoming data

Open a pop-up where the incoming data can be inspected. Note that this is the JSON string generated by the mDOS system. If the syntax of the incoming data is not correct, e.g. not a correct JSON in the case of Input: JSON formatted data, no data is shown.

NTRIP

NTRIP messages are corrections applied to the GPS data and enable RTK precision (centimetre) of the GPS. For this, an external source of corrections is needed, and these are passed through an NTRIP service.

Entry	Description
Enable	Enable/disable NTRIP messages
Host	The IP address or website of the host
Username	The username for the NTRIP service
Password	The username for the NTRIP service
Select mountpoint	The mountpoint used for the RTK corrections. A list can be retrieved by selecting a correct host and port and then using the request mountpoints button. The connection with the NTRIP server can be verified by pressing the request mountpoints button. If there is a valid connection with the NTRIP service, this will give you a list of available mountpoints
RTCM indicator	An indicator showing RTCM the messages that are coming in. The message type is shown and in brackets the count if these messages are shown.

NTRIP services that send corrections that are not dependent on a single location need to receive a position from the device that is requesting the corrections. These services will only start working when a valid GPS position is send to the NTRIP service.

Make sure that the GPS of the spectrometer is receiving valid GPS positions to start the NTRIP correction data stream.