The short version
Different vehicle subsystems evolve at different natural rates. Driver response, powertrain behavior, battery states, and thermal trends do not all need the same update cadence. VEHRON uses fixed multi-rate scheduling so those differences stay explicit instead of being hidden in an ad hoc execution pattern.
Why not a single global time step?
A single fast step makes slow subsystems more expensive than they need to be. A single slow step smooths over behavior that matters for control and energy flow. Multi-rate execution is the compromise that lets VEHRON keep useful resolution where it matters without forcing every model to run on the most expensive cadence.
Why keep the rates fixed?
VEHRON is intended for transparent engineering studies, not opaque convenience. Fixed schedules are easier to explain, easier to test, and easier to compare across cases. When a user inspects outputs, they can reason about timing assumptions without chasing dynamic scheduler logic.
Why this fits VEHRON specifically
The project’s design values are modularity, configuration-driven studies, and reproducible outputs. Fixed multi-rate scheduling supports all three. It gives each subsystem a natural place in time while keeping the overall run structure deterministic enough for case packaging and comparison.
What this means for future posts
More engineering notes can build on this by covering specific subsystem update patterns, model trade-offs, benchmark runs, validation work, and release notes tied to archived versions.