thank you for your fast answer.
actually, I don't need to edit the TCP. and yes you are right they are all TCP with respect to...
But for example in KUKA there is the ability to show the actual position with respect to TCP. in other words my TCP will be the reference. and that is very helpful in teaching some difficult objects.
I don't think you are asking the right thing.
When you reference your TCP as the coordinates system... what then, is going to be the point in that coordinate system, that gives you its position data as the feed back?
Are you asking for something like "Remote TCP(Fanuc)" or "External Reference Point(Motoman)" that's a point in space that is not connected to the robot? If so, you are looking at "User Coordinates" based on robot's world position. I forgot what it's called on KUKA.
The point is, THE TCP, is often referring to a point that will be moving with the robot. And if that is going to be the reference coordinate system, you would have to pick another object of reference somewhere to give you the position data relative to it.
Edit:
On Motoman, you will have to create a "User Coordinate" and then program the robot with EIMOV* to enable the robot to move as if this "User Coordinate" is the center of reorientation. (A special coord mode need to be selected for this interpretation to work when jogging, the icon look like the Joint mode but crossed off with a red line)