ChargeLink Documentation Logo

Overview

  • What ChargeLink is
    • Snapshot highlights
    • Built-in profile families
    • Why teams use ChargeLink
  • 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
  • Glossary
ChargeLink Documentation
  • What ChargeLink is
  • View page source

What ChargeLink is

ChargeLink combines three things in one product surface:

  • A live EVSE simulator that speaks standards-based transport, TLS, and EXI on the wire.

  • A campaign and suite execution engine that turns protocol cases into reusable operator workflows, qualification bundles, and customer-facing exports.

  • A bench-aware validation platform that can stay software-only for fast bring-up or connect to HIL and MCS hardware paths when evidence must be tied to real control and telemetry points.

Snapshot highlights

Area

Snapshot view

Built-in profiles

72 profiles are visible through chargelink profile list in this snapshot.

EVCC reference profiles

8 EVCC profiles are visible through chargelink evcc profiles.

Hardware profiles

5 hardware profiles are visible through chargelink evse hardware-profiles.

Campaign packages

20 packages are visible through chargelink campaign packages.

Named suites

17 suites are visible through chargelink suite list.

Built-in profile families

Family

Count

None

3

ac_wallbox

52

dc_fast_charger

7

din70121_evcc_reference

1

iso15118_20_ac_evcc_reference

1

iso15118_20_dc_evcc_reference

1

iso15118_2_ac_evcc_reference

1

iso15118_2_dc_evcc_reference

1

mcs_dc_bench

1

mcs_evcc_adapter_reference

2

mcs_evcc_reference

1

ocpp_backed_charger

1

Why teams use ChargeLink

  • To validate EVCC implementations against ISO 15118-2, DIN 70121, ISO 15118-20, and MCS-related workflows.

  • To capture evidence artifacts that make protocol failures reproducible and explainable.

  • To separate standards claims, interoperability execution, and hardware proof into explicit packages, suites, and qualification gates.

Previous Next

© Copyright 2026, devLink AB.

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