Release Notes

These notes describe what ChargeLink 0.5.0 delivers. Requirement numbers in brackets refer to ISO 15118-20 (V2G20-...), ISO 15118-2 (V2G2-...) and DIN 70121 (V2G-DC-...). The version identities of the release are in the Release and Version Matrix; what ChargeLink does not do is in Capability Boundaries.

Installation and licensing

• Licences are enforced. ChargeLink's sessions, simulations, conformance runs and servers need a valid DEVlink licence (.dlic) on the computer. Without one they stop before they start, with exit code 20 (CL-LICENSE-001) and a message that gives the reason. See Licensing.
• Licences signed with DEVlink's production key are accepted.
• chargelink license status --json also reports the licences of other DEVlink products found on the computer.
• chargelink license install keeps the earlier licence in place when the new one is revoked or blocked by the clock check. See Activate the licence.
• The setup shows the licence terms. Its charger and vehicle roles install charger\ and vehicle\, and its firewall rules name the side as (charger) or (vehicle). See Install and Activate and Windows Firewall.

Names in the kit and the command line

• Kit folders named for their side. The kit's two folders are charger\ (was pc1\) and vehicle\ (was pc2\), and the installation guides are docs/INSTALL-CHARGER.md and docs/INSTALL-VEHICLE.md. The files and scripts inside, their names and their parameters are unchanged; a script that passes -Pc1Root to the kit's module keeps working. An installation of an earlier version keeps its own layout.
• CHAdeMO session command. chargelink dc-can chademo run runs the CHAdeMO charger and vehicle cases. It runs from the installed ChargeLink alone, with the CHAdeMO cases built in; no profile file is needed. It needs a ChargeLink licence. The earlier command name is still accepted. See IEC 61851-23/-24 System A (CHAdeMO).
• Help texts. The --help texts name the charger side and the vehicle side. Internal CHAdeMO test runners are no longer shown in --help.
• Profile ids. profile list and the gRPC ListProfiles no longer list some earlier reference profile ids; --profile-id and ResolveProfile still accept them. The built-in ISO 15118-20 AC charger profile is listed as iso15118_20_ac_eim, and the DIN 70121 charger profile as din70121_dc. See the Profile Catalog.

Every ISO 15118 and DIN 70121 stack

• SupportedAppProtocol accepts up to 20 AppProtocol entries, the schema's maximum, on DIN 70121, ISO 15118-2 and ISO 15118-20 ([V2G-DC-867], [V2G2-167], [V2G20-167]). The selection follows the EV's priority; 21 or more entries are refused, never cut.
• evse start with a non-loopback bind address refuses to start when its SDP answer would advertise an address the EV cannot reach (exit code 40, CL-RUNTIME-001); the message names --advertise-ipv6. See ChargeLink as Charger.

ISO 15118-20 DC

See ISO 15118-20.

• The EV side (EVCC) ends the communication at its own V2G_EVCC_Msg_Timeout when the charger withholds a response, over TLS and plain TCP ([V2G20-434] to [V2G20-438], [V2G20-1966]).
• The charger side (SECC) and the EV side ignore an invalid V2GTP header ([V2G20-800]).
• The EV's welding-detection model follows [V2G20-1573].
• A SessionStopReq between SessionSetup and PowerDelivery(Start) is answered OK, with the plant off and a safe current before the answer, and TCP is kept open for 5 s ([V2G20-2645], [V2G20-1632], [V2G20-1633]).
• With a measured cable check (a real plant or a hardware-in-the-loop rig), a failed insulation test is answered FAILED ([V2G20-458], [V2G20-2222]). A contactor still open at the PowerDelivery(Start) bound is answered FAILED_ContactorError ([V2G20-862]).

ISO 15118-20 AC

See ISO 15118-20.

• The EV side (EVCC) states whether it accepts a power tolerance when the schedule it picked carries one ([V2G20-1866]), so a charger that offers a tolerance accepts the start.
• The EV side (EVCC) continues when a charger sends per-phase (_L2/_L3) values the EV did not ask for ([V2G20-1209]): it uses the base values and records the charger's deviation ([V2G20-734]).
• The charger side (SECC) answers a confirmed power tolerance with OK_PowerToleranceConfirmed ([V2G20-1944]), as the DC SECC does.
• A SessionStopReq between SessionSetup and PowerDelivery(Start) is answered OK ([V2G20-2645]).
• An AuthorizationReq that selects a service the charger did not offer gets WARNING_AuthorizationSelectionInvalid, with a reselection ([V2G20-2209]).

MCS (Megawatt Charging System)

• MCS sessions run as ISO 15118-20 DC with the MCS service (ServiceID 8, TLS only), in the Scheduled control mode, on both roles, with the MCS limits and the connector (CE and ID) gates from ChargeLink's simulated coupler model. See MCS; what is and is not covered is in Capability Boundaries.

ISO 15118-2

The changes for every ISO 15118 and DIN 70121 stack (above) apply: up to 20 SupportedAppProtocol entries, and the SDP address check at evse start. See ISO 15118-2.

DIN 70121

The changes for every ISO 15118 and DIN 70121 stack (above) apply. The DIN 70121 charger profile is listed as din70121_dc. See DIN 70121.

IEC 61851-23/-24 System A (CHAdeMO)

• chargelink dc-can chademo run runs the CHAdeMO charger and vehicle cases, built in (see Names in the kit and the command line). See CHAdeMO.

NI VeriStand bench

• The bench kit's folders are charger\ and vehicle\, installed by docs/INSTALL-CHARGER.md and docs/INSTALL-VEHICLE.md. See NI VeriStand Bench and Set Up the VeriStand Bench.
• The kit is signed by DEVlink AB, and manifest\SHA256SUMS in the kit lists the SHA-256 of every file.
• With the bench's measured cable check, a failed insulation test is answered FAILED, and a contactor still open at the PowerDelivery(Start) bound is answered FAILED_ContactorError (ISO 15118-20 DC, above).

Evidence and automation

• The V2GTP header of every charger-side ISO 15118-20 frame and of each SDP exchange is recorded in the evidence ([V2G20-2307]). This is evidence only; the protocol behaviour is unchanged. See Trace, Evidence and Reports.
• The gRPC ListProfiles no longer lists some earlier reference profile ids; ResolveProfile still accepts them. See gRPC Integration API.

Known limitations

The limits of ChargeLink 0.5.0, per standard and role, are in Capability Boundaries.