ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | Q&A
Ask Your Question

how to get wheel encoder data on HuskyA200

asked 2018-08-31 23:37:47 -0600

frodyteen gravatar image

I am working with Indigo Husky A200, and I want to try to implement the odometry pose estimation in python myself instead of using the existing Husky odometry node. I am a little confused on what package or node I need to subscribe to in order to use the encoder values in my odometry calculation?

I try to understand the build in odometry node husky_velocity_controller/odom by look at this link and it said that the husky_velocity_controller/odom is from raw odometry as read from Husky encoders. I am pretty new with c++, and looked through the code base but not sure where they processed the encoder information. Can anyone point this out for me?

Any suggestion is appreciated, thank you.

edit retag flag offensive close merge delete

1 Answer

Sort by ยป oldest newest most voted

answered 2018-09-01 11:03:54 -0600

stevejp gravatar image

Answer will depend on what exactly you mean by "implement odometry pose estimation".

If you want to go from raw wheel encoders to odometry estimate, most of that is happening with the diff_drive_controller which has a config file in the husky_control package. It uses the raw wheel encoder data with a diff_drive motion model to estimate odometry (and publishes it on husky_velocity_controller/odom).

The other link you specified ("code base") is the code for the robot_localization package. This package fuses the wheel odometry ("husky_velocity_controller/odom") as well as imu data in an EKF to estimate pose (usually published on odometry/filtered).

edit flag offensive delete link more


Thank you for the reply. I want to use raw wheel encoders's tick signal like in this post to calculate the odometry. So, how can I get the tick signals from the encoder? @stevejp

frodyteen gravatar image frodyteen  ( 2018-09-01 16:38:27 -0600 )edit

Unfortunately I'm not super familiar with the husky hardware interface, you may have to dig into the driver to figure it out. This looks like a good starting point - sorry I can't be of more help!

stevejp gravatar image stevejp  ( 2018-09-07 19:49:50 -0600 )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



Asked: 2018-08-31 23:37:47 -0600

Seen: 600 times

Last updated: Sep 01 '18