You can operate the RobotiQ gripper directly from RoboDK using the driver (Run on robot option). The RoboDK driver for UR and RobotiQ allows you to run programs step by step from RoboDK and see the pointer being run anytime from RoboDK.

It is important to make sure you can connect to the robot to use this feature. You may need administrator privileges on Windows and/or add a Windows Firewall rule to allow this communication (if you disable the Windows Firewall it may help troubleshoot if the issue is related to the Firewall).

Note: The options Generate Program F6 and Send program to Robot should still work without the need to setup the driver (Windows Firewall, antivirus, etc).

You should follow these steps to add support to moving the RobotiQ gripper directly from RoboDK:

1.Download the following script file:
https://robodk.com/files/upload/progrobodk-rq.zip

Note: for older controller that do not support communications through the tool you should use this version:
https://robodk.com/files/upload/progrobodk-rq-no-tool-com.zip.

2.Unzip the progrobodk.script file here:
C:/RoboDK/bin/progrobodk.script

3.Make sure to restart the driver if it was running (double click Disconnect, then, Connect).

4.Select Tools-Options-Drivers

5.Uncheck the option: Manage program calls with RoboDK when connected to a robot.

Tip: UR logs can help you understand if anything fails on the robot side.

To properly operate the gripper using the driver (for example, opening/closing the gripper), you should use the program call to rq_move_and_wait by passing a parameter within the range 0-255.

Example:

rq_move_and_wait( 0 ) # Fully close the gripper

rq_move_and_wait( 255 ) # Fully open the gripper

The number passed as an argument is required by the driver.

Using the RobotiQ gripper with the driver