EV CAN Communication Laboratory 2.0

Six ECUs · CAN arbitration · bus load · DBC decoding · diagnostics · guided experiments

Educational simulator, not a hardware CAN transceiver. ECU traffic, decoding, and control logic are modeled; arbitration, frame errors, ACK, CRC and bus load are simplified teaching models, not bit-accurate physical CAN. No real safety validation. Works fully offline.

1. Six ECUs on one virtual CAN bus

BMS
0x101
VCU
0x201
INVERTER
0x301
ABS
0x181
THERMAL
0x401
DASH
0x501

BMS broadcasts battery status; ABS broadcasts brake/traction data; VCU calculates torque and cooling requests; Inverter and Thermal ECUs report feedback; Dashboard listens to the bus.

Stopped · ready to start

2. BMS

Transmitter

Adjust battery measurements. BMS broadcasts a status frame every 500 ms.

Ready

3. VCU

Decision maker

VCU uses received battery status and inverter feedback to decide if torque is permitted.

WAITING FOR DATA
Torque command0 Nm
Received SOC / battery temperature—
Received motor speed—

4. Inverter

Receiver + transmitter

Receives VCU torque commands and reports simulated motor speed and inverter health.

WAITING FOR COMMAND
Applied torque0 Nm
Motor speed (simplified)0 rpm

5. ABS / Brake ECU

0x181 · 200 ms

Broadcasts braking and ABS intervention. When ABS is active, VCU disables regenerative torque in this teaching scenario.

Waiting

6. Thermal ECU

0x401 · 500 ms

Receives VCU cooling request (0x211) and reports pump and fan operation.

Cooling commandOFF
Pump / fanOFF / OFF
Waiting

7. Dashboard ECU

0x501 · 1000 ms

A CAN listener: uses accepted BMS, Inverter and VCU status frames. Displayed values may become stale.

Battery SOC—
Motor speed—
Drive stateWAITING
Waiting for traffic

8. CAN frame inspector and DBC-style decoder

Select a logged frame to inspect its identifier, DLC, raw hex bytes, and decoded engineering values. The table below acts like a simplified DBC signal dictionary. Download the matching teaching DBC to inspect the signal definitions in a separate DBC-capable tool.

Selected frameNo frame selected
Press Send BMS once or start the simulation.
CAN IDMessagePayload definition
0x101BMS_StatusSOC u8; temp u8 offset −40; voltage u16 LE / 10
0x201VCU_Commandtorque u16 LE (Nm); enable u8
0x301Inverter_Statusspeed u16 LE (rpm); fault u8; torque u16 LE (Nm)
0x181ABS_Statusbrake pressure u8 (%); ABS active u8; wheel speed u16 LE /10 (km/h)
0x211VCU_Coolingcooling request u8 (0/1)
0x401Thermal_Statuspump u8; fan u8; pump fault u8
0x501Dashboard_Heartbeatdashboard alive counter u8

These are teaching definitions, not standardized OEM CAN IDs. u16 LE = unsigned 16-bit little-endian.

Decoded signals

No data yet

Received motor-speed history

Graph shows inverter feedback received by the VCU, not a physical motor model.

9. CAN traffic monitor

Click any row to inspect its frame. Newest first, maximum 250 frames.

Time (s)Sender → receiverCAN IDDLCData hexResult
No traffic yet.

0 frames

10. CAN protocol explorer — simplified arbitration and bus load

CAN arbitration: for simultaneous standard 11-bit data frames, the lowest identifier has highest priority. A dominant 0 beats recessive 1. This interactive demonstration compares ID bits, not real electrical waveforms.

Choose IDs and click Run arbitration.
Estimated virtual traffic load—Estimated from transmitted application messages and a rough standard CAN overhead model, not a wire-level measurement.
Observed application frame rate (last 5 seconds)—

11. CAN diagnostics and fault injection

Use these to diagnose message loss. Corruption and retransmission are intentionally abstract: this browser does not calculate CAN CRC, bit stuffing, error counters, or electrical ACK.

Delivery statistics—

Observe the monitor, then request a hint.

Simulation model: sender logs an attempt, virtual receiver accepts/filters/drops it, and optional retry attempts delivery once. A real CAN controller handles ACK, CRC, arbitration and error confinement differently.

12. Step-by-step student experiments

Complete the tasks in order. Each step includes an action, expected observation, and engineering explanation.

13. Safety rules, assumptions, and student report questions

Safety logic in this exercise: VCU permits torque only if enable is on, brake is released, BMS SOC ≥ 10%, battery temperature ≤ 60 °C, battery voltage ≥ 250 V, no inverter fault, and BMS, inverter and ABS feedback are fresh (≤ 2 seconds). It sends 0 Nm otherwise. The inverter also rejects stale commands (older than 1 second).

Report: (1) Which ECU publishes each message? (2) What is the difference between CAN ID and payload? (3) Decode the first BMS frame by hand. (4) Why does an ID mismatch cause a timeout? (5) Why does the VCU command zero torque after a BMS fault? (6) What is the difference between a browser simulation and a physical CAN bus?

Note: The teaching rules and thresholds are illustrative, not production EV safety requirements. Browser background tabs can throttle timers. Reset before each experiment for a clean result.