Functional Mock-up Interface
The Functional Mock -up Interface ( FMI or ) defines a standardized interface, with the help of various simulation software can be coupled.
Description
The idea behind FMI, is the following: If the real product is made up of a variety of components that interact in complex ways and are controlled by a complex set of physical laws, then it should also be possible to create a virtual product consisting of a number of different physical (software ) models. An example model based on a vehicle might look like this:
- A software provides the motor
- B Software provides the transmission
- Software C provides the control elements
- D software provides ...
By FMI, these models of different software can easily connect and put together to form a complete model.
To create the FMI standards has resulted in a cooperation project in the framework of a European consortium, which was conducted by Dassault Systèmes under the name MODELISAR, worked a large number of software companies and research centers. The MODELISAR project began in 2008 with the definition of FMI specifications, delivered technology studies, the FMI - concept demonstrated by the use cases which were developed by consortium partners, and allowed for tool vendors to create advanced prototypes or in some cases even marketable products.
The four aspects necessary for creating FMI -compatible models have been defined in Modelisar project as follows:
- FMI for model exchange,
- FMI for co - simulation,
- FMI for applications,
- FMI for PLM ( integration of models and the associated data in product lifecycle management).
In practice, the implementation of FMI allows using a software modeling tools to create simulation models which can be coupled together. Another possibility is the creation of a software library called FMU (Functional Mock -up Unit).
License
The FMI specifications are provided as open source licenses:
- The specifications are licensed under CC -BY -SA (Creative Commons Attribution- Share Alike 3.0 Unported )
- The C header and XML schema files are available under the BSD license.
Architecture
Each FMU model ( FMU = functional mock -up unit) is provided as a zip file with the extension " fmu. " Available that includes the following. :
- An XML file that describes, among other things, the definitions of variables, which are used by the FMU;
- All formulas that are used in a model (defined as C functions);
- Optional additional data such as parameter tables, the user interface, documentation, required by the model, etc.
Example
Here is an example of an FMI Model Description in Modelica:
< fmiModelDescription
fmiVersion = " 1.0"
model name = " ModelicaExample "
model identifier = " ModelicaExample_Friction "
...
FMI is supported by the following software:
- AMESim - simulation software for the modeling and analysis of multi-domain system from LMS International
- ASIM - AUTOSAR Builder from Dassault Systèmes
- Adams - High-end multi- body dynamics simulation software from MSC Software
- Atego Ace - Co - simulation environment with AUTOSAR and HIL support
- CATIA V6R2012 - Environment for Product Design and Innovation, including systems engineering tools based on Modelica, by Dassault Systèmes
- Cybernetica CENIT - Industrial product for nonlinear model predictive control ( NMPC ) from Cybernetica
- Cybernetica ModelFit - Software for model verification, state and parameter estimation, using logged process data. by Cybernetica
- ControlBuild - Environment for IEC 61131-3 control applications from Dassault Systèmes
- CosiMate - Co - simulation Environment from ChiasTek
- DSHplus - Fluid power simulation software from FLUIDON
- Dymola 7.4 - Modelica environment from Dassault Systèmes
- FMI add-in for Excel - Batch simulation of FMUs in Microsoft Excel
- FMU compliance checker - Software for verifying FMI standard compliance of FMUs
- FMI Library - C library for importing FMUs in custom applications
- FMU Trust Centre - cryptographic protection and signature of models including PLM Their safe storage; secure authentication and authorization for protected ( co - ) simulation
- FMU SDK - Software Development Kit from FMU QTronic
- GT- SUITE - Multi- Physics Simulation Platform for Powertrain and Vehicle Systems
- Hopsan - Distributed system simulation tool using the TLM method
- Independent ICOS co-simulation - independent co - simulation environment from Virtual Vehicle Research Center
- IPG CarMaker - via Modeling and co-simulation environment by Modelon
- JModelica.org - Open source Modelica environmentsfrom Modelon
- MapleSim - via the MapleSim Connector for FMI from Maplesoft
- MATLAB - via FMI Toolbox from Modelon
- OPTIMICA Studio - Modelica environmentsfrom Modelon
- MWorks 2.5 - Modelica environment from Suzhou Tongyuan
- NI VeriStand - Real-Time Testing and Simulation Software from National Instruments
- LabVIEW - graphical programming environment for measurement, test, and control systems from National Instruments
- OpenModelica - Open source Modelica environment from OSMC
- Python - via PyFMI from Modelon, also available as part of JModelica.org
- Silverlight 2.0 - Virtual integration platform for software in the loop from QTronic
- SIMPACK 9 - High-end multi -body simulation software from SIMPACK AG
- SimulationX 3.4 - Modelica environment from ITI
- Simulink - via Dymola 7.4 using Real-Time Workshop
- Simulink - via @ Source
- Simulink - via FMI Toolbox from Modelon
- TISC - Co - simulation environments-from TLK- Thermo
- TWT Co - simulation Framework - Communication layer tool to Flexibly plug together models for performing a co - simulation; front - end for set -up, monitoring and post-processing included
- TWT Matlab / Simulink FMU Interface - FMI -compatible plug-and -play interface to Matlab / Simulink, available as integrated in block
- Vertex - Modelica environmentsfrom Delta Theta
- Virtual.Lab Motion - Virtual.Lab Motion is a high end multi- body software from LMS International
- XMOD - Heterogeneous model integration environment and virtual instrumentation and laboratory experimentation from IFPEN distributed by D2T.