Flux 12.3.1 Release Notes - Altair...simulation. FX-9695 CAD Export In Flux 12.3, for a geometry...

CAD package for electromagnetic and thermal analysis using finite elements

Flux™ 12.3.1 Release Notes

Connections for multi-domain simulation

Proprietary Information of Altair Engineering

Flux™ 12.3.1 Release note

1

Flux ® 12.3.1 Release note

Reference Date: June 15th, 2017

Version: Flux 12.3.1

Introduction The Release Note describes the content of Flux 12.3.1.

This version contains only few specific corrections.

Contents This document contains the following topics:

Topic See Page Reminder: List of new Features of Flux 12.3 2 Essential Information 3 Corrections implemented 4 Limitations and warnings 5 Known issues 7 Spatial Magnet Orientation: F.A.Q 9 About external software – supported version 12 About protection and installation 13


2

Reminder: List of new Features of Flux 12.3

Introduction To reminder, here is the list of new features of Flux 12.3 version:

For more details

For more details, please consult the New features document describing all the new features present in this new version. This document can be downloaded with the setup of Flux version or viewed from the following path : C:\Altair\FluxDocExamples_12.3\UserGuide\English\01_New_Features_12.3.pdf

� New robust and fast 3D mesh generation

� New volume tetrahedral mesh generator

� High quality meshing technology able to deal with complex geometries

� New efficient way to deal with 3D CAD import

o Import, clean, simplify and mesh in HyperMesh or SimLab

o Use directly the mesh in Flux, assign the physics and solve

� Easy 3D induction machine model setting

� New templates for fast 3D model creation of induction machines

� Many slot and end-ring shapes available

� Geometry, mesh and winding generated in a few clicks

� Design of energy efficient electric drive systems

� solidThinking ActivateTM and FluxTM coupled through co-simulation

� 2D,3D and Skew models, taking into account motion and eddy currents

� Study of load impact on motors or actuators

� Precise control strategies implementation and computation of associated

performance and losses

� Precise evaluation of heat transfer

� Coupling with AcuSolve® for CFD simulation

� First version with one-way coupling

� Any type of electromagnetic device

� Precise evaluation of convection effects and temperature distribution

� Miscellaneous improvements

� New tools for part interference management in 3D modeler

� Faster workflow for application change

� Easy access to FluxTM Macros


3

Essential Information

Essential information

Here are the essential information about the Flux version 12.3.1:

Essential information The setup of Flux 12.3.1 is fully. It is not necessary to have install Flux 12.3 before. For Flux 12.3.1 the user has the possibility to be protected: • either by “Legacy” protection: FlexNet protection • either by “HWU” protection This double possibility of protection will continue for some versions. Only few corrections has been implemented in this version (see the next page) Flux 12.3.1 is qualified for different OS: • Windows 10 • Windows 8.1 • Windows 7 • Linux Red Hat 6 For more information about Flux 12.3, please consult the release note of Flux 12.3 and the documentation of new features of Flux 12.3 (available on Altair Connect).

Disclaimer Altair is not responsible about the database materials data.

This data is given by material manufacturers.


4

Corrections implemented

Issue corrections

This version focused only some corrections.

ID Corrections made

FX-9813 Export OptiStruct In Flux12.3, when exporting the forces harmonics for OptiStruct Flux crashed. In Flux12.3.1 it works well.

FX-9560 Export AcuSolve In Flux12.3, the Nastran file exported for AcuSolve was unreadable. The file format was corrected in Flux12.3.1 so that it can be readable by AcuSolve.

FX-9758

Flux – Activate SolidThinking co-simulation With Flux 12.3, when we launch the cosimulation Flux Activate, Activate display an error message (Resolution is impossible, the project is realized with a more recent version). The dll allowing the co-simulation between Flux and Activate was not compatible. The right dll file has been implemented in Flux 12.3.1 to ensure the co-simulation.

FX-9695

CAD Export In Flux 12.3, for a geometry containing multi cell bodies, the CAD export obtained with Flux was not compatible with Other tools (HyperMesh, SimLab, FEKO, SolidWorks…). In Flux 12.3.1, a correction has been implemented on the CAD export to ensure this workflow. There is still a problem on STEP imports in HyperMesh 2017 where only one body is imported. An issue has been created (HM-87958). However the workflow is ok with HyperMesh for other formats (IGES, SAT, CATIA V5).

FX-9813 FX- 9356 FX- 9134 FX-8696 FX-8557 FX-7437 FX-2036 FX-987

Improvement of magnet orientation Correction has been implemented to manage correctly the orientation of magnet with mobile mechanical set. A FAS has been added, see the page Spatial Magnet Orientation: F.A.Q

FX-9822 RadFlex (integrating ALSDK 13.2) have been updated

FX-9823

Authorize the CATIA V5 CAD import with dimensions exceeding valid working domain… • Before Flux 12.3, Flux didn’t authorize the CAD import, and return an error • Since Flux 12.3, Flux authorize the CAD import with the following warning :

WARNING : Model dimensions exceeds valid working domain ... The user should clean the small unnecessary details This improvement had been done for all CAD import format, except CATIA V5 format

• With Flux 12.3.1, this improvement has been also done for CATIA V5 format


5

Limitations and warnings

Limitations The list of principal limitations (and warnings) of the 12.3.1 version is presented in the table below.

ID General limitations The number of characters in the Flux formula (formula editor) is limited to 80.

5452 The number of circuit component is limited to 10000 (circuit) The names of Flux folders and Flux projects should not contain accents, blank

character, specific characters such as '%', ... Flux accepts the following characters: "+-./0123456789ABCDEFGHIJKLMNOPQRSTUVWXYZ_abcdefghijklmnopqrstuvw&xyz~"

ID 12.3.1 limitations

Application change • Formulas with spatial quantities are not kept, they are set to 0. • The conversion of sensors are not managed. Please check the formula of parameter

using these sensors. • Coil conductors with « circuit » type are not converted in “imposed current” type for

applications without circuit. • The kinematic type of mechanical sets with movement must be redefined and

validated • The magnet orientations are not kept.

Import HyperMesh / SimLab : Temporary limitations

The HyperMesh and SimLab mesh import capabilities have currently some limitations that should be overcome in the future.

Here is a non-exhaustive limitation list:

• Only the mesh elements of maximum dimension are imported: for a file containing surface and volume elements, only volume elements are imported in Flux. • So it is impossible to import a mesh containing the surface elements of shells and

volume elements of the air box • The internal faces of a component are not imported (the assignment of internal

terminal to define current direction in solid conductors is impossible). User has to create two component in SimLab/HyperMesh.

• It is impossible to create the infinite box after importing the mesh and deleting the volume mesh : the commands complete infinite box and build volume do not work in this case

• It is impossible to use point graphical selection in post processing (point sensor, point computation, defining a path with point graphical selection, etc.)

• Only one import is allowed • Superimposed mesh is not checked in Flux (for example: if user forgot to make the

subtraction operation between the air box and the device in HyperMesh or a merge in SimLab). The user may obtain wrong results in some situations.

• Coil conductor region orientation does not work • It is possible to remesh the volumes in Flux after the import, but it is not optimized: a

surface remesh is done and can take a long time and can fail.


6

Import HyperMesh / SimLab : Limitations linked to the method

The mesh import presents limitations that cannot be corrected (linked to the method and technical constraints):

• It is impossible to parameterize a mesh imported with geometrical parameter • It is impossible to enter in the Modeler context (also after deleting the mesh)

Implementation of MeshGems (a 3D volumic mesh generator): • Low relaxation => Increase the number of nodes and the number of mesh elements • Not available for the surface meshing

Flux-AcuSolve coupling: • One way coupling : only an export from Flux to AcuSolve • The Flux project must be in 3D • The computation and export is done on Flux mesh. The Flux data are then

interpolated in AcuSolve. By consequence, the Flux mesh should be fine.

Modeler: The graphic representation of interference of coincidence line-line or point-point or point-line or point-face or line-face is wrong. 2 faces are always highlighted, compatible with a face-face coincidence.


7

Known issues

Principal known issues

The list of principal “Known issues” of the 12.3.1 version is presented in the table below (as well as the “Bypass solutions” when they exist)

ID Summary FX-9709 Flux doesn't manage 2nd order after an Nastran Mesh import

FX-9558 Error during solving with local radiation in this specific case (no error with infinite radiation)

FX-9487 When we do an export of data table, it is not possible to click on OK if the limit min and limit max of the parameter is not valid

FX-9320 When we create the device using the overlay, Flux don't take into account of this unit (Inch)

FX-9311 This skew project cannot be solved if there is more than two regions of type solid conductor no circuit (open circuit)

FX-9135 Load a macro after a motor overlay gives a graphical error Bypass 1: load and run the overlay + save project + load and run the macro Bypass 2: load the macro + load and run the overlay + run the macro

FX-8558 In this MH3D project, the resistance of a non-mesh coil is not taken into account in the electrical circuit.

FX-8341 Issue concerning insulator face region on symmetry surface. A problem concerning a geometry with symmetry and periodicity. When a face region is assigned to a face localized on a symmetry surface, the project is impossible to solve.

FX-8254 When a project is being solved in batch mode, the button "stop current solving" does not work (the solving continues). The bypass is to create by hand the STOP file in the working directory.

FX-8099 Problem of CAD Import with certain file with format .STEP and .IGES

FX-7926

In this 2D magnetostatic project, the same sensors created before and after solving give different results. It is the particular case of punctual sensors linked to a region with mobile mechanical set.

FX-7832 Import Flux Object of a 3D project is not managed By pass : export in a SAT file and then import the SAT file (but the parametering is lost)

FX-7080

If we create a volume region with impedance surface type, Flux create face regions corresponding to this volume regions. If a user associate a sensor to this face regions, and want later to delete results and re-launch the calculation flux reset the sensors, and delete the face regions impedance surface type.

Continued on next page


8

Known issues, Continued

Principal known issues (continued)

ID Summary

FX-5703

Thermal application: The value of the injected power is not available in the postprocessing part. The calculation of power on “Thermal conducting region with heat thermal source” is proposed (Active power), but the result is invalid (= not implemented). Bypass solution: use the integral computation mode in the advanced menu in 2D: face integral of dHeatV on the face region (integration in the domain depth) in 3D: volume integral of dHeatV on the volume region

FX-5101 2D Steady State Thermal application: In the case of axi-symmetric domain, do not use point region of Imposed temperature type: the results cannot be guaranteed.

FX-4640 2D Electrostatics application: With mechanical set (multi-static kinematic), it’s not possible to compute the torque

FX-4167 In skew Transient Magnetic, user can't use line region to represent airgap in 2D multi layers

FX-3818

3D Steady State AC Magnetic coupled with Transient Thermal application: Post-processing with “volume density of Laplace’s force” (dFLapV / dFLap2wV)

is not possible. Bypass: Computation with the formula: dvBJFvL ∫ ∧=

rrr

FX-3816

3D Steady State Thermal application with: • a region of the following type: “Conducting region with heat source” • the heat source is described by a formula that depends on temperature ⇒ the temperature dependence is not taken into account

Bypass : 1) Continuation of the solving process: iterate on one step of the scenario, after several iteration the results converge on the good results. 2) Create a material with a function which has a law which depend on the temperature, to make the system nonlinear and to make more iterations

FX-3145 Impossible to solve a 3D Steady State AC Electric project with a face region of the type "Thin dielectric and no conducting region".

Bypass: Use a volume region instead of the face region.

FX-2819 Mechanical losses due to friction coefficient are not taken into account in the power balance computation. Bypass: Do not forget to take them into account.


9

Spatial Magnet Orientation: F.A.Q

Introduction This F.A.Q intends to give some warning when users work with spatial

formula to define the residual magnetic flux density for a magnet (Br). In presence of mechanical set, some precautions have to be take into account. The following explanation applies for the 12.3.1 version and are valuable for MT application, in 2D/3D and Skew.

Note: Br = residual magnetic flux density of the magnet.

Br tightly linked with mechanical set

User wants define Br tightly linked with the mechanical set. This is the most common case that user can run into (see tab 1).

step 1 step 2 step 3

Tab 1 : residual magnetic field (Br) is not calculated for each step. Br keep the direction of the mechanical set.

To do that, user can follow the procedure above: Use the new menu bar (available before solving since the 12.3.1 version) 'Parameter / Quantity' + 'Store Quantity' + 'New (constant) tabulated spatial quantity by storage of values' (be careful : only available before solving since the 12.3.1 version)


10

Br with spatial formula

User defines Br with a spatial formula, directly in the material or via a spatial quantity of formula type... In this case, user has to keep in mind that a spatial formula is calculated at the beginning of each step during the solving, in the global coordinate system. Rotation of Br due to the rotation of the mechanical set is not taking in account. For example, in MT2D problem, a user defines a spatial formula directly in the material to set up his residual magnetic field Br. Formula could be Vec3(X,0,0), where X is the global coordinate abscissa

Define a spatial formula directly

Define a spatial linear magnet

Define this type of geometry


11

The result The results are going to be the following :

Rotor position In black : rotor region In Yellow : magnet region In Green : stator region

0°

Br orientation keep the same orientation, along X

30°

User can see that the magnet has a half part in the negative abscissa.

60°

90°


12

About external software – supported version

External programs

The use of external programs can be achieved with the versions listed in the table below.

Flux OS Flux

functionality External software

Supported version

Supported OS

Win64 Lin64

Matlab - Simulink

Version 2014b

64 bits

� Flux 12.0

� Version 2015b

� Flux 12.1

�

Version 2016b

� Flux 12.2 Flux 12.3

�

Version 2017a

� Flux 12.3 �

GOT-It

Version 3.0

64 bits � �

CDE

Version 2.2

32 bits (can be installed in a 64 bits to exchange with Flux and Got-It)

� �

Import Speed files (2D)

Speed 64 bits

� �


13

About protection and installation

About FlexNet protection

For Legacy users, the new functionalities contained in the version 12.3 don’t need new features.

About HWU protection

Since the 12.2 version, it is possible to use the HyperWorks Units as protection system The HWUs count is split into 2 parts: • GUI = description of geometry+ mesh + physics + postprocessing of

results • Solver = computation of the model All the applications are covered.

HWU for Flux 3D and Flux Skew

For Flux 3D (and Flux Skew), the HWU licensing system is the same as all HyperWorks solvers: • GUI = 21 HWUs • Solver = 25 HWUs

HWU for Flux 2D

For 2D users exclusively, the offer has been adapted. There is no GUI / Solver distinction. By default, the user has access to all applications and with 15 HWUs.

About installation

The setup of Flux 12.3.1 is fully. It is not necessary to have install Flux 12.3 before.

About installation - documentation

The setup specific to the documentation is integrated on the main setup of Flux. Since Flux 11.2, documents and examples are automatically installed with the main setup of Flux.

About installation - CDE

The Cedrat Distribution Engine tool (CDE) allowing distributing computations, is installed automatically with the main setup of Flux.

Graphic cards It is necessary for the proper functioning of our software that the driver of the

graphics card is as up-to-date as possible. In our experience a "Windows Update" is not sufficient, it is essential to install the latest driver supplied by the manufacturer of the card. Eg for NVIDIA: http://www.nvidia.com/Download/index.aspx?lang=en-us

Date post:	08-Aug-2020
Category:	Documents
Upload:	others
View:	6 times
Download:	0 times

Flux 12.3.1 Release Notes - Altair...simulation. FX-9695 CAD Export In Flux 12.3, for a geometry...

Documents