Flux eMachine Toolbox: About
Introduction
Starting from the 2019.1 version, Flux has a new tool called Flux eMachine Toolbox. This coupling is available in 2D, 3D and Skew for the magnetic transient application.
The aim of Flux eMachine Toolbox is to characterize the behavior of the machine in the "TorqueSpeed" area and allows to postprocess various quantities in this area.
Input parameters like the maximum phase voltage RMS , the maximum phase current RMS and the desired Maximum speed of the machine are considered.
Since FeMT 2024.1:
 MTPA: Maximum Torque Per Ampere
 MTPV: Maximum Torque Per Volt
The two command modes MTPA Fast and MTPV Fast have been removed.
But a new field has been created, entitled Computation mode.

TM: corresponds to the solving process called standard in the previous versions, i.e. the former MTPA and MTPV command modes.
This mode allows to compute the iron losses and the magnet losses.
The solving process is performed in Transient Magnetic.
The computation is more precise than with the MS monoposition computation mode, but takes longer.

MS monoposition: corresponds to the solving process called fast in the previous versions, i.e. the former MTPA Fast and MTPV Fast command modes.
This mode does not allow to compute the iron losses, nor the magnet losses.
The solving process is performed in Magneto Static for a single rotor position.
The computation is very fast.
 MTPAthen when opening this test in version 2024.1 or higher, the input parameters table will display:
 for the command mode: MTPA
 for the computation mode: TM
 MTPVthen when opening this test in version 2024.1 or higher, the input parameters table will display:
 for the command mode: MTPV
 for the computation mode: TM
 MTPA Fastthen when opening this test in version 2024.1 or higher, the input parameters table will display:
 for the command mode: MTPA
 for the computation mode: MS monoposition
 MTPV Fastthen when opening this test in version 2024.1 or higher, the input parameters table will display:
 for the command mode: MTPV
 for the computation mode: MS monoposition
Type of machine
In these first versions, only one machine is taken into account by Flux eMachine Toolbox. It is the Synchronous machine, permanent magnet in three phases (Inner rotor or outer rotor).
Since FeMT 2021, designs where the section represented in Flux contains multiple magnetic poles are supported. You can represent all types of machines, and in particular the fractional slot winding machines which have different periodicities in the stator winding and in the rotor.
In Flux, when generating the coupling component, there is a new field: Repetition number of the stator periodicity (if different of rotor)
 Number of represented pair of poles
 Repetition number of stator periodicity
Type of circuit connection
WYE and DELTA winding connections are supported.
 On Flux side
When generating the component, the associated circuit is automatically analysed to know if it's a DELTA or a WYE connection.

On FeMt side
When opening the coupling component in Altair Flux eMachine Toolbox, the winding connection is displayed in the settings table, in the Circuit section.
About losses
Different losses are computed and postprocessed:
 Stator Winding Joule Losses: on each coil conductor
 Rotor Eddy Current Losses: on solid conductor regions (magnet, fret, can,…)
 Iron losses:
 In 2D and 3D and in Skew since FeMT 2021:
 Only computed on nonconducting laminated magnetic regions
 In Flux, it is advised to choose a material with losses, assigned to these regions (the user has the choice to use LS or Bertotti model)
 If losses are not defined on the material, default Bertotti
coefficients are automatically applied
(K1=151.88 ; K2=0.07 ; K3=1.19 ; A1=2 ; A2=2 ; A3=1.5)
Note: For FeMT versions prior to 2021, for Skew projects: Only computed on nonconducting magnetic regions , because the laminated regions did not exist in Skew
 Default Bertotti coefficients were automatically applied
after the Flux solving process
(K1=151.88 ; K2=0.07 ; K3=1.19 ; A1=2 ; A2=2 ; A3=1.5)
Note: About FeMT Skew coupling components generated from Flux version 2020.1 or older:FeMT 2021 no longer supports computation of iron losses for older Skew projects with no laminated regions.
However, the old Skew projects can be opened in FeMT 2021 and results of previous simulations computed with older FeMT version can be displayed. But, it is not possible to start a new simulation on this old project.
In order to run a new simulation on this old project, you will have to open your Skew project with Flux 2021 and regenerate a FeMT coupling component.
 In 2D and 3D and in Skew since FeMT 2021:
Iron losses computation strategy
With the TM computation mode, the iron losses are computed using an internal method called "Half cycle". This method allows to compute the iron losses over half an angular period, thus reduces the total number of computation steps and therefore improves performance by reducing computation time without altering the results.
Process
Here is the process of the Flux eMachine Toolbox coupling:
Step  Software  Description 

1  Flux  Preparation of the Flux project:
Note: A classic workflow is to use FluxMotor to predesign the
electrical machine and export it in a python srcipt. Then the
python script is run in Flux to obtain a Flux 2D project ready
to generate the coupling component 
2  Flux  Generation of the Flux eMachine Toolbox coupling component Note: In the options of the generation of the coupling
component, it is possible to choose to go directly at the
Step 5. After the generation of the coupling component, Flux
eMachine Toolbox is launched (equal to step 3) and the
generated component is directly opened (equal to step
4)

3  Flux Supervisor  Opening of Flux eMachine Toolbox starting from Flux 
4  eMachine Toolbox  Opening of the Flux eMachine Toolbox coupling component generated by Flux 
5  eMachine Toolbox  Choice of input parameters 
6  eMachine Toolbox  Launching of the simulation
Once the solving process is done, a postprocessing script is run to build the performance mapping 
7  eMachine Toolbox  Postprocessing of results 