M-code Reference

Check auxiliary-function commands, controller notes, and safe sequence expectations for M codes.

모든 도구 영구 무료

Program stop.

Optional stop.

Spindle clockwise on.

Spindle counter-clockwise on.

Spindle stop.

Tool change command.

Coolant on.

Coolant off.

Spindle orientation.

End program and rewind.

Subprogram call.

Subprogram return.

Reference entry for M02.

Reference entry for M07.

Reference entry for M10.

Reference entry for M11.

Reference entry for M13.

Reference entry for M14.

Reference entry for M16.

Reference entry for M17.

Reference entry for M21.

Reference entry for M22.

Reference entry for M23.

Reference entry for M24.

Reference entry for M41.

Reference entry for M48.

Reference entry for M60.

Reference entry for M61.

Reference entry for M62.

Reference entry for M63.

Reference entry for M64.

Reference entry for M65.

Reference entry for M66.

Reference entry for M67.

Reference entry for M68.

Reference entry for M69.

Reference entry for M80.

Reference entry for M81.

Reference entry for M82.

Reference entry for M83.

Reference entry for M84.

Reference entry for M85.

Reference entry for M88.

Purpose

M codes control state changes that can affect safety, restart logic, and machine-side devices. Use the reference to verify whether coolant, spindle, chuck, pallet, or optional-stop behavior is truly what the team assumes. The useful output is a safer program sequence, not just a command definition.

  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

Sequence mistakes are more dangerous with M codes than with pure geometry codes. Verify what happens before and after the command, whether the controller requires extra conditions, and how the machine should restart if the operation stops mid-cycle.

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

M-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.

이 글이 도움이 되었나요?

관련 도구

현재 작업 흐름에 맞는 도구를 함께 확인하세요.