⚡ electrical engineering

VEHRON: A Configuration-Driven BEV Simulation Framework for Subsystem-Level Studies

VEHRON is an open-source, configuration-driven Python framework designed to provide a deterministic and traceable workflow for longitudinal battery-electric vehicle simulations through interchangeable subsystem models and auditable case outputs.

Original authors: Subramanyam Natarajan

Published 2026-04-28

📖 4 min read☕ Coffee break read

CC BY 4.0

Original authors: Subramanyam Natarajan

Original paper licensed under CC BY 4.0 (http://creativecommons.org/licenses/by/4.0/). ✨ This is an AI-generated explanation of the paper below. It is not written or endorsed by the authors. For technical accuracy, refer to the original paper. Read full disclaimer

Imagine you are a chef trying to perfect a new recipe for a high-tech, electric gourmet meal.

In the past, your kitchen was a mess. You had notes scribbled on napkins, ingredients scattered in different cupboards, and every time you tried to recreate a dish, you couldn't remember exactly how much salt you used or what temperature the oven was. If a food critic asked how you made it, you’d have to guess.

VEHRON is like a professional, high-tech "Digital Kitchen" designed specifically for engineers who are designing the future of electric cars (BEVs).

Here is the breakdown of how it works using everyday ideas:

1. The "Recipe Book" (YAML Configuration)

Instead of writing instructions in messy, complicated computer code that only "master chefs" can read, VEHRON uses something called YAML.

The Analogy: Think of this as a very clear, standardized recipe card. Instead of saying "Add some stuff to make it go," the card says: "Car Weight: 2,000kg; Battery Size: 80kWh; Wind Resistance: Low."
Why it matters: Because the "recipe" is so clear, anyone can look at it and know exactly what the car is supposed to do. It makes the whole process auditable—meaning you can prove exactly why the car behaved a certain way.

2. The "Plug-and-Play" Kitchen (Subsystem Slots)

In a normal kitchen, if you want to switch from a gas stove to an induction cooktop, you might have to remodel the whole room. In VEHRON, the kitchen is built with "slots."

The Analogy: Imagine a kitchen where the toaster, the blender, and the oven are all built into specific slots. If a company has a secret, super-advanced "Super-Toaster" (a proprietary battery model) that they don't want to show the world, they don't have to rebuild the whole kitchen. They just "plug" their secret toaster into the slot.
Why it matters: It allows different teams (the battery team, the air conditioning team, the motor team) to work on their own "appliances" and plug them into the main simulation without breaking the whole system.

3. The "Time Capsule" (Deterministic Case Packaging)

Usually, when scientists run a simulation, they get a bunch of results, but they often lose the "settings" they used to get those results.

The Analogy: Imagine if every time you cooked a meal, a robot automatically took a photo of the ingredients, recorded the exact temperature of the room, saved the recipe, and put it all in a labeled box. If you want to eat that exact same meal six months later, you just grab the box and hit "play."
Why it matters: This makes research traceable. You don't have to wonder, "Wait, was that the car with the big battery or the small one?" The "box" (the case package) tells you everything.

4. What is it actually simulating?

VEHRON isn't building a full, 3D video game of a car. It’s doing the "math" of the car's life. It calculates:

The Muscle (Motor): How much power is needed to move the car.
The Stomach (Battery): How much energy is being eaten and how hot the "stomach" is getting.
The Climate Control (HVAC): How much energy is used to keep the passengers cool or warm.
The Braking (Regen): How much energy can be "scavenged" and put back into the battery when the car slows down.

Summary

In short, VEHRON is a highly organized, digital laboratory. It takes the chaos of car engineering—the messy notes, the secret parts, and the confusing math—and turns it into a clean, repeatable, and "plug-and-play" system. It allows engineers to ask, "What happens to my car's range if I change the air conditioning or use a different battery?" and get a perfect, documented answer every single time.

Technical Summary: VEHRON – A Configuration-Driven BEV Simulation Framework

1. Problem Statement

In the early stages of Battery-Electric Vehicle (BEV) engineering and research, energy consumption and thermal studies are often conducted using fragmented workflows. These typically involve a disorganized mix of custom Python scripts, Jupyter notebooks, and spreadsheets. This fragmentation leads to several critical issues:

Lack of Traceability: Engineering assumptions (e.g., drag coefficients, battery internal resistance) are often buried in code comments rather than explicit configuration files.
Poor Reusability: Workflows are often "one-off" scripts that are difficult to extend or repeat for different vehicle archetypes or drive cycles.
Auditability Challenges: It is difficult to reconstruct the exact state of a simulation (inputs, model versions, and parameters) months after a run is completed.

2. Methodology and Architecture

VEHRON (VEHicle Research and Optimisation Network) is an open-source Python-based framework designed to provide a deterministic, traceable, and modular workflow for longitudinal BEV simulation. Its architecture is built on four pillars:

Configuration-Driven Design: The framework separates the Vehicle Definition (hardware, mass, motor specs, battery capacity) from the Testcase Definition (drive cycle, ambient temperature, charging windows) using validated YAML files.
Subsystem Slot Separation (Extensibility): To allow for high-fidelity or proprietary research without modifying the core engine, VEHRON uses "slots." Users can point a YAML field to a local Python file to inject custom, high-fidelity models for the Battery or HVAC systems.
Deterministic Case Packaging: Every simulation run generates a self-contained "case package." This includes the raw time-series data, summary metadata (JSON), standard plots, and—crucially—copies of the resolved configuration files used for that specific run.
Simulation Engine: The engine utilizes a fixed-step, multi-rate execution model. While the master timestep is typically 0.1s (for fast dynamics like motor torque), slower thermal or electrical processes run at lower frequencies to optimize computational efficiency while maintaining accuracy through signal accumulation.

Implemented Models include:

Longitudinal Dynamics: Prescribed-speed motion using standard road-load decomposition (aerodynamic drag, rolling resistance, and grade resistance).
Powertrain: An analytical envelope-based motor model (with optional CSV-based efficiency maps) and a blended regenerative braking model.
Battery: Options for a simple $R_{int}$ model or a higher-fidelity 2-RC Equivalent Circuit Model (ECM).
Thermal/HVAC: A lumped-parameter cabin thermal model coupled with low-order thermal trend models for the battery, motor, and coolant loop.

3. Key Contributions

Workflow Standardization: It moves BEV simulation from "script-based" to "configuration-based," ensuring that study assumptions are explicitly stated and version-controllable.
Modular Integration: It provides a bridge between lightweight, low-order system studies and high-fidelity subsystem modeling via its external module loading mechanism.
Reproducibility: By treating the "case package" as a first-class output, it ensures that any simulation result can be audited and rerun with identical parameters.

4. Results and Validation

The paper validates the framework using six reference vehicle archetypes (Cases A–F) calibrated against publicly available technical data.

WLTP Validation (Cases A–D): The framework was tested against the WLTP Class 3b cycle. The results showed high accuracy, with VEHRON’s energy consumption predictions falling within 0.9% to 2.1% of published manufacturer figures.
MIDC Validation (Cases E–F): Testing against the MIDC cycle showed the framework successfully captures the energy dynamics of different vehicle profiles (e.g., the higher drag/consumption of a compact SUV vs. a coupe).
Energy Budgeting: The framework successfully decomposes energy use into aero, roll, inertia, auxiliary, and HVAC components, providing a transparent "energy balance" for researchers.

5. Significance and Future Work

VEHRON occupies a unique niche between lightweight, high-level fleet analysis tools (like FAST-Sim) and heavy, high-fidelity multi-physics environments (like GT-SUITE). It is specifically optimized for the subsystem-level researcher who needs to test a new battery chemistry or HVAC strategy within a realistic vehicle context without the overhead of a commercial license or complex MATLAB dependencies.

Future Roadmap:

Expansion to Hybrid (HEV), Plug-in Hybrid (PHEV), and Fuel Cell (FCEV) powertrains.
Integration of richer route inputs, such as GPS replay and elevation profiles.
Enhanced validation against physical measurement data.