About interfacing to Abaqus for 3D meshes
Export Fill+Pack (with or without Fiber) results and Warp results for 3D models to Abaqus for further structural (usually Stress) analysis.
This interface is supported on PC for the following mesh type(s):
3D
and for all molding processes except:
- Powder injection molding
- Underfill encapsulation
- RTM or SRIM
The API script, mpi2abq.vbs automatically converts the necessary result and mesh files into a format that Abaqus uses. Results are exported in *.xml format, and the 3D mesh is exported in Abaqus input (*.inp) format. The API script saves the interface files in a folder created in the current project folder. For example, My Documents\My AMI 20XX Projects\Project1<study_name>_interface_files, where
Interfacing to Abaqus
Autodesk Moldflow Insight result and mesh files are binary files, that are converted to ASCII format by the API script, mpi2abq.vbs, for use in Abaqus.
Interface files
The files that are exported depend on what your study file contains.
Mesh file
The API script converts the 3D mesh to the Abaqus input format. This interface file is named
For more information about the Abaqus *.inp format, please refer to your Abaqus manual.
Material properties data files
For fiber-filled materials, these files are produced:
Principal directions
The principal fiber orientation directions are the eigenvectors of the fiber orientation tensor. These data are stored in
Mechanical properties
Are element-based results stored in individual engineering constant component files, such as
Thermal expansion coefficients
Are element-based results stored in
For unfilled materials, these files are produced:
_Moduli.xml _PoissonRatios.xml _ShearModuli.xml _Ltecs.xml
Initial stresses file
Autodesk Moldflow Insight passes the initial stresses to the interface. The API script converts these data and stores them in
Unit conversion
The mpi2abq script takes care of the unit conversion if you select a unit system other than SI.