chargelink evse

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.

Reference syntax

usage: chargelink evse [-h]
                       {start,stop,status,list-state,hardware-profiles,bench-blueprint,bench-bom,io-map,bench-sequence,veristand-map} ...

positional arguments:
  {start,stop,status,list-state,hardware-profiles,bench-blueprint,bench-bom,io-map,bench-sequence,veristand-map}

options:
  -h, --help            show this help message and exit

Subcommands

Subcommand	Purpose
`start`	Start a live EVSE runtime with a selected charger profile, protocol family, network configuration, TLS policy, artifact root, and optional campaign hooks.
`stop`	Request a graceful stop for one EVSE runtime by run ID.
`status`	Read the current status snapshot for a single EVSE run.
`list-state`	List all EVSE state snapshots under the configured runtime root.
`hardware-profiles`	List registered hardware profiles for EL6761, MCS, NI, and VeriStand-backed execution paths.
`bench-blueprint`	Export the bench blueprint for one hardware profile.
`bench-bom`	Export the bill of materials for one hardware profile.
`io-map`	Export the logical or physical I/O map for a hardware profile.
`bench-sequence`	Export the bench orchestration sequence for a hardware profile.
`veristand-map`	Export the VeriStand mapping payload for a hardware profile.

start

Start a live EVSE runtime with a selected charger profile, protocol family, network configuration, TLS policy, artifact root, and optional campaign hooks.

CLI help

usage: chargelink evse start [-h] [--runtime-root RUNTIME_ROOT]
                             [--run-id RUN_ID] [--profile PROFILE]
                             [--profile-id PROFILE_ID]
                             [--protocol {iso15118-2,iso15118-20,mcs,din70121}]
                             [--host HOST] [--interface INTERFACE]
                             [--interface-index INTERFACE_INDEX]
                             [--advertise-ipv6 ADVERTISE_IPV6]
                             [--hardware-profile HARDWARE_PROFILE]
                             [--mcs-hil-driver {mock,http,ni_daqmx,veristand}]
                             [--mcs-hil-endpoint MCS_HIL_ENDPOINT]
                             [--mcs-plca-role {coordinator,follower}]
                             [--mcs-plca-node-id MCS_PLCA_NODE_ID]
                             [--mcs-plca-node-count MCS_PLCA_NODE_COUNT]
                             [--tcp-port TCP_PORT] [--udp-port UDP_PORT]
                             [--tls] [--tls-cert TLS_CERT] [--tls-key TLS_KEY]
                             [--tls-password TLS_PASSWORD]
                             [--tls-cafile TLS_CAFILE] [--tls-verify-peer]
                             [--tls-require-client-certificate]
                             [--exi-mode EXI_MODE]
                             [--artifact-root ARTIFACT_ROOT]
                             [--max-runtime-s MAX_RUNTIME_S] [--foreground]
                             [--campaign-hooks CAMPAIGN_HOOKS]
                             [--campaign CAMPAIGN]
                             [--campaign-case CAMPAIGN_CASE] [--daemon]
                             [--dry-run]

options:
  -h, --help            show this help message and exit
  --runtime-root RUNTIME_ROOT
  --run-id RUN_ID
  --profile PROFILE     Profile name or path to a YAML/JSON profile file
  --profile-id, --profile_id PROFILE_ID
                        Registered profile ID
  --protocol {iso15118-2,iso15118-20,mcs,din70121}
  --host HOST
  --interface INTERFACE
  --interface-index INTERFACE_INDEX
  --advertise-ipv6 ADVERTISE_IPV6
  --hardware-profile HARDWARE_PROFILE
                        Registered hardware profile ID or path to a hardware
                        profile JSON/YAML
  --mcs-hil-driver {mock,http,ni_daqmx,veristand}
  --mcs-hil-endpoint MCS_HIL_ENDPOINT
  --mcs-plca-role {coordinator,follower}
  --mcs-plca-node-id MCS_PLCA_NODE_ID
  --mcs-plca-node-count MCS_PLCA_NODE_COUNT
  --tcp-port TCP_PORT
  --udp-port UDP_PORT
  --tls
  --tls-cert TLS_CERT
  --tls-key TLS_KEY
  --tls-password TLS_PASSWORD
  --tls-cafile TLS_CAFILE
  --tls-verify-peer
  --tls-require-client-certificate
  --exi-mode EXI_MODE
  --artifact-root ARTIFACT_ROOT
  --max-runtime-s MAX_RUNTIME_S
  --foreground
  --campaign-hooks CAMPAIGN_HOOKS
  --campaign CAMPAIGN
  --campaign-case CAMPAIGN_CASE
  --daemon
  --dry-run

Production examples

Launch an ISO 15118-2 DC Plug and Charge EVSE with TLS and artifacts.

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

Launch an ISO 15118-20 AC realistic EIM session for a production lab.

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

stop

Request a graceful stop for one EVSE runtime by run ID.

CLI help

usage: chargelink evse stop [-h] [--runtime-root RUNTIME_ROOT] run_id

positional arguments:
  run_id

options:
  -h, --help            show this help message and exit
  --runtime-root RUNTIME_ROOT

Production examples

Stop a named run.

chargelink evse stop 'demo-run' --runtime-root '.tmp/runtime'

Stop a second named run.

chargelink evse stop 'release-smoke' --runtime-root '.tmp/runtime'

status

Read the current status snapshot for a single EVSE run.

CLI help

usage: chargelink evse status [-h] [--runtime-root RUNTIME_ROOT] run_id

positional arguments:
  run_id

options:
  -h, --help            show this help message and exit
  --runtime-root RUNTIME_ROOT

Production examples

Check a named runtime run.

chargelink evse status 'demo-run' --runtime-root '.tmp/runtime'

Check a second run in the same runtime root.

chargelink evse status 'release-smoke' --runtime-root '.tmp/runtime'

list-state

List all EVSE state snapshots under the configured runtime root.

CLI help

usage: chargelink evse list-state [-h] [--runtime-root RUNTIME_ROOT] run_id

positional arguments:
  run_id

options:
  -h, --help            show this help message and exit
  --runtime-root RUNTIME_ROOT

Production examples

List active state snapshots.

chargelink evse list-state --runtime-root '.tmp/runtime'

List state snapshots under a lab-specific runtime root.

chargelink evse list-state --runtime-root 'artifacts/runtime_root'

hardware-profiles

List registered hardware profiles for EL6761, MCS, NI, and VeriStand-backed execution paths.

CLI help

usage: chargelink evse hardware-profiles [-h] [--output OUTPUT]

options:
  -h, --help       show this help message and exit
  --output OUTPUT

Production examples

List registered hardware profiles.

chargelink evse hardware-profiles

Write hardware profile metadata to JSON.

chargelink evse hardware-profiles --output 'artifacts/hardware_profiles.json'

bench-blueprint

Export the bench blueprint for one hardware profile.

CLI help

usage: chargelink evse bench-blueprint [-h] [--output OUTPUT] hardware_profile

positional arguments:
  hardware_profile

options:
  -h, --help        show this help message and exit
  --output OUTPUT

Production examples

Export data for the direct NI MCS profile.

chargelink evse bench-blueprint 'ni_mcs_direct_ivn8563' --output 'artifacts/hardware/bench-blueprint_ni_mcs_direct_ivn8563.json'

Export data for the PXI VeriStand profile.

chargelink evse bench-blueprint 'ni_mcs_pxi_ivn8563_pxie8623' --output 'artifacts/hardware/bench-blueprint_ni_mcs_pxi_ivn8563_pxie8623.json'

bench-bom

Export the bill of materials for one hardware profile.

CLI help

usage: chargelink evse bench-bom [-h] [--output OUTPUT] hardware_profile

positional arguments:
  hardware_profile

options:
  -h, --help        show this help message and exit
  --output OUTPUT

Production examples

Export data for the direct NI MCS profile.

chargelink evse bench-bom 'ni_mcs_direct_ivn8563' --output 'artifacts/hardware/bench-bom_ni_mcs_direct_ivn8563.json'

Export data for the PXI VeriStand profile.

chargelink evse bench-bom 'ni_mcs_pxi_ivn8563_pxie8623' --output 'artifacts/hardware/bench-bom_ni_mcs_pxi_ivn8563_pxie8623.json'

io-map

Export the logical or physical I/O map for a hardware profile.

CLI help

usage: chargelink evse io-map [-h] [--output OUTPUT] hardware_profile

positional arguments:
  hardware_profile

options:
  -h, --help        show this help message and exit
  --output OUTPUT

Production examples

Export data for the direct NI MCS profile.

chargelink evse io-map 'ni_mcs_direct_ivn8563' --output 'artifacts/hardware/io-map_ni_mcs_direct_ivn8563.json'

Export data for the PXI VeriStand profile.

chargelink evse io-map 'ni_mcs_pxi_ivn8563_pxie8623' --output 'artifacts/hardware/io-map_ni_mcs_pxi_ivn8563_pxie8623.json'

bench-sequence

Export the bench orchestration sequence for a hardware profile.

CLI help

usage: chargelink evse bench-sequence [-h] [--output OUTPUT] hardware_profile

positional arguments:
  hardware_profile

options:
  -h, --help        show this help message and exit
  --output OUTPUT

Production examples

Export data for the direct NI MCS profile.

chargelink evse bench-sequence 'ni_mcs_direct_ivn8563' --output 'artifacts/hardware/bench-sequence_ni_mcs_direct_ivn8563.json'

Export data for the PXI VeriStand profile.

chargelink evse bench-sequence 'ni_mcs_pxi_ivn8563_pxie8623' --output 'artifacts/hardware/bench-sequence_ni_mcs_pxi_ivn8563_pxie8623.json'

veristand-map

Export the VeriStand mapping payload for a hardware profile.

CLI help

usage: chargelink evse veristand-map [-h] [--output OUTPUT] hardware_profile

positional arguments:
  hardware_profile

options:
  -h, --help        show this help message and exit
  --output OUTPUT

Production examples

Export data for the direct NI MCS profile.

chargelink evse veristand-map 'ni_mcs_direct_ivn8563' --output 'artifacts/hardware/veristand-map_ni_mcs_direct_ivn8563.json'

Export data for the PXI VeriStand profile.

chargelink evse veristand-map 'ni_mcs_pxi_ivn8563_pxie8623' --output 'artifacts/hardware/veristand-map_ni_mcs_pxi_ivn8563_pxie8623.json'