InterOp:Connect/CATIA V5/Manufacturing Information Representation
From DocR21
The Connect interface supports translation of manufacturing information (MI) present under Annotation Set from CATIA V5 CATPart format. Manufacturing information includes PMI data with Display Information and Hole feature.
Set the Representation user option to PMI or Manufacturing or PMI+Manufacturing.
Contents |
PMI Data
Manufacturing Information for PMI is called through the use of a representation named PMI. The PMI data includes dimensioning (Driven and Reference types), Geometric Dimensioning and Tolerancing (GD&T), 3D annotation (text and flag note), and Surface Roughness information. To support the translation of PMI data, the following set of DLLs are required in addition to the common DLLs:
- SPAXCATIAV5PMIExporter.dll
- SPAXV5TkPMI.dll
Annotations in CATIA V5
InterOp Connect supports Text Note, Flag Note, Surface Roughness, Dimension, Datum Feature, and GD&T type of annotations in a CATIA V5 file. Other types of annotations such as Note Object Attributes (NOA) are not supported.
- InterOp Connect represents these annotations in ACIS as an attribute on the associated entity.
- InterOp Connect represents these annotations in Parasolid as a dummy body containing the tag_id of the associated entity and all of its attributes.
- PMI annotations created at assembly level (in CATProduct) are exported. However, assembly PMI annotations attached onto workplanes or axis systems in CATPart files are not supported. Set the option Representation to Assembly+PMI to export assembly PMI annotations.
The CATIA V5 annotations are based upon the following rules:
- All angular values of GD&T are converted into degrees and other types of GD&T values are converted into the target document unit.
- In the Text Annotations, the text properties such as Underline, Color, Font Size, and Font Name are not supported.
- In the Flag Note Annotations, URL and Hidden text are not supported and their display properties are given the same as Text Annotation.
Dimensions Mapping
While translating from CATIA V5, the Basic, Reference, and Tolerance type dimensions from CATIA V5 are mapped to BASIC, REFERENCE, or TOLERANCE types.
For example, the Reference type dimension in CATIA V5 is mapped as REFERENCE type. The subtype represents Linear, Angular, or Radius value type. Subtype dimension is based on the corresponding dimensions created in CATIA V5. The following table lists dimension mapping:
| CATIA V5 Dimension Type | Dimension Subtype |
|---|---|
| DrwDimDistance DrwDimDistanceOffset DrwDimLength | DIMSUBTYPE_LENGTH_OR_DISTANCE |
| DrwDimRadius DrwDimRadiusTangent DrwDimRadiusCylinder DrwDimRadiusEdge DrwDimFillet | DIMSUBTYPE_RADIUS |
| DrwDimDiameter DrwDimDiameterTangent DrwDimDiameterCylinder DrwDimDiameterEdge DrwDimDiameterCone | DIMSUBTYPE_DIAMETER |
| DrwDimAngle DrwDimAngleArc DrwDimSlope | DIMSUBTYPE_ANGLE |
| DrwDimLengthCurvilinear DrwDimLengthCircular | DIMSUBTYPE_CURVILINEAR |
Coordinate type dimension is mapped as shown in the table below:
| CATIA V5 Coordinate Dimension Type | Dimension Subtype |
|---|---|
| 0: 2D coordinate dimension | DIMSUBTYPE_COORDDIM2D |
| 1: 3D coordinate dimension | DIMSUBTYPE_COORDDIM3D |
Note: All the CATIA V5 types other than those listed above are mapped into DIMSUBTYPE_UNKNOWN.
Dimension Extremities in CATIA V5
InterOp Connect exports extremity points of linear and ordinate dimensions from CATIA V5.
Hole Feature
Manufacturing Information for Holes is translated by using Manufacturing Representation. To support the translation of Hole feature, the SPAXCATIAV5Manufacturing DLL is required in addition to the common DLLs.
Display Information
The InterOp Manufacturing Information Reader translates PMI display information from source to target formats. The display information includes:
- Anchor points of annotation
- Normal to view plane
- Primary direction of annotation
- Leader line information (head and tail points)
This display information can be used by the receiving application to present the annotation data in the same 3D coordinates as in the source file.
Non-semantic GeomTol PMI
The CATIA V5 Reader translates non-semantic GD&T PMI with the limitation that the value of the tolerance is written out as a part of note. The data in the note has the following structure:
<GeomTol Value> | <upper-note> | <lower-note>
The upper and lower notes are optional; even when absent, empty place holders are provided for them in the notes separated by the delimiter "|". For example, if an <upper-note> is absent but a <lower-note> is present, then the GeomTol note becomes:
<GeomTol Value> || <lower-note>
The value of the tolerance is set to -1.0.
Important: Datum References of Datum Reference Frames associated with non-semantic GD&Ts will not contain any Datums. This is a limitation as that information is not available with CATIA V5 non-semantic GD&Ts.
|
Figure. Non-semantic GD&T PMI illustrates a sample non-semantic GeomTol PMI created in CATIA V5. While exporting from CATIA V5, the tolerance magnitude is set to -1 and the note field of GeomTol is set to 0.005 Tol|Upper Note|Lower Note. |
In this example, the text file has the following PMI information:
Note: The PMI information shown is only for the first two rows.
| Example. Non-semantic Stacked GeomTol PMI |
|---|
Geomtol attribute found
---------------------------------------------------------------------
Owner Count :2
Owner :FACE(id = "17030")
Owner :FACE(id = "17024")
Tolerance Type :11
Mod Dia Type :0
Tolerance Magnitude :-1.000000
Refinement Tol :0.000000
Rate Unit1 :0.000000
Rate Unit2 :0.000000
Zone Modifier1 :0
Zone Modifier2 :0
Projected Magnitude :0.000000
Profile Shift :0.000000
All Around :FALSE
Note :10(M)||
Semantic :FALSE
-----------------------------------------
DRF Information Start{
Note :C
DREF count :1
-----------------------------------------
DREF [ 0] Information Start{
Note :C
Datum count :0
}DREF [ 0] Information End
}DRF Information End
Composite :FALSE
Display Information
-------------------
Display point : ( 0.00000000, -20.75223923, -65.25757599)
Display plane normal : ( 1.00000000, 0.00000000, 0.00000000)
Primary direction : ( 0.00000000, 1.00000000, 0.00000000)
Geomtol attribute found
---------------------------------------------------------------------
Owner :GEOM_TOL(Note:10(M)||)
Tolerance Type :13
Mod Dia Type :0
Tolerance Magnitude :-1.000000
Refinement Tol :0.000000
Rate Unit1 :0.000000
Rate Unit2 :0.000000
Zone Modifier1 :0
Zone Modifier2 :0
Projected Magnitude :0.000000
Profile Shift :0.000000
All Around :FALSE
Note :3.0||
Semantic :FALSE
-----------------------------------------
DRF Information Start{
Note :C
DREF count :1
-----------------------------------------
DREF [ 0] Information Start{
Note :C
Datum count :0
}DREF [ 0] Information End
}DRF Information End
Composite :FALSE
|
Non-semantic Datum PMI
The CATIA V5 Reader translates non-semantic Datum PMI. The translated data is in the same form as the data translated for semantic versions of Datum PMI.
PMI Data Pointing to Hidden BRep Entities
When translating the PMI representation (CATIA V5 to ACIS), the TranslateHiddenEntities option may be overridden for specific bodies if they are referenced by visible PMI annotations. This ensures the completeness of the PMI information provided.
Specifically, if a PMI entity points to a face, an edge, or a vertex of a solid body, the whole solid body will be translated independently of whether it is visible or hidden.
If the TranslateAttributes option is set to true, then hidden solids that are being translated due to this mechanism will be marked as hidden in the target format.
The table below summarizes what to expect depending on your input CATIA V5 data:
| Topology | Visible | Visible | Hidden | Hidden |
| PMI | Visible | Hidden | Visible | Hidden |
| TranslateHiddenEntities=false (default) | Both translated | BRep translated | Both translated | Nothing translated |
| TranslateHiddenEntities=true | Both translated | Both translated | Both translated | Both translated |
This behavior applies to Part translation only and is currently not implemented for Assembly translation. Refer to the following sections for more information about hidden entities and attributes translation:
Current State in Captures
InterOp supports translation of the current state of captures. In CATIA V5, this can be identified with a red dot on the Capture icon. An example is shown in Figure. Captures in CATIA V5 above.
Initial State capture indicates it is a current capture.
Clipping Plane in Capture
If the Clipping Plane command is activated in CATIA V5, the clipping of the active view is displayed. The section profile is displayed as a thick orange line and the clipped surface is shown in green.
Clipping Plane helps you see when the active view in a capture is clipped. The section profile is displayed as a thick line; it is shown only when the active view of the selected capture is a section cut or a section view. For other views, only the clipping will be seen (not the profile).
|
In Figure. Clipping Plane in Capture, Section Cut View.2 is the active view. The clipping plane is displayed in orange dotted lines. The red arrow shows the normal of this clipping plane. In XML the translated clipping plane is displayed with Clipping Plane Display Point and Clipping Plane Display Normal in the following format: <Clipping_Plane_Information>
<Clipping_Plane_Origin X="<double>" Y="<double>" Z="<double>"/>
<Clipping_Plane_Normal X="<double>" Y="<double>" Z="<double>"/>
</Clipping_Plane_Information>
|
Camera Associated with Capture
If Camera is associated with a capture, its properties are translated to ACIS. The camera helps a user to display a 3D model in the required orientation and zoom. The Camera Properties window shows various camera properties such as Name, Type, Origin, Target, View Angle, and Zoom. There are two types of cameras: Parallel and Perspective.
| |
|
Note: Irrespective of camera type, both View Angle and Zoom fields are translated to ACIS. You have to select proper a field depending upon your application.
Hidden CapturesThe CATIA V5 modeler automatically hides some of the captures if the displayed capture is changed. A preview is shown to the right. To translate the hidden captures, the TranslateHiddenEntities option must be set to TRUE; the hidden annotation entities are also translated. The flag Visibility="FALSE" is appended for hidden entities. |
