Using the CATIA V4 Cleaner

This task shows you how to make a diagnostic, and eventually heal a V4 Model data validity before copying it to 3DEXPERIENCE.

You are advised to run the CATCLN (Cleaner) utility on the model to be copied. Again, this operation must be done on CATIA 418 or higher.

  1. If you encounter this kind of message:
    <The selected CATIA V4 element XXX has a bad data structure>

    when checking elements of CATIA V4 models (or copying it to 3DEXPERIENCE), there are a certain number of precautions you should take prior to do the copy operation (again), to manage it successfully as possible. The meaning of this message:

    • This message appears when a problem in the reading of V4 model data has been detected by Catgeo.
    • Check if the V4 model is valid in CATIA V4 and proceed to the following operations:

      • Type < /cln >in the text field

      • FORCE UPDATE (YES) the solids - if there are some in the model

      • Save the model.

  2. A second screen exposes a Model analysis by listing the number of detected invalid elements:


  3. Click the four buttons :
    • Delete (invalid elements),
    • Modify (invalid elements),
    • Pack (memory),
    • All (to see all the messages and results of the checking).
  4. Click YES to Execute and the invalid elements are turned into valid components to be migrated. If you click on YES
    again the "events" number may have turn to 0. Use FORCE UPDATE upon the model's solids.
  5. Save the model.
  6. Then you can migrate the elements of this model from CATIA V4 to 3DEXPERIENCE.
  7. If during a migration from CATIA V4 to 3DEXPERIENCE, you have both messages:
    <The selected CATIA V4 element XXX has a bad data structure>
    < The CATIA V4 solid XXX has not been pasted  <$DRAFT.1 ko...etc>

    It is due to the bad data structure of the solid, detected into the Draft V4.$DRAFT.1.

  8. Type/cln in the text field. The Cleaner's manipulations have modified the V4 Model Data Structure.
  9. If the model contains solids and they depend on modified data. Therefore, it is important to force the solid to compute again, to FORCE UPDATE (YES)
    in order to check that every element is coherent and finally Save the Model before translating it.
  10. If you do not FORCE UPDATE the solid, you may translate an unstable solid.