INTEGRATIONS & STANDARDS
Fits the tools
you already use.
What ChargeLink and DEP connect to, which standards they implement and what they need to run. The user guides list the exact versions and requirements.
Plan an evaluation ↗Read the documentation ↗WORKS WITH
Integrations,
product by product.
| Area | ChargeLink | DEP |
|---|---|---|
| Test benches | Couples the charging session to a plant model in NI VeriStand, so communication and electrical behaviour are tested together. NI VeriStand bench ↗ | Prepares and observes hardware-in-the-loop benches that run on NI VeriStand. HIL and NI VeriStand ↗ |
| Models | Plant models for NI VeriStand as FMI models | FMI models for co-simulation and model exchange, FMU export, and conversion of selected Simulink models. Software, FMI and SSP ↗ |
| System structure | — | SSP system descriptions, 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, and co-simulation through SIL Kit |
| Networks and buses | Charging communication over Ethernet, and CAN for IEC 61851-23/-24 System A (CHAdeMO), in software or on a physical CAN bus | Virtual CAN, CAN FD, LIN and ARINC networks built from your existing network databases. Networks and restbus ↗ |
| Measurement and calibration | — | Calibration data import for offline experiments |
| Automation | Command line and API for scripts, CI pipelines and test controllers. API integration ↗ | Automation interface for CI pipelines |
| Evidence and results | Integrity-protected evidence for every run, ready to review and share | Evidence and reports for reviews and CI, with export of recorded results |
| ChargeLink and DEP together | Provides live charging communication to models in DEP | Connects to a separately licensed ChargeLink for live charging communication. 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 charging communication as charger or vehicle, with secure communication and both scheduled and dynamic control.
ISO 15118-20 runbook ↗DC charging communication as charger or vehicle.
ISO 15118-2 runbook ↗DC charging communication as charger or vehicle.
DIN 70121 runbook ↗CAN-based DC charging as station or vehicle, in software or on a physical CAN bus.
CHAdeMO runbook ↗Megawatt charging communication for heavy-duty vehicles, as charger or vehicle.
MCS runbook ↗Working with GB/T or NACS/J3400? Talk to us about your project.
Platform requirements.
- ChargeLink
- Windows 10 or 11, 64-bit · the bench requirements are listed in the user guide
- DEP
- Windows 10 or 11, 64-bit · install for your own Windows user or, by an administrator, for every user of the PC · signed installer
- 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?
The user guides list the supported NI VeriStand versions. Tell us which version your bench runs.
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.