This page provides a detailed description of how different robot platforms comply with the Industrial Robot Driver specification. It is intended for developers and systems integrators needing to evaluate specific functional capabilities. More general compatibility information can be found here.
This page provides a detailed description of how different robot platforms comply with the Industrial Robot Driver specification. It is intended for developers and systems integrators needing to evaluate specific functional capabilities. More general compatibility information can be found here.
points with out-of-order (or in-the-past) time_from_start should be ignored
N5
N5
N5
N5
N5
N5
?
Required software downloaded "on-the-fly" to robot by UR5 ROS node.
Error logged. Trajectory truncated at max-size and executed anyway (not ignored).
Trajectory streamed to robot. No overflow possible.
Simulator is single-threaded. Will block new trajectories (buffered in ROS) until previous trajectory is completed, then execute new trajectories in the order received.
Moves through all trajectory points, in the order received.
Topic publishers are always created. No topic messages are published if robot doesn't provide required simple_message broadcast.
Streaming trajectory only. Reaction is robot-specific for robots using downloaded trajectories.
This page provides a detailed description of how different robot platforms comply with the Industrial Robot Driver specification. It is intended for developers and systems integrators needing to evaluate specific functional capabilities. More general compatibility information can be found here.
points with out-of-order (or in-the-past) time_from_start should be ignored
N5
N5
N5
N5
N5
N5
?
Required software downloaded on-the-fly to robot by the Universal Robot ROS driver node.
Error logged. Trajectory truncated at max-size and executed anyway (not ignored).
Trajectory streamed to robot. No overflow possible.
Simulator is single-threaded. Will block new trajectories (buffered in ROS) until previous trajectory is completed, then execute new trajectories in the order received.
Moves through all trajectory points, in the order received.
Topic publishers are always created. No topic messages are published if robot doesn't provide required simple_message broadcast.
Streaming trajectory only. Reaction is robot-specific for robots using downloaded trajectories.