Unexpected behaviour from a new TCP

Hi,

I have an existing program which I would like to modify so that all the waypoints are moved e.g 20 millimeters along the Y-axis. I figured this would be easiest to do by creating a new TCP for this program alone.

I created a test program where the new TCP position was translated by 20 millimeters along the Y-axis, in the positive direction. But, for some reason the positions are not translated along this axis, but at an angle (seemingly 45 degrees), so both the X-and Y-coordinates are changed. Any ideas what causes this?

The X and Y illustrated on your drawing; are they with regard to the base frame maybe? That would cause you the issues.
This is fundamental, but maybe you have not thought of it, but the TCP X and Y will be rotated when the tool is rotated in any direction.

If I were you, I would instead make a new feature/frame and shift that along whatever axis you want. A feature is not affected by tool rotation or anything else.
This will, of course, require you to edit all your Moves to use the new feature.

Hi again and thank you for the reply.

Yes, the X and Y are in regard with the base frame. I think I mixed up the concepts of a TCP and a frame here - never really had to move all the waypoints in a program before. I’ll try it the way you suggested, thanks!