3018-PROVer V2 full model; DO NOT conflate original PROVer, 3018-Pro or V2 Lite. Firmware revisions vary.
Fault codes and applicability
GRBL alarms and errors belong to installed controller firmware. Generic GRBL v1.1 codes are not a confirmed code table for every PROVer V2 firmware.
| Code | Manufacturer-defined meaning or evidence limit |
|---|---|
| GRBL alarm codes | Generic firmware diagnostics; supported code list must be matched to installed firmware |
8 repair questions for this model
Each individual guide links a specific symptom or fault code to checks, expected results, possible fixes, and a post-repair test.
A USB connection fault is commonly related to the physical cable, CH340/CH341 serial driver, the selected COM port or a second program holding the port.
A GRBL homing alarm does not by itself identify a motor defect. Limit switch status, axis travel, wiring and enabled homing settings must be checked against the exact V2 board/firmware.
A spindle that stays still can reflect emergency-stop state, spindle power connection, a command not enabling the motor or a controller/power-board fault.
A job that stops or prints “Reset to continue” needs the exact alarm/message captured; losing USB communication and tripping a limit switch have different fixes.
An engaged emergency-stop circuit can prevent movement or keep the controller in alarm. First confirm the stop is released and inspect external connections.
The V2 manual specifies a dedicated Probe port and Candle Z-probe setup. A wrong connection or unsuitable probe parameter can cause a failed touch-off.
For a stationary X, Y or Z axis, inspect its labeled motor and limit connectors and look for mechanical binding before changing GRBL settings.
GRBL alarms depend on the controller firmware and triggered limit inputs. Capture the full ALARM number before deciding whether it is travel, wiring or homing.