Open-source vehicle simulation for engineering work

VEHRON

VEHicle Research & Optimisation Network

VEHRON is an open-source, BEV-focused forward-time vehicle simulation framework built for reproducible engineering studies. Define vehicles and testcases in YAML, run CLI-driven studies, inspect packaged outputs, and extend the simulator with local battery and HVAC model integrations when deeper subsystem work is needed.

Support snapshot

What VEHRON supports today

The current public website should not make users hunt through repository docs to understand scope. This is the supported public flow as of version 0.1.0.

Simulation scope

  • BEV-focused forward-time vehicle studies
  • Longitudinal dynamics and speed-tracking driver control
  • Fixed multi-rate scheduling across subsystem models
  • Deterministic packaged outputs for reproducible studies

Models

  • Driver, dynamics, reducer, motor, inverter, and regen models
  • Rint and ECM 2RC battery electrical models
  • Auxiliary DC loads, low-order HVAC, and thermal trend models
  • Analytical and map-based motor variants documented in the repo

Interfaces

  • Vehicle YAML and testcase YAML inputs
  • Optional drive-cycle CSV using time_s,speed_kmh
  • External battery model slot via local Python file
  • External HVAC model slot via local Python file

Capability overview

What the current model stack actually includes

VEHRON already exposes more detail than the old site communicated. The active stack is not generic marketing language; it is a concrete set of modules and study artifacts technical users can evaluate.

Driver and dynamics

Controller and vehicle motion

PID speed tracking, longitudinal force balance, aerodynamic drag, rolling resistance, grade handling, traction, braking, and forward-time state updates.

Powertrain

Reduction, motor, inverter, and regen

Fixed-ratio reduction, analytical and map-based motor variants, inverter efficiency treatment, regenerative braking blending, and energy-flow bookkeeping through the active BEV path.

Battery and auxiliaries

Electrical models with extension hooks

Public battery electrical paths include Rint and ECM 2RC, with pack parameterization, auxiliary DC loads, optional charging windows, and support for private local battery model integration.

Thermal and HVAC

Low-order trend models for engineering studies

Cabin HVAC load, simplified battery and motor thermal trend behavior, coolant trend modeling, and an external HVAC slot for teams with private subsystem code.

What VEHRON is not

Scope boundaries are part of the value proposition

The repository already does a better job than the old website at being honest about scope. The public site should preserve that honesty rather than overselling scaffolding or future ambitions as current support.

  • Not yet a broad production-grade multi-powertrain public simulator
  • Not yet a high-fidelity electrochemical battery solver
  • Not yet a GPS or latitude/longitude route replay framework
  • Not yet a broad real-vehicle validation library across many climates, vehicles, and packs

Get started

Get started in 3 steps

The public interface today is deliberately practical: install, run a reference case, and inspect a packaged study directory.

1. Clone and install
python3 -m venv .venv
source .venv/bin/activate
pip install .
vehron --help
2. Run a baseline BEV case
vehron run \
  --vehicle src/vehron/archetypes/bev_car_sedan.yaml \
  --testcase src/vehron/testcases/flat_highway_100kmh.yaml
3. Run a standard drive cycle
vehron run \
  --vehicle src/vehron/archetypes/bev_car_sedan.yaml \
  --testcase src/vehron/testcases/wltp_class3b_standard.yaml
Outputs produced
  • summary.json
  • timeseries.csv
  • Plots
  • Copied inputs, resolved configs, and case README

Why VEHRON exists

Engineering-first simulation without black-box workflow assumptions

VEHRON is aimed at teams who need reviewable assumptions, reproducible studies, and a clear path from low-order public reference models to deeper private subsystem integration.

Why teams use VEHRON

  • Transparent subsystem physics instead of opaque monoliths
  • YAML-defined studies that can be reviewed and versioned
  • Case packaging that preserves context alongside outputs
  • Local extension hooks for private battery and HVAC models
  • Research-use posture with DOI-backed archived release citation

Source and archive

Source repository and citable archive are separate on purpose

Use GitHub for source, issues, and project activity. Use the Zenodo record for a citable archived software release. Version 0.1.0 was archived on 2026-04-20 with DOI 10.5281/zenodo.19660006.