Open a log file and interpret the data. Review this data to resolve problems in data transfer.
Learn the default file naming convention used in generating data transfer log files.
In most cases translators automatically create log files using a user-defined filename with a default filename extension. When storing format files the default file name extensions are as follows:
When retrieval is finished without errors, the following message is displayed:
STEP files retrieved successfully.
If there are errors in the retrieval, this message is displayed:
Problem Reading Step File, refer to log file and/or errlog for details.
The Alias errlog file and STEP logfile contain a specific error message for each problem entity that is encountered, along with the entity’s STEP ID and type.
Interpreting CATIA translation log files
The translation log file is produced during both import and export of CATIA files. This log file contains entity mappings, entity counts, and Information, Error, and Warning messages.
Interpreting the import log file
On import of a CATIA file, a translation log file is created in the same directory as the CATIA file. The file name of the log file is the same as that of the CATIA file with the extension.catia2alias added to it.
Interpreting the export log file
On export of a CATIA file, a translation log file is created in the same directory as the CATIA file. The file name of the log file is the same as the CATIA file with the extension .alias2catia added to it.
IGES stands for Initial Graphics Exchange Specification. IGES was the first attempt to make a neutral file format. This enables different systems to transfer data without the need of a specific translator for each system.
The first section of an IGES file typically describes the contents of a file. Each line of this section is displayed on the information line.
If there is more than one line in the section, you can browse the contents of the section after file retrieval is complete by using the prompt history window, or by viewing the comments section of the IGES logfile created by the retrieve process.
The Alias errlog file and IGES logfile contain a specific error message for each problem encountered.
Each error message includes the IGES entity type number and a Directory Section line number where the entity occurs. The errlog file is located at /usr/a1demo/errlog; you can browse it with any UNIX text editor (for example, vi or jot). The IGES logfile is located in the same directory as the retrieved IGES file.
Identifying IGES supported entities in log files
Learn more about the IGES entities supported on import by Alias.
All other entities with an entity use flag value (Definition) are ignored by the input translator.
Type | Form | IGES Entity | Alias Entity |
100 | 0 | circular arc | B-spline curve |
102 | 0 | composite curve | B-spline curves (group) |
104 | 0-3 | conic arc | B-spline curve |
106 | 1 | copious data | B-spline curve |
106 | 2 | copious data | polyline |
106 | 11 | copious data | polyline |
106 | 12 | copious data | polyline |
106 | 63 | closed area | triangle of mesh |
108 | 1 | plane | face |
110 | 0 | line | line |
112 | 0 | parametric curve | B-spline curve |
114 | 0 | parametric surface | B-spline surface |
116 | 0 | point | control vertex |
118 | 0-1 | ruled surface | B-spline surface |
120 | 0 | surface of revolution | B-spline surface |
122 | 0 | tabulated cylinder | B-spline surface |
124 | 0 | transformation matrix | |
126 | 0-5 | rational B-spline curve | B-spline curve |
128 | 0-9 | rational B-spline surface | B-spline surface |
130 | 0 | offset curve | B-spline curve |
140 | 0 | offset surface | B-spline surface |
141 | 0 | boundary entity | trim curve |
142 | 0 | curve on surface | trim curve |
143 | 0 | bounded surface | trimmed surface |
144 | 0 | trimmed surface | trimmed surface |
308 | 0 | subfigure definition | instance geometry |
402 | 7,16 | associativity instance | group |
408 | 0 | singular subfigure instance | instance geometry |
How to interpret NX log files.
The translation log file is produced during both import and export of NX part files. This log file contains Entity Mappings, Entity Counts, and Information, Error, and Warning messages.
How to interpret an import log file
On import of an NX part file, a translation log file is created in the same directory as the NX part file. The file name of the log file is the same as that of the NX part file with the extension .unigraphics2alias added to it.
If you have chosen to use a short log file via the interface options, the log file will contain:
If an error or problem occurs while processing an entity, the NX’s entity’s type name, user identifier name, and instance name are printed, followed by the error or warning message.
If you have chosen to have an extended log file produced, then the log file will contain the same information as the short log file, with the addition of:
The mapping description line in an extended import log file contains:
On export of an NX file, a translation log file is created in the same directory as the NX file. The file name of the log file is the same as the NX file with the extension .alias2unigraphics added to it.
If you have chosen to have a short log file via the interface options, the log file will contain:
If an error or problem occurs while processing an entity, the Alias entity’s type name and node name are printed, followed by the error or warning message.
If you have chosen to have an extended log file produced, then the log file will contain the same information as the short log file with the addition of:
Interpret an NX translation log
If the log file identifies an error during translation between Alias and NX in either direction, you can trace the information in the error message back to the problem geometry. In some cases once the piece of geometry has been isolated, the nature of the problem will be visually obvious and you will need only to delete or manually fix the surface in question.