Different systems.
One vessel view.

The battery view brings together state of charge, pack voltage, current and power, with a 36-cell pack map for more detailed inspection. Solar output and house electrical measurements have their own views and histories.

For an owner or captain, the benefit is context: a clearer picture of energy use, charging contribution and how readings change over time.

An onboard Raspberry Pi service collects and normalizes information from the CAN network, the house electrical gateway and the navigation instrument gateway. A dedicated Android cockpit display receives the shared vessel state over authenticated, encrypted connections.

Keeping collection and interpretation in one place supports a consistent interface and a system that can be understood and maintained. The architecture is tailored to the available equipment and confirmed interfaces.

Source status, age and gaps matter. The system distinguishes a missing reading from a measured zero, and preserves gaps in trends rather than drawing an uninterrupted picture through missing data.

Weather views bring wind, pressure and available temperature measurements alongside the vessel’s electrical information. Useful histories let crew examine changes instead of relying on a single momentary number.

Selected lighting integration uses the onboard controller’s catalog and guarded requests. The interface distinguishes requested settings, controller feedback and the physical result—each needs its own verification.

We carry that same discipline into project scoping: identify what can be monitored, define which controls are appropriate and agree how installed behaviour will be accepted.