Subject:
|
Re: BrickOS Threading...
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Fri, 13 Dec 2002 04:04:20 GMT
|
Viewed:
|
2856 times
|
| |
|
|
In lugnet.robotics.rcx.legos, Mark Riley writes:
> The motor handler is only called once ever 2ms in
> the latest version of BrickOS (as opposed to every
> 1ms in earlier versions). This is a fairly recent change
> and it could be causing a "granularity" type problem
> with certain speed settings in your code.
>
> Maybe try something like:
>
> MotorRunningValue = ((sys_time >> 1) & 7);
>
> and see if this gets you more predictable behaviour. • ...
>
> Other than that, like your subject line says, it could
> be a threading issue - quite a bit of that has changed, too.
This change seem to improve things. Can I change it back to the way it was
before?
Thanks
Steve
|
|
Message has 1 Reply:
 | | Re: BrickOS Threading...
|
| (...) <snip> (...) Steve, Yes, infact I had tested a couple different applications with the motor controller being called every 1 ms and the same ones with a 2 ms interval. I didn't see a difference with those applications, but did recognize the (...) (22 years ago, 13-Dec-02, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | Re: BrickOS Threading...
|
| The motor handler is only called once ever 2ms in the latest version of BrickOS (as opposed to every 1ms in earlier versions). This is a fairly recent change and it could be causing a "granularity" type problem with certain speed settings in your (...) (22 years ago, 12-Dec-02, to lugnet.robotics.rcx.legos)
|
7 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
|
|
|
|
