Join Diameter Check

Pure NX Open for Python: nothing to compile, no licence beyond NX Join and Check-Mate. Verified on NX 2606.5001.

As a Check-Mate test

1. Unzip. Put the diacheck folder somewhere NX can read, for example D:\nx_custom\diacheck. It holds an application folder: NXCheckers.json, the checker’s Python files and its Customize dialog (.dlx).
2. Point NX at it: set UGII_USER_DIR=D:\nx_custom\diacheck before NX starts, or add that folder to the custom_dirs.dat your site already uses.
3. Start NX and open the assembly. In Check-Mate’s Set Up Tests (search for it with Ctrl+Space) the test is under Join › Point Join › Fastener Hardware Diameter.
4. Add it to Chosen Tests. The Customize button beside the list opens its settings (below), for example the path of a hardware XML database. Then Execute Check-Mate Tests: failing fasteners are listed against their FAS object, and the full table goes to the listing window.

Without Check-Mate

With the assembly open, File › Execute › NX Open (Alt+F8) and choose run_diacheck.py. Same code, same table, plus a JSON report beside the part.

run_journal.exe run_diacheck.py -args D:\path\asm.prt D:\path\report.json
run_journal.exe ExecuteChecker.py -args D:\path\asm.prt D:\logs   (through Check-Mate, batch)

Telling it where your hardware library is

NX Join stores only the names of a fastener’s hardware. The checker reads the diameters from the same library the Join dialog reads: the Hardware.xlsx in the folder of each hardware part (found automatically), and Join XML databases, which you list in XML Databases in the Customize dialog. The diameter column is Diameter<Double:Length:in> (or mm); the type column is Type or Hardware Type.

Each fastener remembers where its hardware part was when it was placed. If the hardware library has moved since then, the checker reports those fasteners as could not check rather than guessing; list the library’s new folder under Extra Folders and it is found again.