Log file names

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:

For IGES

Import translation

.alias2iges (filename.alias2iges)

Export translation

.iges2alias (filename.iges2alias)

For VDAIS

Import translation

.alias2vdais (filename.alias2vdais)

Export translation

.vdais2alias (filename.vdais2alias)

For C4

Import translation

.alias2c4x (filename.alias2c4x)

Export translation

.c4x2alias (filename .c4x2alias )

For NX

Import translation

.alias2unigraphics (filename .alias2unigraphics)

Export translation

.unigraphics2alias (filename .unigraphics2alias)

For JAMA-IS

Import translation

.alias2jamais (filename.alias2jamais)

Export translation

.jamais2alias (filename .jamais2alias)

For Granite

Import translation

.alias2granite (filename .alias2granite )

Export translation

.granite2alias(filename .granite2alias)

For STEP

Import translation

.alias2step (filename.alias2step)

Export translation

.step2alias (filename step2alias)

For CAI

Import translation

.alias2catia (filename.alias2catia)

Export translation

.catia2alias (filename .catia2alias)

For TC VisProducts

Import translation

.alias2jt (filename.alias2jt)

Export translation

.jt2alias (filename.jt2alias)

SAT format

To view STEP log files

1. Choose Utilities > Errlog to view these messages.

   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.

Viewing IGES log files

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.

NX log files

Translation log file

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.

Short log file

If you have chosen to use a short log file via the interface options, the log file will contain:

• the pathname of the importedNX part file and the name of the current Alias stage into which the NX part file is being imported.
• the contents of the NX part file. This is a table that documents the number of each type of NX entity in the file. This table includes all entities in the NX part file.
• any information, warning, or error messages that may occur during the translation.

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.

Extended log file

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 Detailed Entity Mapping Report. This report contains a mapping description line for each entity processed.

The mapping description line in an extended import log file contains:

• the NX entity type name (for example, BsplineSurface)
• the NX entity’s user id (for example, WHEEL, or <NONE> if the entity does not have a name)
• the NX entity instance identifier
• the string converted to, indicating that the following information pertains to the Alias entity
• the Alias entity type name (for example, Trimmed Surface)
• the Alias node name (for example, WHEEL or node#50 in the case of a NX entity name of <NONE>).

Interpret an export log file

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.

Short log file

If you have chosen to have a short log file via the interface options, the log file will contain:

• the name of the current Alias stage from which the model was exported (or the name of the Alias Wire file if the command line interface was used) and the pathname of the exported NX file
• any Information, Warning, or Error messages that may occur during the translation
• a table that documents the number of each type of Alias entity converted or not converted to an NX entity.

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.

Extended log file

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 Detailed Entity Mapping Report which contains a mapping description line for each entity processed.

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.