簡體 繁體 Get the app ↗
Technical illustration: CNC lathe G-code list: find and review codes by function
Concept diagram for review and learning. It is not a controller simulation or an executable program.

TURNMATE / TECHNICAL GUIDE · Updated 2026-10-28

CNC lathe G-code list: find and review codes by function

A useful CNC lathe G-code list is more than a pile of code names. Organize codes by function, then check modal state and applicability in the manual for the exact control.

This is a category index, not an exhaustive list for every brand or model and not an executable program. The machine and control manuals take precedence.

Search by function

When reading a program, first group codes by role, then confirm their meaning in the target manual. Common entry points include motion/interpolation, coordinates and planes, tool compensation, spindle and cutting speed, feed, canned cycles, and program control. Meaning can depend on modal state and block context.

  • Motion and interpolation: positioning, linear/circular motion, and plane selection.
  • Coordinates and state: absolute/incremental, work offsets, units, and reference return.
  • Spindle and feed: fixed RPM, constant surface speed, feed per revolution/minute, and speed limits.
  • Turning cycles: roughing, finishing, threading, grooving, and drilling cycles specific to the control.
  • Program and auxiliary functions: flow, pause, end, and machine actions; M functions may be builder-defined.

Why generic lists mislead

Short code tables often omit groups, modal cancellation, options, units, and machine-builder PMC/PLC behavior. Code numbers are reused across brands, and turning and milling controls can differ. A context-free list is not a sound basis for program approval.

Turn an index into a review workflow

Record the exact control model and revision, then use the manual’s code table and relevant format, state, alarm, and safety sections. For cycles and macros, verify all parameters and referenced profiles; for spindle/feed, verify units, limits, and current modes. Flag uncertainty instead of guessing.

The role of static checks

Static checks can flag codes and states they understand, but may not cover builder extensions, macro variables, PLC signals, or full kinematics. Passing is not proof that code matches the installed control or is collision-free. Continue with controller graphics, machine simulation, dry run, and first-article procedures.

Review checklist

  • Use manuals for the exact brand, series, software, and machine-builder revision.
  • Check modal state, units, coordinates, and cancellation by function.
  • Confirm canned cycles, macros, and M functions against the installed machine.
  • Use controller-side validation and shop safety procedures, not an online list alone.

Sources and scope

Related reading

Programs and calculations must be independently verified by a qualified operator against the actual machine, controller manual, tool data, workpiece, and workholding. This guide is not a machining parameter recommendation or safety release.
View TurnMate on the App Store ↗