The site is read-only. Please transition to use Robotics Stack Exchange
| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
 | 1 | initial version |
If you already know where you want your manipulator to go, don't need any sensor-guided motion planning and require (actual) real-time guarantees, then I'm wondering whether ROS, MoveIt or even the universal_robot packages are suited for your specific use case.
Perhaps it would be more efficient to directly send move(..) or speedl(..) URScript commands to TCP 30002 or 30003.
| | 2 | No.2 Revision |
If you already know where you want your manipulator to go, don't need any sensor-guided motion planning and require (actual) real-time guarantees, then I'm wondering whether ROS, MoveIt or even the universal_robot packages are suited for your specific use case.case (right now).
Perhaps it would be more efficient to directly send move(..) or speedl(..) URScript commands to TCP 30002 or 30003.
| | 3 | No.3 Revision |
If you already know where you want your manipulator to go, don't need any sensor-guided motion planning and require (actual) real-time guarantees, then I'm wondering whether ROS, MoveIt or even the universal_robot packages are suited for your specific use case (right now).
Perhaps it would be more efficient to directly send move(..)movel(..)speedl(..) URScript commands to TCP 30002 or 30003.
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
