ug_inspect

If you have an issue with loading a NX part file or want information about it without opening it in NX

Located in the “UGII_BASE_DIR/UGII/” directory lies an application “ug_inspect.exe“. When you run this application in a command prompt with a location and a part file, it returns more information about the file then you can ever get from within NX. This application has been around in NX for as long as I can remember but it still is not known widely.

Example: note: this is a single line, the web page shows the text wrapped

C:\Program Files\UGS\NX 3\UGII>ug_inspect.exe c:\myParts\myPartFile.prt

output from the “ug_inspect.exe -help”:

Usage: ug_inspect [<switches>] <filenames …>
where </filenames><filenames> are NX part file names, and
<switches> are optional command line arguments which may be
one of the following:
-help prints this message
-rm prints Record Manager partition
-cmod prints CMOD partition
-ess prints the Expresssion partition
-occ prints the Occurrences partition
-path prints Path partitions
-ps prints Parasolid partition(s)
-full prints all partitions
-trace prints tracing info as it reads the part
-cookies prints cookie and object id information
-refs prints most recent referenced part information
-all_refs prints all referenced part information
-scan scans for known part corruptions
-extract_all <part file> [<filename>]
-extract <id> <part file> [<filename>]
Extracts Parasolid transmit files – <id> is a
partition id number, <part fileɬ is a part file name,
and <filename>, if specified, is the filename without
extension to use for generating output file names.
If omitted this is generated from the part file name.
Use -extract_all for pre-v12 part files.
-release Just print release information about the part.

Since you can run this against individual files easily, but many files are teadious. I’ve created a batch script that you drop this script into a directory where NX parts are and run the script. It will then create a subdirectory with an output text file of each file it finds. Edit the script file to do more checks. Currently only the general ug_inspect is run. All the other options are commented out.

The general utility output will tell you a lot about the nx part file. The known corruptions is the best for quickly determining if there is a problem before trying to open in NX.

Output
Some of the information it returns is:

  • Save history: Each time it is saved, who saved it, verion of NX running, date it was saved, if it was renamed
  • Parasolid version
  • Entity types that exist and quantity of each
  • contains foreign data
  • contains compenents or not?
  • if it has pattern data
  • Unique part identifier
  • and many more pieces of output that I’m not sure what they are telling me

Download
Download the ug_inspect.bat file

Moved to nx-tools on Google Code

This website uses IntenseDebate comments, but they are not currently loaded because either your browser doesn't support JavaScript, or they didn't load fast enough.

Leave a Reply