Problem with Easel Passing bad commands

Hi,

I am having a problem with Easel when starting a job. I home the tool bit and when I press “raise the bit” it goes up far to high as the result of an “unsupported command” it then goes on to start the job but the Z axis is now too high to the bit does not touch the workpiece.

here is the offending code:

ok
ok
M9
M5
ok
ok
ok
G90 G21 G1 Z3.8100 F200
error: Unsupported statement
G10 L20 P0 X0 Y0 Z0
ok
ok
ok
G91 G21 G0 Z1.0000
ok

Can anyone help?

Hopefully @LarryM or @PhilJohnson will be along soon. They can sort this out quickly.

You could get a head start and post some details on what you are using, like software, hardware, post a link to your Easel file, etc.

The G-code that appears in your post is ok, the problem has occurred earlier in G-code file.

Helpful information: version of grbl you are running, source of the G-code (Easel, or just using Easel as the G-code sender). first 20 lines of the G-code file, $G and $# info from grbl, using a probe for Z zero or not as a start.

Do you home your machine?

Hi,

I am using Grbl 0.8c and using Easel to generate the G code. The machine is home built with Arduino Uno and CNC Shield. When I export the G code from easel and use it with UGS it all works fine. Not using a probe, setting zero by sight as per easel instructions.

Here is some more info:

ok
[G92:0.000,0.000,0.000]
[G30:0.000,0.000,0.000]
[G28:0.000,0.000,0.000]
[G59:0.000,0.000,0.000]
[G58:0.000,0.000,0.000]
[G57:0.000,0.000,0.000]
[G56:0.000,0.000,0.000]
[G55:0.000,0.000,0.000]
[G54:0.000,0.000,0.000]
$#
ok
[G1 G54 G17 G21 G90 G94 M0 M5 M9 T0 F200.000]
$g

And settings:

$0=200.000 (x, step/mm)
$1=200.000 (y, step/mm)
$2=200.000 (z, step/mm)
$3=10 (step pulse, usec)
$4=250.000 (default feed, mm/min)
$5=500.000 (default seek, mm/min)
$6=192 (step port invert mask, int:11000000)
$7=25 (step idle delay, msec)
$8=10.000 (acceleration, mm/sec^2)
$9=0.050 (junction deviation, mm)
$10=0.100 (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=25.000 (homing feed, mm/min)
$20=250.000 (homing seek, mm/min)
$21=100 (homing debounce, msec)
$22=1.000 (homing pull-off, mm)

And the beginning of the G-code file?[quote=“PeterGreen, post:5, topic:34166”]
When I export the G code from easel and use it with UGS it all works fine
[/quote]

Just noticed this. That would indicate that the problem is not in the G-code.

That is what I thought. I have tried to run this from my garage PC and a laptop with similar effects. It just appears to be related to the manual operation of zeroing in easel etc… Do you think it might be worth trying Grbl 0.9?

here is the full file as far as I can see:

ok
ok
M9
M5
ok
ok
ok
G90 G21 G1 Z3.8100 F200
error: Unsupported statement
G10 L20 P0 X0 Y0 Z0
ok
ok
ok
G91 G21 G0 Z-10.0000
ok
ok
ok
G91 G21 G0 Z-10.0000
ok
ok
ok
G91 G21 G0 Z-0.1000
ok
ok
ok
G91 G21 G0 Z-0.1000
ok

It could be a mis-match with version 0.8c.

I would upgrade the firmware and see if that helps. I would go to version 1.0c. If you don’t want to go that far then use 0.9j

There was a pin change between 0.8c and 0.9?

It may not affect you since you don’t home, but the Z axis homing switch moved to D12 and PWM moved to D11.

1 Like

ok, thanks for your input, will try 1.0c and see if that helps. I assume Easel is compatible with 1.0c?

0.9J did the trick :slight_smile: works perfectly, very happy, thanks Larry!

4 Likes