Protocol Operations
This section contains operator runbooks for every charging protocol family exposed by the installed ChargeLink Native application. Start here instead of the low-level CLI reference.
| Protocol | Charging mode | Transport | Recommended starting profile | Runbook |
|---|---|---|---|---|
| ISO 15118-20 | AC, DC, BPT | IPv6, SDP, TCP, optional TLS | iso15118_20_dc | ISO 15118-20 |
| ISO 15118-2 | AC and DC | IPv6, SDP, TCP, optional TLS | iso15118_2_dc_evse_reference | ISO 15118-2 |
| DIN 70121 | DC | IPv6, SDP, TCP | din70121_dc_evse_reference | DIN 70121 |
| CHAdeMO | DC | CAN | adapter-dependent | CHAdeMO |
| MCS, NACS/J3400, ChaoJi/GB/T | protocol-dependent | IPv6 HLC or CAN | package-dependent | Additional protocol stacks |
Common operating pattern
- Open PowerShell as Administrator.
- Set the installed binary and a writable evidence directory.
- Verify the license and discover profiles.
- Run a dry-run or preflight.
- Start the EVSE or EVCC role.
- Observe status and collect artifacts.
- Stop the runtime cleanly.
$CL = "C:\Program Files\ChargeLink Native\chargelink.exe"
$DATA = "C:\ProgramData\ChargeLink"
New-Item -ItemType Directory -Force "$DATA\runs" | Out-Null
& $CL license status --json
& $CL profile list --json
The profile determines protocol, role, connector family and behavior. Network addresses, interface indexes, certificate paths and CAN channels are deployment settings and must be supplied for the current bench.