---
title: "From Simulink Model to Running ECU: How Raptor DEV Speeds Up Prototyping for UK Controls Teams"
description: Raptor DEV lets engineering teams flash Simulink models straight to production-intent ECUs. Here's the workflow, and how EMB Power supports it in the UK.
---

[Skip to content](https://blog.emb-power.com/from-simulink-model-to-running-ecu-how-raptor-dev-speeds-up-prototyping-for-uk-controls-teams#main-content)

![EMB\_Power\_Logo](https://blog.emb-power.com/hs-fs/hubfs/EMB_POWER_logo-16x9-tp-1.png?width=250&height=140&name=EMB_POWER_logo-16x9-tp-1.png)

Open main navigation

Close main navigation

- [Contact us](https://www.emb-power.com/contact-us)

[Contact us](https://www.emb-power.com/contact-us)

 Oct 7, 2026, 2:28:13 PM

# From Simulink Model to Running ECU: How Raptor DEV Speeds Up Prototyping for UK Controls Teams

[EMB Power Team](https://blog.emb-power.com/author/emb-power-team)

Share: [facebook-f icon](http://www.facebook.com/share.php?u=https://blog.emb-power.com/from-simulink-model-to-running-ecu-how-raptor-dev-speeds-up-prototyping-for-uk-controls-teams) [linkedin-in icon](http://www.linkedin.com/shareArticle?mini=true&url=https://blog.emb-power.com/from-simulink-model-to-running-ecu-how-raptor-dev-speeds-up-prototyping-for-uk-controls-teams) [Twitter icon](https://twitter.com/intent/tweet?url=https://blog.emb-power.com/from-simulink-model-to-running-ecu-how-raptor-dev-speeds-up-prototyping-for-uk-controls-teams) [pinterest-p icon](http://pinterest.com/pin/create/link/?url=https://blog.emb-power.com/from-simulink-model-to-running-ecu-how-raptor-dev-speeds-up-prototyping-for-uk-controls-teams) [envelope icon](mailto:?body=https://blog.emb-power.com/from-simulink-model-to-running-ecu-how-raptor-dev-speeds-up-prototyping-for-uk-controls-teams)

Prototyping an ECU fast is one thing. Prototyping one that still looks like the production part six months later is a different problem entirely — and it's the one most controls teams actually have. [New Eagle's](https://www.neweagle.net/) Raptor DEV Dongle closes that gap by letting engineers build, flash and calibrate control strategies directly from Simulink, onto hardware that's already production-intent. EMB Power is New Eagle's exclusive UK supplier and support partner for the Raptor toolchain, so UK and EU teams get that workflow with local engineering support behind it.

## Why ECU Prototyping Needs to Move Faster

Controls teams building electrified and autonomous vehicle platforms are under pressure from several directions at once: tighter time-to-market, a need for hardware that behaves like the production unit from day one, rising expectations for validation and safety compliance, and interfacing requirements that span multiple buses, I/O types and third-party sensors.

Hand-coded prototypes and ad-hoc hardware-in-the-loop setups struggle to keep up with that list. A model-based workflow that goes straight from simulation to flashed hardware removes several of those steps rather than trying to do them faster.

## What the Raptor DEV Dongle Actually Does

The Raptor DEV Dongle lets a controls engineer stay inside MATLAB Simulink for the whole of the early development cycle, while still targeting real Raptor control hardware. In practice that means:

- Authoring, simulating and testing the ECU project entirely in Simulink
- Generating production-quality C code for Raptor control modules through New Eagle's OpenECU-based development environment
- One-click deployment and calibration to supported ECUs via the dongle
- Flash, tune and datalog work either through Raptor-Cal or industry-standard tools such as Vector or ATI Vision

Because the target hardware is the same family of module that ships in production, the usual gap between "it works on the bench" and "it works in the vehicle" is a lot narrower.

## The Workflow: From Simulink Model to Flashed ECU

A typical Raptor DEV project moves through the same handful of stages on most programmes:

1. **Develop the control strategy** in Simulink, using Raptor's native blocks for I/O and communications (CAN, LIN, Ethernet, BMS control).
2. **Select the target hardware** — a general-purpose module for a straightforward project, or a higher-channel-count unit for a multi-bus, multi-sensor application.
3. **Connect the hardware** via the Raptor DEV Dongle, with the appropriate pigtail harness for bench-top flashing and I/O checkout.
4. **Build and flash** the compiled model in a single step — Raptor DEV handles code generation and deployment together.
5. **Tune and validate** using Raptor-Cal or a compatible calibration tool, adjusting calibration tables and datalogging real-world response.
6. **Iterate** inside the same environment, so algorithm, code and hardware stay in sync as the design changes.

## Choosing the Right Control Module for the Job

New Eagle's Raptor range covers general-purpose control modules through to higher-channel gateway units and specialised body or hydraulic controllers. The [GCM111](https://www.neweagle.net/) is one of the current general control modules in active use on EMB Power projects; the right module for a given programme depends on channel count, bus requirements and environmental spec, so it's worth confirming the current part number and availability with EMB Power before committing a design to a specific unit — New Eagle periodically retires or supersedes individual modules as the range evolves.

It's also worth knowing that New Eagle acquired Pi Innovo's [OpenECU](https://openecu.com/) business in 2026. OpenECU controllers and software are now part of the same exclusive EMB Power UK/EU offering as Raptor, which gives teams a wider choice of hardware tiers — from compact single-purpose controllers up to multi-purpose units — without having to go to a separate supplier.

## Practical Tips for Teams Adopting Raptor DEV

- **Partition Simulink models** using referenced models so multi-ECU designs stay manageable as they grow.
- **Automate verification** with Raptor-Test cycles rather than relying solely on manual bench checks — it catches regressions earlier, when they're cheaper to fix.
- **Keep calibration flexible** by supporting both Raptor-Cal and industry-standard XCP/CCP tools, so the choice isn't locked in early.
- **Use Simulink Projects for version control** so algorithm, generated code and hardware configuration stay traceable across a team.

## Why Engineering Teams Work With EMB Power

EMB Power is [New Eagle's exclusive UK supplier](https://emb-power.com/) of Raptor automotive controls hardware and model-based ECU development software, and now of the OpenECU range as well. That means UK and EU teams get direct access to current Raptor hardware and software licensing, engineering support from people who work with the toolchain daily, and training tailored to Simulink-based development rather than a generic reseller handoff.

## FAQ

### Do I need to rewrite my Simulink model to run on Raptor hardware?

No. Raptor's blocks integrate directly into Simulink, so an existing model typically only needs Raptor-specific I/O and communications blocks added, rather than a rebuild.

### How is calibration handled during development?

Live calibration and datalogging can run through Raptor-Cal, or through industry-standard XCP/CCP-compatible tools if that's what the team already uses.

### Does this scale to full production programmes, or is it just for one-off prototypes?

The same model-based workflow is designed to run from early one-off prototyping through to production-volume deployment, without swapping toolchains partway through.

If you're planning a Raptor-based prototyping programme, or want to know which current Raptor or OpenECU module fits your project, [contact EMB Power](https://emb-power.com/contact) to talk it through with an engineer.

[ECUs](https://blog.emb-power.com/tag/ecus), [Rapid Prototyping](https://blog.emb-power.com/tag/rapid-prototyping)

[facebook-f icon](https://www.facebook.com/embpowerltd) [linkedin-in icon](https://www.linkedin.com/company/emb-power-limited/) [instagram icon](https://www.instagram.com/restomods_uk/)

- [Products](https://www.emb-power.com/all-products)
- [Hardware](https://www.emb-power.com/hardware) 
    - [Controllers](https://www.emb-power.com/controllers)
    - [Displays](https://www.emb-power.com/displays)
    - [Data Loggers](https://www.emb-power.com/data-loggers)
    - [Telematics](https://www.emb-power.com/telematics)
    - [I/O Devices](https://www.emb-power.com/io-devices)
- [Software](https://www.emb-power.com/software)
- [Services](https://www.emb-power.com/services)
- [Resources](https://www.emb-power.com/resources)

---

[![EMB\_Power\_Logo](https://blog.emb-power.com/hs-fs/hubfs/EMB_POWER_logo-16x9-tp-1.png?width=250&height=140&name=EMB_POWER_logo-16x9-tp-1.png "EMB_Power_Logo")](http://www.emb-power.com)

Ash Lea, Alderley Road, Chelford, Macclesfield, SK11 9AP UK

Copyright © 2026, EMB Power Limited

```json
{
  "@context" : "https://schema.org",
  "@type" : "BlogPosting",
  "author" : {
    "@type" : "Person",
    "name" : "EMB Power Team",
    "url" : "https://blog.emb-power.com/author/emb-power-team"
  },
  "dateModified" : "2026-10-07T13:28:13.057Z",
  "datePublished" : "2026-10-07T13:28:13.000Z",
  "headline" : "From Simulink Model to Running ECU: How Raptor DEV Speeds Up Prototyping for UK Controls Teams",
  "mainEntityOfPage" : {
    "@id" : "https://blog.emb-power.com/from-simulink-model-to-running-ecu-how-raptor-dev-speeds-up-prototyping-for-uk-controls-teams",
    "@type" : "WebPage"
  },
  "publisher" : {
    "@type" : "Organization",
    "logo" : {
      "@type" : "ImageObject",
      "url" : "https://blog.emb-power.com/hubfs/EMB_POWER_logo-16x9-tp-1.png"
    },
    "name" : "EMB Power Limited"
  }
}
```