Check-Mate for NX Join
Join Diameter Check.
Every fastener’s head-side and tail-side hardware, checked against the fastener diameter by hardware type. Runs as a Check-Mate test or as a plain NX journal, on real FAS objects in the Join container.
Download checker 1.0.2Verification passing on NX 2606.5001 · 2026-10-02
The rule, by hardware type.
The fastener’s diameter is compared with each head-side and tail-side part. Two diameters within 0.0001 in of each other count as equal.
| Hardware type | Passes when | No diameter listed |
|---|---|---|
| BLOCK | diameter is greater than the fastener | Pass |
| NUT | diameter equals the fastener | Could not check |
| RING | diameter is greater than the fastener | Could not check |
| SPACER | diameter is greater than the fastener | Pass |
| WASHER | diameter is greater than the fastener | Pass |
Any other hardware type is reported not applicable. A number the rule needs but cannot find is reported could not check, a Check-Mate warning, and is never counted as a pass. The rules in full, and the decisions behind them.
Where the numbers come from.
The FAS object
NX Join keeps each fastener as a PointJoin feature. Its pin and its head-side and tail-side parts come back by name and type. No diameter is stored on the join.
The hardware library
So the checker reads diameters where the Join dialog does: the Hardware.xlsx beside each part, the Join XML database, and the part family table where a row says mapsTo:.
The whole assembly
It searches the work part and every component, fully loading each one first, so FAS objects in a Join container are found even when the assembly opened partially loaded.
Seen working, not described.
36 fasteners built with the NX Join API in a real Join container: every row of the acceptance criteria, mixed stacks, metric libraries, the libraries NX ships, and the cases a requirement leaves open.