Hi all. The problem I’m having, is that when Im going through the setup for a carve. The stop switches work and the homing function works and sometimes I can get a single jog on the first try but then nothing. And it won’t execute the project. . I have loaded the latest firmware. I’m running Windows 7 Many thanks in advance for any help.
Does Easel report any sort of status ?
If you open up Machine Inspector (CTRL+SHIFT+D) what does it say in the main window?
Need more input 
Thank you for replying. Here is the log report.
Again, thank you.
Console
Show status
ok
$132=100.000
$131=290.000
$130=290.000
$122=50.000
$121=500.000
$120=500.000
$112=500.000
$111=8000.000
$110=8000.000
$102=188.976
$101=40.000
$100=40.000
$32=0
$31=0
$30=1
$27=1.000
$26=250
$25=750.000
$24=25.000
$23=7
$22=1
$21=1
$20=1
$13=0
$12=0.002
$11=0.020
$10=115
$6=0
$5=0
$4=0
$3=7
$2=0
$1=255
$0=10
$$
ok
[OPT:VMP,15,128]
[VER:1.1f.20170417:]
$I
[MSG:’$H’|’$X’ to unlock]
Events
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
error - error:9
Settings
$0=10
$1=255
$2=0
$3=7
$4=0
$5=0
$6=0
$10=115
$11=0.020
$12=0.002
$13=0
$20=1
$21=1
$22=1
$23=7
$24=25.000
$25=750.000
$26=250
$27=1.000
$30=1
$31=0
$32=0
$100=40.000
$101=40.000
$102=188.976
$110=8000.000
$111=8000.000
$112=500.000
$120=500.000
$121=500.000
$122=50.000
$130=290.000
$131=290.000
$132=100.000
Error 9 means that Gcode is locked out during alarm.
This indicates that perhaps your homing cycle is not completing properly.
Check the location of the homing blocks in relation to the switches, and make certain that the switches are activating properly.
One thing you do NOT want to do is to manually clear the alarm state, and attempt to manually jog the carriage. This will most likely result in a machine crash, and could result in damage to the switches.
If you go into the machine console, you can manually activate the homing switches and make sure they are working. (I believe this is still an option in the console).
It also appears that you have soft limits enabled ($20=1), so you may be requesting the machine to move beyond what it thinks is the maximum travel.
I don’t use easel on a regular basis, preferring instead to use vcarve and UGS for routing, and lightburn for laser work, so others may have additional information on this.
Try $21=0, any change in behaviour?
I really suspect noise/false switch trigger is the reason, you could disable $20/21/22 altogether and try a simple small carve to verify/eliminate.
I checked the stops by using the homing option and the 3 axis all worked ok. I couldn’t lower the spindle because the jog buttons don’t respond. So continued through the setup and clicked Carve. Top right of the screen said Carving 0% (8 min left) But no response from the machine. This is the report.
G91 G21 G0 Z-1.0000
G91 G21 G0 Z-1.0000
G91 G21 G0 Z-1.0000
G91 G21 G0 Z-1.0000
G91 G21 G0 Z-1.0000
G91 G21 G0 Z-1.0000
[MSG:Reset to continue]
ALARM:2
ok
ok
G91 G21 G0 Z-1.0000
ok
$H
ok
$132=100.000
$131=290.000
$130=290.000
$122=50.000
$121=500.000
$120=500.000
$112=500.000
$111=8000.000
$110=8000.000
$102=188.976
$101=40.000
$100=40.000
$32=0
$31=0
$30=1
$27=1.000
$26=250
$25=750.000
$24=25.000
$23=7
$22=1
$21=1
$20=1
$13=0
$12=0.002
$11=0.020
$10=115
$6=0
$5=0
$4=0
$3=7
$2=0
$1=255
$0=10
ok
[OPT:VMP,15,128]
[VER:1.1f.20170417:]
$$
$I
[MSG:’$H’|’$X’ to unlock]
Events
alarm - ALARM:2
I also typed $21=0, while in the machine inspector then selected Show status. Lots of text scrolling down. Managed to copy some. <Alarm|MPos:-289.000,-289.000,-99.002|Bf:15,128|FS:0,0|Pn:P>
?
Hope this helps.
Alarm 2 is a soft limits alarm, so for whatever reason, you have requested the machine to go past where it thinks it can go.
Turn off soft limits, and try again…
go to the machine console, and in the console area type this and hit enter:
$20=0
It should report:
ok
if you then pulll up the parameters by typing $$, it should show line $20 as “$20=0”
soft limits will then be turned off.
Retry your jog and carve.
1 Like
Everything seems to be working fine now. Many many thanks for your help.
1 Like
I have a very similar problem. Looking at the error code, it says, "
error - error: Expected command letter
error - error: Expected command letter"
Do you know what problem that indicates? Thanks!
Executing a carve.
And some more background is that I have a 2nd hand Shapeoko 2 and I have not gotten it to work at all yet. When trying to jog or execute a program, the Z-axis starts for half a second, then stops.
Is this from Easel?
Could be an error in the code, but it might be EMI causing issues with the serial communication.
The more info you give, the easier it will be for others to help.
What controller? Grbl version? Can you post your grbl settings? How’d you create the gcode? What are you using to send?
Thank you!
Yes, this error code is from Easel. I’m using an arduino uno R3 and gShield v5b.
I have been trying Easel and Repetier. I am able to connect. But when I try to execute anything, the z-axis spins for a moment, maybe 5 degrees and stops. When I disconnected the z from the gshield, the y attempted to move and stopped.
I have also tried the Universal G-code sender, but same result. I am connected to using a USB cable from laptop to arduino.
I don’t know which Grbl version I have. If I can figure out how to post the grbl settings, I will do it.
Actually now in the Universal G-code Sender, it now says, “Error while starting file stream: Grbl has not finished booting.”
Most of the time this error indicates that you are using the wrong baud rate. Set your baud rate in UGCS to 115200. Check to make sure you are using the correct COM port as well.
In UGCS, using the “Command” tab, enter the command $$ (two dollar signs) and it should print out the grbl settings.
In Easel, when I try to jog in any axis any direction the X AND Z motors try to turn for half a second, but nothing happens. When I lock and unlock, the motors, that works fine.
The Grbl version is 0.8c.
Are these the settings?
$0=0.000 (x, step/mm)
$1=0.000 (y, step/mm)
$2=320.000 (z, step/mm)
$3=0 (step pulse, usec)
$4=0.000 (default feed, mm/min)
$5=0.000 (default seek, mm/min)
$6=0 (step port invert mask, int:00000000)
$7=0 (step idle delay, msec)
$8=0.000 (acceleration, mm/sec^2)
$9=0.000 (junction deviation, mm)
$10=0.000 (arc, mm/segment)
$11=25 (n-arc correction, int)
$12=3 (n-decimals, int)
$13=0 (report inches, bool)
$14=1 (auto start, bool)
$15=0 (invert step enable, bool)
$16=0 (hard limits, bool)
$17=0 (homing cycle, bool)
$18=0 (homing dir invert mask, int:00000000)
$19=0.000 (homing feed, mm/min)
$20=0.000 (homing seek, mm/min)
$21=0 (homing debounce, msec)
$22=0.000 (homing pull-off, mm)
Are these the settings the controller report back to you?
If so they are “empty”.
What hardware are you using? 0.8c is very old. There have been lots of improvements since that version was released.
@WillChildress I’d upgrade to the most current version of Grbl. There was a pin swap after 0.8, so you’ll need to swap a couple of wires or just move one depending on your setup.