Common Import Behavior
This section describes the behavior of CATIA V5 data stored in legacy databases imported into 3DEXPERIENCE that is common to all connectors.
V5 Data Type | 3DEXPERIENCE Content Type | Import Result |
---|---|---|
Mechanisms | Mechanism representation | Fully Imported
If the V5 mechanism includes laws, the 3DEXPERIENCE mechanism representation is placed under the Model node of a new simulation object. |
Law based on formula |
Formula is imported as a Relation, and the Law is imported as an Excitation referring to the formula. |
Fully imported |
Law based on spline sketch |
Spline sketch is imported, and the law is imported as an Excitation referring a resource table and a rule. |
Fully imported |
Considerations
You should take the following considerations into account:
- Import of Mechanisms
- The following items in a CATIA V5 mechanism are not imported to
3DEXPERIENCE:
- Distance, speed, and interference analyses
- Sensors
- Simulations created in DMU Kinematics Simulator
- Import of Joints with Driven Kinematic Commands
- If you import a V5 kinematic joint driven by a command in the 3DEXPERIENCE, no geometry is associated as support for that command.
- Screw Joints - Deleting Constraints
- If you import a V5 Screw joint and delete the Hinge constraint, the Coincidence and Offset constraints are automatically deleted.
- Structure Diagrams - V5 vs 3DEXPERIENCE
- In CATIA V5, the components of a kinematics simulation are collected under the Product node in the tree; in 3DEXPERIENCE a kinematics simulation is a separate object that refers to a product, a mechanism representation, and simulation specifications (excitations, probes, and scenarios).