Profile Catalog

A profile selects the protocol, the simulator role, the connector family and the EXI mode. It does not contain network addresses, ports, certificates, CAN channels or electrical limits; those are supplied on the command line or, for the computed ISO 15118-20 charger session, in the runtime profile file. This catalog lists the built-in ISO 15118-20, ISO 15118-2 and DIN 70121 profiles; profile list on the installed version is authoritative and also lists the DC-CAN and other engineering profiles.

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile list
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile show iso15118_20_dc
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile connectors

What a profile contains

Field	Meaning	Example
`id`	Identifier used with `--profile-id`	`iso15118_20_dc`
`protocol`	For example `iso15118-20`, `iso15118-2` or `din70121`	`iso15118-20`
`role`	`evse` or `evcc`	`evse`
`description`	Human-readable purpose	Reference EVSE ISO 15118-20 DC profile
`exi_mode`	`chargelink-exi` for IPv6 HLC protocols, `dc-can` for CAN families	`chargelink-exi`
`connectors`	Connector families, for example `ccs1`, `ccs2` or `chademo`; `profile connectors` lists them all	`["ccs2"]`
`tags`	Free-form markers such as `live-stack`, `ac`, `dc`, `tls`, `windows-schannel`	`["evse","dc"]`

For ISO 15118-20 EVSE profiles, AC or DC behaviour is derived from the tokens in the profile ID (ac, dc). ChargeLink does not provide bidirectional power transfer (BPT) or Plug & Charge: evse start refuses a profile, built-in or custom, whose ID names either (for example bpt, bidirectional, v2g, pnc, contract or plug) with exit code 70 (CL-UNSUPPORTED-001). An alias behaves exactly like the canonical profile it names.

Custom profile files

Any command that accepts --profile-id also accepts --profile <FILE> with a YAML or JSON file of the same shape. A file path takes precedence over the built-in list. Validate it first:

@'
id: lab_iso20_dc_bench3
protocol: iso15118-20
role: evse
description: Bench 3 ISO 15118-20 DC EIM profile
exi_mode: chargelink-exi
connectors:
  - ccs2
tags:
  - lab
  - dc
'@ | Set-Content -Encoding utf8 "$Data\profiles\lab_iso20_dc_bench3.yaml"

chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json profile validate "$Data\profiles\lab_iso20_dc_bench3.yaml"
chargelink --runtime-root "$Data\runtime" --artifact-root "$Data\artifacts" --json evse start --dry-run --protocol iso15118-20 --profile "$Data\profiles\lab_iso20_dc_bench3.yaml"

The schema (schemas\profile.schema.json) requires id, protocol and role; the other fields are optional and exi_mode defaults to chargelink-exi. Because the charger selects AC or DC from the profile ID tokens, a custom ISO 15118-20 EVSE profile whose ID lacks ac behaves as DC EIM.

Built-in profiles

Charger (EVSE) profiles are used when ChargeLink is the charger and your DUT is a vehicle (evse start). Vehicle (EVCC) profiles are used when ChargeLink is the vehicle and your DUT is a charger (evcc commands). The use column summarises each profile; profile list prints the full description. Which profiles run a live session against your DUT is stated on each protocol page; in short, the ISO 15118-20 vehicle profile iso15118_20_dc_evcc_reference runs a live session, the other vehicle profiles run in dry-run, loopback and simulation only.

ISO 15118-20 — charger, EVSE (2)

Profile ID	Use
`iso15118_20_dc`	Reference DC EIM charger; with a plant endpoint, the computed DC EIM session
`iso15118_20_ac_eim`	AC EIM charger, reference responses

ISO 15118-20 — vehicle, EVCC (4)

Profile ID	Use
`iso15118_20_dc_evcc_reference`	Reference DC EIM vehicle; runs a live session against your charger
`iso15118_20_ac_evcc_reference`	Reference AC vehicle (dry-run, loopback, simulation)
`iso15118_20_dc_evcc_premium_800v`	800 V DC demo vehicle (dry-run, loopback, simulation)
`iso15118_20_dc_evcc_cold_demo`	Cold-condition DC demo vehicle (dry-run, loopback, simulation)

ISO 15118-2 — charger, EVSE (12)

Profile ID	Use
`iso15118_2_dc_evse_reference`	Canonical DC EIM charger for your vehicle
`iso2-dc-eim-nominal`	Alias of the DC EIM charger
`iso2-dc-eim-tls`	DC EIM charger alias for vehicles that require TLS (SChannel)
`iso2-dc-eim-tls-schannel`	DC EIM charger alias for TLS with a Windows SChannel identity; same behaviour as `iso2-dc-eim-tls`
`iso15118_2_dc_tls_evse_reference`	Canonical DC EIM charger with TLS
`iso15118_2_ac_evse_reference`	Canonical AC EIM charger for your vehicle
`iso2-ac-eim-nominal`	Alias of the AC EIM charger
`iso2-ac-eim-tls`	AC EIM charger alias for vehicles that require TLS (SChannel)
`iso15118_2_ac_tls_evse_reference`	Canonical AC EIM charger with TLS
`iso2-current-demand-loop`	DC charger alias for current-demand loop regression
`ac_basic`	AC EIM demo charger alias
`dc_fast`	DC fast demo charger alias

ISO 15118-2 — vehicle, EVCC (3)

Profile ID	Use
`iso15118_2_ac_evcc_reference`	Reference AC vehicle (dry-run, simulation)
`iso15118_2_dc_evcc_reference`	Reference DC vehicle (dry-run, simulation)
`iso15118_2_dc_evcc_aged_demo`	Aged-battery DC demo vehicle (dry-run, simulation)

DIN 70121 — charger, EVSE (2)

Profile ID	Use
`din70121_dc_smoke`	Short smoke-test profile
`din70121_dc_evse_reference`	Canonical DC charger for your vehicle

DIN 70121 — vehicle, EVCC (2)

Profile ID	Use
`din70121_evcc_reference`	Reference vehicle (dry-run, simulation)
`din70121_dc_evcc_reference`	Reference DC vehicle (dry-run, simulation)

Command-specific profile names

Some commands accept profile names that are not in the catalog above because they are resolved by their own command, for example dc_can_virtual_evse (scripted DC-CAN virtual run) and security_tls_pki_sdp_v2gtp (default of the transport-security package). The ISO 15118-2 and DIN 70121 plant-coupled charger profiles iso15118_2_dc_eim and din70121_dc need --plant-grpc-endpoint; the vehicle commands iso2-evcc and din-evcc use their own profiles (iso15118_2_dc_eim_evcc, din70121_dc_evcc). Use them only with the commands that document them.

Values that are not profile data

IPv6 interface index and scoped link-local address (--interface-index, --advertise-ipv6, --peer-ipv6).
Ports (--udp-port, --tcp-port).
Certificate, key, PFX and trust-anchor paths, and PFX passwords (environment variable).
CAN adapter kind, channel, bitrate and termination.
Battery model parameters of the EVCC.
Electrical limits and tolerances of the computed ISO 15118-20 charger session (runtime profile file, CHARGELINK_ISO20_RUNTIME_PROFILE).
On the VeriStand bench: charger\bench-configuration.json and the SHA-256 values in each run's SESSION.json. The kit has a charger\ and a vehicle\ folder.