Subject:
|
Re: Strange BrickOS Timing
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Wed, 3 Dec 2003 11:07:10 GMT
|
Viewed:
|
3724 times
|
| |
|
|
Hi Gunther,
> maybe someone can explain to me why the current brickOS release seems to • have
> msleep()-amnesia ;-)
After some investigation I found this page on YOUR site:
http://www.lepomux.org/patch.html
where YOU state:
Using Lepomux requires a stable timing on the motor port because it is used
as a serial data port. Since brickOS does a lot of stuff simultaneously,
it's not enough to use functions like msleep(). Task scheduling, LCD refresh
and other things may occur, which will make it impossible to generate
constant data rates.
I think I've been cheated :-)
Hi, Guido
|
|
Message has 1 Reply:
 | | Re: Strange BrickOS Timing
|
| Hi Guido, (...) That patch referes to an older transfer-protocol. The one we are using now, does not need SUCH a stable timing. But the Output from BrickOS is a lot worse than it was in older versions. I thing Gunther can explain this better, but I (...) (21 years ago, 3-Dec-03, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Strange BrickOS Timing
|
| Hello out there, maybe someone can explain to me why the current brickOS release seems to have msleep()-amnesia ;-) We've been testing the data transfer to our Lepomux device. For some strange reason we were still using kernel 0.2.6.07nmChg with a (...) (21 years ago, 2-Dec-03, to lugnet.robotics.rcx.legos)
|
5 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
