Main PartBody is no longer used in conversion AS SPEC

This task shows you that the copy/paste CATIA_RESULT or CATIA_SPEC of Solids requires to create several Bodies, and the main PartBody in 3DEXPERIENCE is no longer used.

When copy/pasting a model containing several Solids into a void 3D Shape, the first Solid to be migrated generates 3DEXPERIENCE PartDesign specifications in the main PartBody. This can be a problem in several cases:

  • Using the main PartBody introduces a specific role to one migrated Solid, even when this specificity does not exist in the V4 model.
  • If the first migrated Solid is a DETAIL used in a Macro-Primitive, it is not possible to perform Boolean operations of the main Body under other Bodies.
  • V4 CSG first primitive may be inactive. However in a main PartBody, the first specification cannot be inactive or deleted whereas this restriction does not exist on next Bodies.

If only one Body has to be generated, we still use the main Partbody. If there are several of them, the Partbody is not used.

This task shows you how to:

First example: when a DETAIL is used by a DITTO

This task describes an example when a DETAIL is used by a DITTO.

  1. Open a model.


    In this sample, there is a DETAIL (*SOL 62 in the BOULON tab) used by a DITTO (*DIT25 for example):



  2. Open a new 3D Shape. Copy/Paste Special *DIT25 and select CATIA_SPEC in the dialog box.


  3. Update the 3D Shape if necessary.
    In Geometrical Set.1, there is the geometry of DIT25 which has been copied only once. The DETAIL is the first migrated element; you can visualize it in the Specification Tree, it is called Body.2(*SOL62-wsp BOULON-).

    The DITTO appears further down in the Specification Tree; it is called CARWL of Body.2 (*SOL62-wsp BOULON-). The DETAIL BOULON (*SOL62-wsp BOULON-) remains its reference.

    In the Specification Tree, the Body of the DETAIL appears before the DITTO because it is a reference for the DITTO. The DETAIL is not the main object of the 3D Shape which explains why the PartBody is empty.

Second example: when a DETAIL is used by a Solid or a Macro-Primitive

This task describes an example when a DETAIL is used by a Solid or a Macro-Primitive.

  1. Open a model.


    In this sample, there is a DETAIL (*SOL3 in the GUIDA SUP tab) used by a Solid (*SOL370). This DETAIL plays the role of a Macro-Primitive.



  2. Open a new 3D Shape. Copy/Paste Special *SOL370 and select CATIA_SPEC in the dialog box.


    The DETAIL is the first migrated element (Body.2 (*SOL3 -wsp GUIDA SUP- Non Smart-) because it is then used by the Solid. The DETAIL is not meant to be the main Body of the 3D Shape which explains why the PartBody is empty. In the Specification Tree, the copy of the Solid is represented by: Body.5 (*SOL370 -wsp *MASTER-) further down in the Tree. Body.5 keeps a link with the Body of the DETAIL that has been migrated.

    In the Specification Tree, the copy of the DETAIL always appears before the copy of the DITTOS or the Solids. The DETAIL is the first migrated entity into 3DEXPERIENCE.