Dear Sid,

maybe I didn't explained the problem accurated enough. I have written a simple program in which the mill moves 2 mm away from the workpiece in the Y-direction and than it returns to the start position, away and back again (so 2 times moving away and coming back). The more I run this program, the further the start point moves away from the workpiece and it's initial position.

Entering a backlash isn't a solution because in this case the start point moves further away depending on the number of cycles (away and back). If the movement of the start point, compared to it's initial position, would stay the same independent of the number of cycles, a backlash would be the right solution. Altough, that's what I understand under "backlash". To prove this, I entered a backlash and ran the program a couple of times. Result: the start point kept moving away from it's initial position.

Changing the speed, acceleration, pc... had no influence.

I also ran the same (adjusted: y becomes x) program for the X-direction. The same story here; the more cycles, the further the start point moves away.

To find out what triggers this problem, I ran the same program (both for x and y) with DinCNC. Result: the mill comes back to the same position, independent of the number of cycles. Butt in the future I need to run 4 axes at the same time and this isn't possible with DinCNC. So I downloaded Mach2 and I ran the program again. Result: the mill returns to it's initial position.

Problem not solved, but I got around it.

Although, I'm still wondering what went wrong with Mach3. I double checked all the parameters, but none of them indicates some sort of delay. If someone has any suggestion on how I can solve this Mach3 problem, just reply because I'm still very curious.

Regards,

Kevin