Ask Your Question
1

hector slam problem with imu

asked 2012-06-17 21:43:18 -0500

jas gravatar image

How to combine the hector slam (mapping) with microstrain imu ? will it be cancel out the "SearchDir angle change too large"? thanks

edit retag flag offensive close merge delete

Comments

Can you post a more detailed description of your setup (type of LIDAR/environment you try to use it in etc.) ?

Stefan Kohlbrecher gravatar imageStefan Kohlbrecher ( 2012-06-18 01:35:10 -0500 )edit

Currently I have a Hokoyo Laser Range Finder, PC104 3353f and a Microstrain 3DM-GX3-25 IMU. I am trying to achieve something similar to this video: http://www.gkmm.tu-darmstadt.de/rescue/?q=node/141 However, I do not know how am I supposed to integrate the IMU with hector_slam.

jas gravatar imagejas ( 2012-06-18 17:42:57 -0500 )edit

Now I am already able to get a map when there is only horizontal and slow movement. But this "SearchDir angle change too large" appears frequently

jas gravatar imagejas ( 2012-06-18 17:44:46 -0500 )edit

I launch the following launch file together to get the map : hokuyo test.launch(default launch file) , microstarain default launch file, hector_mapping default launch file and hector_slam ugv launch file (but this i edit it a bit)

jas gravatar imagejas ( 2012-06-18 17:51:19 -0500 )edit

when i type the "roswtf"command i found the following error:ERROR Communication with [/hokuyo] raised an error: ERROR Communication with [/map_nav_broadcaster] raised an error: ERROR Communication with [/nav_base_broadcaster] raised an error: ERROR Communication with [/rosout] raised an error:

jas gravatar imagejas ( 2012-06-18 20:21:06 -0500 )edit

ERROR The following nodes should be connected but aren't: * /hector_mapping->/hector_mapping (/tf) * /hokuyo->/hector_mapping (/scan) * /nav_foot_broadcaster->/hector_mapping (/tf) * /nav_baselink_broadcaster->/hector_mapping (/tf) * /map_nav_broadcaster->/hector_mapping (/tf)

jas gravatar imagejas ( 2012-06-18 20:22:27 -0500 )edit
  • /nav_base_broadcaster->/hector_mapping (/tf)
jas gravatar imagejas ( 2012-06-18 20:22:50 -0500 )edit

Thank you in advanced for your help :D

jas gravatar imagejas ( 2012-06-18 20:23:53 -0500 )edit

1 Answer

Sort by ยป oldest newest most voted
0

answered 2012-06-18 04:59:53 -0500

The velocities in the odometry messages from hector_mapping are always zero. You can try out the angular velocity from the IMU. For the linear velocity you can differentiate the position of the odometry from hector_mapping, integrate the linear acceleration from the IMU, and combine them through averaging or filtering.

My robot doesn't have an IMU, and I get the "SearchDIR angle change too large" message only when my robot is gone crazy so that the map is messed up. If you get the message often or from the beginning, I don't think augmenting your robot with an IMU will fix the issue.

edit flag offensive delete link more

Comments

My robot have neither odometry nor imu. But I am able to produce the map.I have to move very slow else it will show "SearchDIR angle change too large"and at some point of time mapping is stopped.I want to integrate imu now.I am able to produce values over /imu topic.Could you help me fusing with map

NAGALLA DEEPAK gravatar imageNAGALLA DEEPAK ( 2018-02-03 06:04:52 -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

1 follower

Stats

Asked: 2012-06-17 21:43:18 -0500

Seen: 2,119 times

Last updated: Jun 18 '12