Supported, Conditional, and Planned Capabilities
This page prevents a common support problem: treating every visible command, test catalogue row, or roadmap integration as an unconditional production claim. Always distinguish implemented and supported, implemented with environment prerequisites, and planned/not part of the current customer workflow.
How to read the status
| Status | Meaning for the operating user |
|---|---|
| Supported | Intended for customer use in the installed release when licensed and configured as documented. |
| Conditional | Implemented, but successful use depends on hardware, certificates, third-party software, edition, or a validated customer environment. |
| Engineering / readiness | Useful for regression, interoperability preparation, or evidence generation; it must not be represented as accredited certification. |
| Planned | Not part of the current operating workflow. Do not install dependencies or create procedures around it yet. |
Current customer-facing capability matrix
The exact installed version and license are authoritative. Use chargelink --version, chargelink license entitlements, chargelink profile list, and the package catalogue on the target workstation.
| Area | Customer status | Important boundary |
|---|---|---|
| ISO 15118-20 EVSE/EVCC | Supported/conditional by selected AC/DC, security, BPT and physical environment | External interoperability still depends on peer implementation, PLC/network path and PKI where used. |
| ISO 15118-2 EVSE/EVCC | Supported/conditional | Select a profile matching AC/DC and EIM/PnC/TLS behavior. |
| DIN 70121 DC | Supported/conditional | Legacy DC workflow; do not apply ISO 15118-specific expectations blindly. |
| CHAdeMO | Conditional | Physical operation requires the supported CAN adapter, driver, wiring and bench safety controls. |
| ChaoJi / GB/T | Conditional / engineering package depending on edition | CAN/CAN-FD and physical-bench prerequisites apply. |
| NACS / SAE J3400 | Readiness/conditional according to installed package | Connector/PLC/physical coverage and standards claim boundaries must be checked for the actual release. |
| MCS | Readiness/conditional according to installed package | High-power physical validation requires the correct external hardware and safety environment. |
| Native gRPC Integration API | Supported | Remote exposure requires production authentication/TLS/authorization configuration appropriate to the edition. |
| NI VeriStand Native Gateway | Supported/conditional | Uses NI VeriStand ClientAPI/Gateway components and the ChargeLink NativeClientBroker/OperatorLauncher. |
| ASAM XIL for VeriStand | Planned for a later ChargeLink release | Not required for the current VeriStand workflow. Do not configure the present product around XIL. |
| Conformance/ATS packages | Engineering/conformance-readiness unless a separate certification scope says otherwise | A ChargeLink verdict is not automatically an accredited certificate or standards-body approval. |
| Physical high-voltage safety | Outside software claim | Site procedures, interlocks, DUT limits and lab safety systems remain authoritative. |
Package catalogue versus executable reality
A package can contain cases that are not executable in the current environment. Typical reasons:
- the selected PICS/PIXIT makes a case not applicable;
- the required authorization or certificate path is not configured;
- physical CAN/PLC hardware is absent;
- the selected license does not include that package;
- a case is intentionally retained as blocked/audit-only evidence.
Do not report a smaller executed campaign as "missing cases" until applicability and blockers have been reviewed.
Version-sensitive behavior
CLI syntax, defaults, package contents, profile IDs, and integration dependencies can change between releases. For a controlled test procedure:
- record
chargelink --version; - archive the selected profile output;
- archive PICS/PIXIT and campaign inputs;
- record the documentation package version;
- do not copy a command from a newer manual into an older installed build without checking
--help.
External certification and standards text
ChargeLink documentation describes product behavior and customer-safe test metadata. It does not reproduce licensed standards text. Conformance-readiness evidence does not itself establish certification, accreditation, regulatory approval, connector qualification, or high-voltage safety approval.
When to contact support before testing
Contact support before a live run if:
- your installed profile/package does not match the purchased scope;
- the required third-party version is outside the release matrix;
- a production TLS/PnC setup requires a certificate path not described for your edition;
- the DUT requires a nonstandard network/CAN configuration;
- you need to make a certification or formal compliance claim based on ChargeLink output.