DEVlink / DEP

DEVLINK ENGINEERING PLATFORM · DEP

Model the system.
Run the software.
Verify what matters.

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 ↗
DEP
MIL · Model-in-the-Loop
+
SIL · Software-in-the-Loop
+
Traceable evidence
DEP Scenarios and validation view showing a passed MIL scenario with its evidence ready to download
Scenarios and validation: a saved scenario run in MIL, with the evidence ready to download.

THE ENGINEERING CHALLENGE

Components are only
part of the story.

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

Build understanding.
Keep it connected.

01 / MODEL

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 behaviour
02 / CONNECT

Introduce the software.

Bring controller software into the virtual system as a vECU. Connect its signals to the surrounding models and define the execution assumptions.

SIL: investigate real software
03 / VERIFY

Run a shared scenario.

Apply operating conditions, inspect results and compare the response against expected behaviour. Keep the model, configuration and evidence associated with the run.

Evidence: explain the result

WHAT IS IN DEP

Everything you need
for MIL and SIL.

01

System engineering

Compose the system from components on a visual canvas. Each component can carry a model and a software implementation, connected through signal mappings.

02

Model Designer & State Logic

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.

03

Physical modelling

Electrical networks with sources, switches, contactors, battery cells and packs, and loads, simulated together with the rest of the system.

04

Library Center

Ready-made reference models across EV and hybrid, electrical, thermal, hydraulic and aerospace systems, to adapt to your project.

05

FMI, SSP & your software

Bring in FMI and SSP models and your own compiled software as virtual ECUs. Every package is verified before it joins the system.

06

Virtual networks & restbus

Virtual CAN, CAN FD, LIN and ARINC networks built from your existing network databases, with a live decoded trace.

07

Scenarios, campaigns & evidence

Run scenario campaigns in MIL and SIL and keep integrity-protected evidence, ready for reviews, reports and CI pipelines.

08

Operator HMI & results

Operator pages with gauges, trends and alarms. Compare runs, record and replay, export results and run calibration experiments.

09

Requirements to model

Turn requirements into a first model. An optional AI assistant helps, and only with your approval for each request.

VIRTUAL NETWORKS

Real databases.
Virtual buses.

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 ↗
DEP Network Engineering view with a CAN network topology connecting a vehicle plant, drive controller and test bench

FROM MIL TO SIL

Same System. Same scenarios.
Two profiles.

Run the same scenarios against the model and the real software, and see exactly where the software departs from the model.

01

Repeatable results

The same inputs give the same results, run after run.

02

Isolated runs

Every scenario starts from a clean copy of the project, so one test never affects the next.

03

Evidence you can trace

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

Open standards.
Dedicated tools.

DEP focuses on MIL and SIL. For charging communication and hardware-in-the-loop it works with dedicated tools instead of reinventing them.

01

Open model standards

FMI, SSP and SIL Kit let DEP exchange models and co-simulate with the tools your teams already use.

02

Charging with ChargeLink

Model charging behaviour in DEP and connect a separately licensed ChargeLink for live charging communication.

03

HIL through NI VeriStand

DEP focuses on MIL and SIL. For real-time hardware-in-the-loop it works with NI VeriStand.

THREE SECTORS. ONE E-MOBILITY FOCUS.

Electrification changes
the whole system.

01 / AUTOMOTIVE

From battery to vehicle control.

Explore battery and BMS behaviour, charging interactions, power electronics and energy-management software in representative vehicle scenarios.

Automotive applications ↗
02 / AEROSPACE

Understand electric aviation.

Investigate battery systems, electrical power distribution and supervisory control across flight-related operating modes and ground-energy scenarios.

Aerospace applications ↗
03 / INDUSTRIAL

Develop electric equipment.

Explore battery-powered machinery, mobile equipment, charging interfaces and energy use across representative industrial work cycles.

Industrial applications ↗

CAPABILITY BOUNDARIES

Clear about
what it does not do.

We document the boundaries as carefully as the features, so your evaluation has no surprises.

Read the capability boundaries ↗
  • DEP is a MIL and SIL platform. It does not connect to or drive hardware: no physical buses, I/O or power outputs.
  • It runs on a Windows desktop and is not a real-time target. Real-time HIL belongs to NI VeriStand.
  • It does not certify models, software or protocols. A passed scenario is engineering evidence, not a certificate.
  • Example models illustrate behaviour and are not calibrated against real vehicles.

LICENSING

Licensed by role.
Combined as you grow.

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.

Operator

For test operators.

  • Run prepared projects and campaigns
  • View results and recordings
  • Operate HMI pages

Engineer

For model and control engineers.

  • MIL modelling with Model Designer and State Logic
  • FMU export
  • Scenarios, tests and HMI pages

HIL Runtime

For HIL benches running NI VeriStand.

  • One licence per bench target
  • Prepare, deploy and observe from DEP
  • NI VeriStand runs the real-time execution

Enterprise

For teams sharing DEP.

  • All features
  • A pool of seats and targets
  • Floating seats shared across your team

HOW LICENSING WORKS

Simple to start.
No surprises later.

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 ↗
Licence types
Subscription · perpetual licence with maintenance · academic licence for teaching and publicly funded research
Free evaluation
30 days on one PC
Activation
Offline: DEP creates a request file and DEVlink returns a signed licence file, for one Windows user or, set up by an administrator, for every user of the PC
Shared seats
Floating seats shared across your team over your own network
Security updates
Free for every licence, published as advisories at devlink.se/security

Requirements & security.

Availability
Scoped technical evaluation
Licensing
Editions and licence types
Platform
Windows 10/11 64-bit · install for your own Windows user, or an administrator installs for every user of the PC
Installer
Signed by DEVlink AB (Microsoft-verified publisher) · verify your download
Security and updates
Security updates are free of charge for every licence type and published as advisories at devlink.se/security
Works with
ChargeLink · NI VeriStand · SIL Kit · FMI and SSP tools

BEFORE YOU DECIDE

Start with the
engineering fit.

What is the difference between MIL and SIL?

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.

Can we bring our own models and software?

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.

Does DEP connect to hardware or run in real time?

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.

How does DEP relate to ChargeLink?

DEP models the system: battery, power electronics, controllers. ChargeLink handles EV charging communication. Live charging communication uses a separately licensed ChargeLink.

Is AI required? Is our data sent anywhere?

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.

What happened to MIL Studio?

DEVlink’s MIL Studio capabilities have moved into DEP, which is the product for model engineering and connected MIL and SIL verification.

DEP DOCUMENTATION

Start in minutes.
Go as deep as you need.

YOUR NEXT ENGINEERING QUESTION

Bring the model.
Bring the software.

Let’s define a MIL or SIL evaluation around your e-mobility system and the behaviour you need to understand.

Evaluate DEP ↗