List of the main issues

(ref.: FXM-15161).

(ref.: FXM-15099).

In the tests dedicated to the computation of a working point (for synchronous machines or induction machines), if the mode of computation is fast the stator Joule losses are computed, but not displayed in the table of results. However, these can be deduced from the power balance information (ref.: FXM-15142).

The computation of forces on teeth is no more available, since the workflow to compute forces on the teeth in NVH must be updated (ref.: FXM-15086).

When exporting a project from FluxMotor to Flux 2D, the mesh in the slot can be sometime very bad in the region surrounding the represented wires inside the coil conductors (ref.: FXM-15151).

After having exported a Flux Skew project, if you solve the project and delete the results and then solve again, the running of the project fails (ref.: FXM-15075).

Exporting a machine with squared lamination for specific winding architecture. Indeed, the parallel path manager cannot manage odd number of half coils in incomplete parallel path and flux cannot either (ref.: FXM-14956).

Sometimes, the slot filling with wires (solid conductors) fails for the inner slots (ref.: FXM-15150).

When the twist of conductors is selected in the winding area, if the motor presents an anticyclic periodicity, the twist of conductors won't be considered in the flux project (ref.: FXM-14935).

Removing of the housing is not well managed with hairpin winding and potting are selected all together (ref.: FXM-14731).

Null values are not well managed while designing the Frame and shaft

Null values are allowed for designing the housing, bearing or shaft dimensions, but this leads to a wrong thermal analysis. It is highly recommended not to use null values for the considered inputs (ref.: FXM-14705).

Error while opening a motor (2020.1) with null shaft extension

Opening a motor built with the version 2020.1 (or older) and with a null shaft extension leads to an error. With new versions, a null shaft extension is forbidden (ref.: FXM-14684).

The interwire space is not well defined.

The value of the interwire space applied in the resulting finite element model is twice the value set in the user inputs (ref.: FXM-14672).

Transient thermal computation

Sometimes, there is an issue with nonlinear thermal resolution. The convergence criteria doesn't reach from a certain time iteration leading to non-physical results then making the physical properties interpolations impossible. This can occur for duty cycle inside of which there are a huge number of working points for instance (ref.: FXM-14570).

Air material properties are wrong for high temperature

Sometimes, when FluxMotor® launches an optimization in the back end with HyperStudy®, and if there is an error in the internal process (evaluation of the objective functions), this makes FluxMotor® crash.

Moreover, without any log file to explain the issue one cannot understand the cause of system crash (ref.: FXM-13949).

When an IO cannot be loaded, the test results are not accessible

When an IO cannot be loaded, the whole process that loads all the test results is stopped. As a result, no test is visible although the issue may concern one result in a particular test (ref.: FXM-13941).

A wedge and/or inter-coil insulation region leads to a wrong slot equivalent thermal conductivity

The slot radial thermal conductivity, which is automatically provided by the FluxMotor® in "Cooling-Internal" context, and used in all thermal tests is wrong if the slot contains faces "wedge" or "inter-coil insulator" (ref.: FXM-13896).

Power electronics and coupling with HyperStudy®

For tests where settings "Electronics" is available, data like power electronics stage, maximum efficiency and its rated power can be selected for generating a connector for HyperStudy®, but it should not be (ref.: FXM-13726).

Management of multi-parametric settings with HyperStudy® coupling

Some configurations of parameterized topologies can be obtained manually in Motor Factory but cannot be created from HyperStudy® for some connectors. One must be able to manage the case of sequential input update in HyperStudy® connector, especially for topology definitions (ref.: FXM-13612).

Script Factory freezes temporarily when running a script

When running a script, script factory gives the impression of freezing (while still running in the background). The editing window of the script becomes unresponsive until the script is done executing (ref.: FXM-13138).

Winding environment – MMF computation

The Counter-Clockwise sequence (MMF computation) is not considered in the Altair® Flux® model which one can export. Only the clockwise phase sequence is considered (ref.: FXM-10280).Using "phase sequence" set to "Counterclockwise" leads to wrong results in tests (ref.: FXM-13358).

Flux density isovalues

When a skewed topology is considered (Synchronous machines or induction machines), the flux density isovalues, the vector potential isolines and the rotor bars current density isovalues are not displayed (ref.: FXM-12564).

Working point – Square wave – Forced I – Average computation of quantities

The computation of average quantities like the iron losses, the Joule losses in magnets, torque is not done over a full electrical period. That can lead to wrong results (ref.: FXM-14091).

Wrong data in HyperStudy® export area

In the Export-HyperStudy® area, when the selected test is “Working Point, T-N”, the electronic setting "Max efficiency", and "Rated Power" are exported even if the associated option is not selected (ref.: FXM-13726).

Maximum speed computation

The estimation of the maximum speed is wrong for the tests “Working point - Sine wave – Motor - U-I” and “Working point - Sine wave – Motor - T-N”, when the control mode MTPA is selected (ref.: FXM-10916). The computation is always performed by considering a MTPV command mode.

In such case, a Flux 2D computation is performed instead of a Flux Skew meaning the impact of the skewing is not considered in the computation results (ref.: FXM-15301).

This means that after the first test based on a working point, the following tests give the same results whatever is the targeted working point (ref.: FXM-15262).

The reference temperature which is set to define the end ring - Impedance in manual modes is not considered for the tests solving (ref.: FXM-15147)

Power balance of No-load working point

Sometimes, computation of No-load working point (slip=0.1%) leads to a NaN (Not a Number) result. The computed amount of iron losses is not consistent with the power balance (ref.: FXM-12600).

Torque slip curve

Test results are not continuously consistent over a torque slip curve. This occurs with the test Performance mapping T(Slip) - induction machines with skewed squirrel cage. When the user targets a working point as an added value to be computed with the whole Torque-slip curve, sometimes this additional working point doesn't belong to the curve.

(ref.: FXM-12599).

The reference temperature which is set to define the end ring impedance in manual modes is not considered while exporting a project to Flux 2D or Flux Skew (ref.: FXM-15145).

End-ring impedance – Reference temperature is not well applied

While exporting a model from FluxMotor® to Flux® 2D or Flux® Skew environment, if the end-ring impedance has been defined with the “constant computation mode” (= user mode) instead of the automatic one, the reference temperatures set by the user are not used in the resulting Flux® project. Instead, the default values are automatically considered (ref.: FXM-13713)

Wrong management of part borders

An inner part with air region on the bottom border is not allowed (ref.: FXM-13445)

Script Factory does not stop correctly, if FluxMotors has been killed (ref.: FXM-15140).

In Script Factory, the find/replace dialog box must be closed when the end of the file is reached. When the search reaches the end of the file, the only way to restart from the beginning is to close the dialog window, reopen and enter once again the data (ref.: FXM-15138).

The store button is not enabled when a file is opened without modification (ref.: FXM-15136).

When running a script, script factory gives the impression of freezing (while still running in the background). The editing window of the script becomes unresponsive, until the script is done executing (ref.: FXM-13138).

The preferences that require a reboot are not updated after the reboot (ref.: FXM-13121).

While changing the language in Chinese, then in Japanese the automatic reboot of FluxMotor fails (ref.: FXM-15088).