EV CAN Communication Laboratory 2.0
Six ECUs · CAN arbitration · bus load · DBC decoding · diagnostics · guided experiments
0x101
0x201
0x301
0x181
0x401
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.
Adjust battery measurements. BMS broadcasts a status frame every 500 ms.
VCU uses received battery status and inverter feedback to decide if torque is permitted.
Receives VCU torque commands and reports simulated motor speed and inverter health.
Broadcasts braking and ABS intervention. When ABS is active, VCU disables regenerative torque in this teaching scenario.
Receives VCU cooling request (0x211) and reports pump and fan operation.
A CAN listener: uses accepted BMS, Inverter and VCU status frames. Displayed values may become stale.
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.
| CAN ID | Message | Payload definition |
|---|---|---|
| 0x101 | BMS_Status | SOC u8; temp u8 offset −40; voltage u16 LE / 10 |
| 0x201 | VCU_Command | torque u16 LE (Nm); enable u8 |
| 0x301 | Inverter_Status | speed u16 LE (rpm); fault u8; torque u16 LE (Nm) |
| 0x181 | ABS_Status | brake pressure u8 (%); ABS active u8; wheel speed u16 LE /10 (km/h) |
| 0x211 | VCU_Cooling | cooling request u8 (0/1) |
| 0x401 | Thermal_Status | pump u8; fan u8; pump fault u8 |
| 0x501 | Dashboard_Heartbeat | dashboard alive counter u8 |
These are teaching definitions, not standardized OEM CAN IDs. u16 LE = unsigned 16-bit little-endian.
Decoded signals
Received motor-speed history
Graph shows inverter feedback received by the VCU, not a physical motor model.
| Time (s) | Sender → receiver | CAN ID | DLC | Data hex | Result |
|---|---|---|---|---|---|
| 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.
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.
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.