About the Report File

Report Files

The report file gives you information about the import or export, and helps you solve problems. Always check the report file after a conversion: Some problems may have occurred without been visually highlighted.

At Import

After importing DXF/DWG files, the system generates a report file (name_of_file.rpt) where you can find references about the quality of the transfer. This file is created in a location referenced by:

the CATUserSettingPath USERPROFILE variable on NT. Its default value is Profiles\user\Local Settings\Application Data\Dassault SystemesCATReport on NT (user being you logon id)
the HOME variable on UNIX. Its default value is $HOME/CATReport on UNIX.

In this report file (name_of_file.rpt), you will find information about:

The file imported
The transfer options used
The mappings used,

And messages:

Status messages about eventual transfer problems for a given element.
Information messages written by the support teams.

Example of a report file:

E:\tmp\MySettings\CATReport\DxfImport1.rpt
Input: DxfImport1.dxf
Output: DxfImport1.CATDrawing
~~~~~~~~~~~~~~~~~~~~~~~OPTIONS~~~~~~~~~~~~~~~~~~~~~~
Drafting Standard              : ISO
DXF Standard                   : DXF
Unit of the file               : Automatic
Paper Spaces in Background     : Disabled
Keep Model Space               : Disabled
Create end points              : Never
Convert dimensions as          : Exploded Geometry
Color to thickness             : Disabled
~~~~~~~~~~~~~~~~~DETAILED CONVERSION~~~~~~~~~~~~~~~~~
Message types: <E> = Error, <W> = Warning, <I> = Information<W> 
Some elements may be invisible because they are in an invisible layer.
They can be seen with activating the filter named Invisible Imported Layers
<W> Type "insert" Identifier "137" : This element was transferred partially
<W> Type "insert" Identifier "13D" : This element was transferred partially
<W> Type "insert" Identifier "13E" : This element was transferred partially
<W> Type "insert" Identifier "13F" : This element was transferred partially
<W> Type "insert" Identifier "145" : This element was transferred partially
<W> Type "insert" Identifier "146" : This element was transferred partially
<W> Type "insert" Identifier "147" : This element was transferred partially
~~~~~~~~~~~~~~~~~~AUTOMATISATION~~~~~~~~~~~~~~~~~~~~
Format : 
Imported Details -> A1 ISO
Model -> A1 ISO
Unit : Millimeter (mm)
~~~~~~~~~~~~~~~~~~~USED MAPPINGS~~~~~~~~~~~~~~~~~~~~
For Line Types:
CONTINU -> 1
CONTINUOUS -> 1
AXES -> 7
For Text Fonts:
EUCSYMB -> SSS4
=====================================================
~~~~~~~~~~~~~~~~~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  |  
------------------------------------------------------------
| arc           |  156 |    0 |    0 |     0 |     0 |     0 | 
| block         |   50 |    0 |    0 |     0 |     0 |     0 | 
| circle        |   21 |    0 |    0 |     0 |     0 |     0 | 
| dimension     |   80 |    0 |    0 |     0 |     0 |     0 | 
| insert        |   43 |    0 |    0 |     0 |     7 |     0 |
| layer         |    2 |    0 |    0 |     0 |     0 |     0 |  
| layout        |    1 |    0 |    0 |     0 |     0 |     0 |
| line          | 4639 |    0 |    0 |     0 |     0 |     0 |
| point         |  356 |    0 |    0 |     0 |     0 |     0 |  
| polyline      |  408 |    0 |    0 |     0 |     0 |     0 |
| text          |  264 |    0 |    0 |     0 |     0 |     0 | 
------------------------------------------------------------  
|  Result       | 6020 |    0 |    0 |     0 |     7 |     0 | 
------------------------------------------------------------ 
====================================================== 
Transcription time in seconds: 5.289000

The first lines

Indicate:

The name and path of the input file
The name of the input
The name of the output.

OPTIONS

Lists the options used in the settings.

DETAILED CONVERSION

Lists the status messages.

Syntax


Message Type	Element Type	Identifier	Element Status/Information Text
<E>	Type hatch	Identifier 8434	This element was not transferred

Message Type

Either Error, Warning or Information:

Error means that there is a failure.
Warning means that there may be a failure.
Information informs you of the possible cause of failure.

Element Type

Type of the DXF/DWG element processed.

Identifier

Hexadecimal number referencing the DXF/DWG element processed.

Element Status/Information Text

Informative part of the message.

AUTOMATISATION

Lists the format and unit chosen.

USED MAPPINGS

Lists the mappings used in that operation for the line types and the fonts.

Notes:

The mappings can be changed. See About Standards for more information.
Only those actually used are listed.
The report file does not yet indicate whether the mapping is the default one or a customized one.
There is no information yet about an automatic Thickness/Thickness mapping.

CONVERSION SUMMARY

Lists the conversion results.

The last line

Gives the Transcription time.

At Export

After exporting data to DXF/DWG files, the system generates a report file (name_of_file.rpt) where you can find references about the quality of the transfer. This file is created in a location referenced by:

the USERPROFILE variable on NT. Its default value is Profiles\user\Local Settings\Application Data\Dassault Systemes\CATReport on NT (user being you logon id).
the HOME variable on UNIX. Its default value is $HOME/CATReport on UNIX.

In this report file, you will find information about:

The result
The transfer options used

And messages:

Status messages about eventual transfer problems for a given element.
Information messages written by the support teams.

Example of a report file:

E:\tmp\MySettings\CATReport\DxfExportPicturePattern.rpt 
Input: DxfExportPicturePattern --- IN_WORK
Output: DxfExportPicturePattern.dxf
~~~~~~~~~~~~~~~~~~~~~~~OPTIONS~~~~~~~~~~~~~~~~~~~~~~
Exported sheets                : Only current
Version                        : DXF/DWG 2000
Export mode                    : Semantic
Export dimensions as Dimensions: Enabled
Export blocks                  : One level
Export layer mode              : Export layer number
Export Unit                    : Millimeter (mm)
~~~~~~~~~~~~~~~~~DETAILED CONVERSION~~~~~~~~~~~~~~~~~
Message types: <E> = Error, <W> = Warning, <I> = Information
~~~~~~~~~~~~~~~~~~~USED MAPPINGS~~~~~~~~~~~~~~~~~~~~
For CATIA Patterns Motif :
DrwPatternMotifConcret1 -> AR-CONC
===================================================== 
~~~~~~~~~~~~~~~~~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  |  
------------------------------------------------------------
| arc           |    2 |    0 |    0 |     0 |     0 |     0 |
| circle        |    1 |    0 |    0 |     0 |     0 |     0 |
| ellipse       |    1 |    0 |    0 |     0 |     0 |     0 |
| hatch         |    3 |    0 |    0 |     0 |     0 |     0 | 
| line          |   20 |    0 |    0 |     0 |     0 |     0 | 
 ------------------------------------------------------------
|  Result       |   27 |    0 |    0 |     0 |     0 |     0 | 
 ------------------------------------------------------------
======================================================
Transcription time in seconds: 0.749000

The first lines

Iindicate:

Where the report file has been created.
The name of the input.
The name of the output.

OPTIONS

Lists the options used in the settings.

DETAILED CONVERSION

Empty at export.

USED MAPPINGS

Lists the mappings used during export, namely for the patterns.

CONVERSION SUMMARY

Lists the conversion results.

The last line

Gives the Transcription time.

Troubleshooting

Below are some information to solve errors.

The R of a radius dimension is a conglomerate of a P with a small \

The DXF model is probably the result of a graphic export. In this case, texts are no real texts but geometry.

In export/import loops, some line types are lost.

The mapping of the line types is not complete:

For line types between 1 and 8, there is an automatic mapping between AutoCAD and 3DEXPERIENCE line types. The line type is kept during export/import loops.
For line types over 8, there is no automatic mapping between AutoCAD and 3DEXPERIENCE line types. Those line types are exported to DXF with a continuous graphic representation and a name such as CATIA9, CATIA10, etc. Those names enable you to identify them in the DXF file.
You can enhance the mapping. See About Standards.

Problem of alignment of DIMtext to DIMline

This occurs while opening a DXF file created with ANSI standard using an ISO standard (or vice-versa). Select the required Drawing standard.

Inconsistency between the import of dimensions with the semantic preserving option (Convert dimensions as: Dimensions) and the import of dimensions with the graphic preserving option (Convert dimensions as: Details or Geometry

This is generally due to an inconsistency in the DXF/DWG file itself (the aspect is different in AUTOCAD14 and AUTOCAD2000). This happens with files that have not been generated with AUTOCAD. Usually, the graphic mode should be used, but only the author of the file can confirm it. The DXF/DWG file contains both data:

The semantic data is the definition of the dimension: its attach points and all the properties of the value, text, line, leaders, …, most of them inherited from the dimension style.
The graphic data is the resulting representation of the dimension, composed with lines, arcs, texts, gathered in an internal block.

Most of the time, the graphic and semantic data are consistent but nothing in the DXF/DWG format can insure that. The DXF import option lets you choose the data to use during the import. A way to check that the inconsistency comes from the DXF/DWG file itself is to open it in DraftSight. The graphic representation is first displayed. When pointing a dimension and moving slightly a point for example, the graphic representation is recomputed from the semantic data and may be completely different from the original one.

Proxy Entities

Proxy entities are found in a DXF/DWG files that are not generated directly by AutoCAD but by an application based on AutoCAD, e.g. AutoCAD Mechanical. This application manages applicative objects that are not included in the standard DXF format. These objects can be edited and manipulated only by the application that generated them, but for a compatibility purpose, a graphic representation can be associated to this object. This associated representation is optional and is named a Proxy (type ACAD_PROXY_ENTITY). During import the proxy is converted into a graphic block that is imported as a Drawings detail instantiated at the place of the proxy. It can be edited like any detail.

Hatches imported as geometry

The result of import is a geometry instead of a filled area.The original DXF/DWG file does not contain real hatches but geometry or blocks.

Note: Real hatches are mapped automatically.

Incorrect fonts

See About Standards to check the mappings.
Problems with accented characters
True Type fonts on Windows provide the same fonts in your system and AUTOCAD.
Check the Report file in order to identify the fonts that were mapped to default or incorrectly mapped, and correct the DXF standard in consequence.
Texts are larger than their frame. Check the ratio in the TextFontMapping section of the mapping.

Incorrect lines types

DXF lineTypes become CONTINUOUS:

See About Standards to define the mapping between the line types you use in AutoCAD and the line types you will associate in Drawings.
The mapping between DXF and Drawings line types is available in the Line Type Mapping section of the DXF standard.
Check the Report file in order to identify the line types that were mapped to default (continuous) or incorrectly mapped and correct the DXF standard in consequence.

Missing header

Arrows and rectangle are missing when importing a Text with Leader from AutoCAD. The width of the polyline is not correctly processed:

Arrow heads are not supported.
The rectangle will be imported by improving the mapping of thick DXF polylines in the corresponding section of the DXF standard with ThickPolylineMapping/CreateAreaFill and ThickPolylineMapping/MinThicknessForAreaFill. When the width of the polyline is not null:
- CreateAreaFill=yes authorizes the area fill creation. In this case, if width is greater than the value of MinThicknessForAreaFill, an area fill that represents the exact geometry of the thick polyline is created.
- CreateAreaFill=No, or if width is lower than the value of MinThicknessForAreaFill, the lines and arcs are created with a line thickness mapped from the polyline width.

The value taken for the width is the greater one of startWidth or endWidth for each segment of the polyline. The standard values of the parameters above will avoid the missing rectangle. The report file indicates how the thick polylines are mapped.

Notes:

When an area fill is created, the linetype of the polyline is not taken into account. This applies only when the width is greater than the value of MinThicknessForAreaFill given in the DXF standard.
When no area fill is created, in the case of polyline with constant width, arcs or lines will be created for each segment, but no Drawings polyline.

Missing elements

If some elements are missing, make sure that the All Visible or the None filter is activated and restart the export.

Unexpected visible entities

All DXF/DWG invisible layers are gathered in a filter named Invisible Imported Layers.
All DXF/DWG visible layers are gathered in a filter named Visible Imported Layers.

If the expected entities are not visible, activate the Visible Imported Layers filter, or if too many entities are visible, activate the Invisible Imported Layers filter.

Small entities

When importing a DXF/DWG file, the display of small entities may depend on zoom factor. To see the complete Drawing regardless of their size, switch the value of Level of detail/static to zero.

Modified coordinates of points

In export/import loops, coordinates of points have changed:

The export does not yet support views.
The geometry of each view is transferred as seen in the input sheet axis system.

In this case, the coordinates that were seen in the view axis system are not kept: they are given in the sheet axis system.

Too small or too large an imported file

A DXF/DWG file does not contain its units. You must enter the unit used for the creation of the file to import it at the correct scale.

Unexpected exported scale

You have exported a view with a scale 2:1, with geometry in it. The result is not a view with a scale 2:1 but geometry twice as big as the input geometry.

The export does not yet support views. The geometry of each view is transferred as seen in the input sheet axis system. In this case, the scale of the view has been applied to the geometry.

Curve tolerance

When working with V4, if you open a DXF or DWG file created in Drawings, you need to set the curve tolerance to 0.0001 (0.1 as default).

Multi-sheet Drawing

Multi-sheet drawing export has some limitations:

When there are several sheets, the name of the file really created is not that entered by the user in the Save as dialog box, since it is concatenated with that of the sheet. Therefore, it is not possible to check if a file with the same name already exists and any existing file will be overwritten without warning.
If one of the sheets contains no geometry, no DXF file is created.
The number of characters of the name of the result file is limited to 150.
If the name of a sheet contains one of the following characters \ / : * ? " < > ¦ . £ $ % ^ & ! # ~ @ ; or a blank space, the character will be replaced with _ (underscore).

Kanji and Unicode Fonts

Exported Kanji or unicode characters may be missing or displayed incorrectly after opening the DXF/DWG file in the receiving system. In order to visualize them, edit the the text style STANDARD in this system and associate the font associated to this style to an unicode font.

Code Pages

DBCS (Double Byte Character Set) Supported Code Pages are:

932 (Japanese)
936 (Simplified Chinese)
949 (Korean)
950 (Traditional Chinese).