Flux-Portunus co-simulation: preparation of the Flux project

Introduction

Co-simulation requires that the standard description (geometry, mesh, physics) of the Flux project has been done. To prepare the coupling between Flux and Portunus, it is necessary to define, in Flux, the desired input and output parameters, in order to generate a coupling component file.

Flux Inputs

Several types of quantities can appear amongst the input parameters:

  • electrical quantities (ex. resistance, voltage, current…)
  • mechanical quantities (ex. torque, speed, position,…)
  • geometric (air gap,…)

As the coupling between Flux and Portunus uses multiphysics co-simulation, the input parameters must be defined as I/O Parameters of multiphysics type.

Flux Outputs

We can find the exact same quantity types as with the input parameters; namely the electrical, mechanical and geometric quantities.

The output parameters must not be of the multiphysics type.

An output parameter can be:

  • a geometric parameter
  • a I/O non multiphysics parameter
  • a predefined parameter of a mechanical assembly
  • a sensor

The coupling file

The coupling component is necessary in order to ensure the transfer of information from the Flux project to Portunus project. This component data is described in the file *.F2P file.

Once the necessary input and output parameters for the coupling have become available, the user must generate a component:

  • by clicking on the Generate component for Portunus coupling in the Solve menu

The dialog box " Generate component for Portunus coupling" is presented below:

Having generated the coupling file:

  • A file ComponentName.F2P is created by default in the current directory.
  • a Flux project ComponentNameF2P.FLU is created and will be accessed by Portunus during the solving process.

Upon launching of the solving process via Portunus, results are stored in the Flux project with the following name:

ComponentNameF2P.FLU

*.F2P file

This file contains the information necessary for Portunus to be able to automatically detect:

  • the version of Flux
  • the version of F2P
  • the solver used
  • the inputs and the outputs

Solving Scenario

No solving scenario defined in Flux will be taken into consideration by Portunus. It is Portunus that manages the time steps of the simulation imposing them to Flux during the co – simulation.