Operator Glossary
This glossary explains terms in the way an operating user needs them: what it is, why it matters, and when you need to care.
| Term | What it means | Why / when the operator cares |
|---|---|---|
| Artifact root | Directory where ChargeLink stores run outputs, traces, reports and evidence. | Set it deliberately so runs are retained, backed up and shareable under your organization's policy. |
| ATS | Abstract Test Suite. A structured collection of test logic/cases associated with a protocol/standard test scope. | You care when selecting conformance-readiness packages, generating campaigns and interpreting applicability. |
| BPT | Bidirectional Power Transfer. Energy can flow in both charging and discharging directions where the protocol/profile supports it. | Select a BPT-capable profile only when the DUT, bench and license support it. Treat power-direction safety limits as bench-critical. |
| Campaign | A concrete selection of test cases to execute for one DUT configuration. | Generated after role/profile/PICS/PIXIT selection. It is what you actually run, not the whole catalogue. |
| CAN / CAN-FD | Controller Area Network transport used by protocol families such as CHAdeMO and ChaoJi/GB/T integrations. | You must select the correct adapter, channel, bitrate and physical wiring before live use. |
| ChargeLink profile | A named operating configuration describing protocol, role, charging mode, security/authorization and relevant defaults/limits. | Always discover and inspect the installed profile before starting a session. Wrong profiles create misleading failures. |
| CP | Control Pilot. Physical charging-interface signaling used by conductive charging systems. | ChargeLink HLC operation may depend on the external PLC/bench controlling CP state correctly. It is not just a software setting. |
| DUT / SUT | Device/System Under Test. The charger, vehicle controller or other target being tested. | Ticketing, evidence and reports should identify the exact DUT firmware/configuration. |
| EIM | External Identification Means. Authorization is handled outside Plug & Charge contract-certificate authentication. | Useful as a simpler first interoperability path before introducing PnC/PKI complexity. |
| EVCC | Electric Vehicle Communication Controller, the vehicle-side high-level communication role. | Run ChargeLink as EVCC when simulating/testing the vehicle communication side against an EVSE/SECC. |
| EVSE | Electric Vehicle Supply Equipment, commonly the charging equipment. | In ChargeLink menus this often describes the charger-side simulator/operator role. |
| SECC | Supply Equipment Communication Controller, the charger-side high-level communication controller. | In ISO 15118, this is the peer the EVCC discovers and communicates with. ChargeLink EVSE workflows typically implement this role. |
| Evidence bundle | Inputs and outputs sufficient to understand, reproduce and audit a run. | Preserve it for regressions, support, customer acceptance and test-result traceability. Redact before external sharing. |
| EXI | Efficient XML Interchange, the compact binary encoding used by ISO 15118 message exchange. | EXI/codec errors can look like transport failures. Preserve protocol traces when troubleshooting parsing/serialization. |
| gRPC agent | ChargeLink's native chargelink.integration.v1 automation service. | Use it for programmatic session lifecycle, signals, evidence and integrations. Prove health before debugging a client or VeriStand. |
| HIL | Hardware-in-the-Loop. Real hardware is connected to a simulated/controlled environment. | Requires bench safety, adapters and hardware mappings beyond a software-only proof. |
| Interface index / zone ID | Windows identifier that selects the NIC used with IPv6 link-local addresses. | Essential for ISO 15118/DIN networks with link-local IPv6. Selecting the wrong index can make SDP/TCP appear broken. |
| Link-local IPv6 | IPv6 address in the local-link scope, commonly fe80::/10. | ISO 15118 communication commonly depends on it. Link-local addresses often need a zone/interface identifier on multi-NIC PCs. |
| MIL / SIL / HIL | Model-, Software-, and Hardware-in-the-Loop levels. | They indicate how much real hardware is involved. A SIL pass is not proof of physical interoperability. |
| Native Gateway (VeriStand) | ChargeLink integration using NI VeriStand ClientAPI/Gateway components plus ChargeLink NativeClientBroker/OperatorLauncher. | This is the current VeriStand customer workflow. Do not configure ASAM XIL for it. |
| Package | Productized test collection with catalogue metadata, applicability, execution/report contracts and often a license entitlement. | Select the package matching protocol and DUT role. A package can contain blocked/not-applicable cases. |
| PICS | Protocol Implementation Conformance Statement. Describes which protocol features the DUT claims to implement. | Used to decide which tests apply. Fill it from the DUT specification, not from desired results. |
| PIXIT | Protocol Implementation eXtra Information for Testing. Concrete values needed to execute tests. | Contains test-environment details/parameters not represented only by capability yes/no answers. |
| PLC | Power Line Communication used by CCS/ISO 15118 communication over the charging interface. | External ISO/DIN interoperability depends on the PLC path/SLAC environment, not only Ethernet settings on the PC. |
| PnC | Plug & Charge. ISO 15118 authorization using contract/certificate infrastructure. | Requires correct PKI material, trust chain, time and profile selection. Start with EIM when isolating transport issues. |
| Profile ID | Stable-looking but release-specific identifier used on CLI commands. | Always confirm with the installed profile list; do not assume an ID copied from another release exists. |
| Replay | Re-execution/evaluation using previously captured validated evidence rather than a live DUT. | Useful for deterministic diagnosis and report regeneration. It does not create new physical interoperability evidence. |
| Run ID | Identifier for one ChargeLink execution/session/evidence set. | Record it in lab notes and support tickets. It is the fastest way to correlate runtime state, traces and reports. |
| SDP | SECC Discovery Protocol. EVCC discovers the SECC endpoint before the main ISO 15118 TCP/TLS session. | If SDP fails, the EVCC may never reach TCP/TLS. Check NIC, IPv6, UDP 15118 and advertisement/interface selection first. |
| Scenario | A focused behavior or stimulus sequence. | Good for a single reproducible behavior. Multiple scenarios can be grouped into suites/campaigns. |
| Suite | Logical grouping of related tests/scenarios. | Use it to organize regression intent. The executable campaign is still resolved for the selected DUT/profile. |
| TLS | Transport Layer Security. Protects the communication channel and validates configured identities/trust. | Certificate, trust, key, cipher/policy and clock problems can all stop a session before application messages progress. |
| Trace | Machine-readable chronological record of protocol/runtime events. | Primary evidence for diagnosing where a session diverged. Treat it as potentially sensitive customer data. |
| V2GTP | Vehicle-to-Grid Transport Protocol framing used to carry higher-level payloads. | A TCP connection can succeed while V2GTP framing still fails. This is a distinct troubleshooting layer. |
| Verdict | Result assigned by a test/campaign, such as PASS, FAIL, BLOCKED, SKIPPED or ERROR. | Interpret with applicability and evidence. BLOCKED is not the same as FAIL. |
| Watchdog / command age | Safety mechanism detecting stale command/control updates. | A stale command must not leave the bench driving an old power request. Verify fail-safe behavior before production use. |
| ASAM XIL | Standardized test-tool interface planned for a later ChargeLink release in the context of this documentation. | It is not required for the current NI VeriStand Native Gateway workflow. |