04-02-2019, 04:35 PM
I'm not sure I understand the issue.
If you are planning to move the real robot and use the inputs/outputs of the robot I recommend you to make sure you have this setting unchecked:
Tools-Options-Motion-Manage I/O with RoboDK when connected to a robot
(it is unchecked by default)
If the previous solution doesn't work, it would help if you can provide the RDK file.
You can also run this code as a test:
A more detailed example is available here:
//m.sinclairbody.com/doc/en/PythonAPI/exam...rogramming
If you are planning to move the real robot and use the inputs/outputs of the robot I recommend you to make sure you have this setting unchecked:
Tools-Options-Motion-Manage I/O with RoboDK when connected to a robot
(it is unchecked by default)
If the previous solution doesn't work, it would help if you can provide the RDK file.
You can also run this code as a test:
Code:
RDK = Robolink()
robot = RDK.Item('UR10')
robot.Connect() # Make sure you are connected to the robot
RDK.setRunMode(RUNMODE_RUN_ROBOT) # Trigger robot commands on the real robot
robot.MoveJ(point3)
robot.waitDI(1,1) # This should wait for the real Input 1 to be set to True/On
robot.MoveJ(point4)
A more detailed example is available here:
//m.sinclairbody.com/doc/en/PythonAPI/exam...rogramming