Ask Your Question

Revision history [back]

click to hide/show revision 1
initial version

If all you did was change the controller loaded, then that's probably the cause.

The package you use requires a very specific setup of controllers and topics and uses those to (somewhat) simulate how MotoROS would work with a real robot. If you change the controller it's very likely some topics are now missing and that is what is causing the rest of the setup not to work.

If you don't need that, I would not bother with it and just use a regular gazebo_ros_control configuration. From your other question (#q306964) I have the impression that you're only really after kinematic visualisation / trajectory play-out. If that is the case then using Gazebo for this does not make much sense to me: it's a huge CPU hog and you're not using any of it then.

In moto_ros_interface.cpp the Robot status is set to not in motion at the end of the trajSubCB callback. Is this what moveit determines the succes of the trajectory on? I looked at moveits source code but got a bit confused on how the succes of a trajectory is determined.

As I wrote in my comment: please don't consider moto_ros_interface.cpp as an example or how things should be done. It's a bit of a hack to get MotoROS-like behaviour out of a regular Gazebo+gazebo_ros_control setup. If you can clarify what you really want to do then perhaps we can see how that could be accomplished.