GRBL Alarm Codes

Below are some error/alarm codes that you might see on your machine. Not all of them are relevant or likely to occur on Carbide 3D machines, but we include them all here to be complete.

GRBL Alarm Code 1 - Hard limit

Hard limit has been triggered. Machine position is likely lost due to sudden halt. Re-homing is highly recommended. This should never happen on a Shapeoko or Nomad.

GRBL Alarm Code 2 - Soft limit

Soft limit alarm. G-code motion target exceeds machine travel. Machine position retained. Alarm may be safely unlocked. This should never happen on a Shapeoko Nomad.

GRBL Alarm Code 3 - Abort during cycle

This error indicates that the machine controller was reset while in motion. Machine position was likely lost due to sudden halt so you will need to reinitialize the machine to continue working.

GRBL Alarm Code 4 - Probe fail

The probe is not in the expected initial state before starting a probing cycle. This can occur in the following cases:

GRBL Alarm Code 5 - Probe fail

The probe did not contact the workpiece within the programmed travel. This can happen in a few cases:

GRBL Alarm Code 6 - Homing fail

This indicates that the machine was reset while a homing cycle was running. The machine position will be lost, but you can re-initialize the machine to clear this error.

GRBL Alarm Code 7 - Homing fail

Safety door was opened during homing cycle. This should never happen on a Shapeoko.

GRBL Alarm Code 8 - Homing fail

Pull off travel failed to clear limit switch. Carbide Motion does several checks to avoid this error so it is very rare in a Shapeoko or Nomad CNC machine.

See toubleshooting homing for debugging help.

GRBL Alarm Code 9 - Homing fail

Could not find limit switch within search distances. This indicates that one or more of the limit switches may be disconnected or malfunctioning.

See toubleshooting homing for debugging help.

GRBL Alarm Code 10 - Homing fail

Second dual axis limit switch failed to trigger within configured search distance after first. This can only occur on a Shapeoko 5 Pro in a few circumstances:

See toubleshooting homing for debugging help.