ChargeLink Documentation Logo

Overview

  • What ChargeLink is
  • Simulator roles: EVSE, EVCC, and bench-linked execution
  • Standards, protocols, and conformance position
  • Product status and claim boundaries

Getting started

  • Installation and workstation preparation
  • Quickstart: first EVSE session, first campaign, first report

Guides

  • Guide: EVSE operations
  • Guide: EVCC operations and backend orchestration
  • Guide: scenarios, campaigns, packages, qualification, and suites
  • Guide: trace, replay, diagnostics, reporting, and artifacts
  • Guide: MCS, HIL, and bench proof
  • Guide: UI and API surfaces

Reference

  • Data and artifacts reference
  • Profile catalog
  • Hardware profile reference
  • Package and suite catalog
  • API reference overview
  • chargelink-monitor
  • CLI reference
    • 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
      • Reference syntax
      • Subcommands
      • start
        • CLI help
        • Production examples
      • stop
        • CLI help
        • Production examples
      • mcs-list
        • CLI help
        • Production examples
      • mcs
        • CLI help
        • Production examples
    • chargelink ci
    • chargelink sessions
    • chargelink fault
    • chargelink network
    • chargelink fuzz
  • Glossary
ChargeLink Documentation
  • CLI reference
  • chargelink capture
  • View page source

chargelink capture

Start generic captures and run MCS bench capture automation.

Reference syntax

usage: chargelink capture [-h] {start,stop,mcs-list,mcs} ...

positional arguments:
  {start,stop,mcs-list,mcs}

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

Subcommands

Subcommand

Purpose

start

Start a named capture session.

stop

Stop a named capture session.

mcs-list

List predefined MCS bench capture profiles.

mcs

Run an MCS bench capture in dry-run or real mode.

start

Start a named capture session.

CLI help

usage: chargelink capture start [-h] [--runtime-root RUNTIME_ROOT] name

positional arguments:
  name

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

Production examples

Start a generic capture.

chargelink capture start 'cap1' --runtime-root '.tmp/runtime'

Start a second capture.

chargelink capture start 'cap2' --runtime-root '.tmp/runtime'

stop

Stop a named capture session.

CLI help

usage: chargelink capture stop [-h] [--runtime-root RUNTIME_ROOT] name

positional arguments:
  name

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

Production examples

Stop a named run.

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

Stop a second named run.

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

mcs-list

List predefined MCS bench capture profiles.

CLI help

usage: chargelink capture mcs-list [-h] [--output OUTPUT]

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

Production examples

List MCS capture profiles.

chargelink capture mcs-list

Write MCS capture profiles to JSON.

chargelink capture mcs-list --output 'artifacts/mcs_capture_profiles.json'

mcs

Run an MCS bench capture in dry-run or real mode.

CLI help

usage: chargelink capture mcs [-h]
                              [--scope {baseline,safety,fault_injection,all}]
                              [--driver {all,mock,ni_daqmx,veristand}]
                              [--mode {dry_run,real}]
                              [--output-root OUTPUT_ROOT] [--run-id RUN_ID]
                              [--hardware-profile-id HARDWARE_PROFILE_ID]
                              [--real-hardware] [--safe-stop-observed]
                              [--fault-code FAULT_CODE] [--reviewer REVIEWER]
                              [--output OUTPUT]

options:
  -h, --help            show this help message and exit
  --scope {baseline,safety,fault_injection,all}
  --driver {all,mock,ni_daqmx,veristand}
  --mode {dry_run,real}
  --output-root OUTPUT_ROOT
  --run-id RUN_ID
  --hardware-profile-id HARDWARE_PROFILE_ID
  --real-hardware
  --safe-stop-observed
  --fault-code FAULT_CODE
  --reviewer REVIEWER
  --output OUTPUT

Production examples

Run the baseline MCS dry-run capture through NI-DAQmx semantics.

chargelink capture mcs --scope 'baseline' --driver 'ni_daqmx' --mode 'dry_run' --output-root 'artifacts/mcs_capture' --run-id 'baseline' --output 'artifacts/mcs_capture/baseline_result.json'

Run the safety dry-run capture through VeriStand semantics.

chargelink capture mcs --scope 'safety' --driver 'veristand' --mode 'dry_run' --safe-stop-observed --fault-code 'hv_interlock_open' --fault-code 'over_current' --output-root 'artifacts/mcs_capture' --run-id 'safety' --output 'artifacts/mcs_capture/safety_result.json'
Previous Next

© Copyright 2026, devLink AB.

Built with Sphinx using a theme provided by Read the Docs.