[mrutz1]

RoboDK Drivers are not meant for smooth operations, as the Driver will wait for each command to finish before sending the next.
Machining tool paths should be uploaded to the controller using our post processor (right-click the program->send program to robot), and run from the controller.
You can however start a remote program using the Driver, when supported.

Is there a way to write a driver that would be less jerky? For example if it loaded multiple position registers at a time and then cycled through them?