Test Package and Suite Catalog

ChargeLink Native test packages are productized test collections for protocol and security validation. They are designed to give an operator the same basic workflow for every supported protocol:

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

This chapter explains the available package families, what they cover, how to select one, and the exact CLI workflow.

Discover what your installation contains

The package registry is authoritative for the installed build and license.

$CL = 'C:\Program Files\ChargeLink Native\bin\chargelink.exe'
$License = 'C:\ChargeLinkData\licenses\customer.cllic'

& $CL --json --license $License conformance catalog
& $CL --json --license $License conformance packages list --protocol all --role all
& $CL --json --license $License conformance coverage --package all --standard-part all --role all

Filter by protocol and role:

& $CL --json --license $License conformance packages list `
  --protocol iso15118-2 `
  --role evse

A package shown in the catalogue can still require a package-specific entitlement before execution. Verify activation with:

& $CL --json conformance package activate `
  --package iso15118-2-evse `
  --license $License

High-level communication packages

ISO 15118-2 package depth

The ISO 15118-2 packages use the ISO 15118-4 inventory present in the installed test content. The source inventory contains 797 identifiers: 293 SECC-role and 504 EVCC-role cases. Applicability depends on role, profile and PICS/PIXIT; the selected campaign can therefore contain fewer executable cases.

Relevant functional areas include:

• V2GTP framing and transport behavior.
• SupportedAppProtocol negotiation.
• Session setup and service discovery.
• Payment selection and authorization.
• Charge parameter discovery.
• Cable check and pre-charge for DC.
• Power delivery and charging status.
• Metering and receipt behavior where applicable.
• Welding detection and session stop.
• TLS, certificate and Plug & Charge paths when enabled.
• Positive, negative, timeout and sequence behavior.

ISO 15118-20 package depth

The ISO 15118-20 packages combine common ISO 15118-21 inventory with DC-specific ISO/PAS 15118-23 inventory. The source inventories contain 297 common identifiers and 86 DC identifiers. Per role, the current inventories resolve to:

Package applicability is further narrowed by profile choices such as AC/DC, scheduled/dynamic control, EIM/PnC and BPT support.

Relevant areas include:

• Application protocol negotiation and session establishment.
• Authorization setup and authorization.
• Service discovery and service-detail exchange.
• Schedule exchange.
• AC and DC charge-loop behavior where the selected profile applies.
• Dynamic and scheduled control modes.
• Bidirectional power-transfer behavior where licensed and selected.
• Metering, certificate and TLS paths.
• Session stop, error handling and timeout behavior.

DIN 70121 packages

DIN 70121 packages provide engineering conformance-readiness for classic DC charging. They use ChargeLink-authored case areas rather than claiming a bundled normative DIN test-case inventory. Use them for regression and interoperability preparation, not as an accredited DIN certificate.

Typical areas include:

• SDP and TCP connection establishment.
• Session setup and service discovery.
• Payment/authorization handling applicable to DIN operation.
• Charge parameter discovery.
• Cable check, pre-charge and contactor sequencing.
• Current demand loop.
• Welding detection and session stop.
• Timeout, retry and invalid-sequence behavior.

Extended engineering packages

The difference between included and executable counts is normally a physical-bus or hardware-dependent case. Such a case should appear as blocked until the required adapter and bench conditions are available.

Select the correct package

Use this decision path:

1. Identify the DUT role: EVSE/SECC or EVCC.
2. Identify the protocol negotiated by the DUT.
3. Select the exact package ID for that protocol and role.
4. Select a profile matching AC/DC, authorization and TLS requirements.
5. Complete PICS/PIXIT based on the DUT, not on what you hope it supports.
6. Start with dry-run and a limited case count.
7. Move to live execution only after the campaign has no unexplained blockers.

Examples:

End-to-end copy/paste example: ISO 15118-2 EVSE

$CL = 'C:\Program Files\ChargeLink Native\bin\chargelink.exe'
$License = 'C:\ChargeLinkData\licenses\customer.cllic'
$Root = 'C:\ChargeLinkData\conformance\iso2-evse-first-run'
$Pics = "$Root\pics.json"
$Pixit = "$Root\pixit.json"
$Out = "$Root\run"
New-Item -ItemType Directory -Force -Path $Root | Out-Null

& $CL --json --license $License conformance package activate `
  --package iso15118-2-evse `
  --license $License

& $CL --json conformance package pics-pixit `
  --package iso15118-2-evse `
  --role evse `
  --profile-id iso2-dc-eim-tls `
  --pics $Pics `
  --pixit $Pixit `
  --executable-only `
  --max-cases 10

& $CL --json conformance package campaign `
  --package iso15118-2-evse `
  --role evse `
  --profile-id iso2-dc-eim-tls `
  --pics $Pics `
  --pixit $Pixit `
  --executable-only `
  --max-cases 10

& $CL --json --license $License conformance package execute `
  --package iso15118-2-evse `
  --role evse `
  --profile-id iso2-dc-eim-tls `
  --pics $Pics `
  --pixit $Pixit `
  --out $Out `
  --license $License `
  --evidence-mode dry-run `
  --executable-only `
  --max-cases 10

& $CL --json conformance package report `
  --run-dir $Out `
  --out "$Out\verdict_report.json"

End-to-end copy/paste example: CHAdeMO EVCC

$CL = 'C:\Program Files\ChargeLink Native\bin\chargelink.exe'
$License = 'C:\ChargeLinkData\licenses\customer.cllic'
$Root = 'C:\ChargeLinkData\conformance\chademo-evcc'
New-Item -ItemType Directory -Force -Path $Root | Out-Null

& $CL --json --license $License conformance package execute `
  --package chademo-session `
  --role evcc `
  --profile-id chademo_classic_dc_evcc_reference `
  --pics "$Root\pics.json" `
  --pixit "$Root\pixit.json" `
  --out "$Root\run" `
  --license $License `
  --evidence-mode dry-run `
  --executable-only `
  --max-cases 10

Generate PICS/PIXIT first if those files do not yet exist.

What a customer package should deliver

A commercialized package bundle is expected to separate licensed test content from the base runtime while still giving the operator a complete workflow. The product CLI supports:

& $CL --json conformance package commercialize `
  --package <PACKAGE_ID> `
  --license $License `
  --out C:\ChargeLinkData\packages\<PACKAGE_ID>

The resulting package boundary is designed to include customer-safe catalogue metadata, PICS/PIXIT templates, campaign and runner contracts, evidence/report definitions, deviations and live-readiness information. Licensed standards text is not embedded.

Claim boundary

ChargeLink package results are engineering and conformance-readiness evidence. They do not automatically constitute accredited certification, standards-body approval, physical connector qualification, high-voltage safety approval or third-party tool equivalence.