I still don’t understand why when I am in the module, jogging menu, the work object coordinate system, and I jog using the joystick in the direction of the displayed axis, I have to change the Y axis values to get it to move in the direction I want. I have a Lincoln Powerlift positioner, 26 foot long, the axis I need to modify is parallel to the length of the positioner. Sometimes in the work objects that were created by other dude he has X running parallel to the positioner. That is the direction I need to shift the workobject. But I have to modify Y to get it to move along X axis. If I change X, it moves Z. It makes me think something is screwed up somewhere. Or is it always like that?
Sounds weird. I always use RobotStudio when dealing with theses type of issues. Do you have a RobotStudio project (station) of the cell?
I do
Ok. Then I would sync the workobjects to station (nothing else for easier visibility) and then move them by multi selecting all of them and then right click and ”offset”. Then sync back to rapid and copy paste new values to your real robot.
I didn’t even know you could do that. Thank you.
Is it better to use the user frame for the coordinate system to program in Studio, then in the actual cell use the object frame to define and offset off of the user frame?
Not sure exactly what you mean by “program in studio”, but I don’t use the object frame at all unless I have to.
I keep it [[0,0,0],[1,0,0,0]]
E.g.
CONST wobjdata wMachine:=[FALSE,TRUE,“”,[[188.591,-1331.11,993.212],[0.928713,-0.00140822,-0.00661259,-0.370739]],[[0,0,0],[1,0,0,0]]];
Ok.
I import models from the engineers and program all my target using Studio. Is it not called programming?
I fixed the shift. I just ran a modify bullseye with a new torch and it got rid of that issue. How could my TCP get that far off. Could someone have crashed the torch, and then updated TCP?