Release and Version Matrix
Use this page as the operator's compatibility record. The values supplied with the shipping installation package are authoritative; do not infer compatibility from a development repository, a newer website, or a different customer's workstation.
Record the installed product identity
$CL = 'C:\Program Files\ChargeLink Native\bin\chargelink.exe'
& $CL --version
& $CL --json license status
& $CL --json license entitlements
& $CL --json integration capabilities --endpoint http://127.0.0.1:50051
If the gRPC agent is not running, omit the last command or start it as described in the gRPC chapter.
Compatibility record to keep with every released manual
The release owner should populate this table for the actual customer package before publication.
| Item | Released value | Customer verification |
|---|---|---|
| ChargeLink Native product version | See shipping release notes / --version | chargelink --version |
| Documentation package | This documentation bundle | README / package manifest |
| CLI contract | Same installed product version | chargelink --help and subcommand --help |
| Integration API | Reported by installed capabilities | integration capabilities |
| License schema/edition | Purchased customer entitlement | license status, license entitlements |
| Profile catalogue | Installed catalogue | profile list |
| Conformance/test package catalogue | Installed/licensed catalogue | conformance/test catalogue commands |
| Windows versions | Release-note supported set | Get-ComputerInfo |
| NI VeriStand | Release-note validated version(s) | NI About/version + gateway preflight |
| NativeClientBroker | Shipped with matching ChargeLink package | file/product version |
| OperatorLauncher | Shipped with matching ChargeLink package | file/product version |
| Supported CAN adapters/drivers | Release-note validated set | Device Manager/vendor utility |
Protocol-to-profile check
Do not maintain a hard-coded profile table outside the release process. Profiles can be added or renamed. Resolve them from the installed build:
& $CL --json profile list
Then verify the selected profile:
& $CL profile show <PROFILE_ID>
At minimum, release acceptance should confirm applicable profiles for:
- ISO 15118-20 AC;
- ISO 15118-20 DC;
- ISO 15118-20 BPT where licensed;
- ISO 15118-2 AC where included;
- ISO 15118-2 DC;
- DIN 70121 DC;
- CHAdeMO;
- ChaoJi / GB/T where included;
- NACS / SAE J3400 readiness where included;
- MCS readiness where included.
VeriStand compatibility rule
The current integration is the ChargeLink VeriStand Native Gateway using NI VeriStand ClientAPI/Gateway components. The release owner must validate an exact NI version before declaring it supported. Do not mix ClientAPI and Gateway assemblies from different VeriStand releases.
ASAM XIL is planned for a later ChargeLink release and is not part of this matrix for the current customer workflow.
Upgrade rule
When ChargeLink is upgraded, repeat at least:
- installation/package verification;
- license verify/status;
doctor --strict;- profile discovery;
- gRPC health/session smoke;
- one golden run for every protocol family used at the site;
- VeriStand gateway proof when used;
- a trace/report/evidence export;
- support-bundle collection.
Do not assume a previously validated automation script is compatible until its commands have been checked against the upgraded CLI.