Flux-AMESim co-simulation: About

Context

The finite element methods are known for providing accurate results for deeper investigation of phenomena in devices such as the rotating machines and the linear actuators. They take into account the local magnetic saturation and the complex configuration of the current density in the conductive regions of solid conductor type.

The regular progress of the calculus capacity of computers results in the computation time becoming more and more efficient, enabling the co-simulation with simulation system tools to reach full potential for specific applications.

Two domains of application

The co-simulation Flux-AMESim is proposed in two domains of Application:

  • the systems with linear actuators for rapid injection, where the presence of eddy currents have enormous impact over the response time
  • the asynchronous machines, where the accurate consideration of dynamic behavior is difficult to analytically study because of the non-uniformity of the current density in the cross-section of the rotor bars (3-phase rotative motors)

Flux-AMESim Co-simulation

The co-simulation Flux-AMESim is presented in the diagram below. It is a co-simulation of the multiphysical type. The two pieces of software Flux and AMESim operate in parallel, which requires the exchange of data and the synchronization of the data transfer process.

Complementary explanations on the operation of a multiphysical co-simulation are given in the volume 4, chapter 3 « Multiphysical co-simulation: principles » (also accessible in the online help).

Implementation

The operation of a co-simulation process with Flux and AMESim is presented in the table below. This table gives the main operation phases. The particular detailed conditions for linear actuators and induction motors are given in the following paragraphs.

Stage Description
1

The Flux user …

  • describes his device (geometry, meshing, physical properties)
  • creates a component for Flux - AMESim coupling
2

The Flux software …

generates a new Flux project: name_projectf2a.flu

(which includes a file of coupling data: amesim_....f2a )

3

The AMESim user…

  • describes his device
  • introduces a Flux – AMESim co-simulation block and configures this block
4

The AMESim user…

executes/launches the AMESim simulation

5

The AMESim software …

  • launches a Flux server (Flux at the background, without interface)
  • charges the Flux project of co-simulation : name_projectf2a.flu
  • initializes this Flux project if necessary

    (suppression of previous results, updating of the supplementary parameter value, initialization of the solving scenario)

6

The Flux software (Flux server) …

  • recovers the necessary input parameters

    (supply voltage, temperature, angular or linear mechanical position)

  • solves the case for the current time step
  • calculates the necessary output quantities for AMESim

    (intensity of the currents in coils, electromagnetic forces or torques, losses)

  • warns AMESim that the solving process of the current time step is over
7

The AMESim software …

  • recovers the Flux output parameters
  • solves the case of system simulation taking into consideration the Flux output parameters as constant quantities up to the next time step
  • updates the necessary input parameters for the Flux project
8 This process is repeated up to the end of the Flux - AMESim co-simulation
9

The user …

(results postprocessing)