Estlcam GCODE error - Y dim ignoring tool bit size

So this is strange - I’m cutting rectangles out of Foam that _should be 302mm x150mm on my LR3 with a 1/8" 2 flute bit.

First set all came out 302mm x 146mm

So I homed and checked my machine, then made a hole, moved Y 100mm , made a hole and spacing was perfect so I opened the gcode produced by estlcam. I’m using the ‘Part’ operation

Heres the start:

G90
M03 S24000
G00 Z5.0000 F480

;No. 1: Part 5
G00 X8.4125 Y10.0000 F2100
G00 Z0.5000 F480
G01 Z0.0000 F180 S24000
G01 Z-1.0000 F180
G03 X10.0000 Y8.4125 I1.5875 J0.0000 F720
G01 X312.0000 F720
G03 X313.5875 Y10.0000 I0.0000 J1.5875 F720
G01 Y160.0000 F720
G03 X312.0000 Y161.5875 I-1.5875 J0.0000 F720
G01 X10.0000 F720
G03 X8.4125 Y160.0000 I0.0000 J-1.5875 F720
G01 Y10.0000 F720
G01 Z-2.0000 F180

Bottom left of the part is 10mm off the X/Y Origin
So on the X Axis it looks like its starting point is 10mm - /12 the diameter of the tool but on Y it isn’t.

Which makes sense for what I’m seeing in the parts are undersized by the thickness of the bit.

Am I missing something? I can’t figure how such a basic thing can be wrong.

The preview screen will show you where the cut is starting and finishing, same as my ncviewer screenshot.

Maybe if you zip your ESTLcam file and upload it we could take a look. ?

Okay, so paraphrasing the gcode:

Go to the starting point less 1/2 the bit width in X

Turn a curve with radius 1/2 the bit width around the origin point until you get to the starting X point and 1/2 the bit width less in Y.

Go straight 302mm in +X

Turn a curve with radius 1/2 bit width until you get to the start point in Y and +1/2 the bit width in X

Proceed 150mm in +Y

Turn a curve with radius 1/2 bit width until you get to max X size and Y + 1/2 bit width


Estlcam uses curves around the sharp corners (G03 commands ij this case) the 1.5875 is the radius of the bit, so it keeps it your dimensions plus that.

The rectangle that it cuts is from 8.4125/8.4125 to 313.5875/161.5875 this should result in a rectangle 302mm wide and 150mm high. The gcode here matches what you are asking for, provided that your machine is obeying the arc commands correctly.

Estlcam has an option to turn off arc commands. You cound try that and see if it helps. If so, then it is a different error that your machine has. I dont think Estlcam is to blame here

Okay that restores my sanity a bit and what you’re saying makes sense Dan. I’ll zip and attach the gcode but I suspect it’ll look fine.

Weird. So I made a test file with 2 150mm squares, the second rotated by 45 degrees. My reasoning being that if there is a mechanical issue with the Y axis the second square should turn out to be a rhombus.

Here’s the GCODE:
150Squaretest.zip (948 Bytes)

So the first square was as expected - X 150mm Y 146



The rotated second:
Top Left to bottom right length - 150mm
Top right to Bottom left length - 147mm



I mean… what?


What is that happening there? Looks like a problem with tracking.

I wonder if there is a problem with either the belts or with tracking at that location in Y

If you jog Y from zero to as far as it can travel, do a tape measure and the controller agree? Have you used the Estlcam measuring tool (middle click and drag) to more or less confirm (no snap functionality) your imported drawing dimensions?

Good spot! I went back to the machine and gave it the old wiggle test and discovered the left Y motor pulley has a bit of play, the grub screw on the flat of the shaft was loose, not enough to let it spin but enough that there is backlash!

Disassembled the motor mount and reseated the grub screws with some blue loctite before I left for work this morning - I’ll run another test cut when I get home but I am hopeful that’s the issue - the backlash as it takes up the slack on the Y axis.

2 Likes

To close the circle on this -I’ve only got a chance today to get some free time to check after retightening the grub screw on the Y axis motor pulley.

Ran the same 150mm test squares today and they’re both nearly perfectly 150mm across so that was indeed the source of the error.

To aid anyone doing a search later on I’ll reiterate Y axis error in size was caused by a loose grub screw causing backlash. Thanks everyone who helped.

1 Like

Grub screw Grub screw Grub screw!!

1 Like