03-08-2021, 03:43 AM
Hi Thomas,
If you are using the driver, you can't avoid the stops at every point. This is because RoboDK and the controller communicate on a "per command" basis. In other words, RoboDK stream the motion commands one at a time, waiting for the confirmation of the robot before sending another one.
If you want continuous motion, you need to use the post-processor and generate the robot program.
This way the robot will have access to the complete program and can execute fluid motions.
Jeremy
If you are using the driver, you can't avoid the stops at every point. This is because RoboDK and the controller communicate on a "per command" basis. In other words, RoboDK stream the motion commands one at a time, waiting for the confirmation of the robot before sending another one.
If you want continuous motion, you need to use the post-processor and generate the robot program.
This way the robot will have access to the complete program and can execute fluid motions.
Jeremy
Find useful information about RoboDK and its features by visiting our2022世界杯32强赛程表时间
and by watching tutorials on ourYoutube Channel.