-
Notifications
You must be signed in to change notification settings - Fork 176
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
encoder reading #392
Comments
Hi, look for a topic */joint_states, it has the encoder readings. |
joint_states doesn't give the encoder reading. I checked it. Is there any other way to get encoder values? |
The topic has the position. Do you need the increments (/high-low signal)? |
yes, it has the position which is same as what i get in odom topic. I want to get the raw encoder reading. i.e. how many ticks is the motor reporting? Is their any way to get it? |
I see, I'm wondering if the accuracy is sufficient to just divide tick_to_rad(0.002436916871363930187454f) [https://github.com/yujinrobot/kobuki_core/blob/devel/kobuki_driver/src/driver/diff_drive.cpp]. |
so, should i divide the pose i get from /odom by 0.002436916871363930187454? |
Yes, except that I am not aware that there are joint position in the odometry topic (http://docs.ros.org/kinetic/api/nav_msgs/html/msg/Odometry.html):
In the joint states there is
(http://docs.ros.org/kinetic/api/sensor_msgs/html/msg/JointState.html) |
thanks. I will look into it. |
Hello,
I am trying to get encoder reading from the kobuki base, but i didn't find any solution yet. Is it possible to get encoder readings rather than odom data?
The text was updated successfully, but these errors were encountered: