STEP: Trouble Shooting


If you need to recover from transfer failures after importing the data contained in a STEP file into a CATPart document, please refer to the IGES: Trouble Shooting chapter because the repairing scenario is the same with IGES files.
There are however some specificities for STEP data, they are detailed just below:

What you need to know

STEP files may describe assemblies that contain CATParts. The result of the conversion is a Product which contains several components.


=> If needed, each part can be analyzed and corrected individually.

If the components have links between them (for example instantiations), the links are recreated in the product.


=> Corrections on the source part are automatically reported to instances.

You are now ready to create the topology. For more information:


STEP files with syntax errors

When a STEP file is syntactically invalid, there are error messages in the .err file describing those invalidities.
Syntax errors are responsible for partial loss of STEP file data: all invalid entities and all entities pointing directly or not to invalid entities are ignored. In order to recover all the STEP entities, correct the STEP file before reading it in V5.



STEP files with short names

Using short names in STEP files is an out-of-date way to reduce the size of STEP files (available in V4). Therefore V5 imports only STEP files with long names and does not support short names. Please ask your suppliers to send you only STEP files with long names.



Exporting V4 data does not provide the expected result: data placed in the NoShow in V5, or changes of colors or graphic attributes are not taken into account, e.g. if you have sent a V4 element to the NoShow, it will be kept since it is its V4 status that is taken into account. To make those changes effective, you need to make those changes in a V4 session, save the data in V4 and re-import them to V5.