Scripted DC-CAN Lanes

The dc-can command group runs fixed, pre-scripted lists of CAN fixture frames on a virtual bus, with a closure simulator that checks that each run completes. They are for engineering and test development, for example to exercise a CI pipeline, an evidence workflow or a test harness without hardware. For the IEC 61851-23/-24 System A implementation (station and EV roles, dc-can chademo), see the IEC 61851-23/-24 System A runbook; this page covers only the scripted fixture lanes.

Limits. These lanes are not a protocol implementation and must not be reported as charging-protocol capability. The frames come from a small fixture catalogue; nothing is computed from a peer's messages. The adapter kinds (peak-pcan, vector-xl, kvaser-canlib, socketcan, slcan, lawicel, usbtin) are descriptors that never open hardware, and hardware mode is an operator attestation. No physical bus traffic is generated.

$CL   = 'C:\ChargeLink\0.5.0-rc2\pc1\bin\chargelink.exe'
$Data = 'C:\ChargeLinkData'

Commands

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json dc-can catalog
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json dc-can virtual-run --protocol chademo --profile dc_can_virtual_evse --frame-count 8 --sample-period-ms 50
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json dc-can chademo-live-run --run-id dc-can-live-01
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json dc-can chademo-can-adapter-loop --run-id dc-can-loop-01 --adapter-kind peak-pcan --adapter-mode loopback --channel PCAN_USBBUS1 --bitrate-kbps 500
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json dc-can chademo-fault-campaign --run-id dc-can-fault-01
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json dc-can chademo-longrun-campaign --run-id dc-can-longrun-01 --cycles 25 --mode loopback

dc-can catalog lists the fixture frames and profiles. virtual-run plays a number of fixture frames at the given sample period; the --protocol option selects the fixture set. The adapter loop runs the same virtual run bound to an adapter descriptor. The fault and long-run campaigns repeat the scripted run with injected faults or for a number of cycles. Every command writes a run directory with a manifest under the artifact root.

Reading a result

A passing run means that the scripted frame list was played and the closure simulator reached its expected end state. It does not show that any charger, vehicle or third-party implementation would behave the same way. dc-can release-gate reports compliance_claim: none_dc_can_foundation_only for the same reason.

For CAN-based charging standards, contact DEVlink.