Select the role and environment
Choose protocol, profile, network interface, security, model, and software or HIL execution target.
Availability · Scoped technical evaluation
EV charging communication, made observable and controllable.
ChargeLink is an engineering platform for EVSE and EVCC simulation, protocol investigation, campaign execution, and integration with software or hardware test environments.
Dual-role operationEVSE and EVCC simulation paths
Trace-first diagnosisTransport, protocol, state, and artefact context
Integration boundaryCLI, API, SIL, HIL, and external-controller workflows
How teams use ChargeLink
One operating flow from setup to diagnosis
The interface keeps routine operation direct while exposing detailed configuration and analysis for advanced labs.
Start a controlled session
Launch EVSE, EVCC, loopback, external-controller, or campaign workflows with explicit runtime status.
See where communication is
Follow discovery, transport, TLS, EXI, protocol states, model application, measurements, and faults.
Compare and package the result
Inspect traces, messages, diagnostics, run artefacts, and controlled support or review bundles.
Where it fits
ChargeLink owns communication and test orchestration—not charger safety authority
In a HIL or hardware setup, ChargeLink can manage protocol roles, sessions, traces, scenarios, and result artefacts. The customer’s safety controller, power electronics, real-time I/O, and bench-specific adapters remain authoritative for physical actuation.
Typical integration boundary
Operator and automationStudio UI, CLI, API, campaigns, CI, and test orchestration.
ChargeLink runtimeEVSE/EVCC roles, SDP, TCP/TLS, V2GTP, EXI, protocol state, CAN/CAN-FD, diagnostics, and artefacts.
Customer environmentControllers, real-time models, supported xIL environments, networks, I/O, power stages, and safety systems.
Availability
Available through a scoped technical evaluation
There is no public self-service download. DEVlink first agrees the protocol, role, controller or simulator, network, security, target bench, and acceptance evidence so the evaluation has a clear technical boundary.
A useful starting package includes
- One representative EVSE or EVCC use case
- Target protocol and charging mode
- Software, controller, or HIL environment
- Expected traces, decisions, or regression outcome
Product FAQ
Questions before evaluating ChargeLink
Can ChargeLink act as either EVSE or EVCC?
Yes, within the implemented role and profile scope. The selected charging mode, transport, security, controller, and external simulator determine the exact evaluation setup.
Does the scope matrix mean ChargeLink is certified?
No. The matrix reports DEVlink’s current internal engineering baseline. Accredited conformance, formal certification, and physical safety approval require separate authorities and evidence.
Can it connect to an existing HIL or test bench?
ChargeLink provides CLI, API, signal, and adapter boundaries for integration. The target platform, timing, signal map, safety chain, and hardware interface are reviewed before commitment.
What is needed to start?
Provide the role, protocol, charging mode, representative system, network and TLS expectations, current failure or test goal, and the result your team must produce.
Evaluate ChargeLink against one real session or bench problem.
Define the system boundary first, then prove the workflow with representative hardware or software.