About Reports and Troubleshooting

Converter for STEP offers several tools to follow the conversion.

This page discusses:

Detailed Report

The detail of transferred entities can be included in the report file.

You can activate the detailed report under General in the STEP Exchange section of the Preferences.

Report and Error Files

Report and error files give your information about the import or export, and help you solve problems. Always check the report and error files after a conversion: Some problems may have occurred without been visually highlighted.

At Import

Two files are generated at the end of import.

These files are created in a location referenced by the CATReport variable. Its default value is Profiles\user\Local Settings\Application Data\Dassault Systemes\CATReport on NT (user being you logon id), and $HOME/CATReport on UNIX.

Report File

Its name is name_of_file.rpt. It provides references about the quality of the transfer.

Example:

E:\Report\pm6-hc-214.rpt
Input FileName :
G:\Equipe_STEP\STEP\PDES-Prostep\Tr8\Prod\pm6-hc-214.stp
Output FileName :
 =================HEADER===========================
Originating System: HiCAD2 V1009
Preprocessor version: HiCAD2 V1009 STEP 1.2.2001
File Schema: AUTOMOTIVE8DESIGN {1 2 10303 214 0 1 1 1 }
=============DETAILED CONVERSION===================
#30 MANIFOLD_SOLID_BREP #30 Type: MANIFOLD_SOLID_BREP Transferred correctly
#70 MANIFOLD_SOLID_BREP #70 Type: MANIFOLD_SOLID_BREP Transferred correctly
...
#590 MANIFOLD_SOLID_BREP #590 Type: MANIFOLD_SOLID_BREP Transferred correctly
#630 MANIFOLD_SOLID_BREP #630 Type: MANIFOLD_SOLID_BREP Transferred correctly
#14660 ADVANCED_FACE #14660 Type: ADVANCED_FACE Topology transfer failure
#670 MANIFOLD_SOLID_BREP #670 Type: MANIFOLD_SOLID_BREP Degenerated
#710 MANIFOLD_SOLID_BREP #710 Type: MANIFOLD_SOLID_BREP Transferred correctly
====================================================
~~~~~~~~~~~~~~~~~CONVERSION SUMMARY~~~~~~~~~~~~~~~~~~
OK=Transferred
KO=Not transferred
NS=Unsupported
OUT=Out of size
DEG=Degenerated
INV=Invalid
---------------------------------------------------------
| Entity Type          | OK | KO | NS | OUT | DEG | INV |
---------------------------------------------------------
| ADVANCED_FACE        |1498|  3 |  0 |   0 |   0 |   0 |
| MANIFOLD_SOLID_BREP  |  95|  0 |  0 |   0 |   3 |   0 |
---------------------------------------------------------
| Result               |1593|  3 |  0 |   0 |   3 |   0 |
---------------------------------------------------------
====================================================
Transcription time in seconds: 267.965
Error File

Its name is name_of_file.err. It lists the errors that occurred during the transfer.

Example:

E:\Report\pm6-hc-214.err
Input FileName :
G:\Equipe_STEP\STEP\PDES-Prostep\Tr8\Prod\pm6-hc-214.stp
Output FileName :
============================================
*** = Processing new independent element
* = Intermediate processing
!! = Independent element K.O.
! = Intermediate error
--------------------------------------------
<I> = Information
<W> = Warning
<E> = Error
--------------------------------------------
[0000] = Message identifier : 0000
[T=xxx] = Entity Type Step : xxx
[#0000] = Entity identifier number : 0000
============================================
Actual display level : Customer

where:

  • OK = Transferred
  • KO = Not Transferred
  • NS = Unsupported
  • OUT = Out Of Size

    OUT entities are OUT of model size. Most of the time, these entities are curves and they are out of the 3DEXPERIENCE model space. These entities are not created.

  • INV = Invalid

    INV entities are Invalid entities, that is to say their description within the STEP file is invalid (STEP syntax rules are not respected,...). These entities are not created.

  • DEG = Degenerated

    DEG entities are degenerated entities. They are solids (MANIFOLD_SOLID_BREP) or Shells (OPEN_SHELL), or Curves (LINE, CIRCLE,...). Degenerated solids are incomplete solids (at least one Face misses).

At Export

Two files are generated at the end of export.

These files are created in a location referenced by the CATReport variable. Its default value is Profiles\user\Local Settings\Application Data\Dassault Systemes\CATReport on NT (user being you logon id), and $HOME/CATReport on UNIX.

Report File

Its name is name_of_file.rpt. It provides references about the quality of the transfer.

Example:

C:WINNT\Profiles\vmu\Local_Settings\Application
Data\DassaultSystemes\CATReport\03_ClosedTolpology.rpt

Input file:
Output file: E:\users\03_ClosedTolpology.stp
~~~~~~~~~~~~~~~~~CONVERSION SUMMARY~~~~~~~~~~~~~~~~~~
OK=Transferred
KO=Not transferred
NS=Unsupported
OUT=Out of size
DEG=Degenerated
INV=Invalid
---------------------------------------------------------
| Entity Type          | OK | KO | NS | OUT | DEG | INV |
---------------------------------------------------------
| Face                 | 705|  0 |  0 |   0 |   0 |   0 |
| Shell                |   1|  3 |  0 |   0 |   0 |   0 |
---------------------------------------------------------
| Result               | 706|  3 |  0 |   0 |   0 |   0 |
---------------------------------------------------------
=========================================================
Transcription time in seconds: 17.115

Error File

Its name is name_of_file.err. It lists the errors that occurred during the transfer.

Exemple:

C:WINNT\Profiles\vmu\Local_Settings\Application
Data\DassaultSystemes\CATReport\03_ClosedTolpology.err

Input file:
Output file: E:\users\03_ClosedTolpology.stp
===================================================
***=Processing new independent element
*=Intermediate processing
!!=Independent element KO
!=Intermediate error
---------------------------------------------------
<I>=Information
<W>=Warning
<E>=Error
---------------------------------------------------
[0000]=Message identifier:0000
[T=xxx]=Entity Type Step: xxx
[#0000]=Entity identifier number:0000
===================================================
Actual display level: Customer

Troubleshooting

Below are some information to solve errors.

At Import

Too many cuts or invalidities
If a message indicates that making a face boundary C2 continuous results in too many cuts, or if invalidities are detected in the imported data, refer to About Geometry Quality Enhancement to solve the problem. If necessary, use Shape Healing to heal the data.
Syntax Errors
When a STEP file is syntactically invalid, messages in the .err file describe those invalidities. Syntax errors are responsible for partial loss of STEP file data: All invalid entities and all entities pointing directly or indirectly to invalid entities are ignored. In order to recover all the STEP entities, correct the STEP file before reading it in 3DEXPERIENCE.
Transfer failures

We recommend you import huge assemblies in batch mode. If the import of a huge assembly fails in interactive mode, do it again in batch mode.

There are however some specificities for STEP data:

  • STEP files may describe assemblies that contain products, that contain themselves 3D shape representations.
  • If needed, each product can be analyzed and corrected individually.
  • If the products have links between them (for example instantiations), the links are recreated in the product.
  • Corrections on the reference product are automatically reported to instances.

STEP files usually describe solids. It means that they contain the topology of the model. During the conversion of a part:

  • If there is no problem, the geometry and the topology are imported and the result is a solid.
  • If there is a geometric problem, one or several faces of the solid cannot be recreated and the solid itself is degenerated.

The resulting model contains:

  • An empty PartBody
  • A geometrical set with a surface corresponding to all faces OK
  • A geometrical set for each face KO.

There may also be a topological problem, when all the geometry has been converted OK but the topology could not be created. Then the resulting model contains:

  • An empty PartBody
  • A geometrical set with the surfaces that could not be joined properly.

Quality of conversion
Notes:
  • Check recommended practices, licensing and application protocol requirements in Requirements.
  • See also the STEP Exchange section of the Preferences. .
  • Always check the report and error files after a conversion! Some problems may have occurred without been visually highlighted.

We recommend that you use the STEP Validation Properties when they exist. When an error occurs in the comparison, you can locate the problem as follows :

  • An error at solid or shell level means that the geometric translation failed.
  • An error at product level means that a sub-assembly translation failed.
  • An error at instance level means that a component is misplaced.

The error at the lowest level gives the relevant information. It is the first error that appears in the report file:

  • An error at solid or shell level involves an error for corresponding product.
  • An error at product level involves an error for every product including instances of it.

External references

For the exchange of large assemblies, we recommend that you use external references, using several small files instead of one large file (this will reduce memory problems). Using PLMBatch-DXF-IGES-STEP (with external references) on very large assemblies avoids even more memory problems.

See About The Structures for more information.

Possible problems at import

  • If a solid is not created although the import of the STEP file is successful, with no KO faces, try an interactive Join on the Shell.
  • If the import of the STEP file is successful with no KO faces, but some geometries are missing , check the report and error files for NS (Non supported) elements, and consult the list of Supported Entities.
  • If you receive a Low memory state warning message and your STEP file is not totally converted, there is not enough memory to convert the file completely and all the remaining entities are skipped.
  • STEP interfaces import only STEP files with long names and do not support short names( out-of-date way to reduce the size of STEP files, available in V4). Ask your suppliers to send you only STEP files with long names.

At Export

Export from DMU

DMU allows scaling and mirroring while positioning assembly components. Such a position of instance of component cannot be exported to STEP (the position should be a translation and/or a rotation):

  • This issue is detected when you export the assembly to STEP.
  • Check the err file. An error message like
    <E> The instance '00200-411-21' of the product '00200-411-37' was 
        incorrectly positioned by Mirroring  
        <E> The instance '00200-411-21' of the product '00200-411-37' was 
        incorrectly positioned by Scaling
    means the export is wrong, one instance is not correctly positioned.
  • Remove the components positioned by mirroring or scaling and replace them by standards products before exporting.

Possible problem at export
The .rpt file reports that there are one or several KO Faces or the .err reports that an invalid Body has been detected. There are two possible reasons:
  • A bad representation
  • Or a bug in the STEP code.
To check the representation is OK, use the usual tools such as cleaners, connection checkers, and make sure there is no major errors. A internal check is done while exporting and a line is added to the .err to warn if the Body is invalid.