Interpret NX log files
Interpret the 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 imported NX 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
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
).
Interpret the 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 the 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.