Closed AlbertLord closed 1 month ago
MoveIt 2 had some breaking changes since Foxy. I'd recommend taking a look at the migration guide or compare your configs with more up-to-date configs in the moveit_resources repository to make sure your config is correct.
Closing this because the issue seems to be solved
Introduction
Hello, I'm trying to make the TM ROS2 Driver (tmr_ros2) work with the main brach MoveIt2, because I intend to use moveit_py later. I made some alterations to the source material, but I'm not familiar enough with ROS2 to now what I'm doing exactly.
Enviroment
This is how I got here:
I'm using Ubuntu 22.04 and installed ROS2 Humble. Then I followed the Moveit2 guide to bulid it from the main branch. Aside from a couple of type casting warnings, everything went smoothly. Since the TM ROS2 Driver's Humble branch doesn't contain the Moveit2 packages I had to copy it from the Foxy branch (a month ago I used the driver just like this without any issue but I could only use Cartesian Planning in RViz). Building the driver with the source built MoveIt2 :
As best as I could I corrected these until the package built successfully. The end result was:
Before launch I imported my older configs, namely: In
tm_moveit_config_tm5-900/config/ompl_planning.yaml
:In
tm_moveit_config_tm5-900/config/ros_controllers.yaml
:In
tm_moveit_cpp_demo/config/controllers.yaml
:The error
With all of these I launched the demo with
ros2 launch tm_moveit_cpp_demo tm5-900_run_moveit_cpp.launch.py
. The following happened:Generally this is what happens every time, but the "run_moveit_cpp" node dies rarely before the last row's fail. I've checked a few issues regarding the "No kinematics plugins defined.", but with no improvement. What could be a solution?
Thanks in advance!