Live Yacht Data On Every Screen, Feeding Every Module
YOS speaks your yacht's native protocols: SignalK over REST and WebSocket (Victron Cerbo GX, OpenPlotter), NMEA 0183 sentence parsing, and NMEA 2000 with full PGN decoding — through Actisense, iKonvert, and Yacht Devices gateways. The Monitoring section of the Navigation hub renders it live: Navigation (position, SOG, COG, heading, wind speed and angle, air temperature and pressure, water temperature, dual depth), Engines port and starboard (RPM, load, coolant, oil pressure, fuel rate, hours), Tanks (fresh water, fuel daily, fuel storage, grey, black), and Batteries — with an active alarms banner across the top. And the data works for a living: it feeds logbook entries, drives Equipment and PMS running hours, and fills the dashboard.
The Problem
Sensor data on individual gauges in the engine room. Bridge repeaters show basic navigation. Tank levels checked manually. Engine hours logged on paper. Nobody aggregates trends. Temperature alerts come after the damage. When the engineer asks 'what was port engine coolant temp at 14:00?' — nobody knows.
What you get
- SignalK over REST and WebSocket — Victron Cerbo GX and OpenPlotter ready
- NMEA 0183 sentence parsing — GGA, RMC, GLL, VTG, HDT, DBT, DPT, MTW, MWV, MWD
- NMEA 2000 PGN decoding via Actisense, iKonvert, and Yacht Devices gateways
- Navigation: position, SOG, COG, heading, wind, air temp and pressure, water temp, dual depth
- Engines port and starboard: RPM, load, coolant, oil pressure, fuel rate, running hours
- Tanks: fresh water, fuel daily, fuel storage, grey and black water
- Battery monitoring and an active alarms banner
- Sensor-assisted logbook entries and running hours fed to Equipment and PMS
Works Offline — Live telemetry requires yacht network connectivity. When offline, the last known sensor state is cached and displayed with timestamp. Logbook entries created from sensor data sync normally.
Connected modules