TURNMATE / TECHNICAL GUIDE · Updated 2026-10-28
What a CNC lathe G-code checker can and cannot verify
Static checks can flag selected issues in text and entered project data. They cannot fully simulate the controller, machine structure, fixtures, workpiece, tooling, and cutting process. Passing a check does not mean a program is safe to run.
What static checking can inspect
TurnMate’s current checker parses program blocks and tracks some modal state. It checks selected program structure, cycle references, arc geometry, unit/feed/spindle risks, and unsupported codes. Project checks may also use entered machine data, such as a maximum spindle speed, to flag selected conditions.
The checker only knows the code, rules, and project information it receives. Incorrect entries, machine-parameter differences, unparsed macros, vendor extensions, PLC logic, and physical machine state can fall outside its scope.
A 2D toolpath view is not machine simulation
A 2D view draws selected profile and path information to help review visible geometric or motion relationships. It does not model full machine kinematics, chuck/fixture/tailstock solids, turret interference, servo dynamics, material deformation, or cutting forces. It cannot prove that a collision will not occur.
Four layers of verification
Treat an app result as one part of a verification chain, never as a release decision by itself:
- Static text review: conditions visible to implemented rules and entered project fields.
- Controller graphics or simulation: the target controller/machine interprets cycles under its configuration.
- Machine dry run and single block: the operator controls feed and spindle according to the machine builder’s procedure.
- Trial cut and first-article measurement: confirm actual dimensions, finish, workholding, and tool condition before production.
How to respond to a warning
Read the referenced line and project field, confirm the control’s interpretation in its manual, then have a programmer review coordinates, modal state, tooling, and workholding. Do not add code blindly just to remove a warning, and do not treat “no warnings” as “no risk.”
Review checklist
- Verify control series/version, units, coordinate mode, work zero, and offsets.
- Check stock, workholding, chuck/tailstock, tool geometry, and clearance.
- Review canned cycles, macros, modal states, and vendor extensions in the target manual.
- Complete controller graphics/simulation, dry run, single block, and first-article measurement.
Sources and scope
- FANUC CNC Technical Support — Manufacturer channel for documentation matching a particular control family and configuration.
- FANUC Series 0i-TC Operator’s Manual B-64114SP/01 (public mirror) — Its safety section calls for checking input data and conducting a trial run; confirm the current machine-builder manual.
- Haas Lathe Operator’s Manual — Haas controller documentation only; it does not replace another control’s manual.