SIMULIA Co-Simulation Engine FMU Execution

Any number of Functional Mockup Unit (FMU) files can be used in a signals/actuators co-simulation with Abaqus/Standard or Abaqus/Explicit. FMU files conform to the Functional Mockup Interface (FMI) standard defined by the Modelisar organization. For more information on this standard or for a list of tools that provide the FMU file export capability, refer to http://fmi-standard.org/. You will use separate invocations of the FMU execution procedure for each FMU instance participating in your co-simulation.

Warning:

Use of this procedure is recommended only in cases where the more general co-simulation execution procedure (Abaqus/Standard, Abaqus/Explicit, and FMU Co-Simulation Execution) does not support your co-simulation use of FMUs.

The FMU capability is intended primarily for co-simulation analyses involving Abaqus solvers; however, if you have a co-simulation containing only FMUs, then the only supported time negotiation method is constant time step.

This page discusses:

Command summary
Command line options
Examples

Command summary

abaqus fmucsedirectorCSE director hosts:port-number fmufmu-file-name instanceco-simulation-instance-name interactive timeouttimeout value in seconds

Command line options

csedirector: This option is used to specify the connection for co-simulation messages between the CSE director and the FMU execution. The CSE director entry consists of a host name and the listener TCP/UDP port number separated by a colon (e.g., earth:30000 indicates that the CSE director is running on machine “earth” and using a listener port of “30000”).
fmu: This option specifies the FMU file name to be used in the co-simulation.
instance: This option specifies the instance name for the FMU. This instance name will correspond to the componentInstance name in the co-simulation configuration file provided to the CSE director. You can employ a single FMU file multiple times in a co-simulation by making repeated use of the FMI execution procedure with unique instance names.
interactive: This option causes the director to run interactively.
timeout: This option is used to specify a timeout value in seconds for the co-simulation director connection. The FMI execution terminates if it does not receive any communication from the CSE director during the time specified. The default value is 3600 seconds.

Examples

The following example illustrates using the FMU execution procedure in a co-simulation involving Abaqus/Standard and an FMU. This example considers the FMU to be interacting with the Abaqus/Standard job; Abaqus/Standard provides an interface to FMUs.

Running the Co-Simulation Director

Use the following command for the co-simulation director running on machine "mercury" to operate according to the co-simulation configuration defined in the file cosim_config.xml and to receive communication via port 44444:

abaqus cse job=cosim listenerport=44444
   configure=cosim_config.xml

Based on the contents of the file cosim_config.xml, the director will await connections from Abaqus/Standard and an FMU.

Running the First FMU-Based Simulation

Use the following command for the FMI analysis, which will connect to the CSE director on machine "mercury" via port 44444:

abaqus fmu fmu=controller.fmu instance=controller1
   csedirector=mercury:44444

Running the Second FMU-Based Simulation

Use the following command for the FMI analysis, which will connect to the CSE director on machine "mercury" via port 44444:

abaqus fmu fmu=controller.fmu instance=controller2
   csedirector=mercury:44444

Running the Abaqus/Standard Simulation

Use the following command for the Abaqus/Standard analysis, which will connect to the CSE director on machine "mercury" via port 44444:

abaqus job=standard csedirector=mercury:44444