To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.robotics.rcx.legosOpen lugnet.robotics.rcx.legos in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / RCX / legOS / 1671
1670  |  1672
Subject: 
Re: legOS lcd management and thoughts on velocities
Newsgroups: 
lugnet.robotics.rcx.legos
Date: 
Fri, 2 Feb 2001 10:43:22 GMT
Viewed: 
1739 times
  
Hello jochen,

The timeout is really "expected time till next rotation tick + 50 %".
And the velocity will not drop to 0, because my code assumes, a new
rotation could happen any moment.

If you check for speed < 7 ticks/sec (or 142 msec/tick) you should get
a response time of 213 ms.  But in your case it may be enough to
assume a collision happened when a timeout occurred.  You can check if
the velocity drops while the rotation sensor has still the same value.

If you want to change the 50 %, it is hardcoded in kernel/dsensor.c
line 183:
     next_rotation[channel] = time + time_diff * 3 / 2;
and line 209: ... time_diff / 2;


Thank you for your precision about your velocity handler
For now, unfortunaly my the hard disk does not boot any more,
and, fortunatly, my wife gave birth to a girl on wednesday! So
I'll test all those nice handlers in a few weeks!

merci encore,
Michael.



Message is in Reply To:
  Re: legOS lcd management and thoughts on velocities
 
(...) The timeout is really "expected time till next rotation tick + 50 %". And the velocity will not drop to 0, because my code assumes, a new rotation could happen any moment. If you check for speed < 7 ticks/sec (or 142 msec/tick) you should get (...) (24 years ago, 29-Jan-01, to lugnet.robotics.rcx.legos)

5 Messages in This Thread:

Entire Thread on One Page:
Nested:  All | Brief | Compact | Dots
Linear:  All | Brief | Compact
    

Custom Search

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR