02-18-2021, 06:43 PM
Hi,
With more research I found that it's perhaps the Robot Driver that's causing the problem://m.sinclairbody.com/doc/en/Robot-Drivers....iverCustom
'When the driver is run from RoboDK, the virtual robot will follow the movement of the real robot in real time. A new command will not be processed until the Ready message is sent.'
Is there a way to overcome this issue and allow a new command to be processed before Ready message is sent?
With more research I found that it's perhaps the Robot Driver that's causing the problem://m.sinclairbody.com/doc/en/Robot-Drivers....iverCustom
'When the driver is run from RoboDK, the virtual robot will follow the movement of the real robot in real time. A new command will not be processed until the Ready message is sent.'
Is there a way to overcome this issue and allow a new command to be processed before Ready message is sent?