It is no longer enough to say that a product supports a charging standard or feature. OEMs, charger manufacturers, test laboratories, and system integrators increasingly need proof of what was executed, under which profile, with which result.
Charging support is not one binary claim
EV charging behaviour depends on protocol generation, EVCC or SECC role, AC or DC mode, authentication method, TLS configuration, certificates, negotiated services, timing, safety behaviour, and customer-specific limitations. A generic pass result hides the conditions that actually determine whether the result is useful.
Professional validation therefore starts with an explicit profile. The profile defines what the product is expected to support and what the test actually exercised.
Evidence should be produced by execution
A meaningful run should produce more than a green status. It should preserve the configuration, message flow, timing, state transitions, verdict logic, and exported artifacts needed to review or repeat the result. Engineering, quality, product management, and customer-facing teams should be able to understand what was proven without reconstructing the session manually.
Keep claims proportional to proof
Conformance and compliance language must be handled carefully. Formal certification depends on defined scopes, licensed test corpora, accredited processes, and appropriate release evidence. An engineering validation platform should make supported coverage and gaps visible rather than turning a limited profile result into a broad marketing claim.
Complement the existing HIL environment
Many teams already use HIL applications for CP/PP behaviour, contactors, CAN communication, measurements, power-stage models, fault insertion, and safety chains. The charging communication layer should connect to those investments, not force a complete laboratory replacement.
DEVlink remains hardware-vendor agnostic. ChargeLink is intended to integrate with suitable HIL platforms and external automation. Through DEVlink’s long-term collaboration with ALIARO, the xMove platform can be proposed where it fits the application, while other platforms remain valid choices.
Keep the operator workflow understandable
Complex technology does not require a complex daily workflow. The essential pattern is clear: select the protocol and profile, establish the session, run the scenario, inspect the evidence, compare the outcome, and export a reviewable result.
That is the purpose of ChargeLink: turn protocol complexity into explainable, repeatable, and claim-safe engineering confidence.