-
Notifications
You must be signed in to change notification settings - Fork 41
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
Robot turns with no velocity commands #18
Comments
Hi Jorge, Thanks for reporting the issue. This argument enables the execution of the ekf_localization_node that fuses odometry and imu to provide a better odom estimation. It looks that something is wrong with the config so it's better not to use it. I will disable this option by default. Best regards, Román |
Hi Román, Thank you for your solution. It solves the problem of turning without giving any move command to the robot. Nevertheless, the problem now is that the Summit drifts a lot in Gazebo (that happens also before), but as there's no IMU now, it gets crazy in RViz, spinning a lot because odometry saids that is turning so much, but really, it hasn't turn too much because is drifting in Gazebo. Do you think is possible to improve the reaction of the robot in Gazebo and reduce the drift? Kinds regards, |
I have test the robot with the other IMU sensor: <xacro:sensor_imu prefix="$(arg prefix)imu" parent="$(arg prefix)base_link"> The problem of turning seems to be solved. But I don't if this is the solution. Kinds regards, |
You mean witn the robot_localization enabled plus the other IMU sensor?. Right now I don't know how to reduce the drift in Gazebo. Regards, Román |
Hi all!,
I've just download the package and install it at the instructions. I compile it and everything is perfect.
But when I launch the simulation (with just one Summit, I have no test with more) it starts to turn counterclockwise without given to it any cmd_vel.
Here are 2 videos were you can appreciate it.
Video1 and video2.
How can I solve it?
I'm on Ubuntu 16.04 and I have update Gazebo to 7.14
Thank you,
Jorge
The text was updated successfully, but these errors were encountered: