[MathijsM08]

Hi everyone,
I’m new to RoboDK and having trouble controlling the I/O of our robot through the RoboDK UI.
We’re using a Doosan H2017 equipped with a vacuum gripper. To activate the gripper, we currently use the teach pendant by manually toggling Digital Output 1 (DO 1), which works fine.
However, when trying to control the same output from RoboDK, nothing happens.
The motion programs run perfectly, but I can’t get the gripper to activate.
In the “Manage I/O” window, I’ve already tried different I/O names and value formats such as:

• Names:1, DO 1, DO_1
  
• Values: 1/0, True/False, On/Off
  
  

None of these seem to trigger the real I/O on the robot.
Has anyone successfully controlled Doosan robot I/O through RoboDK?
Is there a specific naming convention or driver setup required to get this working?
Thanks in advance for any help or tips!

[Albert]

When you run a program in RoboDK it will run in simulation by default.

However, if you want to run programs directly on the robot you should enable the run on robot option (right click the program and check the option Run on Robot). This will run the program on the real robot using the driver (make sure to properly configure the driver).

Also, when you run programs on the robot make sure that digital inputs/outputs used are the ones on the real robot (not the simulated ones) by following these steps:

1. Select Tools-Options
   
2. Select the Driver tab
   
3. Check the option Trigger IO actions on the robot
   

[MathijsM08]

Hi Albert,

The option 'run on Robot' was on as all movements were executed fine. Also, I checked the 'trigger IO actions on the robot' option and this one was also checked on. So, the issue is somewhere else. Can you clarify what you meant with configuring the driver?

Regards

[Albert]

Can you share your RoboDK project and the driver log when you try to manipulate digital outputs?

We can better take a look.