Sure, you would need to write a node which converts the wheel RPMs into a nav_msgs/Odometry
message which robot_localization
would consume.
Originally posted by John Hoare with karma: 765 on 2016-04-11
This answer was NOT ACCEPTED on the original site
Post score: 1
Original comments
Comment by badrobit on 2016-04-11:
would you suggest just performing this as a 1:1 treating RPM as the same thing as encoder ticks just with much less resolution?
Comment by Icehawk101 on 2016-04-11:
You would use Speed = (RPM (diameter * PI) / 60) to find the velocity of each wheel, then put that into the kinematic equations of the robot to determine the robot's overall velocities along the x and y axis and about the z axis
Comment by badrobit on 2016-04-12:
I am not that familiar with using the kinematic part of the system we have TF2 setup does this just refer to changing the reference frame for the two velocities?
Comment by Icehawk101 on 2016-04-13:
The transform is the change in reference between odom frame and the world frame. The kinematic equations are used to determine what effect the individual wheel velocities have on the robot as a whole.
Comment by badrobit on 2016-04-13:
I guess I am not sure how exactly I would go about doing that. I have the values like you said and I have a rover model loaded through URDF which has all of the required frames listed I am just not sure how to put the speeds into the system in a way that would output the desired result.