[ros-users] TrajectoryPlannerROS does not take parameter

[Eric Perko]

Eitan,

Is there any reason why a transform timeout would cause the move_base
to command those illegal velocities beyond the limits set in the
configuration? I've also seen transform timeouts from the costmaps,
but I've never seen the commands be out of range when that happens;
I'd like to ensure that I won't have to deal with a robot randomly
zooming backwards anytime soon if one of my sensors dies :)

- Eric

On Fri, Jun 25, 2010 at 12:20 PM, Christian Verbeek
<verbeek at servicerobotics.eu> wrote:
> It seems as if the problem is solved. I noticed a "Costmap2DROS
> transform timeout" in the log of move_base.
>
> I tracked down the latency in the transform tree and foudn out that my
> laser range finder node (Sick S300) published with 3Hz only. I improved
> the parser and got 6Hz now. That seems to be sufficient. I failed to set
> the baudrate of the S300 to values larger than 115200 baud, but 6Hz
> seems to be enough.
>
> The robot is driving very meaningful paths in an extremely narrow
> environment.
>
> Its a real joy working with ROS. In the near future you will see the
> second commercial robot coming from REC running ROS.
>
> Regards
> Christian
>
> _______________________________________________
> ros-users mailing list
> ros-users at code.ros.org
> https://code.ros.org/mailman/listinfo/ros-users
>