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

Bypassing – Externally or Directly on the ECU

New Functions for Existing Controllers

Unlike fullpass approaches, where the ECU is completely replaced by the prototyping system, bypassing is used to develop only individual parts of the ECU software from scratch or modify them, e.g., single control functions. These parts run either on a prototyping system that is connected to an existing ECU (external bypassing) or directly on the ECU (on-target bypassing). dSPACE offers a comprehensive range of hardware and software that help prepare an existing ECU for bypassing and that support the different bypass methods.

Fast and Flexible Bypass Integration

To use external and on-target bypassing, the existing ECU code has to be prepared. With service-based bypassing as supported by dSPACE, virtually any number of functions in the ECU code can be prepared for bypassing by integrating service calls (bypass hooks). These service calls can be flexibly used in the MATLAB®/Simulink® modeling environment for the synchronous measurement and calibration of ECU variables and parameters, for ECU flash programming, and for bypassing. To help you prepare the ECU code for bypassing, dSPACE offers the ECU Interface Manager with the Binary Code Management Module as an easy-to-use tool with an intuitive, graphical view on a given ECU code structure. It gives you a convenient and flexible way to implement bypass services directly and automatically in the ECU HEX code without requiring the ECU supplier to modify the source code or running through the whole production development process and tooling. This saves time and money, and increases flexibility. You can also implement services for bypassing manually by using the ECU source code. dSPACE offers its generically designed bypass services and service calls as C sources, so they can be compiled and linked to the ECU code. With the RTI Bypass Blockset (part of the ECU Interface Base Package) dSPACE provides a convenient, model-based access to the service calls from within Simulink to implement a new bypass function. 

External Bypassing

This bypass method is an efficient way to develop new control functions and optimize existing controller strategies. ‘External’ means that a dedicated RCP system is attached to the ECU to execute a new control function f(x)’ synchronously to the original code running on the target ECU. Since the RCP systems have almost no resource constraints with regard to available RAM, ROM (flash) as well as processor performance, and provide additional I/O channels, external function bypassing allows even complex Simulink® models to be executed as bypass functions. Real-time behavior is ensured by specific synchronization mechanisms of the ECU interface.  

Example of an external bypassing scenario with dSPACE tools for a combustion engine.

In case of a vehicle-in-the-loop simulation where an ECU is tested in a real vehicle but under (partly) virtual conditions (e.g., virtual traffic or camera object lists), the same method allows you to simulate a virtual environment on a dSPACE real-time system that can be fed into the ECU in real time (external environment bypassing).   

dSPACE supports numerous interfaces for connecting the prototyping system to the ECU. In case of standard CAN, CAN FD or Ethernet interfaces on the ECU, a direct access via the XCP protocol without further hardware is possible. If such bus interfaces are not available to be used for bypassing, and high real-time performance with a high bandwidth are required, you can use the Generic Serial Interface (DCI-GSI2), which is connected to the ECU’s on-chip debug interface, such as NEXUS or DAP. For cases in which using such an interface is not possible either, dSPACE provides a service for an ECU-specific plug-on device (POD).

On-Target Bypassing

If an ECU provides all relevant I/O interfaces and sufficient free resources, function development can be performed directly on the ECU. This reduces development costs, because no additional hardware and wiring harness is necessary. The new functions are executed directly on the target hardware, which means there are no communication latencies to external development hardware, so the functions can be integrated into very fast control loops. Using dSPACE TargetLink as a code generator allows for a seamless transition to production and a more efficient use of the limited ECU resources. In this context, the resources required to run the function on the final production ECU can be determined very early on. Furthermore, using the certified TargetLink code generator together with an ECU that was already cleared for production can improve the overall operational safety for the prototyping phase, e.g., during fleet tests.  

Example of an on-target bypassing scenario with dSPACE tools for an efficient use of the limited ECU resources.

More Information Product Information Video Literature