X axis moved to work offset well cutting

[Stephen Sheehy]

Just switched from Mach 4 to UCCNC version 1.2113 firmware 1.0370
I have a simple wood router.

Well I am cutting and not the same point in the gcode, the x axis moves to G54 work offsets

Usually the first cut when starting the machine is fine.
After selecting the next toolpath and reprobing the next tool this seems to happen.

Attached a picture.
the machine is at physically at X0 Y0 Z.09

[Stephen Sheehy]

After doing a bunch of testing I was wondering if anyone has had the same problem be caused by the gcode the post processor made?
It only seems to happen on v carving where it tries to clear out pockets and goes back and forth very quickly.

[ger21]

Well I am cutting and not the same point in the gcode, the x axis moves to G54 work offsets

I don't think you understand how work coordinate systems work. You have to be using some coordinate system at all times, and G54 is the default. If you zero your X axis, you are setting your X axis work offset.
The machine can't be switching to G54, unless it's in some other coordinate system to start, and the g-code switches it to G54
You need to post your g-code, and explain more clearly exactly what you think is happening.

[Stephen Sheehy]

Trying to learn at new system and troubleshooting at the same time.

When troubleshooting I was looking for coordinates that matched the amount my x axis moved out away from zero. The G54 has a similar coordinate number.
Appen further testing I kept getting different numbers.

I ran an MDI code G0 X40 and then G0 X0 for several times and changing the jogging speed, acceleration and velocity, each time it would be perfect. (trying to also figure my max acceleration)

Ran a simple cut toolpath it was fine. Ran a tile toolpath with three tiles, they all lined up great and no problems.

So that this point I think the problem is during cutting a V carve tool path with a flat bottom the gcode had the machine go back and forth very quickly. And at some point, I believe the x axis could not cut fast enough and lost steps when it was stop by the material it was trying to cut.

It maybe my stepper motor is starting to fail.
The x axis is smaller than my y axis, maybe the y stepper can power through better.

I am looking for a simple wood router screenset and a post processer that Vetric can use to generate my Gcode.

Appreciate any help you can offer.

[Stephen Sheehy]

Thank you again for responding.