What the tool-table audit checks
Each non-comment line must contain a unique unsigned tool number T and pocket number P. The inspector accepts the documented axis offsets XYZABCUVW, diameter or compensation value D, lathe front and back angles I/J, and lathe orientation Q. It finds malformed or repeated words, missing required fields, duplicate tools and pockets, pockets above 1000, orientations outside 0–9, and non-ascending tool entries. Axis offsets may be positive, zero, negative, or omitted. A negative D is flagged for review rather than rejected because LinuxCNC also permits a small signed nominal-path or wear correction.
Using the baseline comparison
Use a previously reviewed table from the same machine and unit system. Exact tool numbers are the identity key. Added and removed tools stay separate; changed rows list every pocket, offset, diameter, lathe-geometry, and comment difference, with numeric deltas when both values exist. The comparison is blocked if either table contains a structural error, because duplicate tool numbers make matching ambiguous.
Manual, fixed, and random changers
LinuxCNC supports manual, fixed-location, and random-location workflows. The table format requires unique pockets. For a random changer, pocket 0 represents the spindle and pocket assignments can be rewritten as tools move. With the default non-random configuration, LinuxCNC preserves P but does not use it internally in the same way. Select the actual machine configuration; this page does not infer hardware behavior from the file.
Machine-safety boundary
A structurally valid table is not a verified setup. This page cannot establish which physical tool is in a pocket, whether an offset was touched off from the correct reference, whether machine units match, or whether diameter, nose radius, orientation, signs, fixtures, and compensation commands are safe. It does not edit a running controller. Back up the original file, compare values with the machine and setup sheet, reload only while the interpreter is idle, and verify compensation above the workpiece before cutting.
Frequently asked questions
Are T and P both required?
Yes. LinuxCNC documents both the unsigned tool number and pocket number as required fields. Axis offsets and tool geometry are optional.
Why is a negative Z offset not automatically an error?
The tool-table format permits positive, zero, and negative axis offsets. Their correct sign depends on the machine configuration and measurement convention, which cannot be inferred safely from the file alone.
Does normalized export preserve the entire original file?
No. It writes parsed entries in source order with canonical field order and attached remarks. Standalone comments, blank lines, original spacing, lowercase letters, and numeric spelling are intentionally not preserved. Use the analysis CSV when you need a full audit record, and review any normalized table as a new file.
Does this replace LinuxCNC tooledit?
No. It is a read-only browser audit and comparison tool. LinuxCNC’s own editor and controller-aware workflows remain responsible for applying and reloading tool data.
Primary references: LinuxCNC’s current Tool Table Format and compensation documentation and Tool Edit GUI guide.
Solve a lathe change-gear train · Validate G2/G3 arc geometry · Browse machining tools