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 |
moveit_servo holds indeed panda specific values.
Best practice would be to have a generic upstream package , that way you can git clone it and add your robot specific files. Then you can just do a git pull to get the latest changes. However this is in my opinion not realistic for moveit_servo because there are hardware parameters required. moveit_servo without panda reference wouldn't be a working simulation, or it would be over abstracted.
in this case (moveit2 is rolling, and this specific package is active on git) I'd keep the panda stuff, and add your robot configs in new files (i.e: "myrobot_simulated_config.yaml"). Then when you pull an from git you can easily compare diff between your local and remote. (for release/distribution clean it up and remove panda references)
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.
