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
      • Reference syntax
      • Purpose
      • Production examples
    • 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
  • Glossary
ChargeLink Documentation
  • CLI reference
  • chargelink campaign-stress
  • View page source

chargelink campaign-stress

Stress the campaign engine across protocol families to exercise concurrency and pacing.

Reference syntax

usage: chargelink campaign-stress [-h] [--sessions SESSIONS]
                                  [--protocol {iso15118-2,iso15118-20,mcs,din70121}]
                                  [--tls] [--stagger-ms STAGGER_MS]
                                  [--duration-ms DURATION_MS]
                                  [--max-parallel MAX_PARALLEL]
                                  [--output OUTPUT]

options:
  -h, --help            show this help message and exit
  --sessions SESSIONS
  --protocol {iso15118-2,iso15118-20,mcs,din70121}
  --tls
  --stagger-ms STAGGER_MS
  --duration-ms DURATION_MS
  --max-parallel MAX_PARALLEL
  --output OUTPUT

Purpose

Use this single command when you want to stress the runtime across parallel sessions and protocol families.

Production examples

Stress the ISO 15118-20 campaign path with eight sessions.

chargelink campaign-stress --protocol 'iso15118-20' --sessions 8 --stagger-ms 250 --duration-ms 60000 --max-parallel 4 --output 'artifacts/stress/iso20.json'

Exercise the MCS path with TLS enabled and a JSON summary.

chargelink campaign-stress --protocol 'mcs' --tls --sessions 4 --stagger-ms 500 --duration-ms 120000 --max-parallel 2 --output 'artifacts/stress/mcs.json'
Previous Next

© Copyright 2026, devLink AB.

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