G-code Reference

Look up common G-code functions, controller notes, and restart cautions in one place.

Tất cả công cụ miễn phí mãi mãi

Rapid traverse move.

Linear interpolation at feed rate.

Clockwise circular interpolation.

Counter-clockwise circular interpolation.

Select XY plane.

Metric units mode.

Return axis to machine reference.

Cancel cutter compensation.

Cutter compensation left.

Cutter compensation right.

Apply tool length compensation.

Work offset 1.

Coordinate rotation.

Cancel canned cycle.

Simple drilling cycle.

Peck drilling cycle.

Absolute programming mode.

Incremental programming mode.

Reference entry for G04.

Reference entry for G05.

Reference entry for G06.

Reference entry for G07.

Reference entry for G08.

Reference entry for G09.

Reference entry for G10.

Reference entry for G15.

Reference entry for G16.

Reference entry for G18.

Reference entry for G19.

Reference entry for G20.

Reference entry for G30.

Reference entry for G31.

Reference entry for G32.

Reference entry for G33.

Reference entry for G34.

Reference entry for G44.

Reference entry for G49.

Reference entry for G50.

Reference entry for G51.

Reference entry for G52.

Reference entry for G53.

Reference entry for G55.

Reference entry for G56.

Reference entry for G57.

Reference entry for G58.

Reference entry for G59.

Reference entry for G61.

Reference entry for G64.

Reference entry for G65.

Reference entry for G66.

Reference entry for G67.

Reference entry for G69.

Reference entry for G70.

Reference entry for G71.

Reference entry for G72.

Reference entry for G73.

Reference entry for G74.

Reference entry for G76.

Reference entry for G84.

Reference entry for G85.

Reference entry for G86.

Reference entry for G87.

Reference entry for G88.

Reference entry for G89.

Purpose

A reference is useful only when it shortens safe interpretation. Use it to confirm modal behavior, command scope, and controller caveats before copying code into production. It works best alongside a dry-run process and a review of offsets, tool data, and restart points.

  1. Confirm the actual part target, tool condition, and controller constraints first.
  2. Use the tool to build a reviewable baseline, not an unverified production extreme.
  3. Compare the output with machine limits, holder clearance, finish targets, and restart logic.
  4. After prove-out, tune one variable at a time and store the accepted rule with revision context.

How to interpret the result

This tool is most valuable when it helps the team answer three questions: Is the target clear? Is the process controllable? Can the result be repeated across shifts and machines? Whether the output is a chart, an estimate, or a program skeleton, it should be read together with machine capability, inspection method, tooling condition, and recovery expectations. That is what turns a convenient calculation into a usable production baseline.

Common risks and checks

The biggest risk is assuming a command works the same way across controllers or across restart scenarios. Use the reference to ask better questions: what mode is active, what parameters influence this code, and what safe block should surround it?

When the result disagrees with the shop floor, check units, defaults, controller assumptions, tool condition, and recovery steps before questioning the core math. Teams get the best value when they feed the prove-out result back into setup notes, revision logs, and shift handoff documents.

Visual reference

G-code Reference

Final recommendation

Put the tool inside a fixed engineering loop: establish a baseline, validate the first piece, tune one variable at a time, and freeze the accepted rule with context. That approach delivers repeatability instead of one-off numbers.

Bài viết này có hữu ích không?

Công cụ liên quan

Khám phá thêm công cụ phù hợp với quy trình này.

Thuật ngữ liên quan