[FraserRoboLboro]

Hi,

I've been trying to get a demo working using an ABB robot. I have a python script in place that uses a mounted camera to locate objects and place appropriate targets in the RoboDK simulation environment.

The script runs perfectly as a simulation, but when selecting 'run on robot' with the real robot connected, the simulation continues but the real robot does not move at all.

For background, the robot is connected via socket connection, RoboDK sees the robot connected and can succesfully move the real robot with the Get Position, Move Joints and when running a Program on the robot.

The issue comes from not being able to move the robot via the python script. I tested a simpler script that just reads as 'robot.MoveL(Target 1)      robot.MoveL(Target 2)', but still no movement occurs on the real robot.

Any support for why the robot cannot be driven by the python script but can be by other methods would be appreciated. If any more information is needed I can provide.

Thanks

[Albert]

Did you load the RoboDK driver MOD file on the ABB controller?
Can you share your RoboDK project file and the robot connection log?

[FraserRoboLboro]

Hi Albert,

I have the RDK_DriverSocket.mod file uploaded to the ABB pendant, which has allowed me some control of the robot with RoboDK.

Whether this is important or not, but I am currently only using the robot in manual mode, but by running the driver MOD in manual mode I can connect the robot and move the robot using Move Joints and RoboDK programs, its only python programs that don't seem to work.

Could you point me in the direction of where to find the robot connection log?

[Albert]

You should call Connect before running any movements. Example:

Code:

robot.Connect()
robot.MoveL(target)