Bug? Non-Safety Height G0 in GCode output

Easel Easel Pro
1

Project:
Easel - G0 Bug Project (gcode I get is attached)

I found an odd G0 line in my gcode output (machine is Onefinity, I download GCode to zip, machine shouldn’t matter here?). The spiral pocketing cut gets most of the orca body for each depth, but then has to do a bit of the tail. For MOST of the depths, after finishing that bit of the tail it moves to the safety height (+0.15") to transfer back over to the starting point for the body. However, two times (line 13,216 and 17,621) it does not move to safety height, it only moves up to -0.0675. Fortunately, the path it traverses is within the space already cut, so no harm is done to this carve. However, this would be easy to not be true, as it is definitely lower than the surface of my stock, and the shape is irregular. I could also understand if Easel already understood that the space was clear, but then I would expect every other G0 between those two points to be at the same height, but they aren’t. The rest of the G0s between those points are at the safety +0.15"

G0 Bug Project.nc (617.0 KB)

I have simlar projects with other shapes, none of which are generating this non-safety G0.

2

I have seen the same thing on my carvings, have not really talked about it because it always seems to be on a area that will be cut out anyway after the fact. If you really want to see it, do your finish v carv cut first the the ruff cut, it will really show up then because the v bit drags across area’s that will be cut by the ruff bit later on. I am guessing they were trying to save time on a carve but not waiting for the bit to raise so high but that is just a guess.

3

Hi Michael,

Easel does have logic to make rapid paths through regions that are known to be carved already in order to save some time when it knows that’s safe to do. That’s most likely what you saw.