Skip to content
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

ros_force_based plugin has a problem with TF #63

Open
kamoonty opened this issue Jul 11, 2019 · 1 comment
Open

ros_force_based plugin has a problem with TF #63

kamoonty opened this issue Jul 11, 2019 · 1 comment

Comments

@kamoonty
Copy link

kamoonty commented Jul 11, 2019

Hi, I am quite new to ROS and Gazebo. I use ros force based plugin for my Mecanum robot instead of the planar move because your plugin does not override the physics engine. However, I have found a problem here.

  1. When I spawn the robot, there are always offset of robot position in my map and also the yaw direction offset for 90 degrees. Hence, I have to edit the arguments for static transform node in order to solve this problem. Here are some parts of my launch file to call a single robot with the namespace.
    <node pkg="tf" type="static_transform_publisher" name="odom_map_broadcaster" args="0 0 0 0 0 0 /map $(arg robot_name)/odom 10" />
    Note that when I set to 0 0 0 0 0 0 the robot will offset in Rviz when compare to the Gazebo
    So I have to change the offset here. But if I use the original planar move there is no problem.

  2. When I move robot sideways in the y-axis, the odometry in Rviz does not change even though in gazebo it has change position already. For move straight and backward in X-axis, there is no problem.

Here is the part of my URDF file to call the plugin in
<gazebo> <plugin name="ros_force_based_controller" filename="libgazebo_ros_force_based_move.so"> <commandTopic>cmd_vel</commandTopic> <odometryTopic>odom</odometryTopic> <odometryFrame>odom</odometryFrame> <odometryRate>100.0</odometryRate> <robotBaseFrame>base_link</robotBaseFrame> <publishOdometryTf>true</publishOdometryTf> <yaw_velocity_p_gain>500</yaw_velocity_p_gain> <x_velocity_p_gain>1000</x_velocity_p_gain> <y_velocity_p_gain>1000</y_velocity_p_gain> <cmdVelTimeOut>0.25</cmdVelTimeOut> </plugin> </gazebo>

@CzJaewan
Copy link

CzJaewan commented Mar 8, 2021

I have the same problem. Did you solve it?

If you have resolved it, we would appreciate it if you could share the solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants