Re: [Playerstage-users] Player at Magellan/rFlex: delayed position

[Toby C. <tco...@di...>]

The rflex hardware has a simple safety feature that makes the robot stop
if it does not receive continuous updates at a particular rate (not sure
what the exact timeout is, somewhere between 10ms and 100ms i think).
The driver was designed to maintain this behaviour, so to answer your
question, yes this is by design.

in anser to question 2, are you calling read before checking the new
position? and are you calling read often enough, if you are updating at
a rate less tham 10Hz then change player into PUSH_NEW mode..

Toby Collett

Rafael Rivas wrote:

>Hi,
>
>I'm using player  1.6.3 in a Magellan Pro with rFlex driver,  I'm
>doing a simple client: set velocity and read the odometry. My problems
>in this case are:
>
>1.- I need send  playerc_position_set_cmd_vel()  several times to
>maintain constant the speed, ¿is this correct  form?. if I send
>several times a movement order and next I request to him that it
>stops, the robot continues moving.
>
>2.-  Some time the robot is moving, but the odometry proxy don´t shows
>the change of position.
>
>
>Thanks in avanced,
>
>Rafael Rivas
>
>
>-------------------------------------------------------
>SF.Net email is sponsored by: Discover Easy Linux Migration Strategies
>from IBM. Find simple to follow Roadmaps, straightforward articles,
>informative Webcasts and more! Get everything you need to get up to
>speed, fast. http://ads.osdn.com/?ad_idt77&alloc_id492&op=click
>_______________________________________________
>Playerstage-users mailing list
>Pla...@li...
>https://lists.sourceforge.net/lists/listinfo/playerstage-users
>
>  
>