ChargeLink documentation

ChargeLink is a software-defined EVSE simulator and validation platform built for CCS interoperability, conformance-style execution, evidence capture, and bench-linked hardware validation. This site is structured for both newcomers and advanced lab operators.

What is included in this site

• Newcomer-friendly explanations of EVCC, EVSE, SECC, EXI, TLS, HIL, MCS, and bench proof.

• Step-by-step installation and first-run guides for Windows 11 PowerShell and Linux operators.

• A full CLI reference for 36 top-level chargelink command groups plus chargelink-monitor.

• Catalog pages generated from the snapshot: 72 built-in profiles, 8 EVCC profiles, 5 hardware profiles, 20 campaign packages, and 17 named suites.

• An API overview generated from 83 FastAPI route handlers and the websocket event endpoint.

Note

This documentation reflects the provided snapshot. It intentionally documents both the strong current baselines and the current claim boundaries, especially around MCS and commercial-core cleanup.

Overview

• What ChargeLink is
  • Snapshot highlights
  • Built-in profile families
  • Why teams use ChargeLink
• Simulator roles: EVSE, EVCC, and bench-linked execution
  • Key concepts
  • When you run chargelink evse ...
  • When you run chargelink evcc ...
  • When you run chargelink hil ... or chargelink capture mcs ...
  • How newcomers should choose a mode
• Standards, protocols, and conformance position
  • Supported protocol families in the snapshot
  • How to read the package catalog
  • Important claim boundary
• Product status and claim boundaries
  • Current strengths
  • Still gated
  • How the docs handle this

Getting started

• Installation and workstation preparation
  • Prerequisites
  • Recommended setup
  • Windows PowerShell equivalent
  • Lab network checklist
• Quickstart: first EVSE session, first campaign, first report
  • 1. Start a software-only EVSE session
  • 2. Run a packaged campaign
  • 3. Generate a report and inspect the trace
  • What to look at next

Guides

• Guide: EVSE operations
  • Recommended decision sequence
  • Profiles that are useful for first runs
  • When to add a hardware profile
• Guide: EVCC operations and backend orchestration
  • Backends in the snapshot
  • When to stay native
  • When to use external backends
• Guide: scenarios, campaigns, packages, qualification, and suites
  • Packages visible in the snapshot
  • Suites visible in the snapshot
• Guide: trace, replay, diagnostics, reporting, and artifacts
  • Core artifacts to know
  • Recommended operator loop
• Guide: MCS, HIL, and bench proof
  • What MCS means in ChargeLink
  • Why HIL and captures matter
  • Registered MCS capture profiles in the snapshot
  • Hardware profiles that matter for MCS
• Guide: UI and API surfaces
  • What the UI is expected to expose
  • API categories visible in the snapshot

Reference

• Data and artifacts reference
  • Typical artifact roots
• Profile catalog
  • EVSE and charger profiles
  • EVCC reference profiles
• Hardware profile reference
• Package and suite catalog
  • Packages
  • Suites
  • Workstreams
• API reference overview
• chargelink-monitor
  • CLI help
  • Production examples
• 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
  • chargelink ci
  • chargelink sessions
  • chargelink fault
  • chargelink network
  • chargelink fuzz
• Glossary