Hi guys, i think my problem is similar to this one.
I am a complete beginer regarding CNC machines. The one i got is 3018 pro. After thinkering a bit with settings etc. Im getting a buzzing noise from motors, but machine is not moving accross any axis, or responding to comands. I am using UGS software.
The buzzing stops once I start homing, but it allways ends with alarms —
com.willwinder.universalgcodesender.AbstractController$UnexpectedCommand: An unexpected command was completed by the controller.
at com.willwinder.universalgcodesender.AbstractController.commandComplete(AbstractController.java:830)
[catch] at com.willwinder.universalgcodesender.GrblController.rawResponseHandler(GrblController.java:158)
at com.willwinder.universalgcodesender.AbstractController.rawResponseListener(AbstractController.java:851)
at com.willwinder.universalgcodesender.AbstractCommunicator.sendEventToListeners(AbstractCommunicator.java:222)
at com.willwinder.universalgcodesender.AbstractCommunicator.lambda$new$0(AbstractCommunicator.java:244)
at java.lang.Thread.run(Unknown Source)
Any chance you could help me with this one?
my settings are
0 = 10 (Step pulse time, microseconds)
$1 = 25 (Step idle delay, milliseconds)
$2 = 0 (Step pulse invert, mask)
$3 = 0 (Step direction invert, mask)
$4 = 1 (Invert step enable pin, boolean)
$5 = 0 (Invert limit pins, boolean)
$6 = 0 (Invert probe pin, boolean)
$10 = 115 (Status report options, mask)
$11 = 0.010 (Junction deviation, millimeters)
$12 = 0.002 (Arc tolerance, millimeters)
$13 = 0 (Report in inches, boolean)
$20 = 0 (Soft limits enable, boolean)
$21 = 1 (Hard limits enable, boolean)
$22 = 1 (Homing cycle enable, boolean)
$23 = 0 (Homing direction invert, mask)
$24 = 25.000 (Homing locate feed rate, mm/min)
$25 = 500.000 (Homing search seek rate, mm/min)
$26 = 250 (Homing switch debounce delay, milliseconds)
$27 = 1.000 (Homing switch pull-off distance, millimeters)
$30 = 1000 (Maximum spindle speed, RPM)
$31 = 0 (Minimum spindle speed, RPM)
$32 = 0 (Laser-mode enable, boolean)
$100 = 800.000 (X-axis travel resolution, step/mm)
$101 = 800.000 (Y-axis travel resolution, step/mm)
$102 = 800.000 (Z-axis travel resolution, step/mm)
$110 = 1600.000 (X-axis maximum rate, mm/min)
$111 = 1600.000 (Y-axis maximum rate, mm/min)
$112 = 100.000 (Z-axis maximum rate, mm/min)
$120 = 20.000 (X-axis acceleration, mm/sec^2)
$121 = 20.000 (Y-axis acceleration, mm/sec^2)
$122 = 20.000 (Z-axis acceleration, mm/sec^2)
$130 = 300.000 (X-axis maximum travel, millimeters)
$131 = 180.000 (Y-axis maximum travel, millimeters)
$132 = 45.000 (Z-axis maximum travel, millimeters)
Error 0 – STATUS_OK
All Good, This is an error code suggesting that there is NO error
Error 1 – STATUS_EXPECTED_COMMAND_LETTER
Gcodes should start with a Letter, what ever was just sent to GRBL did not
Error 2 – STATUS_BAD_NUMBER_FORMAT
The number part of the Gcode was invalid
Error 3 – STATUS_INVALID_STATEMENT
Usualy a bad GRBL Specific $ instruction
Error 4 – STATUS_NEGATIVE_VALUE
Negative value received for an expected positive value.
Error 5 – STATUS_SETTING_DISABLED
A call to a disabled function was issued – EG you issued $H for homing but your $20 (homing enable) parameter is set to 0 (off)
Error 6 – STATUS_SETTING_STEP_PULSE_MIN
Your $0 (step pulse time) is to short, set it back to its default value, $0=10
Error 7 – STATUS_SETTING_READ_FAIL
Corrupt EEPROM values, you will need to reconfigure all your $ values as they have been reset to default – this time once you have worked them all out, make a copy! This is a rare error.
Error 8 – STATUS_IDLE_ERROR
You have issued a command only allowed when the machine active state is Idle. Example you sent $$ while the Active state was run (job was in progress)
Error 9 – STATUS_SYSTEM_GC_LOCK
machine is locked in error of some sort, and you tried to issue a movement command. Did you forget to $X the machine? Or is it sitting on a Limit Switch?
Error 10 – STATUS_SOFT_LIMIT_ERROR
You will see this if you try to enable soft limits without also enabling homing cycle. Soft limits cannot work unless you first home the machine so it knows where it is!
Error 11 – STATUS_OVERFLOW
GRBL has a max number of charactors it will accept in one command, it received on that was too long – often happens when CAM software puts long comments in file
Error 12 – STATUS_MAX_STEP_RATE_EXCEEDED
You tried to set a Step rate that was too high, look at your $110, $111,$112 values!
Error 13 – STATUS_CHECK_DOOR
You have the safety door funtion turned on and it is showing not closed…close it
Error 14 – STATUS_LINE_LENGTH_EXCEEDED
You should not see this error and if you do you should know what it means!
Error 15 – STATUS_TRAVEL_EXCEEDED
You have got soft limits turned on and configured, and the job your trying to run is larger than you have told grbl that your machine actualy is. Either fix your soft limit values and if they are correct, look at why your cam setup is trying to use more space than you actually have.
Error 16 – STATUS_INVALID_JOG_COMMAND
Jogging command issued was not valid, possibly forgot the =… part
Error 17 – STATUS_SETTING_DISABLED_LASER
Probrably happened when you turned on $32 wthout enableing PWM – We don’t know a lot about this error – email us if you work it out and we can add it to this list
Error 20 – STATUS_GCODE_UNSUPPORTED_COMMAND
Unsupported or invalid g-code command found in block.
Error 21 – STATUS_GCODE_MODAL_GROUP_VIOLATION
Read: http://linuxcnc.org/docs/html/gcode/overview.html#_modal_groups
Error 22 – STATUS_GCODE_UNDEFINED_FEED_RATE
You cannot issue a movement if no feed rate has been set – so issue something like F1000 (feed at 1000mm/min) before sending a movement command. You will likely only see this error when bashing stuff into the command prompt and not when using a gui
Error 23 – STATUS_GCODE_COMMAND_VALUE_NOT_INTEGER
Look into the command you sent, did it include a non integer value?
Error 24 – STATUS_GCODE_AXIS_COMMAND_CONFLICT
Two G-code commands that both require the use of the XYZ axis words were detected in the block.
Error 25 – STATUS_GCODE_WORD_REPEATED
A G-code word was repeated in the block.
Error 26 – STATUS_GCODE_NO_AXIS_WORDS
A G-code command implicitly or explicitly requires XYZ axis words in the block, but none were detected.
Error 27 – STATUS_GCODE_INVALID_LINE_NUMBER
N line number value is not within the valid range of 1 – 9,999,999 – why not turn off line numbers in your CAM software
Error 28 – STATUS_GCODE_VALUE_WORD_MISSING
A G-code command was sent, but is missing some required P or L value words in the line.
Error 29 – STATUS_GCODE_UNSUPPORTED_COORD_SYS
Grbl supports six work coordinate systems G54-G59. G59.1, G59.2, and G59.3 are not supported.
Error 30 – STATUS_GCODE_G53_INVALID_MOTION_MODE
The G53 G-code command requires either a G0 seek or G1 feed motion mode to be active. A different motion was active.
Error 31 – STATUS_GCODE_AXIS_WORDS_EXIST
There are unused axis words in the block and G80 motion mode cancel is active.
Error 32 – STATUS_GCODE_NO_AXIS_WORDS_IN_PLANE
A G2 or G3 arc was commanded but there are no XYZ axis words in the selected plane to trace the arc.
Error 33 – STATUS_GCODE_INVALID_TARGET
The motion command has an invalid target. G2, G3, and G38.2 generates this error, if the arc is impossible to generate or if the probe target is the current position.
Error 34 – STATUS_GCODE_ARC_RADIUS_ERROR
A G2 or G3 arc, traced with the radius definition, had a mathematical error when computing the arc geometry. Try either breaking up the arc into semi-circles or quadrants, or redefine them with the arc offset definition.
Error 35 – STATUS_GCODE_NO_OFFSETS_IN_PLANE
A G2 or G3 arc, traced with the offset definition, is missing the IJK offset word in the selected plane to trace the arc.
Error 36 – STATUS_GCODE_UNUSED_WORDS
There are unused, leftover G-code words that aren’t used by any command in the block.
Error 37 – STATUS_GCODE_G43_DYNAMIC_AXIS_ERROR
The G43.1 dynamic tool length offset command cannot apply an offset to an axis other than its configured axis. The Grbl default axis is the Z-axis.
Error 38 – STATUS_GCODE_MAX_VALUE_EXCEEDED
You sent a number higher than expected, maybe for a tool change you tried to select tool 50000 or something?
ALARM 1 – EXEC_ALARM_HARD_LIMIT
Hard Limit Error, A limit switch was triggered, this always results in the end of your job. The only time a limit switch should be hit is during a homing cycle, at any other time it will stop the system. Either your machine went to far in one direction and hit a switch or you have electrical noise getting into your limit switch wiring. Do not restart your jhob without rehoming or resetting / confirming the machines position, it will unliely be correct still!
ALARM 2 – EXEC_ALARM_SOFT_LIMIT
Soft Limit Error, Either you or a Gcode file tried to send some axis past further than you have suggested it can in your $130, $131 ,$132 parameters
ALARM 3 – EXEC_ALARM_ABORT_CYCLE
The Estop was hit! Same as a hard limit, just a different button – look at details above for Alarm 1
ALARM 4 – EXEC_ALARM_PROBE_FAIL_INITIAL
Grbl was expecting your probe to be in a state other than that it is before starting a probing cycle – ie your tool is already touching the probe or similar
ALARM 5 – EXEC_ALARM_PROBE_FAIL_CONTACT
Z axis was sent down as far as it dared (instructed) and did not hit a switch. Instead of digging to china it assumes you forgot to put an aligator clip on or that something else is wrong and so stops.
ALARM 6 – EXEC_ALARM_HOMING_FAIL_RESET
Reset was issued during a homing cycle, or maybe falsely triggered by electrical noise in your system/environment if your estop button is connected to the Abort pin and not to the reset pin that is
ALARM 7 – EXEC_ALARM_HOMING_FAIL_DOOR
Safety door was opened during a homing cycle, or maybe falsely triggered by electrical noise in your system/environment
ALARM 8 – EXEC_ALARM_HOMING_FAIL_PULLOFF
Grbl tries to pull back of a switch and hit it a second time (slowly) during a homing cycle. Your Homing Pulloff value was not sufficient to enable the axis to move far enough away from the switch. Increase $27 to maybe 3 or 5mm – $27=5.000
ALARM 9 – EXEC_ALARM_HOMING_FAIL_APPROACH
When homing, grbl will not travel further than the values in parameters $130, $131 ,$132 while trying to locate a limit switch. So even if your soft limits are off, make sure these values are correct or larger than your machine. Homing fail. Could not find limit switch within search distance. Defined as 1.5 * max_travel on search and 5 * pulloff on locate phases.”
Hold 0 – Hold complete. Ready to resume
Hold 1 – Hold in-progress. Reset will throw an alarm
Door 0 – Door closed. Ready to resume.
Door 1 – Machine stopped. Door still ajar. Can’t resume until closed.
Door 2 – Door opened. Hold (or parking retract) in-progress. Reset will throw an alarm.
Door 3 – Door closed and resuming. Restoring from park, if applicable. Reset will throw an alarm.
I just bought an Ortur Laser Master 2 20w and its like the the laser in the axis assembly is going straight to the right and hitting the end, then errors out. What do you believe it is?
Thank you for your time.
Amanda
ok
Starting stream
Layer C00 [SC7A20:(365)
Shock and Movement detected!]
Ortur Laser Master 2 Ready!
OLF 140.
Grbl 1.1h [‘$’ for help]
[MSG:’$H’|’$X’ to unlock]
error:9 G-code locked out during alarm or jog state.
On or near line 105:
Job halted
Stream completed in 0:03
Starting stream
Layer C00
error:9
G-code locked out during alarm or jog state.
On or near line 0:
Hi @CityLotHomestead,
At Grbl startup, error 9 is normal: When powering up, Grbl enters Alarm mode to force the origin point because it cannot know its position.
To unlock, all you have to do is running the homing procedure (Grbl command $H). You can also unlock the alarm with the $X command, but be careful, this does not allow Grbl to know its position. So you will have to make sure by yourself that the Gcode program does not exceed the limits of your machine.
It is also possible to deactivate the Alarm mode on power-up by deactivating the homing in the parameters of Grbl ($22 = 0).
It doesn’t seem to me that the version of Grbl used on your Otur Master 2 machine is grbl-Mega-5X. I couldn’t help you more, I don’t know the other versions as well.
@++;
Gauthier.
Thank you so much! I truly appreciate you. It is a Laser Master 2 20w.
…
On Thu, May 13, 2021 at 4:02 AM Gauthier Brière ***@***.***> wrote:
Hi @CityLotHomestead <https://github.com/CityLotHomestead>,
At Grbl startup, error 9 is normal: When powering up, Grbl enters Alarm
mode to force the origin point because it cannot know its position.
To unlock, all you have to do is running the homing procedure (Grbl
command $H). You can also unlock the alarm with the $X command, but be
careful, this does not allow Grbl to know its position. So you will have to
make sure by yourself that the Gcode program does not exceed the limits of
your machine.
It is also possible to deactivate the Alarm mode on power-up by
deactivating the homing in the parameters of Grbl ($22 = 0).
It doesn’t seem to me that the version of Grbl used on your Otur Master 2
machine is grbl-Mega-5X. I couldn’t help you more, I don’t know the other
versions as well.
@++;
Gauthier.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#197 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AUBWWFCHGNX22IA6RGHHXUTTNOBS3ANCNFSM44ZUS5WQ>
.
Loading
Welcome to Our Community
Some features disabled for guests. Register Today.
- Thread Status:
-
Not open for further replies.
-
Builder
- Joined:
- Nov 6, 2017
- Messages:
- 464
- Likes Received:
- 104
I almost finished building my Arco System and started working on electronics. I have CNC xPro V3 board with GRBL V1.1. I use GrblControl software. I didn’t connect anything to the board. I got Error Codes 6 and 9. I found out that Error Code 6 means no homing switches are installed. I don’t know that Error Code 9 means. I didn’t buy any switches. I connected the board to an 24VDC PSU made for CNC routers and 3D printers. How can I fix the Error Code problems?
-
Builder
- Joined:
- Nov 6, 2017
- Messages:
- 464
- Likes Received:
- 104
I can’t enter anything in the textbox because GRBLControl keeps on flashing the error codes every second.
-
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Aug 6, 2013
- Messages:
- 2,713
- Likes Received:
- 1,565
use the Arduino serial console, or UGS to change the settings.
-
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Aug 6, 2013
- Messages:
- 2,713
- Likes Received:
- 1,565
but wait, if you are using ‘grblcontrol’ and GRBL1.1 then it will never work since GRBLcontrol has not been updated to work with GRBL 1.1.
rather use Candle 1.1.7 Releases · Denvi/Candle · GitHub -
Builder
- Joined:
- Nov 6, 2017
- Messages:
- 464
- Likes Received:
- 104
How can I turn off homing and limits?
-
Builder
- Joined:
- Nov 6, 2017
- Messages:
- 464
- Likes Received:
- 104
I found out that GRBL Panel software works. I can jog the machine. I should be getting the switches from Probotix.
-
Builder
- Joined:
- Apr 12, 2018
- Messages:
- 6
- Likes Received:
- 4
I’m having a similar issue — Running a CNC xPRO V3 on an oxcnc build with macOS. It was running fine, but my old mac died, so I replaced it and now I get an endless loop of error:9 whenever I connect to the board. Did alot of reading and tried every possible solution I could find but to no avail. Would appreciate anyone’s suggestions on how to resolve this problem.
Cheers.
-
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Aug 6, 2013
- Messages:
- 2,713
- Likes Received:
- 1,565
error:9 is «G-code locked out during alarm or jog state«.
so why is it in an alarm state?
do you have homing switches? anything changed?
check the GRBL setup carefully.
What GUI are you using? it may have had settings on the old machine that you need to duplicate on the new. -
Builder
- Joined:
- Apr 12, 2018
- Messages:
- 6
- Likes Received:
- 4
I can’t pinpoint why it is an alarm state. Yes, I have homing switches and physically nothing changed other than running it on a new computer. I even tried physically disconnecting the switches to see if I would get a different response but it’s the same.
I did reflash the board to GRBL 1.1f to see if that made any difference but same error and I have gone through the GBRL setup to check that the settings are the same as when it was operating properly.
I was using UGS. I’ve also tried UGS platform and OpenBuilds CONTROL but all report that the board is in an alarm state that I can’t get out of. -
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Mar 1, 2017
- Messages:
- 11,880
- Likes Received:
- 3,669
Dump out your Grbl settings for us to check. Otherwise we can only offer guesswork
Send $$, copy, paste in a reply
Also, copy paste the output of «$N» -
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Aug 6, 2013
- Messages:
- 2,713
- Likes Received:
- 1,565
First
Change the GRBL settings to turn off homing entirely and check that it then comes up without an alarm.
Home will then be wherever you turned it on.Then:
Use the OpenBuildsCONTROL troubleshooting page to check that the switches are working correctly.
Once the switches are confirmed to be working correctly you can reenable homing (but leave soft limits off)
Make sure you set the ‘homing pull off’ to enough to release the switches reliably.
The default is 1mm which is pretty much always too small.Note that the serial console will usually display details about the cause of the alarm.
-
Builder
- Joined:
- Apr 12, 2018
- Messages:
- 6
- Likes Received:
- 4
Ok, so here are my GRBL settings along with most of the message string. I turned off homing but that didn’t seem to resolve the issue, it was still in an alarm state. I was able to check the limit switched using OpenBuildsCONTROL and they are working correctly.
It’s very hard to actually change any of the settings because of the frequency of the alarm/error pop up window.
I’ve posted the result of «$N» at the end.
Thanks.
-
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Aug 6, 2013
- Messages:
- 2,713
- Likes Received:
- 1,565
error 1 and 2 mean:
1 G-code words consist of a letter and a value. Letter was not found.
2 Numeric value format is not valid or missing an expected value.
so I’d say that your PC or controller is not communicating correctly over usb. Tried a different (short) USB cable? -
Builder
- Joined:
- Apr 12, 2018
- Messages:
- 6
- Likes Received:
- 4
Tried a shorter cable, no luck.
Not sure what else to try. -
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Mar 1, 2017
- Messages:
- 11,880
- Likes Received:
- 3,669
1) Run ‘$RST=*’ from the Serial Console tab
2) go to Wizards and Tools — grbl Flash. Reflash your controller.
3) unplug everything to avoid any external faults from putting us on a goose chase, connect just the board, via USB to computer
4) reboot Pc
5) test again -
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Mar 1, 2017
- Messages:
- 11,880
- Likes Received:
- 3,669
Oh and of course all this is OpenBuilds CONTROL (known to work… Get it working here first it miggt be your other software)
-
Builder
- Joined:
- Apr 12, 2018
- Messages:
- 6
- Likes Received:
- 4
Managed to reflash the controller, unplugged everything, rebooted & still got error messages. See below
-
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Mar 1, 2017
- Messages:
- 11,880
- Likes Received:
- 3,669
While it starts up fine, then starts erroring… what are you sending/doing/clicking when the errors start…
At the end, the port closed. Did you hit disconnect, or did the port die on its own…
Still looks like USB comms issues if you didnt send/do anything1) Try a different cable
2) Try a different PC
3) Make sure you have the official FDTI Drivers Virtual COM Port DriversLast suggestion — sure you are on latest version of CONTROL (v1.0.172 at the time of this post) OpenBuilds Software — FREE Software for CNC Control: OpenBuilds CONTROL and OpenBuilds CAM
Might be a clue here too… That new Mac might be the issue… Either drivers, or the ports are broken? Try a different PC (bet its gonna work fine on another PC)
-
Builder
- Joined:
- Apr 12, 2018
- Messages:
- 6
- Likes Received:
- 4
Peter & David, thanks for your time and input — looks like it was the FDTI drivers. You both pointed to a USB communications issue. I had neglected to install the correct drivers on my new computer — I installed them tonight and the board is responding as it should. Haven’t had a chance to cut anything yet but through OpenBuilds CONTROL, I’ve been able to jog and home the machine which I could not do before. Looking forward to doing some cutting tomorrow. Thanks again!
-
Builder
- Joined:
- May 25, 2020
- Messages:
- 38
- Likes Received:
- 4
Hey Jeff, I am getting the same error 6 and then 9….. What did you do to remedy the error codes…. Thanks!
-
Staff Member
Moderator
Builder
Resident Builder- Joined:
- Mar 1, 2017
- Messages:
- 11,880
- Likes Received:
- 3,669
Read gnea/grbl — all errors and alarms
But you need to know what ALARM (note difference between errors and alarm) put it in locked mode first
Please don’t split off from your existing thread about the same issue Error 9 carving Paradise Box — just makes it harder to keep track of the troubleshooting steps. In that thread the same applies. Each error 9 has a very clear history leading up to it. Please go back to that thread and provide the requested information so we can tell you what the root cause is
- Thread Status:
-
Not open for further replies.