An FMU proxy participant is alternative method for running FMUs. Instead of being run within the System Coupling environment, they run in a separate process that has a separate environment. It allows you to run FMU files that are not capable of running in the current System Coupling co-simulation environment.
This participant type must be selected manually, so use it when the default FMU participant fails. For example, if the FMU uses a Python interpreter it may not run with the default method.
Note:
Not all FMU files can be run with this method as the proxy participant uses a subset of the FMI standard.
This method runs significantly slower than a default FMU participant.
The FMU proxy participant does not support:
Non-real variables: integer, boolean, string, enumeration
Parameters
Initial variable values
Variable bounds
To add participant definitions, use the Add Participant dialog or run the AddParticipant() command for each participant. For FMU Proxy participants:
Set the Input File field or the InputFile argument to the *.fmu file.
Set the Participant Type field or the ParticipantType argument to
FMU-PROXY.
Note: You can use the same *.fmu file multiple times. For example, you might load three instances of it — that is, adding three distinct participants defined by that file.
When the dialog is used or the command is run, the participant definitions are loaded and the data model is populated with information from the *.fmu file.
Example 57: Add an Ansys participant and an FMU Proxy participant in the CLI
>>> AddParticipant(InputFile = 'cfx.scp') >> AddParticipant(InputFile = 'spring.fmu', ParticipantType = 'FMU-PROXY')