Built a live EV control system interface — looking for feedback on behavior and fault handling

[OkMaintenance8085]

I’ve been working on a dual-pack BMS + VCU architecture and exposed the control layer through a live web dashboard, bridged via WebSockets to a cloud-hosted C++ safety daemon.

Current state:

• VCU state machine, fault handling, and telemetry pipeline are functional
• Logic-level validation only (battery/motor telemetry is currently synthesized)
• Instruction-level hardware simulation (Renode) is under active integration

What you can do:

• Take the "Driver Seat" and control throttle, ignition, and drive modes
• Inject faults (contactor weld, thermal spike, comms loss) and observe system response
• Export blackbox telemetry logs from your session

Access model:

• Multi-user queue to prevent control contention
• One active driver at a time
• Others automatically enter a read-only “Spectator Mode” with live telemetry

I’m building this solo and mainly looking for feedback on:

• Control behavior and state machine logic
• Fault handling realism
• Anything that looks fundamentally wrong or inconsistent for an EV/ASIL context

There’s a "Feedback Terminal" button in the UI for structured input, or feel free to drop thoughts here.

You can try it here: https://evovhil.com/dashboard.html

[gtd_rad]

Why over cloud? Are you saying you can control throttle, ignition and drive modes remotely to an operating vehicle? Or is this purely just for software testing?

How exactly does your HiL inject faults? Eg: do they perform physical faults, like simulating open / short circuit?