| ROS Resources: Documentation | Support | Discussion Forum | Index | Service Status | ros @ Robotics Stack Exchange |
Hi guys,
I am currently looking at using odometry with the position given by an optical mouse.
As I couldn't find any package/node driver that would allow me to have access to the position of the mouse, I was wondering if anyone had already looked into that and could give some feedback.
Thanks in advance for the replies
Just adding the sketch as requested:
@Mehidi: Your description is right. Indeed, that was what I meant.
One comment: if the sensor on the base is too far from the floor, it may not work, or you will need lenses to focus/compensate the distance.
This also reduces the hight of your base and the possibility of going over obstacles.
But it is cheap, and tends to be precise: optical mouses can work with resolution of typically 300 dpi.
Quick explanation of sketch: gray wheel: free wheel. Black wheel (yellow core) drive wheels. "Robot" is mounted on a triangular base.
Ok, so let's think about the possibilities on what kind of data you can gather from this.
The concept is simple physics: distance over time.
2) If the linear speed of the wheel and the linear speed detected by the base sensor are the same, you robot is moving.
3) If the linear speed of the wheel is greater than the linear speed of the "floor", your drive wheel is skidding.
4) If the linear speed of the floor is greater than the linear speed of the wheel, your robot is being dragged or going down a very slippery path.
5) if the base sensor detects movement in the X and Y axes, your robot is either making a curve, or spinning. You can calculate angular speed of the curve, if you think you need it.
6) If you detect that the wheel speed is fluctuating, your robot may be on some sort of low cohesion soil, like pebbles.
Thanks for the sketch ccapriotti. So if the sensor on the wheel tells you that the wheel is rotating but the one at the back tells you that the robot isn't moving then you can tell that you're robot is skidding. Is that about right or can you actually get more out of your sensors?
If you put other lenses on the sensors you can actually get some distance between it and the surface. There´s been very interesting research on using mouse sensors for obstacle avoidance in UAVs as well as using multiple sensors on ground vehicles for highly accurate odometry. See for example http://www.et.byu.edu/~beard/papers/p... or http://botsnlinux.net/school_projects... .
You can check this
and this
The Python code to get mouse coordinates on the screen is really short and you can easily integrate it into your project. In that case you maybe need to calibrate by yourself the ratio between Pixels/Meters by doing some tests. If the mouse gets stuck at the border of the screen you could also implement something to automatically take the mouse to the opposite border such that it could continue moving.
If you are more into hacking hardware and getting directly odometry data without plugging the mouse to a computer then check this :
Thanks for the ideas Mehdi. My first approach was to get the real world coordinates of the mouse from the position of the cursor on the screen. But you can not use this method if you are ever to use more than one of these sensors, or at least I do not see how you could make it work.
What operating system will the mouse driver run on? In Linux, reading mouse data is a simple file read:
http://www.linuxquestions.org/questio...
You can just create a ROS node that reads the mouse file data into the I/O event data structure and then your code can just look at the type/code values from the event data structure to tell which direction and how far the mouse was moved and publish that information into an ROS Topic for other ROS nodes to consume.
Thanks for the the link, I will definitely look into that. Although I am focusing more on solutions including 'hacking' by connecting to the output of the sensor. It seems to be the way to go as I am probably going to buy off the shelves sensors in the future (as opposed to buying an actual mouse).
Asked: 2014-07-01 07:47:37 -0600
Seen: 3,421 times
Last updated: Jul 05 '14
ROS Answers is licensed under Creative Commons Attribution 3.0 Content on this site is licensed under a Creative Commons Attribution Share Alike 3.0 license.
Very good approach ! Thinking outside the box at its best !
can't really take any credit for that, many people have already successfully done what I'm trying to do :), just wondering if anyone has done with ROS
Since we are thinking outside of the box here, you could use two mouse-based sensors: one on the robot, close to the floor, and another on your wheel's surface (mechanics permitting) , so you could measure skidding, implement cliff-avoidance, and some other good stuff.
I am definitely interested in any idea that may help the odometry work better, although I do not see where you want to put the second sensor. Could you maybe draw a quick sketch or just elaborate a bit might be enough for me to understand?
I think he means to fix the second mouse above one of the wheels, with very small distance between the mouse's sensor and the wheels surface (wheel has to be flat in this case)
Hi, did you finally happen to work on this type of Odom? any good resources?