Functional Mockup Interface - Versionsgeschichte

Cg: /* Medium Level */

2023-06-22T01:18:36Z

Medium Level

← Nächstältere Version		Version vom 22. Juni 2023, 01:18 Uhr
Zeile 42:		Zeile 42:
	==== Simulation ====		==== Simulation ====

	=== ~~Medium~~ Level ===		=== High Level Usage ===

	==== Generate ~~Accessors~~ ====		==== Generate FMU Actions ====
			This is invoked via the "''Extra''"- "''Generate''" menu of the attachment editor's own toolbar (i.e. this is not the main toolbar, but the editor's toolbar at the right).

			It reads a modelDescription and generates a separate library containing all required actions to load, instantiate and execute an FMU within any activity diagram.

			This is "work in progress".

	== Future ==		== Future ==

Cg: /* Future */

2023-06-19T09:46:21Z

Future

← Nächstältere Version		Version vom 19. Juni 2023, 09:46 Uhr
Zeile 49:		Zeile 49:

	This is a first version of the FMU support inside expecco,		This is a first version of the FMU support inside expecco,
	providing mechanisms to execute FMU's an to connect I/O variables inside a single running expecco application.		providing mechanisms to execute FMU's and to connect I/O variables inside a single running expecco application.

	=== Orchestration ===		=== Orchestration ===

Cg: /* Introduction */

2023-06-19T09:45:21Z

Introduction

← Nächstältere Version		Version vom 19. Juni 2023, 09:45 Uhr
Zeile 2:		Zeile 2:

	== Introduction ==		== Introduction ==
	Functional Mockup Units are modules to simulate physical and non-physical components in an orchestrated setup. Each such module implements a well defined interface ("FMI" for ''Functional Mockup Interface'') and is packaged in a standardized container (actually a zip container), ~~which~~ contains both the executable code (as binary and optional source) and a meta description, which describes the input/output parameters and other simulation details.		Functional Mockup Units are modules to simulate physical and non-physical components in an orchestrated setup. Each such module implements a well defined interface ("FMI" for ''Functional Mockup Interface'') and is packaged in a standardized container (actually a zip container). This contains both the executable code (as binary and optional source) and a meta description, which describes the input/output parameters and other simulation details.

	The motivation behind is that manufacturers of hard- and software components can provide such simulation components for their real components, and that a project engineer can use those to simulate the system in an early planing phase. This includes both fully simulated systems, but also in-the-loop setups, where simulated parts interact with real components.		The motivation behind is that manufacturers of hard- and software components can provide such simulation components for their real components, and that a project engineer can use those to simulate the system in an early planing phase. This includes both fully simulated systems, but also in-the-loop setups, where simulated parts interact with real components.

Cg: /* FMUs in Expecco */

2023-06-12T16:32:10Z

FMUs in Expecco

← Nächstältere Version		Version vom 12. Juni 2023, 16:32 Uhr
Zeile 9:		Zeile 9:
	Expecco can load binary FMUs (i.e. ".fmu" files) and execute them within an automation or test scenario.		Expecco can load binary FMUs (i.e. ".fmu" files) and execute them within an automation or test scenario.
	The functionality is provided by the CBridge and an API is provided by the "FMU Interface Library".		The functionality is provided by the CBridge and an API is provided by the "FMU Interface Library".
			Currently, the FMI2 API is supported; FMI3 is work in progress.

	=== Low Level Actions ===		=== Low Level Actions ===

Cg: /* Write Value */

2023-06-12T16:14:28Z

Write Value

← Nächstältere Version		Version vom 12. Juni 2023, 16:14 Uhr
Zeile 34:		Zeile 34:

	==== Write Value ====		==== Write Value ====

			Similar to the above, both setters by index and setters by name are provided.

			See an example in the "FMU [Set Value by Name]" action's Test/Demo page.

	==== Simulation ====		==== Simulation ====

Cg: /* Read Value */

2023-06-12T16:13:39Z

Read Value

← Nächstältere Version		Version vom 12. Juni 2023, 16:13 Uhr
Zeile 26:		Zeile 26:

	==== Read Value ====		==== Read Value ====

			Low level "FMU [Get XXX Value]" call directly into the FMU's "fmi2GetXXXValue()" functions, to retrieve Booleans, Integers, Reals or Strings by an integer variable-reference index.

			Medium level "FMU [Get Value by Name]" use the model description to determine the type and reference index. So variables can be retrieved more conveniently by name.

			See an example in the "FMU [Get Value by Name]" action's Test/Demo page.

	==== Write Value ====		==== Write Value ====
	==== Simulation ====		==== Simulation ====

Cg: /* Future */

2023-06-12T16:08:44Z

Future

← Nächstältere Version		Version vom 12. Juni 2023, 16:08 Uhr
Zeile 33:		Zeile 33:

	== Future ==		== Future ==


			This is a first version of the FMU support inside expecco,
			providing mechanisms to execute FMU's an to connect I/O variables inside a single running expecco application.

			=== Orchestration ===

			There exists (currently) no orchestration or interprocess communication mechanisms to distribute FMUs among remote machines. This will be added in a future version. However, by providing a forwarding mechanism, such inter-FMU communication can be implemented even on top of the current system.

	=== Expecco as FMU ===		=== Expecco as FMU ===
			In development are mechanisms to allow for an FMU to be implemented as an activity (compound action), and allow for an orchestrator to integrate this transparently into a network of communicating FMUs.

Cg: /* Low Level Actions */

2023-06-12T16:00:08Z

Low Level Actions

← Nächstältere Version		Version vom 12. Juni 2023, 16:00 Uhr
Zeile 16:		Zeile 16:
	See an example in the "FMU [Load]" action's Test/Demo page.		See an example in the "FMU [Load]" action's Test/Demo page.

	~~======~~ Possible Errors ~~======~~		* Possible Errors
	'Failed to Extract binaries/xxx'		:'Failed to Extract binaries/xxx'
	~~<br>~~happens if the FMU container does not contain binaries for your architecture (for example, when executing on a MAC, but the FMU only contains compiled code for a windows machine). Either ask the developer of the FMU to provide such a version, or else execute the CBridge on such a machine (which could be a virtual machine).		:happens if the FMU container does not contain binaries for your architecture (for example, when executing on a MAC, but the FMU only contains compiled code for a windows machine). Either ask the developer of the FMU to provide such a version, or else execute the CBridge on such a machine (which could be a virtual machine).

	==== Instantiate FMU ====		==== Instantiate FMU ====

Cg: /* Load FMU */

2023-06-12T15:58:11Z

Load FMU

← Nächstältere Version		Version vom 12. Juni 2023, 15:58 Uhr
Zeile 15:		Zeile 15:

	See an example in the "FMU [Load]" action's Test/Demo page.		See an example in the "FMU [Load]" action's Test/Demo page.

			====== Possible Errors ======
			'Failed to Extract binaries/xxx'
			<br>happens if the FMU container does not contain binaries for your architecture (for example, when executing on a MAC, but the FMU only contains compiled code for a windows machine). Either ask the developer of the FMU to provide such a version, or else execute the CBridge on such a machine (which could be a virtual machine).

	==== Instantiate FMU ====		==== Instantiate FMU ====

Cg: /* Instantiate FMU */

2023-06-12T15:47:44Z

Instantiate FMU

← Nächstältere Version		Version vom 12. Juni 2023, 15:47 Uhr
Zeile 17:		Zeile 17:

	==== Instantiate FMU ====		==== Instantiate FMU ====
	The "FMU [Instantiate]" action takes as input an FMU-Identifier as generated by "FMU [Load]" and tells the CBridge to perform the instantiation, eventually leading to the FMU's "fmi2Instantiate()" function to be called.<br>The action generates a Component-identifier at its output which is needed later to interact with the unit.<br>~~Notice, that in~~ principle, an FMU can be instantiated multiple times.		The "FMU [Instantiate]" action takes as input an FMU-Identifier as generated by "FMU [Load]" and tells the CBridge to perform the instantiation, eventually leading to the FMU's "fmi2Instantiate()" function to be called.<br>The action generates a Component-identifier at its output which is needed later to interact with the unit.<br>In principle, an FMU can be instantiated multiple times.

	See an example in the "FMU [Instantiate]" action's Test/Demo page.		See an example in the "FMU [Instantiate]" action's Test/Demo page.