Functional Mock-up Interface: Difference between revisions

Revision as of 16:54, 26 July 2011

Revision as of 17:24, 26 July 2011

Line 9:

| abbreviation = FMI

| ___domain = [[Computer simulation]]

| license = [[Creative Commons licenses|CC_BY_SA 3.0]]

| website = [http://functional-mockup-interface.org/ FMI website]

}}

Line 20:

To create FMI, a large number of software companies and research centers have worked in a cooperation project established through a European consortium that is conducted by [[Dassault_Systèmes|Dassault Systèmes]] under the name of '''MODELISAR'''.

The [http://www.itea2.org/public/project_leaflets/MODELISAR_profile_oct-08.pdf '''MODELISAR'''] project has been initialized in 2008 to define the FMI specifications, deliver technology studies, and prove the FMI concepts through Use Cases elaborated by the consortium partners.

The development of the FMI specifications was coordinated by [[Daimler AG]].

The [http://www.modelisar.com/fmi.html FMI specifications] are distributed under open source licence.:

* Specifications are licensed under CC-BY-SA (Creative Commons Attribution-Sharealike 3.0 Unported) [[Creative Commons licenses|CC_BY_SA 3.0]]

* The C-header and XML-schema files that accompany this document are available under the [http://www.opensource.org/licenses/bsd-license.html BSD] license with the extension that modifications must be also provided under the BSD license.

The four required FMI aspects of creating models capable of being assembled have been covered in in Modelisar project:

Line 30 ⟶ 32:

* FMI for Co Simulation,

* FMI for Applications,

* FMI for [[Product life cycle management (marketing)|PLM]] (integration of models and related data in the Product Life Cycle Management).

In practice the FMI implementation by a software modeling tool enables the creation of a simulation model that can be interconnected or the creation of a software library called '''FMU (Functional Mock-up Unit)'''.

<ref name="modelica_Jan10">{{cite web

Line 41 ⟶ 44:

| accessdate=2011-012-22}}</ref>

== The FMI approach ==

FMI has two objectives<ref>{{cite web

The FMI typical approach is described in the following stages:

| url=http://modelisar.org/fmi.html

* A modeling environment describes a product sub system by differential, algebraic and discrete equations with time, state and step-events. These models can be large for usage in offline or online simulation or can be used in embedded control systems;

| title=FMI

* As an alternative, an engineering tool defines the controller code for controlling a vehicle system

| publisher=modelisar.org

* Such tools generate and export the component in a FMU (Functional Mock-up Unit);

| accessdate=2011-01-22}}</ref>:

* FMU can then be imported in another environment to be executed

* A modeling environment can export a model composed of [[C (programming language)]] code packaged with an XML definition documenting the model. This XML definition is for a model is called FMU (Functional Mock-up Unit)

* Several modelsFMUs can communicate– by this way – cooperate at runtime inthrough a co-simulation environment by, usingthanks to the FMI definitions of their interfaces.

==Architecture==

Line 98 ⟶ 101:

* S-Functions are not suited for [[embedded system]]s, due to the memory overhead of S-Functions

==SupportTools support==

As of JanuaryJuly 2011, FMI is supported on the following simulation frameworks<ref name="modelica_Jan10"/>:

See full list and details in [http://www.modelisar.com/tools.html FMI web pages].

* [[AMESim]] (import and export)

* AMESim - Modelica environment from LMS-Imagine

* [[Dymola]] (import and export)

* ASIM - AUTOSAR Builder from Dassault Systèmes

* [[SimulationX]] (import and export)

* Atego Ace - Co-simulation environment with AUTOSAR and HIL support

* [[SIMPACK]] (import only)

* CATIA V6R2012 - Environment for Product Design and Innovation, including systems engineering tools based on Modelica, by Dassault Systèmes

* Control Build - 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

* FMU SDK - FMU Software Development Kit from QTronic

* IPG CarMaker - via Modeling and Co-Simulation environment by Modelon

* JModelica.org - Open source Modelica environment from Modelon

* MATLAB - via Modelica Physical Modeling Toolbox from Modelon

* MPMT - Modelica Physical Modeling Toolbox from Modelon

* MWorks 2.5 - Modelica environment from Suzhou Tongyuan

* NI VeriStand - Real-Time Testing and Simulation Software from National Instruments

* NI LabVIEW - Graphical programming environment for measurement, test, and control systems from National Instruments

* OpenModelica - Open source Modelica environment from OSMC

* Python - via JModelica.org from Modelon

* Silver 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 Modelica Physical Modeling Toolbox from Modelon

* TISC - Co-simulation environment from TLK-Thermo

* Vertex - Modelica environment from deltatheta

== Application scenarios ==

''To be completed''

==See also==