Importing Finite Element Data from a V4 Model

This task shows you how to import finite element data from a V4 model.
This import is based only on a result review.

The following V4 entities will be transferred:

• FEM Model: mesh, selections, elements, materials, properties, axis system.
• Preprocessing Specifications: restraints, loads, NS-masses.

Only available with the ELFINI Structural Analysis (EST) product.

• The import of V4 data is only available for V4 models created using the CATIA FEA (Level 1.1 to Level 1.9) Tables. The Super-Elements, Thermal analysis, Axi-Symmetric analysis or Coupled analysis are not taken into account.
• Before importing a V4 model, make sure the model has been saved in the ANPHYSIC, ANVISU or ANELFINI V4 functions or using a batch utility were GFIENV (mode 2) has been called.
• The following entities are not transferred:
  • History file
  • ANMESH and ANSOLID specification
  • Links between geometry and Finite Element Model entities
  • Images
  • Solver entities (for example: matrices).
     

1. Open a new .CATAnalysis.

2. Right-click the Links Manager.1 set in the specification tree.

3. Select the Import contextual menu .

   The File Selection dialog box appears.

4. Select CATIA V4 model as Type of file option.

5. Select the desired V4 model (.model).

6. Click OK in the File Selection dialog box.

   You can find here an example of the result in the specification tree of a V4 model import.

Synchronizing

If the model has been modified outside of the V5 session, you can synchronize all the features of the analysis document with the performed modifications.
This functionality is limited for small changes in the model: mesh, material, properties or existing sets (Restraints, Loads, Masses).
Do not use the synchronization to replace a model by an other one.

The synchronization scans the V5 features that are concerned by an import, tries to retrieve the V4 objects that have provided the values for import.
If the V4 objects are not found, the V5 feature is deleted.
If the V4 object are found, the previous version of import is replaced by a new one and the list of V4 families (features under the Imported Mesh set) is also updated.

To synchronize:

1. Double-click Link to File under the Links Manager.1 in the V5 specification tree.

   The Synchronize with Model dialog box appears.

2. Click Synchronize if the Synchronization status is set to Not synchronized with source.

3. Click OK.

You will find here the correspondence between V4 finite element data and V5 finite element data:

• Mesh
• Selections
• Elements
• Materials
• Properties
• Axis System
• Preprocessing specifications
   

Mesh

All transferred meshes are grouped in one single mesh part under the Nodes and Elements set (in the V5 specification tree).

For connection mesh parts, it is possible to move some nodes of this mesh part according to some geometry constraints.

Selections

All V4 SLG elements are automatically transferred as V5 user groups.
One V5 group entity is automatically created for each V4 SLG under the Groups set in the V5 specification tree.

You cannot modify transferred groups in a V5 session.

Elements

The following tables give you the correspondence capabilities.

Membrane Elements

Shear Panel Elements

Shell Elements

Beam Elements

Bar Elements

Volume Elements

Spring, Contact and Kinematics Elements

Quasi-3D Elements

Nearly Incompressible Volume Elements

Conductivity Elements

Convection Elements

3D-Axis-Symmetric Elements

Material

All transferred materials are grouped in one single object under the Materials set in the V5 specification tree.

The following table gives you all the correspondence capabilities:

Properties

All transferred properties are grouped in one single object under the Properties set in the V5 specification tree.

Any new property applied on V4 transferred elements will overload existing properties.

The following table gives you all the correspondence capabilities:

The V4 property does not have any sense without an associated element.
For more details about the combination between elements and properties, you can also refer to the Elements section.

This is an example for the TR3S V4 element:

Axis System

The following table gives you all the correspondence capabilities:

* only if the V4 property is FIBER or COMP.

Preprocessing

All transferred preprocessing data are grouped in one single object under the All V4 Preprocessing Sets set in the V5 specification tree.

Loads and Masses If the V4 model contains only computed data (from Compute and Purge option of the CATMSH utility), the data are transferred as preprocessing data. For data stored in External Storage, the transfer requires DLName declaration both in V4 and V5. Indeed, the external storage directory used for the V4 model computed data must be declared with DLName. If it is not the case, the DLName association must be done in the V4 environment. The path of this external storage directory must be associated with the same DLName in V5 document environment (Tools > Options > General > Document). DLName is not required for other files (V4 model or CATAnalysis containing an imported model). When importing the V4 model, it is not necessary to make the DLName the current environment. Note that you can transfer V4 external storage on Windows (by FTP) and work fully on Windows.

Restraints

One V4 Restraint set is converted into a V5 Restraint object.
All the entities of a V4 Restraint set are grouped in one single object in the V5 specification tree (this V5 object is created but hidden).

The following table gives you all the correspondence capabilities:

Masses

One V4 NS_Mass set is converted into one V5 Mass object.
All the entities of one V4 set are grouped in one single object in the V5 specification tree but (this V5 object is created but hidden).

The following table gives you all the correspondence capabilities:

Axis-symmetric Loads

The following table gives you all the correspondence capabilities:

Thermal Loads

The following table gives you all the correspondence capabilities:

Loads

One V4 Load set is converted into one V5 Load object.
All the entities of one V4 set are grouped in one single object in the V5 specification tree (this V5 object is created but hidden).

Combined load cases are transferred as any standard load case.

The following table gives you all the correspondence capabilities: