Open-source vehicle simulation for engineering work

VEHRON

VEHicle Research & Optimisation Network

A modular, configuration-driven simulation platform for transparent vehicle analysis. VEHRON is built for research teams who want swappable subsystem physics, reproducible case outputs, and a clear path from reference models to higher-fidelity workflows.

Approach

Designed for transparent engineering simulation

VEHRON is intended for teams who want visibility into model structure, confidence in assumptions, and a workflow that can grow from simple studies to more advanced subsystem development.

Architecture

Modular subsystem physics

Each subsystem is designed as its own model path, making it easier to improve one area without rewriting the whole simulator.

Timing

Fixed multi-rate integration

A master simulation clock coordinates models running at their natural rates, from fast driver tracking to slower battery and thermal updates.

Workflow

Configuration-driven studies

Vehicles and experiments are defined through YAML inputs so studies are easier to review, share, and reproduce.

Battery

Hot-swappable battery interface

Teams can integrate private battery models locally while keeping the open reference path available in the public repository.

Current capabilities

What works today and what the platform is growing toward

VEHRON already supports a working BEV 4W simulation path, with planned extensions toward higher model fidelity and additional vehicle classes.

Working today

  • Driver speed tracking
  • Longitudinal dynamics
  • Fixed-ratio drivetrain reduction
  • Motor and inverter models
  • Charging and regenerative braking
  • Energy bookkeeping and case packaging

Input and output flow

  • Vehicle archetype YAML
  • Testcase YAML
  • Optional drive-cycle CSV
  • summary.json and timeseries.csv
  • Plots and copied case metadata
  • Reproducible study directories

Still developing

  • BEV 2W as the next major path
  • Richer battery OCV behaviour
  • Higher-fidelity tyre and cooling models
  • More resolved battery thermal modelling
  • Broader validation and calibration workflows

Research use

Created for research groups, engineering teams, and open development

VEHRON is as much a reproducible experiment framework as it is a simulator. That makes it useful for benchmarking, validation work, coursework, and subsystem model iteration.

Typical use cases

  • BEV energy consumption studies over standard drive cycles
  • Thermal and HVAC trend analysis
  • Battery-team integration workflows with private models
  • Transparent teaching material for vehicle systems
  • Reusable case packages for comparison and review

Journal

An engineering journal for architecture, modelling, and validation work

The VEHRON blog serves as a technical journal for design decisions, model evolution, benchmark studies, and notes from the development process.

First post

Why VEHRON uses fixed multi-rate simulation

A first look at the timing model behind VEHRON, why multi-rate execution matters for engineering studies, and how it keeps the simulator usable as subsystem fidelity grows.

9 April 2026

Planned themes

  • Architecture notes and timing design
  • Battery, thermal, and drivetrain model deep-dives
  • Validation studies and benchmark runs
  • Reproducible workflow notes and release logs

Download

GitHub is the current home for source, releases, and project activity

The current download path leads directly to the VEHRON GitHub repository, where users can access the source tree, releases, issue tracking, and ongoing project updates.

Licensing

Licensed under the GNU AGPL v3 by design

VEHRON is licensed under the GNU AGPL v3. This is an intentional choice. VEHRON is independent work built through personal engineering effort, time, experimentation, and iteration rather than institutional sponsorship.

The goal of the license is to keep the simulator and its improvements in the commons, including in hosted or networked use, while preserving clear long-term stewardship of the project as it grows. Contributions are welcome, and non-trivial contributions are handled under a contributor agreement so governance and future licensing flexibility remain clear from the start.

Community and contact

Project questions, collaboration, and feedback currently run through GitHub

For now, the main public contact path for VEHRON is GitHub. That keeps bug reports, feature requests, and technical discussion attached to the source and visible to contributors.

Where to reach the project