DMU Space Analysis
(SP1) - P1, (SPA, MSA) - P2

This page deals with the following products:

 


DMU Space Analysis (SP1) - P1

General Issues

Measure Item vs. mass computation
improvement
Measure Item takes advantage of the improvements made to the mass computation precision on the R18 level. Consequently,   measure item results on a same CATPart vary between R17 and R18 levels.
Knowledgeware rule-based clash computation
for SDD Design Units or SFD Systems
If you want to launch a knowledgeware rule-based clash computation under the following circumstances:
  • The knowledgeware clash rule contains SddDesignUnit or SfdSystem objects.
  • SddDesignUnit or SfdSystem objects are saved in ENOVIA database.
  • The cache system is activated (The Working with the Cache system check box is selected in Tools > Options > Product Structure > Cache Management).
Multi-CPU computer mode and clash
calculation
Multi-CPU computer mode (designed to distribute the clash calculation among processors) is no longer activated by default because it could lead to serious problems.

Workaround: It is still supported but is only available on request (we provide a specific variable for those who want to continue to work in multi-CPU computer mode).
 

Exporting section results in VRML format To view the section results in a browser that is different from the CATIA dedicated viewer, change the background color of that browser.
Measures Update in Scenes
 
Automatic update in product Setting:
In Tools > Options > Parameters and Measures > Measure Tools:
  • If the automatic update in product check box is selected, measures made using Measure Between, Measure Item, Measure Inertia and Measure Arc through Three Points are updated in a scene context.
  • If the automatic update in product check box is cleared, measures made using Measure Between, Measure Item, Measure Inertia and Measure Arc through Three Points are not updated in scene context.
Measuring geometry & inertia Measures made using Measure Between, Measure Item, and Measure Inertia take all items into account even those located in the No Show space.
Measure Inertia
Measure Item
The center of gravity value result differs depending on the command you are using (Measure Inertia or Measure Item). This is a standard behavior because:
  • Measure inertia takes into account the material applied on parts and/or products whereas,
  • Measure Item calculates the geometric center of gravity without taking into account the applied material.
Measure Between
  • The three planes that can be selected in an axis system are considered to be semi-infinite planes relimited by two corresponding axes of the axis system. As a result, you may obtain incorrect results using the Measure Between command on those planes.

Workaround: Use Any geometry, infinite mode for Measure Between.

Measuring distances (Measure Between) in the Section viewer
 
  • The Arc center mode is no longer activated when measuring distances (Measure Between command) in the Section Results window using Any geometry and Any geometry, infinite selection modes.

Workaround: To measure distances between centers of arcs, set the Selection mode to Arc center.

Measures (Item and Between) and 3D XML In 3D XML format, when you save a product containing Measure Between or Measure Item that is stored in a complex DMU Review structure (with sub-reviews), the measures between are also saved in the 3D XML file.
However, when you reopen the 3D XML file, the Measure Between is created in a default DMU Review but the complex DMU Review structure is not retained.
Sections and 3D XML
  • New product > Insert a 3D XML containing a section:
    The section appears in the specification tree but is not valid.
    The section is not displayed in the geometry.
  • The plane visualization mode (plane, slice or box) is not exported.
  • The fill mode of the section result is not exported.
  • The Section Freeze mode is not retained.
  • The information related to the grid (activated, values, behavior) is not retained.
Clash Results export in XML
 
  • French and Japanese languages are not supported by the first XML type (First XML type: the XML Export for clash process purpose check box is cleared. For this XML type any filters applied to the results in the Clash dialog box are taken into account so you can use the filters to export pertinent results only ).
  • The Zoom in interferences option is now available in the Tools > Options > Digital Mockup > Space Analysis > DMU Clash Process tab. By default, the check box is selected.
CATIA/ENOVIA Interoperability - XML Export
 
Customizing XML Export Clash Settings
If you want to export clash results (saved in ENOVIA V5 VPM and sent to CATIA) with associated pictures in XML format:
  • We recommend you to select the Compute all numeric and graphic results option button in During initial Computation area using the Tools > Options > Digital Mockup > DMU Space Analysis > DMU Clash tab.
Japanese Language Support in Second XML type Second XML type: To ensure the availability of Japanese language support, select the Support for long filenames check box in DMU Clash - Process tab (Tools > Options > Digital Mockup > DMU Space Analysis).
Measuring Distances on Section Results The maximum distance cannot be computed on the Section Results.
Measure Item A curve segment to be measured is not identified as an arc if the tessellated points (corresponding to the segment to be measured) cannot be approximated by an arc, such that the tessellated points are within tolerance (which is equal to sag) to the arc.

The image describes a scenario where the segment to be measured will not be considered as an arc. The number of points in the tessellated data is greater than, or equal to, 4.
There is at least one point from the tessellated data which is at a distance greater than sag from the arc fitted through the tessellated points.

Open Issues

Measures (Item and Between) and 3D XML


 

 
DMU Reviews and Measures
  • In 3D XML format, when you save a product containing Measure Between or Measure Item that is stored in a complex DMU Review structure (with sub-reviews), the measures between are also saved in the 3D XML file.
  • Associativity is not retained when you save in 3D XML. The re-created measure between is broken and, thus, is nonassociative.

Measure Customization
 

  • The customization of the repositioning of lines and text for a measure (green-colored) is not retained in the 3D XML file: when you reopen the 3D XML file, all measures appear in the default position.
  • The customization of the measure display is not retained in 3D XML format: when you reopen the 3D XML file, all values are saved and the measure is displayed using the current customization.

Supported Measures in 3D XML

  • Measure Between or Measure Item stored in a complex DMU Review structure (with sub-reviews) can be saved in 3D XML. Note the measures between are also saved in the 3D XML file.
  • Only Measure Item and Measure Between can be exported to 3D XML format. Measure Thickness and Measure Arc (by 3 points) are not taken into account. In Measure Between the angle measured is not exported either.
  • Measures with names such as "MeasureBetween.5" or "MeasureBetween.XXX" will be saved as "MeasureBetween.1", "MeasureBetween.2", etc.
  • The maximum distance cannot be saved in 3D XML format.
Sections and 3D XML This issue will be corrected on a forthcoming SP level:
  • In 3D XML, when you save a product containing sections stored in a complex DMU Review structure (with sub-reviews), the sections are also saved in the 3D XML file; however, when you reopen the 3D XML file, the sections are created in a default DMU Review: the complex DMU Review structure is not retained. The selected objects that are cut are not retained.
Measure Item When you perform a measure on a solid (for example, a pad), the measure value is the one of the whole Part Body document (The selected object is not taken into account for the measure calculation). Therefore, the measure result is incorrect.
Sectioning and CATDrawing documents This issue will be corrected on a forthcoming SP Level:

The current V5 session is inadvertently terminated under the following circumstances:

  • A CATDrawing is open along with the Section Result window.
  • You close the Section Result window.
    The same issue is applicable to Distance Result window.

Workaround: Close the Section Result window before opening a CATDrawing document.

Sectioning and CATAnalysis documents To take advantage of sectioning capabilities in a CATAnalysis document, open the linked CATProduct before running the sectioning command.
Measuring in Visual Comparison viewer Measures made in the Visual Comparison viewer are displayed in the main document window.

Documentation

None  

DMU Space Analysis (SPA, MSA) - P2

General Issues

Measure Item vs. mass computation
improvement
Measure Item takes advantage of the improvements made to the mass computation precision on the R18 level. Consequently,   measure item results on a same CATPart vary between R17 and R18 levels.
Knowledgeware rule-based clash computation
for SDD Design Units or SFD Systems
If you want to launch a knowledgeware rule-based clash computation under the following circumstances:
  • The knowledgeware clash rule contains SddDesignUnit or SfdSystem objects.
  • SddDesignUnit or SfdSystem objects are saved in ENOVIA database.
  • The cache system is activated (The Working with the Cache system check box is selected in Tools > Options > Product Structure > Cache Management).
Multi-CPU computer mode and clash
calculation
Multi-CPU computer mode (designed to distribute the clash calculation among processors) is no longer activated by default because it could lead to serious problems.

Workaround: It is still supported but is only available on request (we provide a specific variable for those who want to continue to work in multi-CPU computer mode).

Exporting section results in VRML format To view the section results in a browser that is different from the CATIA dedicated viewer, change the background color of that browser.
Measures Update in Scenes Automatic update in product Setting:
In Tools > Options > Parameters and Measures > Measure Tools:
  • If the automatic update in product check box is selected, measures made using Measure Between, Measure Item, Measure Inertia and Measure Arc through Three Points are updated in a scene context.
  • If the automatic update in product check box is cleared, measures made using Measure Between, Measure Item, Measure Inertia and Measure Arc through Three Points are not updated in scene context.
Measuring geometry & inertia
 
Measures made using Measure Between, Measure Item, and Measure Inertia take all items into account even those located in the No Show space.
Measure Inertia
Measure Item
The center of gravity value result differs depending on the command you are using (Measure Inertia or Measure Item). This is a standard behavior because:
  • Measure inertia takes into account the material applied on parts and/or products whereas,
  • Measure Item calculates the geometric center of gravity without taking into account the applied material.
Measure Between
  • The three planes that can be selected in an axis system are considered to be semi-infinite planes relimited by two corresponding axes of the axis system. As a result, you may obtain incorrect results using the Measure Between command on those planes.

Workaround: Use Any geometry, infinite mode for Measure Between.

Measuring distances (Measure Between) in the Section viewer
  • The Arc center mode is no longer activated when measuring distances (Measure Between command) in the Section Results window using Any geometry and Any geometry, infinite selection modes.

Workaround: To measure distances between centers of arcs, set the Selection mode to Arc center.

Measures (Item and Between) and 3D XML
 
In 3D XML format, when you save a product containing Measure Between or Measure Item that is stored in a complex DMU Review structure (with sub-reviews), the measures between are also saved in the 3D XML file.
However, when you reopen the 3D XML file, the Measure Between is created in a default DMU Review but the complex DMU Review structure is not retained.
Sections and 3D XML
  • New product > Insert a 3D XML containing a section:
    The section appears in the specification tree but is not valid.
    The section is not displayed in the geometry.
  • The plane visualization mode (plane, slice or box) is not exported.
  • The fill mode of the section result is not exported.
  • The Section Freeze mode is not retained.
  • The information related to the grid (activated, values, behavior) is not retained.
Clash Results export in XML
  • French and Japanese languages are not supported by the first XML type (First XML type: the XML Export for clash process purpose check box is cleared. For this XML type any filters applied to the results in the Clash dialog box are taken into account so you can use the filters to export pertinent results only ).
  • The Zoom in interferences option is now available in the Tools > Options > Digital Mockup > Space Analysis > DMU Clash Process tab. By default, the check box is selected.
CATIA/ENOVIA Interoperability - XML Export Customizing XML Export Clash Settings
If you want to export clash results (saved in ENOVIA V5 VPM and sent to CATIA) with associated pictures in XML format:
  • We recommend you to select the Compute all numeric and graphic results option button in During initial Computation area using the Tools > Options > Digital Mockup > DMU Space Analysis > DMU Clash tab.

Open Issues

Measures (Item and Between) and 3D XML DMU Reviews and Measures
  • In 3D XML format, when you save a product containing Measure Between or Measure Item that is stored in a complex DMU Review structure (with sub-reviews), the measures between are also saved in the 3D XML file.
  • Associativity is not retained when you save in 3D XML. The re-created measure between is broken and, thus, is nonassociative.

Measure Customization

  • The customization of the repositioning of lines and text for a measure (green-colored) is not retained in the 3D XML file: when you reopen the 3D XML file, all measures appear in the default position.
  • The customization of the measure display is not retained in 3D XML format: when you reopen the 3D XML file, all values are saved and the measure is displayed using the current customization.

Supported Measures in 3D XML

  • Measure Between or Measure Item stored in a complex DMU Review structure (with sub-reviews) can be saved in 3D XML. Note the measures between are also saved in the 3D XML file.
  • Only Measure Item and Measure Between can be exported to 3D XML format. Measure Thickness and Measure Arc (by 3 points) are not taken into account. In Measure Between the angle measured is not exported either.
  •  Measures with names such as "MeasureBetween.5" or "MeasureBetween.XXX" will be saved as "MeasureBetween.1", "MeasureBetween.2", etc.
  • The maximum distance cannot be saved in 3D XML format
Sections and 3D XML This issue will be corrected on a forthcoming SP level:
  • In 3D XML, when you save a product containing sections stored in a complex DMU Review structure (with sub-reviews),
    the sections are also saved in the 3D XML file; however, when you reopen the 3D XML file, the sections are created in a default DMU Review: the complex DMU Review structure is not retained. The selected objects that are cut are not
    retained.
  • When reopening your 3dxml in 3DLive, Product may not be visible in Examine due to too many volume cuts.
Measure Item When you perform a measure on a solid (for example, a pad), the measure value is the one of the whole Part Body document (The selected object is not taken into account for the measure calculation). Therefore, the measure result is incorrect.
Sectioning and CATDrawing documents This issue will be corrected on a forthcoming SP Level:

The current V5 session is inadvertently terminated under the following circumstances:

  • A CATDrawing is open along with the Section Result window.
  • You close the Section Result window.
    The same issue is applicable to Distance Result window.

Workaround: Close the Section Result window before opening a CATDrawing document.

Sectioning and CATAnalysis documents To take advantage of the sectioning capabilities in a CATAnalysis document, open the linked CATProduct before running the sectioning command.
Measuring in Visual Comparison viewer Measures made in the Visual Comparison viewer are displayed in the main document window.
 

Documentation

More About the Section Result Window > Section Results Window The section filling capability will not give the expected results in the following cases:
  • When the intersection consists of a duplicated polyline, it is identified as a non-closed surface and hence it is not filled as expected.
  • When the intersection curve consists of two closed areas which do not form the outer boundary of the surface, it is recognized as non-closed curve and hence it not filled.