NX Automations · Check-Mate test
Join Diameter Check
Download 1.0.4Checks every Join fastener’s head-side and tail-side hardware against the fastener diameter, by hardware type, and flags each one that does not fit.
Verification passing on NX 2606.5001 · 2026-10-03 · repo b9f63ea
For the people who asked
Each has a default today and a setting in the Customize dialog, so an answer changes a setting, not the code.
The requirement’s description says a washer must be greater than the fastener; its acceptance criteria also pass a washer with no diameter. The checker follows the acceptance criteria. Is that the intent?
Setting: Washer Must Have a Diameter switches to the description reading.
The requirement does not say. The checker reports it as could not check (a warning), never a pass and never a fail. Should it fail instead?
BLOCK, NUT, RING, SPACER and WASHER are taken from the hardware type in the library (the Type or Hardware Type column), matched as a whole word, any case. Is that the field meant by nomenclature?
Setting: Type Aliases maps other types onto the five, e.g. Collar=NUT.
Types other than the five are reported not applicable rather than judged. Should any of them follow one of the five rules?
Setting: Type Aliases.
Other defaults, stated so they can be changed on purpose
The pin’s row in the hardware library. If the pin has no diameter there, the Diameter of its specification in the Join XML database. If neither has one, every part on that fastener is could not check.
Setting: XML Databases lists the hardware.xml files to read; Extra Folders adds folders searched for Hardware.xlsx.
Within 0.0001 in. Exact comparison fails a 6.35 mm nut on a 1/4 in fastener, because 6.35 / 25.4 is not exactly 0.25 in floating point; the verification shows it.
Setting: Equality Tolerance (in).
Point joins of the Fastener subtype (Join ID prefix FAS): the Fastener option of the Join Fastener command. Rivets and other point-join subtypes are left alone.
Setting: Join Subtypes, e.g. Fastener; Rivet.
Not yet covered
Verified on this project’s own test hardware library and the sample library NX ships, in native mode. Not yet run on a production hardware library or a Teamcenter-managed assembly. Hardware whose data source is Teamcenter Classification resolves only if the same names are in a Hardware.xlsx or XML database the checker can read; otherwise it reports could not check.