Connectivity between StarNavPilot and
StarNavPilot uses service technology. The
communication layer between StarNavPilot and the various instruments to which
the software connects (GPS, depth sounder, wind vane, electronic compass,
autopilot, AIS receiver or transponder, etc.) uses independent services
depending on the desired communication mode (called positioning engines). To
change the connection mode used by the program, simply select it from the
drop-down list of installed positioning engines. Switching from one positioning
engines to another is instantaneous. All installed positioning engines have a
default configuration applied on first use. Unless there is a specific reason,
they can be used without any configuration.
Currently the positioning
engines available when installing the software are:
NMEA on USB or
serial port with automatic port detection.
AIS on USB or serial port
with automatic port detection.
High speed NMEA + AIS multiplexed on USB
or serial port with automatic port detection.
NMEA + AIS Wifi or
network preconfigured for use on the standard port normally reserved for NMEA
NMEA + AIS by communication file preconfigured to
use StarNavPilot communication files.
AIS for maritime traffic control
with no configuration required.
NMEA simulator without configuration
Each positioning engines has its own configuration utility
independent of the general NMEA configuration.
The advantages of using independent services for each of
the communication layers and the main StarNavPilot module are:
configuration of NMEA/AIS decoding does not depend on the communication engine
used. All the NMEA/AIS parameters are found if you change the communication
- A slowdown due for example to saturation of the AIS data in a
high traffic area will have no effect on the decoding of the navigation data
(position, speed, heading, route following, etc.) nor on the program whose the
display will remain perfectly fluid as well as any alarms
StarNavPilot can receive NMEA and AIS data from an external
application. In this case, even if this application is independent from
StarNavPilot, it is managed by StarNavPilot as a service. In this case, the file
or UDP communication engine will generally be used to receive the
As the positioning engine is
independent from the main module, StarNavPilot can use different engines
suitable for special purposes:
Example: Remote transmission of
positions onshore for monitoring a fleet of mobiles, remote control of drones,
autonomous positioning beacons, etc...
An additional positioning
engine installs in 1 click and is immediately available. Inquire about any