Posts by Lemster68

I suggest that you read my first reply once more.

Tool0 is not a remote TCP. Of course it will be relative to Tool0, it is held by the robot.

You have a syntax error for two reasons. The Rx is not allowed, and you omitted the tool. You might be able to combine the Offset function with a reltool, but the tool would need to be a dummy, remote TCP which has an origin either the same X,Y,Z of the point to move to, or, just a null value 0,0,0. The quaternions should be 1,0,0,0.

That is most likely a part of Production Manager robotware option. I knew it seemed familiar, but I have not ever used it, this is from the manual:

ExecEngine is the Production Manager Execution Engine instruction. The

instruction takes no arguments and has no-step-in behavior. The user calls this

routine from his main routine in each motion task. Typically the user-defined main

routine should have a procedure call to ExecEngine and nothing else.

The ExecEngine routine contains a simple while-loop that monitors the Execution

Engine I/O interface for orders specified by the Production Manager GUI or other

I have not used that new a version. Maybe it is telling you that it is not being used. Make a new one so that you know it is not in use and see if it acts the same. Maybe toggle off dark mode too.

That would be highly dependent upon the make of your robot. Would you kindly tell us?

You could also setup a virtual machine on the new computer which would run XP.

Like Hermann says, it is just forcing a reboot, but only the pendant. I have done it many, many times, with no ill effect.

There is a small recess in the middle back of the pendant. Use the tip of the stylus to press in the recess for a moment until you see it begin to reset.

Have you tried resetting the pendant? Since about RW 6.05 I have seen bugs, peculiarities with the pendant. After weeks or so, the top left button for selecting other windows(and pretty much the touch screen) is frozen and requires a TP reset. Also, the button to select linear/reorient seem laggy, and even if they do show changed, will operate in the previous mode if you try to jog too soon. For a much longer time, the jogging decides to stop by itself, even though you did not let up on the joystick.

Did you download the document regarding this procedure from the manuals sub forum?

What version of robot controller is it? I would suspect that it is older and that the contact for that start button is not working. Is there a PLC controlling the robot that can give the system input START?

Might need a P-start

My thought is that an option was omitted when reinstalling the system.

Since it is a stationary tool, is robhold set to FALSE? And workobject robhold is set to TRUE?

Typically, when making circular paths it looks more like this:

MoveL p20

MeveC p30, p40

MoveC p40, p50

MoveC p50, p60

MoveC p60, p50

MoveC p50, p40

You mentioned tool0, I hope that you have not programmed with tool0.

Is it a rotating or linear axis? Are the brakes releasing?

Is this a new or existing setup? How do you use the axis? If it is new, you can move it to the zero position marker and fine calibrate. If it is already programmed, doing so will throw off your program's positioning.

The version of controller would be helpful. Anyway, you might just remove the contactor wires from that part of the keyswitch.

I had pretty much the same thought. It seems like a controls programmer who wants absolute control maybe.

That is very likely impossible. You could use TriggL/J IO to send out numbers or use something like path segments, though.