Use Scenario B

In this scenario, two RapidPro units form a stack including signal conditioning and power stages, so that complex I/O signals can be acquired and generated independently of the main CPU of the prototyping system.

Intelligent I/O Subsystems for dSPACE Prototyping Systems

Applications such as engine management need to acquire complex I/O signals, for example, for crankshaft and camshaft positions, and to generate complex signals for ignition and injection independently of the RCP system’s main processor and the model’s simulation step size. Offloading specific, time-critical tasks like these to a dedicated microcontroller decisively reduces the main processor’s load. The RapidPro Control Unit variant with MPC565 is used in this scenario as a slave microcontroller to extend existing prototyping systems with additional I/O functionality. The RapidPro Control Unit variant can be used together with the MicroAutoBox or a modular DS1005-based system (with DS4121 ECU Inter-face Board) or can additionally be combined with other RapidPro units.
An integrated Unit Connection Bus (UCB) allows you to connect several RapidPro SC or Power Units directly to the Control Unit without external wiring. Communication between the RapidPro Control Unit and the prototyping system is performed via a high-speed link. A RapidPro Control Unit Blockset for MicroAutoBox and modular DS1005-based systems is available as an I/O Real-Time Interface (RTI) for Simulink. dSPACE‘s ConfigurationDesk^® provides intuitive configuration of the unit and diagnostics handling. In this use scenario, the RapidPro hardware can be used for developing control applications in fields such as engine, transmissions, chassis, body, and drives control.

The RTI RapidPro Control Unit Blockset for MicroAutoBox and DS1005.

RTI RapidPro Control Unit Blockset

In conjunction with the MPC565-based RapidPro Control Unit, a generic Real-Time Interface (RTI) Blockset for Simulink is available for MicroAu-toBox and modular DS1005-based systems. The blockset provides extensive standard I/O functionalities (PWM, bit I/O, A/D) including incremental encoder interface and stepper motor control, as well as diagnostic functionalities and special functionalities for engine, chassis and drives control. Examples:

• Crankshaft signal measurement
• Engine speed and status
• Camshaft signal measurement
• Injection and ignition pulse generation
• Angle-sychronized task triggers
• Reading diagnostic data of modules
• Checking the status of a carrier board

Functionalities can be combined with each other in realtime applications, e.g., drives and engine functionalities.
When combining the MPC565-based RapidPro Control Unit and MicroAutoBox or the modular DS1005-based system, you gain additional functionalities for engine control compared to using the MicroAutoBox on its own:

MicroAutoBox plus RapidPro Control Unit
Topic	Examples of Extended Functionality
Crankshaft control	Crankshaft signals with up to 3600 pulses per wheel with or without gaps
Camshaft control	Support of virtually every type of camshaft wheel Phase measurement of camshaft position Up to 4 camshaft wheels at a time
Injection control	Generation of boost-and-hold pulse patterns Up to 15 injection pulses for one injection cycle
Common	Up to 12 channels for injection plus 12 channels for ignition simultaneously High engine angle resolution of 0.1° 4 periodical and 16 absolute angle-based interrupts per engine cycle