Hi, I'm actually having the opposite problem of other previous users, that is the odometry error is null, at least for PeopleBot and Pioneer2DX (in Gazebo 5.2), so the position given by "PositionProxy" and "TruthProxy" are basically the same even after moving the robot for several minutes. Different is the behaviour of the Pioneer2AT instead, which has a realistic error.
I wonder, is the odometry error related in some way to the CPU speed, so for some users it's big and for others (like me) null? Is there a way to set up the error "level"? Where should I look in case I want to modify the code to fix it? Thanks, Nicola -- ------------------------------------------ Nicola Bellotto University of Essex Department of Computer Science Wivenhoe Park Colchester CO4 3SQ United Kingdom Room: 1N1.2.8 Tel. +44 (0)1206 874094 URL: http://privatewww.essex.ac.uk/~nbello ------------------------------------------ ------------------------------------------------------- This SF.Net email is sponsored by xPML, a groundbreaking scripting language that extends applications into web and mobile media. Attend the live webcast and join the prime developer group breaking into this new coding territory! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642 _______________________________________________ Playerstage-gazebo mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/playerstage-gazebo
