Trouble Shooting Of Your CNC Machine

Does the CNC Connect in the ALARM Mode?

The SENDER software will be in the “ALARM” mode when the computer is first connected to the CNC. This is normal. The computer has no way of knowing where the CNC spindle is positioned in the cutting area, therefore it shows ALARM to let the operator know the CNC is not ready to be used.
If the CNC does not show “ALARM” when you have connected it, please check the:
Comm Port
Firmware
Controller
Hardware

Does your CNC successfully homeing?

To sync the computer with the CNC, the CNC will need to be homed. When you click the Home All button the CNC should move the Z axis up and down a couple of times, then move both X and Y to the home corner where the switches are located. If successful, the CNC will go from the ALARM mode to the READY (or IDLE) mode and is ready to setup and use. You will need to Home the CNC each time you power your CNC.
If the CNC does not home successfully, please check:
That there is power
Correct home switch operation
Correct controller connections
Set screws are tightened
Eccentric spacers are adjusted correctly
Other obstructions

Does your CNC jogging?

Jogging the CNC is when you move one or more axes to the desired location. There are settings for how far and how fast the axes will move.
If the CNC homes correctly, then it should be functioning correctly. Please make sure the CNC has successfully homed before jogging. You will be locked out of the jogging functions until the CNC is in the IDLE or home move.
If the CNC makes a low hum or clicking sound, it is probably jogging extremely slow. Check to make sure you are in the right units (millimeters or inches) and check the jog feed rate. Initial jog rates are typically 100 to 200 inches per minute (2500 to 5000 mm per minute)
If the machine does not seem to move, check the jog distance setting. If the setting is very small, then axis movement may not be noticeable.

Are there errors when you run a program?

We run a modified version of grbl1.1. When running a gcode the firmware will send an error code back to the SENDER to help us understand what wen wrong. The SENDER then gives a brief explanation of each error or alarm. All of the error codes and descriptions are listed below.
The error list can be found here: https://github.com/gnea/grbl/wiki/Grbl-v1.1-Interface
ERROR_CODES:
RUN Basic SENDER is currently sending a gcode program to Grbl
IDLE Grbl is in idle state and waiting for user commands
HOLD Grbl is on hold state. Click on resume (pause) to continue
ALARM The alarm is an emergency state. Something has gone terribly wrong when these occur. Typically, they are caused by limit error when the machine has moved or wants to move outside the machine space and crash into something. They also report problems if Grbl is lost and can't guarantee positioning, or a probe command has failed. Once in alarm-mode, Grbl will lock out and shut down everything until the user issues a reset. Even after a reset, Grbl will remain in alarm-mode, block all G-code from being executed, but allows the user to override the alarm manually. This is to ensure the user knows and acknowledges the problem and has taken steps to fix or account for it.
NOT_CONNECTED Grbl is not connected. Please specify the correct port and click Open.
CONNECTED Connection is established with Grbl

Do you have sudden stops without error messages?

Electrical interference, sometimes called electrical noise, can cause the controller to stop working. It can be hard to find as there can be many causes and it is not visible.
We spent a lot of time routing our wires to ensure that we reduce the risk of electrical noise. We recommend that you follow the manuals recommendation.

Here is a list of things to check for:
Tools or a refrigerator on the same circuit.
Dust collector system that is not grounded
Power cords close to the USB
Nest of wires (not neatly organized)
Loose or intermittent connection
It may be useful to try an isolate the cause. For example, run a project without the dust collection system or run the project without the spindle on. This may help find the root cause of the sudden stop.
If you are running the CNC with a laptop you will want to have it plugged in. Some laptops reduce the voltage to the communication port to save battery. You will also want not to make sure the comport is not going to sleep.

Is the cutting performance poor?

There are many reasons why CNC performance is not what we are expecting.
Creating a quality CNC project is complicated. The CNC, the gcode file, material and the cutter all play a part in the final results.

CNC 3D Printer

Getting more help

We want all our customers to be successful. If you have additional questions or cannot find the answer you are looking for, please contact us through email or by phone.
Email: helpdesk @mecitlabs.com
Phone number: +91 9000801731
Most of the time we will be in the shop. If we do not answer, please leave a message and we will get back to you as soon as we are available.
Also, look us up on social media.
Please include The CNC you have and the questions you have in the email or message. Pictures can be helpful and can be added to the email or texted to the phone number This will helps us serve you more efficiently.