Charging software stacks

What software runs the charging communication in a charger, a car and a backend: the open source stacks (EVerest, the SwitchEV iso15118 stack, pyPLC, OpenV2G, libcbv2g, open-plc-utils, SteVe, MaEVe, CitrineOS), commercial ones, the capture tools built on them, and how a stack shows in a capture.

What runs where

Charging communication is software on both ends of the cable and behind the charger. Each layer below can come from a different project or vendor, and a charger often mixes them.

LayerIn the chargerIn the carBehind the charger
Modem control and SLACSLAC responder on a HomePlug Green PHY modemSLAC initiatorNo
SDP, V2GTP, TCP and TLSSECC: SDP server, TCP or TLS serverEVCC: SDP client, TCP or TLS clientNo
EXI codecEncodes and decodes every V2G messageThe sameNo
Protocol state machineDIN SPEC 70121, ISO 15118-2, ISO 15118-20 as SECCThe same as EVCCNo
Charger control and backend linkPower stage, meter, authorization, OCPP clientBattery managementOCPP server (CSMS), Plug and Charge certificate services

A capture on the charging cable sees the first four layers of both sides; an OCPP log sees the last one. Inside a charger shows where the parts sit in the hardware and OCPP 2.0.1 and ISO 15118: the backend behind the cable how the two protocols meet in the charger.

Open source in the charger and the car

ProjectWhat it isLicence and home
EVerestA modular charger software stack backed by LF Energy, started by PIONIX GmbH. Modules talk over MQTT; it covers ISO 15118-2, -3 and -20 and OCPP 1.6, 2.0.1 and 2.1, with drivers for charge controllers, meters and payment terminals.Apache 2.0, github.com/EVerest
libcbv2g and cbExiGenThe EXI codec of EVerest for DIN SPEC 70121, ISO 15118-2 and ISO 15118-20, generated by the cbExiGen code generator. This analyzer embeds it.Apache 2.0, EVerest
libiso15118A C++ SECC for ISO 15118-20 (with ISO 15118-2 and DIN SPEC 70121): TLS 1.2 and 1.3, AC and DC, bidirectional, scheduled and dynamic mode; Plug and Charge listed as work in progress.Apache 2.0, EVerest
libslacAn ISO 15118-3 SLAC implementation. Archived on 4 December 2025; the work continues in the main EVerest repository.Apache 2.0, EVerest
libocppOCPP 1.6 with all six feature profiles, OCPP 2.0.1 with all functional blocks and OCA certification on several hardware platforms, OCPP 2.1 in development. Archived on 27 April 2026 and moved into the main EVerest repository.Apache 2.0, EVerest
SwitchEV iso15118 (Josev)Python EVCC and SECC for DIN SPEC 70121, ISO 15118-2 and ISO 15118-20. Josev Community uses the Java EXIficient codec; Josev Professional uses a Rust codec of its own. EVerest carries it as ext-switchev-iso15118.Apache 2.0, github.com/SwitchEV
OpenV2GAn early EXI codec and basic ISO 15118 implementation by Siemens, hosted on SourceForge. OpenV2Gx is a fork (based on version 0.9.5 of March 2022) with a command line interface; it covers the DIN schema in part.LGPL v3 or later
pyPLCPython tools for CCS investigations on cheap QCA7420 powerline adapters, in three modes: listen between a car and a charger, act as a charger, or act as a car. Uses OpenV2Gx for EXI.GPL-3.0, github.com/uhi22
open-plc-utilsThe open version of the Qualcomm Atheros powerline toolkit: tools to configure modems (plctool, int6k, PIB and NVM tools) and SLAC tools.Clear BSD (since 2013), github.com/qca
SmartEVSE, OpenEVSE, openWBFirmware and software for AC wallboxes: Control Pilot, load management, OCPP 1.6j (SmartEVSE), solar surplus charging (openWB). No ISO 15118 stack is claimed.MIT (SmartEVSE), GPLv3 (openWB), OpenEVSE on GitHub

Open source behind the charger

ProjectWhat it isLicence and status
SteVeA charge point management system from RWTH Aachen University (2013), written in Java; OCPP 1.2, 1.5 and 1.6 in SOAP and JSON, including the 1.6 security extensions.GPL-3.0
MaEVeA CSMS by Thoughtworks that began as a proof of concept for ISO 15118-2 Plug and Charge; OCPP 1.6j and 2.0.1, contract certificates through the Hubject CPO EST service.Apache 2.0; archived on 2 June 2025
CitrineOSA modular CSMS runtime in TypeScript on Node.js, part of the LF Energy ecosystem; OCPP 1.6 and 2.0.1.Apache 2.0

An OCPP server never sees the charging cable. What it logs (Authorize, TransactionEvent, StatusNotification and the rest) is what the OCPP tool of this analyzer reads beside a capture; see OCPP: the charger's link to its backend.

Commercial stacks and tools

  • Josev Professional: the commercial edition of the SwitchEV stack, with its own Rust EXI codec.
  • chargebyte: the Charge SOM platform with Linux distribution layers and EVerest modules for its hardware.
  • Pionix: ChargeBridge reference designs and evaluation boards built for EVerest, and an SDK for a TI AM62x based EVSE.
  • Vector: vSECC, a communication controller for charging infrastructure.
  • dSPACE: dsV2Gshark, a free Wireshark plugin that decodes V2GTP, SDP, the app handshake, DIN SPEC 70121, ISO 15118-2 and (preliminary) ISO 15118-20, and decrypts TLS 1.2 and 1.3 live from secrets that a test device discloses in UDP packets.
  • ChargePoint: wireshark-v2g, an open Wireshark dissector for V2G traffic built with OpenV2G.

The stacks inside cars (for example as part of an AUTOSAR platform) and the SECC software of the large charger makers are rarely documented in public. Vendor claims about them were not confirmed for this page.

How a stack shows in a capture

The standards leave room, and each stack fills it in its own way. Captures from the same charger model with different cars, or the same car on different chargers, often differ in these places:

  • Response times: how fast the SECC answers each request, most visible in the charge loop (TIM-01, and the Timers tool).
  • Retries: how many SLAC attempts and SDP requests a side sends before it gives up, and how long it waits between them (SL-07, SD-02).
  • The app handshake: which protocols the car offers and in what priority, and which the charger picks (HS-01, HS-02).
  • TLS: the versions, cipher suites and groups offered and chosen (TL-02, TL-05, TL-06), and whether the stack can write a key log.
  • Optional elements: which optional fields a side fills in, for example the meter reading or the departure time.
  • Error handling: what a side does after a FAILED response or a timeout, and whether it sends SessionStop at all.

The Compare tool puts two sessions side by side and names the first message where they part, which is often where two stacks behave differently.

In this tool

  • The analyzer decodes EXI with libcbv2g, compiled to WebAssembly and embedded in the page, so no codec is fetched at run time. A small decoder in TypeScript reads the message headers when the WebAssembly does not load (SPEC section 5.5).
  • A message the codec cannot decode is reported by VT-02 with its raw bytes. The Codec page decodes a pasted message against every schema and encodes it again (EXI: how V2G messages are encoded).
  • TLS is opened with a key log in the NSS format that Wireshark and many test tools write, or with secrets disclosed in the capture (TL-08, TLS in charging captures).
  • An OCPP-J log from the charger or its CSMS is placed beside the capture on its own lane (FR-TOOL-06).

Sources