The length of time that read waits is dependant on the data rate from
the server. Basically in its default mode of operation read will block
until a message is received from the server. If you wish it to return
immediately you should use the ReadIfWaiting() method instead.
Incidently in CVS at the moment read if waiting will not work in pull
mode (now the default?) due to peek never requesting data. The best
solution to this is still being worked out.
> Hi everyone,
> I just found that when I use robot.Read() to update the data, this method
> takes different time say between 0.05sec and 0.15sec. Since this takes too
> much time (even worse if it is 0.15sec), does anyone know when this
> robot.Read() is necessary to be called and why it takes so long time.
> I am trying to reduce the call to robot.Read() but I am not sure whether I
> have to call it each time the robot's status changes.