Siemens nx журнал ошибок

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:

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.

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.

Now that recording is under way, choose Edit -> Object Display… from the menu, pick the solid body of interest, and pick a new display color. OK the changes and then stop the journal recordingTools -> Journal -> Stop recording.

Time to test out the journal. Change the color of the solid body, or perform an Undo to get the original color back; now navigate to Tools -> Journal -> Play… and browse to your new journal file. Select your journal from the list and press the Playbutton. After a short pause, your solid body will change to the color you picked when you recorded the journal.

Option Strict Off
Imports System
Imports NXOpen
 
Module NXJournal
Sub Main
 
Dim theSession As Session = Session.GetSession()
Dim workPart As Part = theSession.Parts.Work
 
Dim displayPart As Part = theSession.Parts.Display
 
' ----------------------------------------------
'   Menu: Edit->Object Display...
' ----------------------------------------------
Dim markId1 As Session.UndoMarkId
markId1 = theSession.SetUndoMark(Session.MarkVisibility.Invisible, "Start")
 
theSession.SetUndoMarkName(markId1, "Class Selection Dialog")
 
Dim markId2 As Session.UndoMarkId
markId2 = theSession.SetUndoMark(Session.MarkVisibility.Invisible, "Class Selection")
 
theSession.DeleteUndoMark(markId2, Nothing)
 
theSession.SetUndoMarkName(markId1, "Class Selection")
 
theSession.DeleteUndoMark(markId1, Nothing)
 
' ----------------------------------------------
'   Dialog Begin Edit Object Display
' ----------------------------------------------
' ----------------------------------------------
'   Dialog Begin Color
' ----------------------------------------------
Dim markId3 As Session.UndoMarkId
markId3 = theSession.SetUndoMark(Session.MarkVisibility.Visible, "Edit Object Display")
 
Dim displayModification1 As DisplayModification
displayModification1 = theSession.DisplayManager.NewDisplayModification()
 
displayModification1.ApplyToAllFaces = False
 
displayModification1.ApplyToOwningParts = False
 
displayModification1.NewColor = 103
 
Dim objects1(0) As DisplayableObject
Dim body1 As Body = CType(workPart.Bodies.FindObject("BLOCK(0)"), Body)
 
objects1(0) = body1
displayModification1.Apply(objects1)
 
displayModification1.Dispose()
' ----------------------------------------------
'   Menu: Tools->Journal->Stop Recording
' ----------------------------------------------
 
End Sub
End Module

Hand Editing the Journal:
The reason that the journal in its current state will end in a error message when applied to a different file is that your journal is looking for the exact solid that you selected when the journal was recorded. This behavior is referred to as ‘selection stickiness’ and its removal is one of the main reasons for hand-editing journal code. You can greatly increase the usefulness of your code by replacing the hard coded reference to a specific object with a more general selection routine.

Below you will find the same script without the useless undo marks and with the selection stickiness removed.  This journal can now be used on various files to change the selected solid body’s color.

Option Strict Off
 
Imports System
Imports NXOpen
Imports NXOpen.UF
Imports NXOpenUI
 
Module NXJournal
Sub Main
 
Dim theSession As Session = Session.GetSession()
Dim workPart As Part = theSession.Parts.Work
Dim displayPart As Part = theSession.Parts.Display
Dim ufs As UFSession = UFSession.GetUFSession()
 
Dim markId3 As Session.UndoMarkId
markId3 = theSession.SetUndoMark(Session.MarkVisibility.Visible, "Edit Object Display")
 
Dim displayModification1 As DisplayModification
displayModification1 = theSession.DisplayManager.NewDisplayModification()
displayModification1.ApplyToAllFaces = False
displayModification1.ApplyToOwningParts = False
displayModification1.NewColor = 103
 
Dim objects1(0) As DisplayableObject
'Dim body1 As Body = CType(workPart.Bodies.FindObject("BLOCK(0)"), Body)
Dim body1 As Body = SelectSolid()
objects1(0) = body1
displayModification1.Apply(objects1)
displayModification1.Dispose()
 
End Sub
 
Function SelectSolid() As Body
 
    Dim ui As UI = ui.GetUI
    Dim message As String = "Select solid body"
    Dim title As String = "Selection"
 
    Dim scope As Selection.SelectionScope = Selection.SelectionScope.WorkPart
    Dim keepHighlighted As Boolean = False
    Dim includeFeatures As Boolean = True
 
    Dim selectionAction As Selection.SelectionAction = _
       Selection.SelectionAction.ClearAndEnableSpecific
 
    Dim selectionMask_array(0) As Selection.MaskTriple
    With selectionMask_array(0)
       .Type = UFConstants.UF_solid_type
       .Subtype = 0
       .SolidBodySubtype = UFConstants.UF_UI_SEL_FEATURE_SOLID_BODY
    End With
 
    Dim selectedObject As NXObject = Nothing
    Dim cursor As Point3d
 
    ui.SelectionManager.SelectObject(message, title, scope, _
                                    selectionAction, includeFeatures, _
                                    keepHighlighted, selectionMask_array, _
                                    selectedObject, cursor)
 
    Dim solid As Body = CType(selectedObject, Body)
 
    If solid Is Nothing Then
       Return Nothing
    End If
 
    Return solid
 
End Function
 
End Module

Join Eng-Tips^® Today!

Join your peers on the Internet’s largest technical engineering professional community.
It’s easy to join and it’s free.

Here’s Why Members Love Eng-Tips Forums:

• Talk To Other Members
• Notification Of Responses To Questions
• Favorite Forums One Click Access
• Keyword Search Of All Posts, And More…

Register now while it’s still free!

Already a member? Close this window and log in.

Join Us             Close