CHAdeMO Operator Runbook
CHAdeMO uses CAN rather than the IPv6/SDP/TCP path used by ISO 15118 and DIN 70121. Complete the virtual-CAN workflow before connecting a physical adapter or power stage.
1. Discover the installed CAN surface
$CL = "C:\Program Files\ChargeLink Native\chargelink.exe"
& $CL dc-can catalog --json
& $CL evse hardware-profiles --json
2. Run a virtual session
& $CL dc-can virtual-run `
--protocol chademo `
--profile dc_can_virtual_evse `
--frame-count 100 `
--sample-period-ms 50 `
--json
Confirm that frames are produced, timestamps advance, requested voltage/current values remain within the test limits and the run terminates cleanly.
3. Connect a physical adapter
Identify the adapter kind and channel from dc-can catalog. Then replace the placeholders below.
$ADAPTER = "<adapter-kind-from-catalog>"
$CHANNEL = "<adapter-channel>"
& $CL dc-can chademo-can-adapter-loop `
--adapter-kind $ADAPTER `
--adapter-mode hardware `
--channel $CHANNEL `
--bitrate-kbps 500 `
--require-hardware `
--json
4. Bench safety checklist
Before enabling power:
- Use an isolated, current-limited supply or approved HIL interface.
- Verify CAN-H, CAN-L and reference ground.
- Confirm termination resistance with the bench powered down.
- Confirm the adapter channel and bitrate.
- Run receive-only or virtual validation first where supported.
- Keep the emergency stop accessible.
- Start with contactors inhibited and verify state progression.
5. Fault and watchdog validation
The implementation includes CHAdeMO fault categories such as missing or late heartbeat, invalid voltage/current request, current-demand timeout, stop timeout, malformed CAN frame, unexpected EVCC state transition, unavailable adapter channel and bus silence after session start. Use the installed CLI help to list the exact campaign command and accepted fault names:
& $CL dc-can --help
& $CL dc-can chademo-can-adapter-loop --help
Do not treat a virtual-CAN pass as evidence that a physical charger, vehicle or adapter is safe or interoperable.

