Test Package Catalog

ChargeLink Native test packages are productised test collections for protocol and security validation. Every package follows the same operator workflow:

select package → select role/profile → generate PICS/PIXIT → generate campaign → execute → review verdict and customer report

The installed registry is authoritative; conformance catalog lists every package of the installed build. This page describes the packages for ISO 15118-20, ISO 15118-2, DIN 70121 and transport security.

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance catalog
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance packages list --protocol all --role all
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance packages hlc-catalog
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance packages extended-catalog
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance coverage --package all --standard-part all --role all
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance protection-policy

chargelink ats packages and chargelink ats package are identical to the conformance forms.

High-level communication packages

Source inventories: ISO 15118-4 797 identifiers (293 SECC, 504 EVCC), ISO 15118-21 297 (149 SECC, 148 EVCC), ISO/PAS 15118-23 86 (38 SECC, 48 EVCC). ISO 15118-2 areas include V2GTP, SDP, SupportedAppProtocol, SessionSetup, ServiceDiscovery/Detail, PaymentServiceSelection, PaymentDetails, Authorization, CertificateInstallation/Update, ChargeParameterDiscovery, CableCheck, PreCharge, PowerDelivery, CurrentDemand, ChargingStatus, MeteringReceipt, WeldingDetection and SessionStop; ISO 15118-20 areas include the common application layer, AuthorizationSetup/Authorization, ServiceDiscovery/Detail/Selection, ScheduleExchange, PowerDelivery, DC CableCheck/PreCharge/ChargeLoop, MeteringConfirmation, CertificateInstallation, SessionStop and LinkTermination. ChargeLink ships identifiers and execution bindings only; licensed standards text is never included.

Transport-security package

The security package contains ChargeLink-authored engineering cases with IDs such as cl_sec_tls_expired_certificate_negative.

Claim boundary

All packages carry the claim boundary "Licensed execution and engineering verdict evidence only; not accredited certification or standards-body approval." Excluded from every package: Python or Java runtimes, external oracle bridges, licensed normative text, unlicensed corpus material and raw customer private keys.

The package runner emits inconclusive for dry-run executions and blocked for replay and live executions until evidence is bound; pass and fail verdicts are produced by the protocol-first test run flow with an evidence manifest (Test Workflow).

Select the correct package

End-to-end example: ISO 15118-2 EVSE

$CL   = 'C:\ChargeLink\0.5.0-rc2\pc1\bin\chargelink.exe'
$Data = 'C:\ChargeLinkData'
$License = "$Data\licenses\customer.cllic"
$Root = "$Data\tests\iso2-evse-first-run"
New-Item -ItemType Directory -Force $Root | Out-Null

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance package activate --package iso15118-2-evse --license $License
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance package pics-pixit --package iso15118-2-evse --role evse --profile-id iso2-dc-eim-tls `
  --pics "$Root\pics.json" --pixit "$Root\pixit.json" --executable-only
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance package campaign --package iso15118-2-evse --role evse --profile-id iso2-dc-eim-tls `
  --pics "$Root\pics.json" --pixit "$Root\pixit.json" --executable-only --max-cases 10
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json --license $License conformance package execute --package iso15118-2-evse --role evse --profile-id iso2-dc-eim-tls `
  --pics "$Root\pics.json" --pixit "$Root\pixit.json" --out "$Root\run" --evidence-mode dry-run --executable-only --max-cases 10
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance package report --run-dir "$Root\run" --out "$Root\run\verdict_report.json"

The PICS/PIXIT generator also prints a live_bridge_command: the exact evse start --external-evcc-session line that matches the package's transport contract. Use it as the starting point for the bench session whose evidence you will bind.

Commercial bundle export

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance package commercialize --package iso15118-2-evse --license $License --out "$Data\tests\packages\iso15118-2-evse"
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json conformance package protect --package iso15118-2-evse --role evse --evidence-mode dry-run --out "$Data\tests\packages\protected"

commercialize writes a separately licensed bundle with the case catalogue, PICS/PIXIT templates, runner configuration, evidence requirements, report contract and applicability notes. protect writes the protected-package distribution manifest. Neither embeds standards text.