ChargeLink Native

Complete CLI Reference

Generated from the help output of the shipping chargelink binary, version 0.5.0-rc2 (JSON contract native-core-0.55). The installed binary remains the final authority: run chargelink --help and chargelink <command> --help on the machine you operate. The help text comes from pc1\bin\chargelink.exe of the 0.3.1 package.

Global syntax

chargelink [--json] [--runtime-root DIR] [--artifact-root DIR] [--license FILE] <COMMAND> [SUBCOMMAND] [OPTIONS]
Global optionDefaultMeaning
--jsonoffEmit a machine-readable JSON payload on stdout. On failure a single JSON diagnostic envelope is emitted instead of console text.
--runtime-root DIR.chargelink/runtime (relative to the current directory)Session state, PID, lock and heartbeat files. The license store is the sibling directory <parent>/licenses.
--artifact-root DIR.chargelink/artifacts (relative to the current directory)Run directories with manifest.json, traces, reports and evidence.
--license FILEnoneUse this license file for the command instead of the activated license. A missing file fails with CL-LICENSE-001 before the command runs.
-V, --versionPrint the CLI version (chargelink 0.3.1 for the documented release).

Global options may be written before or after the subcommand. Environment variables the CLI reads: the one named by --tls-pfx-password-env; CHARGELINK_API_TOKEN_FILE (the gRPC access token file for every --endpoint / --grpc-endpoint client); CHARGELINK_ISO20_RUNTIME_PROFILE, CHARGELINK_ISO20_LIVE_SEMANTIC_CASE, CHARGELINK_ISO20_FULL_WIRE_SESSION_MANIFEST and the CHARGELINK_ISO20_PNC_* fixture variables of the ISO 15118-20 lanes. Logging is fixed at info level on stderr.

Top-level commands

CommandPurpose
integrationNative ChargeLink Integration API v1 server and client operations
signalsCanonical ChargeLink signal discovery, read, write and verification operations
veristandNI VeriStand operator bridge and reference SIL operations
evseRun and inspect the EVSE (charger-side, SECC) role: dry-run, live listener, TLS/PKI diagnostics, preflight and evidence lanes.
evccRun and inspect the EVCC (vehicle-side) role: dry-run, direct TCP or SDP sessions, loopback smoke, battery models and TLS probe.
profileList, show and validate built-in and custom profiles.
envEnvironment doctor.
doctorAlias for env doctor
backendBackend adapter diagnostics (compatibility alias of the environment doctor).
diagnosticsExit-code policy, error taxonomy and sample diagnostic envelopes.
exiNative EXI codec catalog, fixtures, round trips and negative corpus.
licenseLicense status, verification, activation, deactivation and offline requests.
standardsStandards compliance matrix and entitlement gate.
runtimeRuntime session lifecycle: list, inspect, recover, locks and policy.
artifactsArtifact manifests: index, inspect, integrity, redaction and support bundles.
uiDashboard contracts.
hilHIL adapter policy, virtual HIL run and evidence import.
dc-canScripted DC-CAN virtual runs, adapter loops and campaigns for test development; not a protocol implementation.
iso2-evccthe ISO 15118-2 DC EIM EVCC role (SDP, TCP or TLS 1.2, one session)
iso2-pkia new engineering ISO 15118-2 private-environment TLS identity (SECC chain and key, EVCC root)
din-evccthe DIN 70121 DC EVCC role (SDP, TCP only, one session)
atsNative ATS registry, PICS/PIXIT, campaigns and licensed package operations.
testProduction protocol-first test discovery, planning, execution and reporting
conformanceProduct CLI: protected conformance/security package operations
studioServe or open the EVCC simulator dashboard.
simDeterministic paired EVSE/EVCC simulation, scenario suites, TLS/PKI campaigns and replay.

Exit codes

See Monitoring, JSON and Exit Codes for the full exit-code and error-code policy.