For a better experience on, enable JavaScript in your browser. Thank you!

Real-Time Interface Bypass Blockset

ECU interfacing for rapid control prototyping and intrusive testing of existing ECU software

The dSPACE tool chain for bypassing and ECU interfacing, consisting of the RTI Bypass Blockset and the ECU Interface Manager, can be used for applications in rapid control prototyping, hardware-in-the-loop (HIL) testing as well as for white-box testing of existing ECU software.

Application Areas

When only some parts of an existing ECU software need to be optimized or enhanced, bypassing is a powerful and proven method for rapid control prototyping. It can be employed when no Simulink® models of the original control algorithms are available, or when there is no access to the source code of ECU software. MATLAB®/Simulink models can be used to bypass and, as a consequence, replace original ECU functions.

The dSPACE tool chain for bypassing and ECU interfacing also makes test case development considerably easier. You can use the tool chain to apply test stimuli in real time that are triggered by ECU-internal events. In addition, ECU-internal memory can be read and written in real time. ECU functions can be stimulated with specific, reproducible test data, which makes it easier to cover test cases with a complex setup. External sensors or actuators in the ECU that are difficult to stimulate or hard to access externally can be bypassed in order to directly stimulate the ECU functions under test. Thus, the test coverage of ECU software can be enhanced considerably.



As the RTI Bypass Blockset hides ECU-specific information on the bypass interface, control and test engineers can completely concentrate on function design and test case development. Based on the ECU description file (A2L file), users can flexibly select model inputs and outputs as well as triggers without modifying the ECU software.

A variety of ECU interfaces are supported, such as CCP, XCP on CAN, XCP on Ethernet, XCP on FlexRay, and dedicated ECU interfaces such as dSPACE DCI-GSIs, or DPMEM PODs. If you use the dSPACE bypassing services, dedicated mechanisms ensure data consistency and safe operation.
The RTI Bypass Blockset is part of a complete tool chain for service-based bypassing that supports different bypass methods and different platforms for model execution:
  • External bypassing on dedicated RCP systems
  • Internal bypassing directly on the target ECU
  • Virtual bypassing of virtual ECUs in a PC-based simulation or on MicroAutoBox  II without using a physical target ECU at all
The RTI Bypass Blockset supports all bypass methods and all ECU interfaces with the same intuitive look and feel. It is easy to switch between the different bypass methods and platforms, because no changes to the Simulink model are required. The blockset allows developers to reuse legacy functions, only available as C source code, in their Simulink models. Furthermore, a powerful automation API facilitates the integration of the RTI Bypass Blockset into customer-specific development tool chains.

Functionality Description
Selecting ECU functions and variables
  • Flexibly mapping new Simulink models to ECU functions to trigger their execution
  • Selecting ECU variables via an integrated A2L file browser or by defining new ones via dialogs
Measurement and calibration
  • Uploading and downloading ECU variables including data vectors
  • Real-time data acquisition and data stimulation of ECU variables including data vectors
  • Measuring of internal events and execution times of the ECU
Configuration of bypass interfaces and services
  • Switching between bypass execution platforms without changes to the Simulink model
  • Specifying several variable description files (A2L files) for the same bypass interface
  • Model-based configuration of bypass services and interfaces based on A2L files
Dynamic model configuration
  • Switching on/off the bypass function during run-time
  • Enabling and disabling service calls in the ECU code
  • Deactivating read/write access to selected ECU variables during run time without recompiling the model
  • Changing the ECU addresses, data types and value conversion methods of variables dynamically without modifying or recompiling the Simulink model
Interrupt configuration
  • Subinterrupt number assignment
Tool automation
  • Automation API for configuring bypass blocks via scripts
External bypassing Supported ECU interfaces and standards for external bypassing
  • XCP on CAN/CAN FD, XCP on Ethernet (UDP/IP), XCP on FlexRay
  • CCP (CAN Calibration Protocol)
  • Seed & key access to ECU for XCP and CCP
  • Dual-port memory (DPMEM)
Supported bypass services
  • dSPACE Calibration and Bypassing Service
  • dSPACE XCP Service for external bypassing via CAN, FlexReay and Ethernet buses
  • Third-party XCP services for measurement and calibration
  • Configurable failure checking and double buffer mechanism
  • Configurable fallback strategy when the connection between the RCP system and ECU is interrupted
XCP-related options
  • Switching calibration pages via XCP
  • XCP on CAN gateway functionality for arbitrated access to the ECU via multiple tools
Internal bypassing Microcontroller support
  • Supported microcontroller families:
  • Freescale MPC55xx, MPC56xx, and MPC57xx
  • ST Microelectronics SPC56 and SPC 57
  • Infineon Tricore incl. AURIX
  • Renesas V850 and RH850 Support of whole microcontroller families; no ECU-specific licenses required.
Reuse of existing software functions
  • Integrating functions that are available as C source code into the Simulink model
  • Calling ECU-internal functions from the Simulink model
Supported bypass services
  • dSPACE Internal Bypassing Service
Virtual bypassing Supported bypass services
  • dSPACE Bypassing Service integrated in VEOS® and MicroAutoBox II

Real-Time Interface (RTI) Automatic implementation of MATLAB®/Simulink®/Stateflow® models on dSPACE hardware Compiler The compilers are automatically invoked in the code generation phase dSPACE ECU Flash Programming Tool ECU flash programming via calibration interfaces dSPACE XCP Service The dSPACE XCP on CAN service is designed for various use cases such as measuring ECU variables, calibration, and ECU flash programming. dSPACE Calibration and Bypassing Service The dSPACE Calibration and Bypassing Service can be used for measurement, calibration, bypassing, and flash programming. dSPACE Internal Bypassing Service ECU service for internal bypassing and on-target prototyping ECU Interface Manager The ECU Interface Manager is an easy-to-use tool for quickly integrating bypass services and hooks directly into the ECU software. DS1005 PPC Board The DS1005 PPC Board is ideal for computing models with high sampling rates and high I/O requirements, and for use in dSPACE AutoBox. DS1006 Processor Board The DS1006 Processor Board is ideal for computing very complex, processing-intensive models, and for use in laboratories. DS1007 PPC Processor Board The DS1007 processor board provides high computing power combined with fast I/O access. Additional I/O Solutions Solutions for I/O and busses not covered by our standard boards DS2211 HIL I/O Board The DS2211 HIL I/O Board is the central I/O board for HIL simulations, especially in the field of engine simulation and vehicle dynamics simulation. It combines a variety of typical HIL I/O signals on one board. DS4121 ECU Interface Board The DS4121 connects an electronic control unit (ECU) and a dSPACE modular system, for example for bypassing tasks. DS4505 Interface Board The DS4505 Interface Board connects a dSPACE system with modular hardware to a FlexRay and/or a CAN FD communication system. Generic Serial Interfaces DCI-GSIs Generic serial interfaces for function bypassing, measurement, ECU calibration and flash programming. MicroAutoBox Hardware Compact, stand-alone prototyping unit with real-time hardware, I/O, and signal conditioning
Related Topics