 | | ***legOS new name : deadline is 18.07.***
|
|
As Steve mentioned, the 23.07. is too late for the announcement of the new name at Brickfest. I think it would be great to do so, so I decided to make the deadline at Thursday, 18.07. I will publish the new name around midnight of the 18.07 and (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | lnp error message..huh?
|
|
woolley thnx for the tip on checking the RCX memory.. now i have another question.. after having run continous messages back and forth between the RCX and my program on my PC for ~10 minutes. i get this error message: ---...--- Transmit error: (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
(...) I'd built a maze solver. When the solver makes a step (for example forward) it uses the light sensor to search for a wall and the rotation sensor to measure the distance it has traveled. If a wall is hit, the solver steps back until it reaches (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
"Joel Uddén" wrote (...) not (...) Actually, each task gets equal "wakeup" checking. The only difference between a low priority task and a high priority task is that the high priority task gets a larger time-slice when it is awake. This is not an (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
(...) Thanks for the link, your solution of proportional timeslicing is more straightforward than mine which I like. The only downside would be that a high prioritized process would have it's wakeup conditions checked less frequently than a low (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
