Inputs
1. Introduction
The total number of user inputs is equal to 18.
Among these inputs, 11 are default inputs and 7 are advanced inputs.
2. Standard inputs
2.1 Current definition mode
There are two 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 »
Electric current can be defined directly by indicating the value of the maximum line current (the RMS value is required).
In this case, the current definition mode should be « Current »
2.2 Maximum line current, rms
When the choice of the 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.
2.3 Maximum current density, rms
When the choice of current definition mode is “ Density ”, the rms value of the maximum current density in electric conductors “ Max. current dens., rms” ( Maximum current density in conductors, rms value ) must be provided.
2.4 Maximum LineLine voltage, rms
The rms value of the maximum LineLine voltage supplying to the machine: “ Max. LineLine voltage, rms” ( Maximum LineLine voltage, rms value ) must be provided.
2.5 Command mode
One command mode is available:
 The maximum Torque Per Amps (MTPA)The first step of the process consists of computing the torquespeed curve and the second step is to compute the efficiency map bounded by the torquespeed curve.
More information is available on this topic in section 13.4 (Main principles of computation)
2.6 Maximum speed
The computation and analysis of the torquespeed curves are performed over a given speed range.
The maximum allowed value for the « Maximum speed » corresponds to 53000 rad/s  about 506000 rpm.
Notes: 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 N _{base} (corner point speed of the torquespeed curve) N _{max} < N _{base} .
In that case, whatever is the command mode (MTPA or MTPV), the behavior of the machine will be studied over the speed range [0, N _{max} ].
That allows the user to choose precisely the range of speed to be considered for computing and displaying the torquespeed curve and especially maps like efficiency map.
Case 2 : The maximum speed is greater than the base speed (corner point speed) N _{max} > N _{base} .
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.
2.7 Additional losses
The “ Additional losses ” ( Additional loss percentage of electrical losses ) must be provided.
It is used to consider losses which are not computed (like losses due to eddy currents, proximity effects due to electronic devices). These additional losses will be considered in the computation of power balance and efficiency.
Additional losses must be evaluated as a percentage of total electrical losses (Joule + iron losses).
The default value is 0. This input parameter value must be set in a range: 0% to 100% when the unit is in “%” and 0 to 1 when represented in “P.U.” (“Per Unit”).
When the default value is equal to 0, it means the power balance is computed without considering additional losses.
2.8 User working point(s) analysis
It is possible to perform additional analysis on working point(s) located under the torque speed curve. The user 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 which must be specified by the user with the targeted speed and torque.
In that case the next two fields must be filled in 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 take into account the user inputs 4 Button to run the computation 
User working point(s) analysis = Duty cycle
This allows computing the machine performance all over the 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 the table line by line or by importing an excel file in which all the working point of the duty cycle are defined.


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 and take into account the user input data 
4  Button to run the computations 


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

Excel file template to define the duty cycle 
3. Advanced inputs
3.1 Number of computations for J _{d} , J _{q}
First, it is needed to compute the Daxis and Qaxis flux linkage in the J _{d}  J _{q} plane.
To get maps in the J _{d}  J _{q} plane, a grid is defined. The number of computation points along the daxis and qaxis can be defined with the user input « No. Comp. for J _{d} , J _{q} » (Number of computations for Daxis and Qaxis currents) .
The default value is equal to 5. This default value provides a good compromise between accuracy and computation time. The minimum allowed value is 5.
3.2 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 torquespeed curve and the efficiency map. However, that also means longer computation time.
3.3 Number of computation for torque
With the Low Speed command mode, the number of computation for torque is imposed by the input parameter “ No. comp. for torque ” (Number of computations for torque)  Black points in the graph shown below.
The default value is equal to 7. The minimum allowed value is 3. The maximum recommended value is 20.
The number of computation for torque is imposed by the number of computations for speed in the speed range [N _{base} ; N _{max} ] (Red points in the image shown below).
The advanced user input parameter “ No. comp. for torque ” allows to finalize the grid within the torque range [0, T(N _{max} )] at the maximum speed (Black points in the image shown below).

Definition of the number of computations for torque – MTPV command mode 
3.4 Rotor initial position mode
The computation is 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).
According to the input “ Rotor initial position mode ”, the angular position can be defined either automatically using an internal computation process « Auto » (Automatic) or specified by the user « User » (User).
By default, the “ Rotor initial position mode ” is set to “ Auto ”.
3.5 Rotor initial position
When the “ Rotor initial position mode ” is set to “ Auto ”, the initial position of the rotor is automatically defined by an internal computation process.
The resulting relative angular position corresponds to the alignment between the axis of the stator phase 1 (reference phase) and the direct axis of the rotor north pole.
When the “ Rotor initial position mode ” is set to “ User ”, the initial position of the rotor considered for computation must be set by the user in the field « Rotor initial position » (Rotor initial position). The default value is equal to 0. The range of possible values is [360, 360].
For more details, please refer to the section "Rotor and stator phase relative position".
3.6 Skew model – Number of layers
When the rotor magnets 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 ).
3.7 Mesh order
To get the results, the original computation is performed using a Finite Element Modeling (inside Flux software).
Two levels of meshing can be considered for this finite element calculation: first order and second order.
This parameter influences the accuracy of results and the computation time.
By default, second order mesh is used.
3.8 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 software, 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 giving a very high mesh density and 2 giving a very coarse mesh density.
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.