For dialog-based configuration of bypass applications and real-time ECU access.
Highlights:
- ECU access via CCP, XCP (CAN, Ethernet, FlexRay), on-chip debug ports, and DPMEM PODs
- Integrated A2L file browser for selecting ECU variables
- Failure checking and data consistency mechanisms for bypass communication
- Powerful API for configuring ECU interface and bypass blocks via scripts
Application Areas
For developing ECU functions by means of the external bypass approach, it is usually necessary to configure the bypass interface in the modelling environment and to change the input and output signals of the bypass model without ECU code modifications. The RTI Bypass Blockset provides a generic user interface for this purpose, with the same look and feel no matter what ECU interface is actually used for bypassing. The Blockset allows flexible selection of functions to be bypassed in the ECU code (bypass hooks) and variables to be transferred without changing the ECU code itself. In addition, with ECU testing and hardware-in-the-loop simulation, ECU-internal data are captured in real-time for validation purposes or for controlling test sequences.
Key Benefits
The RTI Bypass Blockset allows you to use dedicated Simulink® blocks and user interfaces to set up the bypass application in the modeling environment. ECU-specific information, such as on the bypass interface, the bypass hooks implemented in the ECU code, and the available variables, is automatically adopted from the ECU description file (A2L file) and control engineers can fully concentrate on function design. The blockset allows you to 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, the DCI-GSI1, and DPMEM PODs. When you use the dSPACE calibration and bypassing service or the dSPACE XCP service, dedicated mechanisms are provided to monitor the bypass communication, detect errors, and ensure consistent data transmission. 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 having to modify and recompile the Simulink model itself.
Import of ASAM-MCD 2MC Files
An ASAM-MCD 2MC (ASAP2) variable description file can be easily imported as a database. An intuitive variable browser facilitates the handling of large description files by search options and hierarchical representation of variables. The variable names are mapped to the respective addresses on the ECU. The blockset allows you to access ECU variables via their names and automatically performs conversion between ECU hex and the physical representation on the dSPACE system.