I am very sorry for the change of the default. It was unintended. In fact with the current algorithm of Goto driver, 3.0 is too fast for me also but I was playing with some values and recompiling before I decided that it would be faster to just have them as configuration options and it seems that my last test value survived till the commit ...

Sorry for giving you a fright


On Sun, Aug 30, 2009 at 1:24 AM, Paul Osmialowski <newchief@king.net.pl> wrote:

Hi,

I didn't expect anyone would like to make any changes in this driver so it
almost ended in heart attack when I ran recent SVN snapshot and my roomba
robots started to run like a crazy. The reason is in recent changes in the
driver done by Jordi Polo who added missing configuration entries (which I
never had time to add) changing one default value by the way (max speed
was changed from 0.7 to 3.0 m/s which is quite fast). In the driver
description it is still said that default max speed is 0.7, so something
need to be changed: driver description or TVMAX define. For me either
value is ok, robots completed the task at 3.0m/s, although going that fast
did not help it at all as the room for the task was bit too small and it
was hitting the wall.

Paul

------------------------------------------------------------------------------
Let Crystal Reports handle the reporting - Free Crystal Reports 2008 30-Day
trial. Simplify your report design, integration and deployment - and focus on
what you do best, core application coding. Discover what's new with
Crystal Reports now.  http://p.sf.net/sfu/bobj-july
_______________________________________________
Playerstage-developers mailing list
Playerstage-developers@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/playerstage-developers



--
Jordi Polo Carres
NLP laboratory - NAIST
http://www.bahasara.org