Picture
Installation Photo Gallery - ScreenShots - Introduction, Access to configuration page, Configuring the communication ports   
(Serial & UDP)
- Setting up Sensors and Conditions - List of Values, presentation of values in the Navigation page - Configuring Relative Wind  Sensor - Configuring True Wind Sensor - Configure GAUGE1 as Rudder
Understanding Value Type

The most important part of the setup is the sensor configuration. The installer has to create the right conditions in order to decode the input data.
During software development we had to deside between a simple ready made configuration with fixed conditions according to NMEA 0183 or a system that uses the NMEA protocol and additionally is able to accept any comma delimited sentences from special hardware, analog data etc.
In the configuration of Pytheas the installer can add a lot more than typical hardware and can deside what value and where will be proccessed.

Pytheas has 42 available values assigned to specific indicators in the software (numeric values, string values or graphic presentations).
Another 20 indicators are available in the software. Some of them are fixed like the navigation lights and some of them can be assigned to specific operations for example a Led that lights when an alarm arrives. 
During setup for every condition you have to declare the Value Type. 
The type of value directs the proccessing to a special routine for decoding.
Value type: Numeric

In a condition we declare the value as numeric if the data to be proccessed is a number
Example
An example is the sentence arriving from echo sounder
$SDDPT,107.1,*7B
We want to create a condition that reads the depth every time that DPT sentence arrive and assign it to Value_13 (FWD Echo Sounder).
The value in red is always a number or "null", so we declare it as Numeric

Value type: Numeric with Status

A value is declared as numeric if the data to be proccessed is a number and additionaly
is taking care of a status. It is common for example in NMEA 0183 to find the operating status of the talker V (invalid) or A (valid)
Example
The $GPRMC arrives from GPS unit $GPRMC,103126,A,5321.160,N,00710.361,E,10.0,210.1,2056.2,031001,10,E*6D
We want to decode the COG (course over ground) but only when the GPS is
fixed and sending valid data.
In this case we declare the value as Numeric with Status and we create two conditions, the first if the status is valid and the second when the status is invalid

Value type: String

A value is declared as string if the data to be proccessed is a string (no number) 
Example
The $GPGGA arrives from GPS unit $GPGGA,103126,5321.160,N,00710.361,E,1,4,002,05,M*3E
We want to decode the latitude hemisphere N or S, so in this case we declare the value as string 

Value type: String with Status

A value is declared as string if the data to be proccessed is a string and additionaly is taking care of a status. It is common for example in NMEA 0183 to find the operating status of the talker V (invalid) or A (valid)
Example
The $GPRMC arrives from GPS unit $GPRMC,103126,A,5321.160,N,00710.361,E,10.0,210.1,2056.2,031001,10,E*6D
We want to decode the latitude hemisphere but only if the GPS is fixed and sending valid data.
In this case we declare the value as String with Status and we create two conditions, the first if the status is valid and the
second when the status is invalid

Value type: LED Status

A value is declared as LED Status if the data to be proccessed are giving a condition to switch On or OFF the indicator

Value type: LED Status with REF

A value is declared as LED Status if the data to be proccessed are giving a condition to switch On or OFF the indicator and taking care of a specific reference

Value type: Analog

A value is declared as analog if the data to be proccessed arriving from an analog module

Value type: Navtex

If a Navtex unit is connected