GRBL 1.1 Error 9

GRBL 1.1ErrorPosition is kept

The controller is in an alarm or jog state, so it refused the G-code.

Position is kept. An error means the controller refused that one line or command, so nothing moved for it. (Hamrun's reading)
What to do
  1. Look for the alarm that came before this error: that's the real problem.
  2. Fix that, then unlock ($X) or home ($H).
What users reported CLAIMED · forum and issue reports, not official
  • Repeated Alarm 3 and Error 9 mid-cut on a 3018 Pro. First blamed on electrical noise; the real cause was the cable chain nudging the Z limit switch. (one owner's report) r/hobbycnc thread, Jul 2026
Official GRBL 1.1 message: “G-code commands are locked out during alarm or jog state.” source

Got a different message?

Paste it into the decoder. Hamrun's editor checks your G-code before you run it, so a toolpath that leaves the machine's travel or a missing feed rate is caught before the machine stops. Have the whole file? Check it here, free: it finds the line that triggers this, and the file never leaves your computer.

Related codes

  • grblHAL Error 9: The controller is in an alarm or jog state, so it refused the G-code.
  • FluidNC Error 9: The controller is in an alarm or jog state, so it refused the G-code.
  • Grbl_Esp32 Error 9: The controller is in an alarm or jog state, so it refused the G-code.
  • uCNC Error 9: The controller is in an alarm or jog state, so it refused the G-code.

Official text copied from the GRBL 1.1 source on 2026-11-01. Steps and the position answer are Hamrun's reading unless marked “firmware says”. User reports are labelled CLAIMED.