-
Notifications
You must be signed in to change notification settings - Fork 280
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failed to load system plugin gz::sim::Systems::DiffDrive #2715
Comments
The error messages shows you're trying to load |
Thanks! and yes that was part of the problem. I already fixed the problem and it works fine now. Just a note, I realized that it's actually called Gazebo Sim (version 8.7.0) and not Gazebo Harmonic. This was very confusing since I ended up installing wrong libraries. For diff-drive plugins, these are the ones which work now I also had a message type mismatch and that's why I couldn't control the robot with my Xbox 360 joystick, they joy node will pass in Twist but then in the gz_bridge.yaml, we must convert it to TwistStamped to pass it to gz, otherwise it won't work.
|
Glad it's working now. Did you follow the https://gazebosim.org/docs/harmonic/ros_installation/ ? You don't have to install Gazebo directly if you're using it with ROS. It's better to drop the <plugin filename="gz-sim-diff-drive-system" name="gz::sim::systems::DiffDrive"> I'll close this issue since it's not a bug. |
Sure, thanks for the tip. I'll maintain without |
I'm using ROS2 Jazzy on Ubuntu 24.04. I'm encountering an error when launching the diff drive plugin in Gazebo for my robot. The error message on the terminal after ros2 launch is
I'm also using the joystick as a teleop, which doesn't work, meaning the robot cannot move. The topic /cmd_vel is also not published, only /cmd_vel_joy shows up on "ros2 topic list". I setup my diff drive control plugin as below in ros2_control.xacro
<gazebo> <plugin name="gz_ros2_control::GazeboSimROS2ControlPlugin" filename="libgz_ros2_control-system.so">
The gazebo_control.xacro is set as below:
The text was updated successfully, but these errors were encountered: