A/B/C Model LCD Messages

A/B/C Model Error Codes

E49 – Tracking Roller Failed

This error occurs only during the initial homing and measurement routine before the carving.  It occurs when STOP is pressed during “Check Tracking Roller” error message.  This error is shown because of out of limit numbers when measuring the length of the board.

A/B/C Model Error Codes

E48 – Waiting on Motion While Servoing Disabled

Motion was requested in software when the X/Y/Z servos were disabled.  The machine will report “motion flush w/o servo”, then throw error E48 to the screen when the user presses a key.  Cycle the machine power and retry the project.  If the error persists, record the seven digit error code and contact CarveWright customer support.

A/B/C Model Error Codes

E44 – User Calibration Failure

During the user “Sensor” calibration, the board cut/edge test failed to perform within its tolerances.  The machine is told to cut a small (0.050″ or so) slice from the notches it puts in the board with the 3/8″ bit.  The board sensor re-reads the slice and checks if the machine cut the proper amount.  If

A/B/C Model Error Codes

E34 – Back Roller Fault

While searching for the back edge of the board, the machine is waiting for the back roller to release and then activate the board sensor to find the edge.  The “Back Roller Fault” occurs when the front roller releases before the back roller indicating that the back roller is actually stuck.  Go to the “Stuck

A/B/C Model Error Codes

E33 – Front Roller Fault

While searching for the front edge of the board, the machine is waiting for the front roller to release and then activate the board sensor to find the edge.  The “Front Roller Fault” occurs when the back roller releases before the front roller indicating that the front roller is actually stuck.  Go to the “Stuck

A/B/C Model Error Codes

E32 – Tracking Sensor Fault

This error occurs only during the initial homing and measurement routine before the carving.  It occurs when the measured backlash on the X–drive is too large or movement was not detected.  It most likely occurs when there is an issue with the board that causes tracking problems.  Go to the “Possible Board Problem” message section

Scroll to Top