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

Real-Time Interface Bypass Blockset

Dialog-based configuration of bypass applications and real-time ECU access
  • ECU access via CCP, XCP (CAN, Ethernet, FlexRay), on-chip debug ports, and DPMEM PODs
  • Internal bypassing and on-target prototyping
  • Failure checking and data consistency mechanisms for bypass communication
  • Integrated A2L file browser for selecting ECU variables
Application Areas
To develop ECU functions by means of the bypass approach, it is usually necessary to configure the bypass interface in the modeling environment and to change the input and output signals of the bypass model without modifying the ECU code. The RTI Bypass Blockset provides a generic user interface for this purpose, with the same look and feel no matter what bypass method is applied (internal or external) or what ECU interface is actually used for external bypassing. You can flexibly select the functions to be bypassed in the ECU code (bypass hooks) and the variables to be transferred, without changing the ECU code itself. The Internal Bypass Plug-In for the RTI Bypass Blockset is used to generate target code for the internal bypass function and merge it into the ECU image file. This approach utilizes the ECU’s free RAM and flash resources, allowing new functions to be prototyped and tested directly on the target ECU.
In addition, with ECU testing and hardware-in-the-loop simulation, ECU-internal data is captured in real-time for validation purposes or for controlling test sequences.
 
Key Benefits
The RTI Bypass Blockset provides dedicated Simulink® blocks and user interfaces for you to set up the bypass application in the modeling environment. ECU-specific information on the bypass interface, the bypass hooks implemented in the ECU code, the available variables etc., is automatically taken from the ECU description file (A2L file), so control engineers can fully concentrate on function design. The blockset lets you select model inputs and outputs flexibly without ECU code modification. A variety of ECU interfaces are supported, such as CCP, XCP on CAN, XCP on Ethernet (UDP/IP), XCP on FlexRay, DCI-GSI, and 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. This makes it easy to change from internal to external bypassing and vice versa without having to change the Simulink model.
A powerful API lets you configure RTI bypass blocks automatically by means of scripts, for example, to update the Simulink model with a new A2L file. It is even possible to change the ECU variables to be read or written by the real-time platform during simulation without modifying or recompiling the Simulink model itself.