Quickstart: first EVSE session, first campaign, first report

A newcomer can get productive quickly by treating ChargeLink as a three-step loop: start a runtime, run a case, inspect the artifacts.

1. Start a software-only EVSE session

chargelink evse start --host 'fe80::640b:3f3d:c4fe:3d9f%19' --interface-index 19 --advertise-ipv6 'fe80::640b:3f3d:c4fe:3d9f%19' --protocol 'iso15118-2' --profile-id 'abb_pnc_realistic' --tcp-port 55000 --udp-port 15118 --tls --tls-cert 'server.pem' --tls-key 'server.key' --tls-cafile 'ca.pem' --artifact-root 'artifacts/evse_runtime' --foreground

2. Run a packaged campaign

chargelink campaign run 'campaigns/interoperability/iso15118_20/ac/cl_int_iso20_ac_negative_realistic.json' --artifact-root 'artifacts/evcc_campaign_runs'

3. Generate a report and inspect the trace

chargelink campaign report 'artifacts/evcc_campaign_runs/cl_int_iso20_ac_negative_realistic' --output 'artifacts/reports/iso20_ac_negative_report.json'
chargelink trace show 'artifacts/evcc_campaign_runs/cl_int_iso20_ac_negative_realistic/case_1' --limit 20
chargelink protocol validate 'artifacts/evcc_campaign_runs/cl_int_iso20_ac_negative_realistic/case_1'
chargelink report generate 'artifacts/evcc_campaign_runs/cl_int_iso20_ac_negative_realistic' --output 'artifacts/reports/iso20_ac_negative_run_report.json'

What to look at next

summary.json for the high-level outcome.
session.json for the selected protocol and session identity.
protocol_report.json and conformance_traceability.json when you want standards-oriented evidence.
message_trace.json and trace.jsonl when you want message-by-message behavior.