Closed mqcmd196 closed 11 months ago
Please consider server-side (robot-side) solution, instead of requireing each users to setup individually, specially this solution requires different workspace for different robots, that means, if you prepared a demo code for your robot, and try to apply that system to other robots, you need to setup different worksapce.
If the differentce of moveit_msgs
are CollisionObjects.msg (https://github.com/ros-planning/moveit_msgs/compare/0.11.4...melodic-devel) and that is only used to publish pr2eus to moveit, one ides it to start node that take noetic veresion of CollisionObjects within robot, as AnyMsg and republish as CollisionMsg as original topic name (https://github.com/jsk-ros-pkg/jsk_robot/pull/898), If you need to subscribe melodic version of CollisionObject within roseus running at noetic client , you can use https://github.com/jsk-ros-pkg/jsk_roseus/pull/631
I agree with your point. Close then create another PR
Hmm, create rospy.AnySrv
fixes https://github.com/jsk-ros-pkg/jsk_robot/issues/1855