ChargeLink Native
DEP docs ↗Developed byDEVlink

Protocol Operations

This section contains operator runbooks for the charging protocols of ChargeLink Native. Start here instead of the low-level CLI reference.

ProtocolCharging modesTransportWhat the EVSE listener doesRunbook
ISO 15118-20DC Scheduled and Dynamic (plant-coupled), DC/AC/BPT (reference responder), EIM; PnC by fixtureIPv6 link-local, SDP, TCP, TLS 1.3 mutual, V2GTP, EXIDC EIM with a plant model: full semantic session. Other profiles: validated reference responses per message, for engineering and test development.ISO 15118-20
ISO 15118-2DC EIM, AC EIM, AC PnCIPv6, SDP, TCP, optional TLS 1.2 (SChannel) or rustls, V2GTP, EXIValidated reference responses per message; 12-message DC sequence. The ChargeLink SECC and EVCC also run a full DC EIM session (iso2-evcc). For engineering and test development.ISO 15118-2
DIN 70121DCIPv6, SDP, TCP, V2GTP, EXI (no TLS)Validated reference responses per message. The ChargeLink SECC and EVCC also run a full DC session (din-evcc). For engineering and test development.DIN 70121
IEC 61851-23/-24 System ADCCAN: virtual CAN hub over TCP or a Kvaser CANlib channel; plant link over TCPStation and EV roles with a simulated plant; 29-case matrix on one PC; two-PC SIL lane.IEC 61851-23/-24 System A

The scripted DC-CAN lanes play fixed CAN fixture frames on a virtual bus for test development; they are not a protocol implementation. For other charging standards, contact DEVlink.

Two kinds of EVSE session

The two kinds of EVSE session: reference responder and plant-coupled runtime A · Reference‑responder session evse start --external-evcc-session (any protocol) Vehiclerequest decode · matchmessage type validated referenceresponse vector response Proves discovery, TLS, framing, sequencing of the peer. Does not compute values from the request; never controls a power stage. B · Plant‑coupled runtime (ISO 15118‑20 DC EIM) iso15118_20_dc + --plant-grpc-endpoint + runtime profile Vehicletargets session state machinescheduled control, budgets plant model (VeriStand FMU)voltage · current · contactor encoded response Responses computed from session and measurements; PreCharge, PowerDelivery and ChargeLoop react to the vehicle. Fail‑safe ownership; delivered by the VeriStand workspace.
A: the stand-alone listener answers with validated reference responses. B: the plant-coupled ISO 15118-20 DC EIM runtime computes responses from the session and the plant model.

Understanding this distinction prevents most misread results:

  • Reference-responder session. evse start --external-evcc-session without plant coupling. ChargeLink performs real SDP discovery, TCP accept, TLS handshake and V2GTP framing with the external vehicle, decodes each request and replies with the validated reference response for that message type. This exercises discovery, transport, security, framing and message sequencing of the peer. It does not compute values from the vehicle's request (for example, it does not follow a requested current), so it is not a charge controller.
  • Plant-coupled runtime session (ISO 15118-20 DC EIM). Profile iso15118_20_dc with --plant-grpc-endpoint and a runtime profile file. Every response is encoded from the session state and the plant measurements; PreCharge, PowerDelivery and the DC charge loop react to the vehicle's targets and to the simulated electrical behaviour. This is the lane of the NI VeriStand bench in the package.

Both are engineering evidence. Neither is accredited certification or a physical-hardware validation.

How a session is established

The layers of an ISO 15118 session and where each one is diagnosed Order in which a session is established, and in which failures must be isolated 1 · SDP UDP 15118, multicastto ff02::1 on thelink-local interface Fails on: wrong NIC,IPv6 off, zone index,firewall Evidence:sdp_diagnostics.json 2 · TCP Advertised addressand port: 50118 or49152–65535 Fails on: wrongadvertise-ipv6, portrule, peer routing Evidence:evse_listener_status 3 · TLS ISO 15118-20:TLS 1.3 mutualISO 15118-2: optionalDIN 70121: none Fails on: version,chain, clock, missingclient certificate Evidence:tls_handshake_diagnostics.json 4 · V2GTP Frame header andpayload type0x8001 … 0x8004 Fails on: invalidlength or payloadtype, truncation Evidence: traces\live-v2gtp-frames 5 · EXI SupportedApp-Protocol, then theselected schema Fails on: decodeerror, unmatchedrequest encoding Evidence: decodeverdict per frame 6 · Session Setup, authorize,schedule, precharge,charge loop, stop Fails on: sequence,response budget,plant safety state Evidence: session_handshake_gate evse live-closure-gate --require-sdp --require-tcp-peer --require-tls --require-v2gtp --require-exi reports which layers were observed for a run.
Establish and troubleshoot in this order. A failure in a later layer does not invalidate earlier layers.

Common operating pattern

  1. Open PowerShell and define $CL and $Data (Install and Activate); chargelink is on PATH.
  2. Verify the license and discover profiles: chargelink --json license status, chargelink --json profile list.
  3. Run the dry-run and the live preflight with the bench NIC values.
  4. Start the EVSE or EVCC role in window 1; observe status from window 2.
  5. Stop cleanly with evse stop / evcc stop and collect the run directory.
$CL   = 'C:\ChargeLink\0.5.0-rc2\pc1\bin\chargelink.exe'
$Data = 'C:\ChargeLinkData'

$IfIndex   = <INTERFACE_INDEX>
$Advertise = 'fe80::<ADDRESS>%' + $IfIndex

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json license status
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile list

The profile determines protocol, role, connector family and EXI mode. Network addresses, interface indexes, certificate paths and CAN channels are deployment settings supplied on the command line for the current bench.

Which role is ChargeLink playing?

You test a...ChargeLink roleCommand family
Vehicle, EVCC or vehicle simulatorEVSE (charger, SECC)evse start --external-evcc-session
Charger or SECCEVCC (vehicle)evcc tls-handshake-probe, evcc activate-profile
Nothing yet; you validate the softwareboth, in one processevcc local-loopback-smoke, sim paired

For the vehicle role, read the boundaries in the EVCC Role Guide first: a full ISO 15118-20 session against a real charger requires the EV case files delivered with the package.

HomeTop