Quicktech S32 issues

[amazingjosh]

Running a simple face and pocket job on a quicktech S32, the machine keeps overshooting the first X‑50 move, bails out of a G12.1 pocket cut a few millimeters early, and leaves a tiny jog line mid finish pass and all the while without throwing alarms. Code validates fine in simulation and offsets look clean, but on the floor it still drifts. Anyone seen a quicktech wander like this?

 

[verywhiteman]

Running a simple face and pocket job on a quicktech S32, the machine keeps overshooting the first X‑50 move, bails out of a G12.1 pocket cut a few millimeters early, and leaves a tiny jog line mid finish pass and all the while without throwing alarms. Code validates fine in simulation and offsets look clean, but on the floor it still drifts. Anyone seen a quicktech wander like this?

Check G12.1/G13.1 modal cancel, I've seen cases where it doesn't reset clean between ops and messes with X comp.

 

[Cn.Dale]

Check your backlash comp, especially on X, if it's even slightly off, that first X-50 move can overshoot just enough to throw the whole cycle out of sync and yeah another thing, if your code simulates clean and offsets are good, then the problem is mechanical or control side, period, do a manual test cut with simple G1/G2s and see if it holds a circle

 

[cuts&circuits]

Great call on checking the backlash compensation, I'm thinking along the same lines. If the simulation looks good and there are no alarms, we might be dealing with either mechanical drift or control lag. I'm also interested in what the backlash readings are showing on that X axis right now