Operating system

OpenECU has been tested to work with Windows XP SP3 and Windows 7 SP1, 32-bit and 64-bit. OpenECU is not compatible with Windows Vista, Windows 8 or earlier versions than Windows XP SP3. At the moment, OpenECU is compatible with versions of 64-bit MATLAB starting with 2013b.

C-API

For C based development, OpenECU requires (at a minimum) one of the following compiler tools:

• Wind River® Diab™ compiler
• GCC compiler

GCC is an optional component in the OpenECU installation (installed by default). GCC support is currently in a beta stage. As such, there a number of known limitations for compiling an OpenECU application with GCC. Please see the release notes for a list of known issues.

To program and calibrate an OpenECU with an application, OpenECU integrates with the following calibration tools. Only one calibration tool is required:

• OpenECU Calibrator
• ATI VISION®
• ETAS INCA®
• Vector CANape®

Sim-API

For Simulink® model based development, OpenECU requires (at a minimum) the following MathWorks tools:

• MATLAB® (base product)
• Simulink® (to develop the models)
• Simulink Coder™ (to generate C code from the models), or Real-Time Workshop® for versions R2010b or earlier
• MATLAB Coder™ for versions R2011a or later (Simulink Coder depends on this)

In addition, if you need to add state diagrams to the model, then you will also need:

• Stateflow® (to develop state flow diagrams inside your model)
• Stateflow® Coder (to generate C code from the state flow diagrams inside your model) for versions R2010b or earlier. In R2011a and later, Simulink Coder fulfils this function.

Simulink Coder generates C code which does not lend itself to efficient repeatable testing. When creating a production version of your product, you may need better control of the structure of the C code generated from the model to reduce the cost of testing the C code against any industry standards. Under these circumstances you will also need:

• Embedded Coder® (to generate C code from the models), or Real-Time Workshop® Embedded Coder® for versions R2010b or earlier

To compile the generated C code (from either Simulink Coder or Embedded Coder), you will need one of the following compilers:

• Wind River® Diab™ compiler
• GCC compiler (free compiler but with known issues)

To program and calibrate an OpenECU with an application, OpenECU integrates with the following calibration tools. Only one calibration tool is required:

• OpenECU Calibrator
• ATI VISION®
• ETAS INCA®
• Vector CANape®

Compatibility

In summary, the following third party tools are compatible with OpenECU version 2.7.0.:

^a OpenECU has been tested to work with Windows XP SP3 and Windows 7 SP1, 32-bit and 64-bit. OpenECU developer software does not support earlier versions of Windows than XP (SP3), does not support Windows Vista or Windows 8. Windows 10 support will be added in a later release.
OpenECU developer software may not function correctly on encrypted drives. OpenECU developer software must be able to create files on the host file system. If using an encrypted drive, be sure that permission settings will allow OpenECU to create files. Dana cannot provide support for issues with encrypted drives.
^b Mathworks Simulink Coder includes functionality of RTW and Stateflow Coder.
^c OpenECU has only been tested using GCC Compiler version 4.7.3 and is in the beta stage. As such, there are a number of known issues to keep in mind when compiling an OpenECU application using GCC. For further details, please see “Integration notes for third party tools” for a list of known issues.
^d The OpenECU method of configuring ATI Vision uses standardised ASAP2 files. As a result, all future versions of Vision are expected to be backwardly compatible (e.g., version 3.7 and version 4.0 are known to be compatible).
^e The following Vision toolkits are typically used when working with OpenECU: Data Acquisition Toolkit, Calibration Toolkit, Universal ECU Interface Standard Toolkit, APOLLO Data Analysis Toolkit, CAN Interface Toolkit and HORIZON Scripting/Remote API Toolkit. In particular, the HORIZON Scripting/Remote API Toolkit is required if OpenECU builds are to generate Vision strategy files (.vst).

Some third party tools have been marked deprecated and support for these tools will be removed in a future release of OpenECU.