INTEGRATIONS & STANDARDS
Fits the tools
you already use.
What ChargeLink and DEP connect to, which standards they implement and what they need to run. Versions are stated exactly, so you can check your setup before you ask.
Plan an evaluation ↗Read the documentation ↗WORKS WITH
Integrations,
product by product.
| Area | ChargeLink | DEP |
|---|---|---|
| Test benches | NI VeriStand 2024 Q4: the charging session is coupled to a plant model through an FMI 2.0 FMU, with a 500 Hz SIL timing profile. NI VeriStand bench ↗ | NI VeriStand 2024 Q4 with its Gateway: discover targets, review a deployment and observe channels. NI VeriStand runs the real-time execution. HIL and NI VeriStand ↗ |
| Models | Plant model as an FMI 2.0 FMU for NI VeriStand | FMI 2 and FMI 3 FMUs (co-simulation and model exchange, Windows x64); FMU export; a restricted Simulink MDL/SLX subset for inspection and conversion. Software, FMI and SSP ↗ |
| System structure | — | SSP 2.0.1 (restricted subset) import and export |
| Your software | Your EVCC, SECC or OBC software as the system under test, against ChargeLink as charger or vehicle | Your compiled ECU software as virtual ECUs through documented adapters; SIL Kit participants |
| Networks and buses | IPv6 link-local, SDP, TCP, V2GTP and EXI; CAN for IEC 61851-23/-24 System A through a virtual CAN hub or a Kvaser CANlib channel | DBC (CAN, CAN FD), LDF (LIN) and FIBEX import; virtual CAN, CAN FD, LIN and ARINC 429/825 networks. Networks and restbus ↗ |
| Measurement and calibration | — | A2L (ASAP2) import |
| Automation | CLI with JSON output and stable exit codes; a local gRPC integration API. gRPC integration ↗ | A headless automation interface for CI |
| Evidence and results | Run manifests with a SHA-256 hash per file, integrity checks, redaction and support bundles | JSON evidence, JUnit XML, reports, CSV, Vector ASC and DEP recordings |
| ChargeLink and DEP together | Plays the charger in a live ISO 15118-20 DC session with DEP | Connects to a separately licensed ChargeLink for live ISO 15118-20 DC sessions. Charging and the EVSE console ↗ |
CHARGING STANDARDS
What ChargeLink speaks.
Every protocol has a runbook in the ChargeLink user guide with the exact roles, modes and limits.
DC in Scheduled and Dynamic control with external identification (EIM), as charger or vehicle; AC reference responses for test development. IPv6, SDP, TCP, mutual TLS 1.3, V2GTP and EXI.
ISO 15118-20 runbook ↗DC and AC with external identification (EIM). Full DC sessions as charger and vehicle, and an EVSE reference responder, for engineering and test development. Optional TLS 1.2.
ISO 15118-2 runbook ↗DC. Full sessions as charger and vehicle, and an EVSE reference responder, for engineering and test development.
DIN 70121 runbook ↗The CAN-based DC charging scheme. Station and vehicle roles with a simulated plant, on one PC, across two PCs or on a physical CAN bus.
System A runbook ↗Working with GB/T, NACS/J3400 or MCS? Talk to us about your project.
Platform requirements.
- ChargeLink
- Windows 10 or 11, 64-bit · Microsoft Visual C++ 2015–2022 Redistributable · .NET 10 runtime for the NI VeriStand host · installs from a ZIP archive
- DEP
- Windows 10 or 11, 64-bit · no administrator rights needed · each version installs into its own folder
- Licensing
- Offline activation for both · ChargeLink · DEP
- Security updates
- Free for every licence · devlink.se/security
BEFORE YOU ASK
The practical questions.
Do ChargeLink or DEP need an internet connection?
No. Both run on your own PC or bench. Licences are activated offline with a request file and a signed licence file, and ChargeLink's gRPC API listens only on the local machine.
Which NI VeriStand version do you support?
NI VeriStand 2024 Q4, for both products. Tell us if your bench runs a different version.
Can we bring our own models and software?
Yes. DEP runs FMI 2 and FMI 3 FMUs and your compiled software as virtual ECUs. ChargeLink tests your own EVCC, SECC or OBC software as the system under test.
Our tool or format is not listed. What now?
Tell us what your toolchain looks like. We check it during a scoped technical evaluation and say plainly what works and what does not.
YOUR TOOLCHAIN
Not on the list?
Tell us what your bench and tools look like. We will tell you plainly what fits.