In particular, the HORIZON Scripting/Remote API Toolkit is required if OpenECU builds are to generate Vision strategy files (.vst). 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).Į 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. For further details, please see “Integration notes for third party tools” for a list of known issues.ĭ The OpenECU method of configuring ATI Vision uses standardised ASAP2 files. As such, there are a number of known issues to keep in mind when compiling an OpenECU application using GCC. Dana cannot provide support for issues with encrypted drives.ī Mathworks Simulink Coder includes functionality of RTW and Stateflow Coder.Ĭ OpenECU has only been tested using GCC Compiler version 4.7.3 and is in the beta stage. If using an encrypted drive, be sure that permission settings will allow OpenECU to create files. OpenECU developer software must be able to create files on the host file system. OpenECU developer software may not function correctly on encrypted drives. Windows 10 support will be added in a later release. OpenECU developer software does not support earlier versions of Windows than XP (SP3), does not support Windows Vista or Windows 8. Reprogramming, data logging and calibration toolsĪ OpenECU has been tested to work with Windows XP SP3 and Windows 7 SP1, 32-bit and 64-bit. In summary, the following third party tools are compatible with OpenECU version 2.7.0.: Third party tool GCC compiler (free compiler but with known issues).To compile the generated C code (from either Simulink Coder or Embedded Coder), you will need one of the following compilers: Embedded Coder® (to generate C code from the models), or Real-Time Workshop® Embedded Coder® for versions R2010b or earlier.Under these circumstances you will also need: 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. Simulink Coder generates C code which does not lend itself to efficient repeatable testing. In R2011a and later, Simulink Coder fulfils this function. Stateflow® Coder (to generate C code from the state flow diagrams inside your model) for versions R2010b or earlier.Stateflow® (to develop state flow diagrams inside your model).In addition, if you need to add state diagrams to the model, then you will also need: MATLAB Coder™ for versions R2011a or later (Simulink Coder depends on this).Simulink Coder™ (to generate C code from the models), or Real-Time Workshop® for versions R2010b or earlier.Only one calibration tool is required:įor Simulink® model based development, OpenECU requires (at a minimum) the following MathWorks tools: To program and calibrate an OpenECU with an application, OpenECU integrates with the following calibration tools. Please see the release notes for a list of known issues. As such, there a number of known limitations for compiling an OpenECU application with GCC. GCC support is currently in a beta stage. GCC is an optional component in the OpenECU installation (installed by default). C-APIįor C based development, OpenECU requires (at a minimum) one of the following compiler tools: At the moment, OpenECU is compatible with versions of 64-bit MATLAB starting with 2013b. OpenECU is not compatible with Windows Vista, Windows 8 or earlier versions than Windows XP SP3. OpenECU has been tested to work with Windows XP SP3 and Windows 7 SP1, 32-bit and 64-bit.
0 Comments
Leave a Reply. |
Details
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |