On Thu, 29 Nov 2007, syt wrote:
> Hello Everyone,
> When running this function on the simulation, the time it spends is
> reasonably small, which is good. However, if this function is run to set a
> real robot odometry, it normally takes much longer time. Maybe this partly
> depends on the speed of the CPU?
"Any ideas" were asked, so here is my guess:
Drivers behind position2d interface are different in the simulation and
in the real robot. In simulation I guess you can set new value for
odometry when ever you want, but in real robot you would be working in
real time and probably driver have to wait for right moment for update not
to mess motor control algorithm or velocity measurement.