ChargeLink Native User Documentation
Welcome to ChargeLink Native. This manual is written for operators, test engineers, integration engineers and administrators who receive the installed ChargeLink Native customer package. Normal operation does not require a source-code checkout, Rust toolchain, internal patch package, or development repository.
New user? Follow this path
- Install and Activate — install the customer package and prove the license.
- First Successful Session — complete a short software-only smoke test.
- First 60 Minutes — establish a supportable workstation baseline and archive evidence.
- Environment and Bench Preflight — validate the actual NIC, certificates, CAN adapter or VeriStand environment.
- Select a Protocol — choose the correct runbook/profile for ISO 15118-20, ISO 15118-2, DIN 70121, CHAdeMO or the additional supported/readiness stacks.
- Golden Reference Runs — keep a known-good baseline for upgrades and troubleshooting.
Choose by task
| I want to... | Start with... |
|---|---|
| Install a new PC | Install and Activate → First 60 Minutes |
| Connect a real EV or EVSE | Environment and Bench Preflight → Select a Protocol |
| Run ISO 15118-20 | ISO 15118-20 runbook |
| Run ISO 15118-2 | ISO 15118-2 runbook |
| Run DIN 70121 | DIN 70121 runbook |
| Run CHAdeMO | CHAdeMO runbook |
| Create/run test campaigns | Test Workflow → Test Package Catalog |
| Understand traces/replay/reports | Evidence and Reports |
| Integrate NI VeriStand | NI VeriStand Native Gateway |
| Automate through gRPC | gRPC Automation |
| Fix a failure | Troubleshooting: Symptom to Action |
| Open a support case | Support Escalation |
| Check what is supported/planned | Capability Boundaries |
| Verify version compatibility | Release and Version Matrix |
| Look up exact CLI syntax | Complete CLI Reference |
Command convention
Examples use Windows PowerShell and the packaged installation path:
$CL = 'C:\Program Files\ChargeLink Native\bin\chargelink.exe'
Values shown as <LIKE_THIS> are customer/environment placeholders and must be replaced. Profile IDs, package IDs and optional command flags are version-sensitive; the installed binary and installed catalogues are the final authority.
Production operating principle
The manual is organized around three questions:
- Why am I doing this? — the purpose and prerequisites of the task.
- What exactly do I do? — copy/paste commands and ordered procedures.
- What do I do when it fails? — expected checkpoints, failure isolation and support evidence.
For a controlled release, the Documentation Acceptance Test should be executed against the shipping installation package before this manual is published to customers.