04-03-2025, 02:04 PM (This post was last modified: 04-06-2025, 07:54 PM by Albert.)
I’m trying to control the Robotiq 2F-85 gripper connected to a UR10e from RoboDK. When I send the rq_move_and_wait() program from RoboDK and click "Send program to robot", it works. The problem is that the robot disconnects from RoboDK afterwards and the driver stops working.
I am using the attached driver. The question is if it is possible to move the gripper sending the program without the driver stops working and RoboDK does not disconnect to the physical/real robot.
Continuing with yesterday's post, I should mention that I'm using method 'A' to move the gripper, which is 'Send program to the robot.' As I mentioned before, when I send my robodk program, it disconnects from my robot. I'll include my log in case it helps:
Program DriverRoboDK started
socket_read_binary_integer: timeout
socket_read_binary_integer: timeout
Program Grpper_movement started
Gripper 1: connected and socket open.
socket_read_byte_list(): timeout
Program Gripper_movement stopped
Using the "Send program to robot" option or the robot driver are two different methods of programming robots.
The Send program to robot option will transfer the program on the robot and with some robot controllers (like Universal Robots) it may execute the program right after it has been sent. However, using the driver will execute one movement at a time on the real robot as you simulate the robot in RoboDK.
(04-06-2025, 07:58 PM)Albert Wrote: Using the "Send program to robot" option or the robot driver are two different methods of programming robots.
The Send program to robot option will transfer the program on the robot and with some robot controllers (like Universal Robots) it may execute the program right after it has been sent. However, using the driver will execute one movement at a time on the real robot as you simulate the robot in RoboDK.
Hello! Thanks for your answer but I think I am missing something.
I’m using the "Send program to robot" option with the "Universal Robots RobotiQ" post-processor. First, I connect to the physical robot, and when I select "Send program to robot", it disconnects, and then the gripper opens and closes exactly as I specified in the program shown in the picture.
My question is: is it normal for it to disconnect in order to execute the gripper action, or is there something I’m missing?
