Hi,
I'm using an UR10e and have a OnRobot 2FG7 gripper.
I've a problem, that when I have a RoboDK program with a Python Script in it that is connecting on an other port to the robot, that I can't continue in the RoboDK program.
So what I actually want to do:
I want to open and close the OnRobot gripper via RoboDK, but that didn't work directly, so I built a workaround.
What the RoboDK does now (
):
1. Setting a digital output to TRUE or FALSE.
2. Starts a Python script (
start program.py (Size: 1.31 KB / Downloads: 25)
) that connects the computer to the robot with the Dashboard (Port: 29999) to start a program. This program is loaded in the Teach pendant, before switching to external control. (The program on the robot is opening or closing the gripper depended on the Value of the digital output.)
3. Starts the Python script to reconnect to RoboDK (
reconnect.py (Size: 295 bytes / Downloads: 28)
)
4. It should set the digital output again to a different value and then start and stop the program on the robot again.
This is just a test to see, if it works. In the end I want to have this kind of program between the movement of the robot to open and close the gripper.
When I execute the program it works till the reconnection, but after that it looks like it is just skipping the rest of the program tree and finish it.
Here is the video of the hole thing:
Video 2025-07-27.mp4 (Size: 2.15 MB / Downloads: 31)
In the background you can hear, that the gripper is closing/opening, so that works and in the end the RoboDK also says it is connected again, but it skips the rest of the program.
Do you have any idea what my problem here is or have a suggestion how to do it in a different way?
Thanks for your time and help!
I'm using an UR10e and have a OnRobot 2FG7 gripper.
I've a problem, that when I have a RoboDK program with a Python Script in it that is connecting on an other port to the robot, that I can't continue in the RoboDK program.
So what I actually want to do:
I want to open and close the OnRobot gripper via RoboDK, but that didn't work directly, so I built a workaround.
What the RoboDK does now (
1. Setting a digital output to TRUE or FALSE.
2. Starts a Python script (

3. Starts the Python script to reconnect to RoboDK (

4. It should set the digital output again to a different value and then start and stop the program on the robot again.
This is just a test to see, if it works. In the end I want to have this kind of program between the movement of the robot to open and close the gripper.
When I execute the program it works till the reconnection, but after that it looks like it is just skipping the rest of the program tree and finish it.
Here is the video of the hole thing:

In the background you can hear, that the gripper is closing/opening, so that works and in the end the RoboDK also says it is connected again, but it skips the rest of the program.
Do you have any idea what my problem here is or have a suggestion how to do it in a different way?
Thanks for your time and help!