Release and Version Matrix
Use this page as the operator's compatibility record. This manual documents ChargeLink 0.5.0: one application that runs the charger or the vehicle role for ISO 15118-20 (including MCS), ISO 15118-2, DIN 70121 and IEC 61851-23/-24 System A (CHAdeMO). The values reported by your installed package are authoritative for your machine.
Documented release
| Item | Documented value | How to read it on the installed machine |
|---|---|---|
| CLI version | chargelink 0.5.0 | chargelink --version |
| Integration API | chargelink.integration.v1, api_version 1.8.0 | chargelink --json integration capabilities (embedded, no server needed) |
| gRPC server product version | product_version 0.5.0, product ChargeLink Native (one version for every component) | chargelink --json integration health --endpoint ... |
| Binary | charger\bin\chargelink.exe (in the kit, charger\ holds the charger-side files and vehicle\ the vehicle-side files); its SHA-256 is listed in manifest\SHA256SUMS | Get-FileHash |
| Management API access | loopback only; bearer token in <state-root>\api-token, new at every start | integration health without a token fails with CL-RUNTIME-001 |
| Canonical signals | 94 | canonical_signal_count in capabilities |
| Built-in profiles | 64 | chargelink --json profile list |
| Conformance packages | 13 | chargelink --json conformance catalog |
| Protocol-first test cases | ISO 15118-2: 797; ISO 15118-20: 383 | chargelink --json test protocols list |
| Deterministic scenarios | 10 ISO 15118-20, 12 TLS campaigns | sim iso20-catalog, sim tls-catalog |
| Documentation | this manual, matching the help output of the same binary | footer of every page |
The CLI version and the gRPC product version are read from different components of the same build. Record both.
Reported claim boundaries. Integration: The integration API exposes ChargeLink engineering simulation and evidence functions. It does not itself establish accredited certification, standards-body approval, hardware validation, or vendor equivalence.
Test bindings: Execution bindings are engineering test definitions; PASS/FAIL requires live-SUT or validated replay evidence.
Conformance catalog: commercial protected package catalog only; not accredited certification or vendor-tool equivalence
Third-party compatibility
The NI VeriStand, plant-model and bench rows match the package's INSTALL-CHARGER.md.
| Component | Supported version | Notes |
|---|---|---|
| Windows | Windows 11 Pro (build 26200) on the reference workstation; Windows 10/11 64-bit supported | Get-ComputerInfo |
| NI VeriStand | 2024 Q4 (ClientAPI, Gateway, veristand-server); the package's INSTALL-CHARGER.md lists the expected file hashes | use this NI build; other NI VeriStand versions are not supported |
| .NET | .NET Framework 4.8 (ChargeLink.Veristand.NativeClientBroker.exe); .NET 10 runtime x64 (ChargeLink.Veristand.XilHost.exe; LTS until November 2028) | installed by the customer, never redistributed; tested with 10.0.10 |
| C++ runtime | Microsoft Visual C++ 2015-2022 Redistributable x64 | required by chargelink.exe |
| Plant model | FMI 2.0 Co-Simulation FMU (26 inputs / 18 outputs / 6 parameters) in charger\veristand\ChargeLink\Models and the system definition ChargeLink_Blank_Windows.nivssdf in charger\veristand | 64 User Channels, 44 mappings; VeriStand loops placed on logical processors 10, 11 and 12 of the reference PC |
| TLS | Built-in TLS for ISO 15118-20 (TLS 1.3 only, named groups secp521r1 and x448, cipher suites TLS_AES_256_GCM_SHA384 and TLS_CHACHA20_POLY1305_SHA256) and for the ISO 15118-2 TLS 1.2 roles; optionally Windows SChannel (TLS 1.2) for the ISO 15118-2 reference responder with your vehicle. Third-party notices and an SBOM ship with the kit. | ISO 15118-20 Annex B certificate profile (ECDSA P-521, SHA-512); engineering material is generated per run and needs --allow-engineering-tls-identity. The ISO 15118-20 handshake offers and accepts only secp521r1 and x448; --allow-legacy-tls-named-groups adds secp256r1 for peers that offer only P-256 |
| CAN adapters | Kvaser CANlib (canlib32.dll) for CHAdeMO sessions on a Kvaser channel, Kvaser Leaf v3 | the adapter kinds of the scripted DC-CAN sequences (PEAK, Vector, Kvaser, SocketCAN, SLCAN, Lawicel, USBtin) are descriptors and open no hardware |
| OPC UA | OPC Foundation stack discovered at runtime; probe only | no endpoint opened |
Protocol-to-profile check
Resolve profiles from the installed build, not from this page:
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile list
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile show <PROFILE_ID>
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json evse external-evcc-session-policy # the activation catalog with the exact commands per protocolAcceptance of an installation should confirm the profiles you use, for example ISO 15118-20 DC (iso15118_20_dc), ISO 15118-20 AC, ISO 15118-2 DC and AC and DIN 70121 DC, as listed in the Profile Catalog.
Upgrade rule
When ChargeLink is upgraded, repeat at least: package hash verification; --version; license status; doctor --strict; profile list; gRPC health and session smoke; one golden run per protocol family used at the site, including the deterministic simulation hash comparison; the two Start-SeccSession.ps1 -ValidateOnly checks on the VeriStand bench when used; an artifact integrity check and a support-bundle export. Check commands copied into your own procedures against chargelink <command> --help of the new binary.