Ask Your Question
0

Does odom starting at 0 affect amcl?

asked 2019-07-10 17:43:15 -0500

Usui gravatar image

updated 2019-07-10 17:43:46 -0500

Hello community! I am using an iRobot package that has the odom always starting at position: (0,0,0) orienation: (0,0,0,1) and the hokuyo laser + package urg_node. I am wondering if having position at 0 everytime the robot starts affects the amcl package in anyway. Is it good as long as I set the initialpose?

On another note, since I read that the orientation on iRobot isn't that great, I just wrote a node that publish the x,y of odom in the iRobot package and the orientation of the imu plus frame and header of odom. Oh and the imu I am using also is 0 when it starts up. I made it like that to match the odom since odom is 0 when it starts. Then I just put that as odom in amcl since all amcl cares about is x,y and orientation of odom. Is that a good idea? or should I use efk?

Answers to any part of these questions are appreciated! Thank you! Thanks!

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted
1

answered 2019-07-10 18:19:00 -0500

billy gravatar image

First question: Is ODOM at 0 an Issue? Answer: No. Not an issue. When you set initial pose the MAP->ODOM TF gets setup and all is OK. Second question: Is that good idea or should I use EKF? Opinion: Keep it as simple as possible but no simpler. If ODOM and laser scanner give you good results then no need to use IMU and EFK IMHO. If you are on a Discovery Voyage (Stranger Things reference) and want to get broad experience with ROS, then absolutely it's a good idea. The more complicated you make it, the more experience you get.

edit flag offensive delete link more

Comments

I am asking because for some reason every time I turn 360 degree, the map in rviz drifts really hard. Could it be something wrong with my hokuyo laser scanner? I use imu because when I was searching online, people said that irobot odometry is not very good. btw I use create_autonomy package for iRobot. Oh and when I wrote a cmd_vel using just the /odom topic from create_autonomy (with laser scanner) to go 1 meter it only goes 0.9 meter. I was hoping that using laser scanner could help it localize better.

Usui gravatar imageUsui ( 2019-07-10 19:49:36 -0500 )edit

I would suggest you study the odom a bit more before and tune it. There is a tutorial on how to tune ODOM here. http://wiki.ros.org/navigation/Tutori...

billy gravatar imagebilly ( 2019-07-11 11:26:04 -0500 )edit

I already tried tuning it. Also my problem starts at amcl so I haven't tried move_base since the laser scan keeps drifting

Usui gravatar imageUsui ( 2019-07-11 12:13:08 -0500 )edit

If it repeatably goes 0.9m when you tell it 1m, then it needs re-tuning. And poor tuning will cause drift when you rotate as well. That's all I got. I guess an IMU is unlikely to fix your issue if ODOM is really as bad as you say.

billy gravatar imagebilly ( 2019-07-13 23:27:06 -0500 )edit

how should i tune it? I am using the create_autonomy package btw

Usui gravatar imageUsui ( 2019-07-13 23:54:03 -0500 )edit

Your Answer

Please start posting anonymously - your entry will be published after you log in or create a new account.

Add Answer

Question Tools

2 followers

Stats

Asked: 2019-07-10 17:43:15 -0500

Seen: 16 times

Last updated: Jul 10