|
Quick Links
OpenECU overview
Hardware Overview
M100
M250
M460
M461
G850
S050
Software Overview
Sim32
C-API 32
C-API 16
Operating systems
Custom Hardware
|
|
The OpenECU Developer Platform Sim32 is a blockset and set of software libraries which enable control algorithms and strategies developed as MATLABTM Simulink/Stateflow models to be quickly created and tested on real OpenECU hardware.
MATLABTM Simulink/Stateflow, produced by The Mathworks Inc., is one of the premier tools for creating rapid prototyping control models. |
|
Development Flow
- The OpenECU Developer Platform Sim32 takes models created using MATLABTM, SimulinkTM, StateflowTM and the Real-Time WorkshopTM along with the WindRiverTM Diab Compiler and builds them into code that can be loaded directly onto an OpenECU module.
- Models are autocoded with all the interfacing to the systems I/O and low level logic handled by the OpenECU platform.
- MATLAB's Simulink graphical interface allows quick implementation from design concepts to working prototypes.
- Models written with OpenECU Developer Platform Sim32 can be built in one key-press using our complete automatic build system.
- This time is better invested in the control strategy itself and the generation of Intellectual Property.
Pi Shurlok has incorporated its extensive knowledge of developing automotive control systems in the design of the OpenECU Developer Platform
Blockset integration
The Model Based Developer Software is installed as a set of Simulink libraries and provides the following functionality:
|
 |
Input blocks:
- analogue
- digital
- frequency
- period
- quadrature
- ...
|
Example: Digital Input blocks are provided to allow the developer to select a hardware pin and read frequency, state, or duty cycle. 
|
Output blocks:
- digital
- PWM
- stepper motor
- constant current
- H-Bridge
- ...
|
Example: Digital Input blocks are provided to allow the developer to select a hardware pin and read frequency, state, or duty cycle. 
|
Driver blocks:
- Send
- Receive
- Use dbc file
- ...
|
For example, Blocks are provided to allow sending or receiving CAN messages 
|
Utility blocks
- Lookup 1d/2d
- Debounce
- ECU reset
- Fault storage
- ...
|
Example: 
|
| Build process
The autocode generation process is invisible to the user. However if you would like to understand how the build process works, the diagram on right shows the code generation and compilation processes.
Build System - Inputs
- Simulink models defining the control strategies
- Data dictionaries defining the key system parameters
Build system - outputs
- A configuration file for the ASAP2/CCP calibration tool
- The Motorola S-record file (containing executable and calibration data)
|
| |