Inputs

Introduction

The total number of user inputs is equal to 19.

Among these inputs, 10 are default inputs and 9 are advanced inputs.

Sharing data between tests

An import button is available for allowing sharing the data simulated in Flux between “Characterization / Model / Map” and “Performance mapping / Efficiency map” tests.

Indeed, by implementing the rotor position dependency option for the model map test and efficiency map test of synchronous machines, this update facilitates the seamless transfer of settings, inputs, and crucially, simulated data in Flux between the two tests. As they use the same Flux data in most cases and significant computation time is required to obtain it, users can now accelerate the test resolution and optimize their workflow.

To streamline this process, an import button has been introduced in both the “Characterization / Model / Map” and “Performance mapping / Efficiency map” tests of the following machines:

Reluctance Synchronous Machines - Inner rotor
Synchronous Machines with wound field – Inner Salient Pole - Inner rotor

Note: The import button will be added to the tests of Synchronous machines – Permanent magnets - Inner & Outer rotor in the next version.

Upon completing a model map test, users can activate the import button in the efficiency map test GUI. This enables them to effortlessly import the settings and corresponding Flux data from the previous test, eliminating the need to rerun Flux for identical data, a step that typically consumes a substantial portion of computation time during efficiency mapping.

Conversely, upon concluding an efficiency map test, users can use the import button in the efficiency map test GUI to import settings and Flux data from the efficiency map test, further enhancing workflow efficiency.

Note: Only the most recent test results can be imported, saved test results are not yet able to be imported.

Note: While there are shared settings and inputs between the tests, each test may have its own unique settings and inputs. In such cases, the default settings, and inputs of the second test are automatically applied.

Note: When importing from the efficiency map test to the model map test, the quadrant setting defaults to the value specified in the model map test. For certain machine types (SMWF: 2nd quadrant, SM-RSM: 1st quadrant), specific quadrant selections are applied.

Note: In instances where quadrant inputs lead to incompatibility between the model map test and the efficiency map test, only settings and inputs are imported. A warning is issued, and Flux simulation is initiated to rectify the discrepancy.



Import function in Model Map test and Efficiency Map test to accelerate test resolution. Example for Wound field synchronous machines
1	Open model map test environment when an efficiency map test is available for import
2	Click the import button and import the settings, inputs, and Flux data of the latest efficiency map test
3	Open efficiency map test environment when a model map test is available for import
4	Click the import button and import the settings, inputs, and Flux data of the latest model map test

Standard inputs

Field Current and line current definition mode

There are 2 common ways to define the electrical current.

Electrical current can be defined by the current density in electric conductors.

In this case, the current definition mode should be « Density ».

Electrical current can be defined directly by indicating the value of the line current (the RMS value is required) and field current (AC value).

In this case, the current definition mode should be « Current ».

Maximum field current, rms

When the choice of current definition mode is “Current”, the maximum DC value of the field current supplied to the machine “Max. field current, rms” (Maximum field current, rms value) must be provided.

Note: The number of parallel paths is automatically considered in the results.

Maximum field current density, rms

When the choice of current definition mode is “Density”, the maximum rms value of the current density in electric conductors “Max. field current dens., rms” (Maximum current density in field conductors, DC value) must be provided.

Note: The number of parallel paths is automatically considered in the results.

Maximum line current, rms

When the choice of current definition mode is “Current”, the maximum rms value of the line current supplied to the machine “Max. line current, rms” (Maximum line current, rms value) must be provided.

Note: The number of parallel paths and the winding connections are automatically considered in the results.

Maximum Line-Line voltage, rms

The rms value of the maximum line-line voltage supplying to the machine: “Max. Line-Line voltage, rms” (Maximum Line-Line voltage, rms value) must be provided.

Note: The number of parallel paths and the winding connection are automatically considered in the results.

Maximum speed

The computation and analysis of the torque-speed curves are performed over a given speed range.

The maximum allowed value for the « Maximum speed » corresponds to 53000 rad/s - about 506000 rpm.

Note: As a function of the maximum speed value, following different cases must be considered:

Case 1: The maximum speed is lower than the base speed Nbase (corner point speed of the torque-speed curve) Nmax < Nbase.

In that case, for any command mode (MTPA or MTPV), the behavior of the machine will be studied over the speed range [0, Nmax].

That allows the user to precisely choose the range of speed to be considered for computing and displaying the torque-speed curve and especially maps like efficiency map.
Case 2: The maximum speed is greater than the base speed (corner point speed) Nmax > Nbase.

The relevance of the maximum speed given by the user is analyzed to evaluate if it is reachable by the machine.

If the user maximum speed is unreachable by the machine, the correction of this value is automatically performed.

The resulting new maximum speed is linked to a limit torque. This limit torque is obtained by applying a reduction coefficient to the base point torque.

Rotor position dependency

It defines the rotor position dependency of electromagnetic data used for the optimization of the efficiency map such as D-axis magnetic flux, Q-axis magnetic flux, electromagnetic torque, iron losses. By default, the rotor position dependency is set to “No” but it can be set to “Yes”. In this case the computation will be done along the three dimensions Jd – Jq – If, with an additional fourth axis corresponding to the rotor position θr.

Note: This option allows to have a better accuracy in the evaluation of magnetic flux, electromagnetic torque as well as iron losses. It is worth noting that only with rotor position dependency that the rotor iron losses can be evaluated.

Additional losses

Note: “Additional losses” input is not available in the current version (The input label is written in grey).

User working point(s) analysis.

It is possible to perform additional analysis on working point(s) located under the torque-speed curve. The user’s input “User working point(s) analysis” (additional analysis on working point(s)) gives three possibilities to the user:

User working point(s) analysis = None (=default mode)
This corresponds to the basic configuration of the test, with no additional working point analysis.

User working point(s) analysis = Single point

This allows computing the machine performance on a working point specified by the user with the targeted speed and torque. In that case the next two fields must be filled with the targeted speed and mechanical torque.



User working point analysis = Single point
1	Select the “Single point” option to perform a computation on one working point.
2	Define the targeted working point mechanical torque and speed.
3	Button to validate and consider the user inputs
4	Button to run the computation

User working point(s) analysis = Duty cycle

This allows computing the machine performance all over a considered duty cycle.

This duty cycle must be defined by using the next field: "Duty cycle description" and by clicking on the button "Set values".

Two ways are possible to fill in the table: either filling in the table line by line or by importing an excel file which all the working points of the duty cycle are defined.

Note: A working point is defined by a time, a speed, and a mechanical torque.



User working point analysis = Duty cycle
1	Select the “Duty cycle” option
2	Click in the button “Set values” of the field “Duty cycle” to open a dialog box to define the duty cycle. Refer to the next illustration which shows how to fill the Duty cycle table.
3	Button to validate the user input data
4	Button to run the computations

Note: Once the test results have been computed, new user working point and duty cycle values can be set, and results will appear instantaneously when relaunching the test.



User working point analysis = Duty cycle – Dialog box to define the duty cycle
1	Dialog box opened after having clicking the button “Set values” in the field “Cycle description”
2	Browse the folder to select an Excel file which is described the duty cycle
3	Button to refresh the table data when the considered Excel file has been modified
4	Fields to be filled with data to describe the duty cycle to be considered

Note: The Excel template used to import a duty cycle is stored in the folder Resource/Template in the installation folder of FluxMotor®. An example of this template is displayed below



Excel file template to define the duty cycle

Advanced inputs

Number of computed electrical periods

The user input “No. computed elec. periods” (Number of computed electrical periods only required with rotor position dependency set to “Yes”) influences the computation time of the results.

The default value is equal to 0.5. The maximum allowed value is 1 according to the fact that computation is done to characterize steady state behavior based on magnetostatic finite element computation. The default value provides a good compromise between the accuracy of results and computation time.

Note: The outcomes obtained at 0.5 or 1 electrical period are identical across all presented outputs, except for slight variations in rotor iron losses arising from the symmetrical assumption regarding the magnetic flux waveform on the rotor.

Number of computations for IF-axis field current

First, it is needed to compute the D-axis and Q-axis flux linkage in the Jd - Jq planes at various levels of If.

To get D-axis and Q-axis flux linkage maps along IF dimension, the field current is discretized from zero to its maximum value. The number of computation points along the If-axis can be defined with the user input « No. comp. for IF » (Number of computations for If-axis field currents).

The default value is equal to 6. This default value provides a good compromise between the accuracy of results and computation time. The minimum allowed value is 5.

Number of computations for Jd, Jq per quadrant

To get D-axis and Q-axis flux linkage maps in the Jd - Jq planes, a grid is defined. The number of computation points along the d-axis and q-axis can be defined with the user input « No. Comp. for Jd, Jq » (Number of computations for D-axis and Q-axis currents per quadrant).

The default value is equal to 6. This default value provides a good compromise between accuracy and computation time. The minimum allowed value is 5.

Note: As a synchronous machine with wound field machine operates in both 1st and 2nd quadrants, the total number of computations for the D-axis is twice the number entered for « No. Comp. for Jd, Jq » minus one as the zero value is shared between the two quadrants. For example, if « No. Comp. for Jd, Jq » is 6, there will be 11 computations for the D-axis.

Number of computations for speed

The “No. comp. for speed” (Number of computations for speed) corresponds to the number of points to be considered in the speed range from 0 to the maximum speed.

Half of these points are distributed from 0 to the base speed. The remaining points are distributed from the base speed to the maximum speed.

In both cases, base speed is considered as an additional point.

Note: If the user input parameter “No. comp. for speed” is an odd number, one discretization point is automatically removed.



Definition of the number of computations for speed

The default value is equal to 15, the minimum allowed value is 5. The maximum recommended value is 40.

Note: Increasing the number of computations can improve the convergence of the optimization used to define the torque-speed curve and the efficiency map. However, that also means longer computation time.

Number of computations for torque

For the speed range [Nbase; Nmax.], the number of computations for torque is imposed by the number of computations for speed in the speed range [Nbase; Nmax.] (Red points in the image shown below).

The advanced user input parameter “No. comp. for torque” allows finalizing the grid within the torque range [0, T (Nmax.)] at the maximum speed (Black points in the image shown below).

The default value is equal to 7. The minimum allowed value is 3. The maximum recommended value is 20.



Definition of the number of computations for torque – MTPV command mode

Skew model – Number of layers

When the rotor or the stator slots are skewed, the number of layers used in Flux® Skew environment to model the machine can be modified: “Skew model - No. of layers” (Number of layers for modelling the skewing in Flux® Skew environment).

Rotor initial position mode

The computations are performed by considering a relative angular position between rotor and stator.

This relative angular position corresponds to the angular distance between the direct axis of the rotor north pole and the axis of the stator phase 1 (reference phase).

The value of the rotor d-axis location, which is automatically defined, for each saliency part, in Part Factory, can be visualized in the output parameters in the saliency area of Motor Factory – Design environment.

Airgap mesh coefficient

The advanced user input “Airgap mesh coefficient” is a coefficient which adjusts the size of mesh elements inside the airgap. When the value of “Airgap mesh coefficient” decreases, the mesh elements get smaller, leading to a higher mesh density inside the airgap and increasing the computation accuracy.

The imposed Mesh Point (size of mesh elements touching points of the geometry), inside the Flux®, is described as:

MeshPoint = (airgap) x (airgap mesh coefficient)

Airgap mesh coefficient is set to 1.5 by default.

The variation range of values for this parameter is [0.05; 2].

0.05 gives a very high mesh density and 2 gives a very coarse mesh density.

CAUTION: Be aware, a very high mesh density does not always mean a better result quality. However, this always leads to a huge number of nodes in the corresponding finite element model. So, it means a need of huge numerical memory and increases the computation time considerably.