All machines

Flow Simulator Export Fails when a cooling system has been defined

This bug concerns all the machine types with a Flow Simulator export available. The generated export file is not readable by Flow Simulator when a cooling system is defined in the machine model. This issue applies to cooling systems defined in either the shaft or the housing.

The root cause has been identified as a discrepancy in version numbering. An effective bypass is to modify the .flo file and change the version number to 2025.1 instead of 2026.0 (ref. : SLVFXM-18435).

Wrong results for working point computation in generator mode

This concerns both SMPM and RSM machines. The issue occurs when the computation of the working point is performed in accurate mode and with the generator mode. In that case, the computations are not performed with the good quadrant, leading to wrong results (ref.: SLVFXM-18275).

The graphical display of service cycles is partial

All the intermediary working points between two states are not displayed as they should be (ref.: SLVFXM-18265).

Tests WP I,PSI,N – Fast mode with rotor position dependency - Average quantities wrongly computed

This concerns all the machines (SMPM & SMWF & SMRSM) and all the tests with “Fast mode with rotor position dependency” (Test WP I,PSI,N & Test Maps & Test EMv & Export LUT) (ref.: SLVFXM-18270).

The computation of the end winding inductances appears to be inaccurate

In some cases, the end winding inductances obtained with FluxMotor appear to be too high compared to those calculated with Flux 3D (ref.: SLVFXM-17626).

Opening Materials from Motor Factory failed when Materials are already opened

(ref.: SLVFXM-18101)

FluxMotor export report misses the values on the DQ map

(ref.: SLVFXM-18106)

Launch error message when importing incorrect geometries for SimLab

FluxMotor does not accept non-circular part - e.g., no rotor / stator circular - and then running a test is not possible. However, when a non-circular part is created by SimLab it is possible to import it into FluxMotor, and then an error will be obtained when an export / test is launched.

The import of such geometry must not be permitted, and an error message must be generated while importing it in FluxMotor.

(ref.: SLVFXM-18148).

Interfaces equal to 0 (Design – Internal cooling) leads to an error

This occurs when any thermal computation is launched (ref.: SLVFXM-18191).

There is no overview for illustrating the export of reports

(ref.: SLVFXM-18229)

The graphs displayed in the test Mechanics / NVH have bad quality

Immediately after obtaining the results, the quality of the graphics is good. It deteriorates when you change windows and then come back to see the results (ref.: SLVFXM-17258).

Problem while exporting project to Flux2D

When the machine has a high number of slots and when the machine is fully represented, sometimes, the export of the project to Flux 2D (or Flux Skew) takes a huge computation time and fails (ref.: SLVFXM-17694).

Thermal computations - Problem of convergency

When losses are very high, there is a convergence issue with the thermal computations (ref.: SLVFXM-15900).

This issue will be reevaluated since the thermal solver has been changed.

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 the wrong thermal analysis. It is highly recommended not to use null values for the inputs considered (ref.: SLVFXM-14705).

The color of the wires is bad

The color of wires displayed in the slots is not correct while using Flux Skew export (ref.: SLVFXM-16942).

Air material properties are wrong for high temperature

This issue impacts our internal computation processes during transient thermal solving. Indeed, some iterations involve very high temperature (more than 3000 °K), according to the Newton Raphson non-linear solving method. During the resolution, this can lead to negative conductivity and viscosity, which may make the computation fail (ref.: SLVFXM-14465).

Note: In case of a problem, an “Air material” with the right parameters can be provided.

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.: SLVFXM-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 the "Cooling-Internal" context and used in all thermal tests, is wrong if the slot contains faces "wedge" or "inter-coil insulator" (ref.: SLVFXM-13896).

Winding environment – MMF computation

The counterclockwise sequence (MMF computation) is not considered in the Altair® Flux® model, which one can export. Only the clockwise phase sequence is considered (ref.: SLVFXM-10280).

Using "phase sequence" set to "Counterclockwise" leads to wrong results in tests (ref.: SLVFXM-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.: SLVFXM-12564).