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 plant-coupled ISO 15118-20 lane, 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 build 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

For ISO 15118-20 EVSE profiles, AC/DC, BPT and PnC behaviour is derived from the tokens in the profile ID (ac, dc, bpt, pnc). Profiles whose description says "alias" resolve to the same lane as the canonical profile they name; they exist so that procedures written for earlier releases keep working.

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 runtime lanes key their behaviour on the profile ID tokens, a custom ISO 15118-20 EVSE profile whose ID lacks ac, bpt or pnc behaves as DC EIM.

Built-in profiles

ISO 15118-20 — EVSE (8)

ISO 15118-20 — EVCC (10)

ISO 15118-2 — EVSE (16)

ISO 15118-2 — EVCC (3)

DIN 70121 — EVSE (3)

DIN 70121 — EVCC (2)

Lane-specific profile names

Some commands accept profile names that are not in the catalog above because they are resolved inside their own lane, for example dc_can_virtual_evse (scripted DC-CAN virtual run) and security_tls_pki_sdp_v2gtp (default of the transport-security package). 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 plant-coupled ISO 15118-20 lane (runtime profile file, CHARGELINK_ISO20_RUNTIME_PROFILE).
• On the VeriStand bench: pc1\bench-configuration.json and the SHA-256 values in each run's SESSION.json.