All machines

Thermal computation results can be very different between FluxMotor and Flux2D

Thermal computation with FluxMotor can be very different from the one exported to Flux2D with the same settings.

Indeed, the second-order temperature interpolation does not manage very well high temperature variations on an element.

That's why, sometimes, in Flux2D, the result got for a single thermal node of the mesh can "hide" the real temperature distribution when the temperature map is displayed by default.

As a workaround, we can change the temperature scale manually to make the results become closer to what is expected (ref.: FXM-16393).

This issue has been modified into an improvement task since such a case must be fixed by improving the meshing.

Thermal computations - Problem of convergency

Solving problem during the pre-computation of thermal circuit with negative temperature can occur (ref.: FXM-16948).

This issue has been corrected.

Japanese language and Flux software exports

When we export a Flux project (Flux2D, FluxSkew and Flux3D) some characters are written in Japanese which makes the file crash during the execution. A workaround consists of deleting all the Japanese characters and then execute the python file (ref.: FXM-16590).

This issue has been corrected.