Garmin–Victron Vehicle Control Integration
Developing Garmin-based vehicle interfaces that combine Victron power data, RV-C device control, and customer-specific automation in one operating surface.
Control-system boundary
One surface, coordinated behavior
I develop Garmin-based control interfaces that bring Victron power data, RV-C devices, and vehicle subsystems into one operating surface. The work includes programming customer-specific systems, mapping device state and commands, and translating the electrical architecture into controls that are usable without requiring the operator to understand every component behind them.
On the Noovo Next platform, that meant supporting a move from 12 V to 48 V power while building a fully branded Garmin interface for lighting, climate, power, connectivity, and system monitoring. We extended the available Garmin framework with an embedded HTML interface so the product could be developed more like a modern web application without separating the user experience from the underlying vehicle controls.
The harder part is not displaying the data; it is defining how the systems cooperate. Shore-power availability, battery state, temperature, and user intent can change which loads should run and which energy source is appropriate. I test those rules against real hardware and firmware updates so the single-screen interface remains consistent with the state of the power system and the physical vehicle.
- Human-machine interfaces
- CAN and RV-C
- Embedded web interfaces
- Energy-aware automation
- OEM integration
- Format
- Embedded interface integration
- Threads
- Engineering · Fieldwork
Deployed integrations · ongoing platform development