Subject:
|
Re: Strange BrickOS Timing
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Wed, 3 Dec 2003 14:56:29 GMT
|
Viewed:
|
7806 times
|
| |
|
|
Hi Guido,
> 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.
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 think you get the meaning
of this.
Regards,
Dietmar
|
|
Message has 1 Reply:
Message is in Reply To:
 | | Re: Strange BrickOS Timing
|
| Hi Gunther, (...) have (...) After some investigation I found this page on YOUR site: (URL) 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 (...) (23 years ago, 3-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
|
|
|
|
