Represent the system.
Create native and physical models or bring in suitable FMUs. Define the behaviour, parameters and interfaces needed for the question you want to answer.
MIL: explore model behaviourDEVLINK ENGINEERING PLATFORM · DEP
DEP builds one System from your models, FMUs and compiled ECU software, runs it in MIL and SIL in deterministic logical time, and keeps every result as traceable evidence.
Discuss a DEP evaluation ↗Read the documentation ↗
THE ENGINEERING CHALLENGE
A battery model can behave as expected on its own. A controller can pass its isolated tests. The next question is how they behave together—across operating modes, limits and software changes.
DEP brings model engineering and virtual software verification into a shared workflow. Connect the plant, controller software and scenario so that the team can investigate the system interaction.
FROM MODEL TO SOFTWARE
Create native and physical models or bring in suitable FMUs. Define the behaviour, parameters and interfaces needed for the question you want to answer.
MIL: explore model behaviourBring controller software into the virtual system as a vECU. Connect its signals to the surrounding models and define the execution assumptions.
SIL: investigate real softwareApply operating conditions, inspect results and compare the response against expected behaviour. Keep the model, configuration and evidence associated with the run.
Evidence: explain the resultWHAT IS IN DEP
Compose the system from components on a visual canvas. Each component can carry a model and a software implementation, connected through signal mappings.
Block diagrams and state machines for controllers, supervisors and sequencers, plus a dedicated designer for electric drives. Check a model and export it as an FMU.
Electrical networks with sources, switches, contactors, battery cells and packs, and loads, simulated together with the rest of the system.
Ready-made reference models across EV and hybrid, electrical, thermal, hydraulic and aerospace systems, to adapt to your project.
Bring in FMI and SSP models and your own compiled software as virtual ECUs. Every package is verified before it joins the system.
Virtual CAN, CAN FD, LIN and ARINC networks built from your existing network databases, with a live decoded trace.
Run scenario campaigns in MIL and SIL and keep integrity-protected evidence, ready for reviews, reports and CI pipelines.
Operator pages with gauges, trends and alarms. Compare runs, record and replay, export results and run calibration experiments.
Turn requirements into a first model. An optional AI assistant helps, and only with your approval for each request.
VIRTUAL NETWORKS
Import the DBC, LDF or FIBEX files your project already uses, map components to network nodes and let generators provide the rest of the bus. Every frame is decoded live and kept with the run.
Networks and restbus in the documentation ↗
FROM MIL TO SIL
Run the same scenarios against the model and the real software, and see exactly where the software departs from the model.
The same inputs give the same results, run after run.
Every scenario starts from a clean copy of the project, so one test never affects the next.
Evidence ties every verdict to the exact project and software version that produced it. DEP never reports a pass it did not observe.
WORKS WITH YOUR TOOLCHAIN
DEP focuses on MIL and SIL. For charging communication and hardware-in-the-loop it works with dedicated tools instead of reinventing them.
FMI, SSP and SIL Kit let DEP exchange models and co-simulate with the tools your teams already use.
Model charging behaviour in DEP and connect a separately licensed ChargeLink for live charging communication.
DEP focuses on MIL and SIL. For real-time hardware-in-the-loop it works with NI VeriStand.
THREE SECTORS. ONE E-MOBILITY FOCUS.
Explore battery and BMS behaviour, charging interactions, power electronics and energy-management software in representative vehicle scenarios.
Automotive applications ↗Investigate battery systems, electrical power distribution and supervisory control across flight-related operating modes and ground-energy scenarios.
Aerospace applications ↗Explore battery-powered machinery, mobile equipment, charging interfaces and energy use across representative industrial work cycles.
Industrial applications ↗CAPABILITY BOUNDARIES
We document the boundaries as carefully as the features, so your evaluation has no surprises.
Read the capability boundaries ↗LICENSING
DEP editions follow how people work with the platform. Licences add up: install more than one and their features combine. Every licence includes free security updates.
For test operators.
For model and control engineers.
For software and system integrators.
For HIL benches running NI VeriStand.
For teams sharing DEP.
HOW LICENSING WORKS
Prices depend on the editions and the licence type. Tell us how your team will use DEP and we will send a quote.
Request a quote ↗BEFORE YOU DECIDE
MIL investigates modelled system and control behaviour. SIL brings compiled controller software into the same virtual System. In DEP both run the same scenarios, so the results can be compared case by case.
Yes. DEP runs FMI models and your own compiled software as virtual ECUs. Every package is verified before it runs, and the evaluation confirms the formats you use.
No. DEP runs MIL and SIL on the desktop with simulated networks. For hardware-in-the-loop, DEP works with NI VeriStand as the real-time platform.
DEP models the system: battery, power electronics, controllers. ChargeLink handles EV charging communication. Live charging communication uses a separately licensed ChargeLink.
No. AI is optional and only used in Requirements to model. Nothing is sent without your approval for each request, and local AI endpoints are supported.
DEVlink’s MIL Studio capabilities have moved into DEP, which is the product for model engineering and connected MIL and SIL verification.
DEP DOCUMENTATION
YOUR NEXT ENGINEERING QUESTION
Let’s define a MIL or SIL evaluation around your e-mobility system and the behaviour you need to understand.