[Jeremy]

We are currently testing out a new method and if approved we will have a section in the documentation in the very near futur.

Here's the procedure:

在机器人运行选项(使用驱动程序):
On the other hand, the driver allows you to run programs step by step from RoboDK and see the pointer being run anytime from RoboDK. It is important to first be able to connect to the robot to use this feature. Otherwise, the optionSend program to Robotshould still work with less headaches (Windows Firewall, antivirus, etc).

To properly run custom programs using the driver (for example, opening/closing the gripper), you should use program calls instead of "Insert Code" . This should have no impact when you generate programs or send them to the robot in one shot, but it is important to have an effect with the driver. See attached image and RDK file.

Furthermore, I would like to add thefollowing correctionfrom what I said in previous emails:
You should make sure the number 255 or 0 is separated by a space before and after the brackets. Example:
rq_move_and_wait( 0 )
/ /而不是of rq_move_and_wait(0)
This is required so the driver received the correct ID. We'll remove this requirement in future versions of RoboDK.



Important:
For the RobotiQ gripper to work using the driver as described in this email, make sure to use the same file I sent on May 25th:

1. You can take the following script file:
   //www.sinclairbody.com/files/upload/progrobodk-rq.zip
   
2. And 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).
   

Keep an eye on the UR logs to see if anything fails on the robot side as well.