CLI reference
The pages in this section document the actual chargelink command tree found in the repository snapshot. Every page below includes the raw argparse help output plus production-oriented examples built around profiles, packages, suites, and hardware IDs present in the snapshot.
CLI command groups
- chargelink evse
- chargelink evcc
- chargelink hil
- chargelink scenario
- chargelink campaign
- chargelink qualification
- chargelink suite
- chargelink report
- chargelink trace
- chargelink replay
- chargelink lab
- chargelink beckhoff
- chargelink protocol
- chargelink artifacts
- chargelink sequence
- chargelink macro
- chargelink verdict
- chargelink step
- chargelink profile
- chargelink template
- chargelink library
- chargelink batch
- chargelink campaign-stress
- chargelink service
- chargelink requirements
- chargelink backend
- chargelink evidence
- chargelink audit
- chargelink ports
- chargelink env
- chargelink capture
- chargelink ci
- chargelink sessions
- chargelink fault
- chargelink network
- chargelink fuzz
Group |
What it controls |
|---|---|
Operate ChargeLink as an EVSE simulator and lab endpoint. This is the operator surface you use to start, stop, inspect, and hardware-bind live SECC runtime sessions. |
|
Operate ChargeLink as an EVCC simulator or as a controller for external EVCC backends such as Josev and EVerest. |
|
Run the HIL adapter layer for bench-oriented MCS and hardware-backed execution paths. |
|
Validate and execute single JSON scenarios. |
|
Run packaged interoperability and conformance campaigns and inspect their outputs. |
|
Build or verify protocol qualification bundles and launch gates. |
|
Run named ChargeLink suites that aggregate campaigns and qualification checks. |
|
Generate, archive, comment, and filter human-readable run reports. |
|
Inspect protocol traces and stream or export message-level evidence. |
|
Replay stored runs and compare two traces or sessions. |
|
Perform lab preflight checks and document a network or HIL topology. |
|
Export Beckhoff synchronization metadata used in EL6761 or ADS-backed bench environments. |
|
Decode, validate, inspect, and sequence protocol artifacts. |
|
Inspect a run directory and export it as a bundle. |
|
Record repeatable operator sequences and execute them later. |
|
Store and replay short CLI macro strings. |
|
Assign a final verdict to an operator-controlled run. |
|
Track operator steps and their pass, warn, or fail outcomes. |
|
List, inspect, validate, clone, and derive connection settings from profiles. |
|
Create starter JSON files for scenarios and campaigns. |
|
Validate catalog or library directories. |
|
Run a folder of inputs and continue or retry a batch later. |
|
Stress the campaign engine across protocol families to exercise concurrency and pacing. |
|
List service names and validate service behavior against a trace or run. |
|
Map campaign content to requirements and link imported requirement IDs to runs. |
|
Inspect and diagnose EVCC backend adapters. |
|
Map evidence, validate manifests, attest, sign, import, list, and export MCS or release evidence bundles. |
|
Run commercialization and source-origin audits, including SBOM and release-blocker exports. |
|
Check whether important operator ports are available on the current host. |
|
Run an environment doctor for the current workstation. |
|
Start generic captures and run MCS bench capture automation. |
|
Run scenario, campaign, or job inputs under CI-style wrappers and export reports or JUnit XML. |
|
List or inspect runtime sessions by run ID. |
|
Inject protocol faults from the supported fault catalog. |
|
Apply or disable network impairments such as delay, jitter, and packet loss. |
|
Run protocol-family fuzzing passes and store their results as artifacts. |