 | | Re: anyone know how to check free space on RCX?
|
|
(...) v0.2.6) When you press the View button (with no program running) LegOS will (...) Joseph, what do you mean by most significant / least significant? I'm under the impression that those two calls just display the same value, in decimal first and (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | RE: Re: Scheduler patch
|
|
Can someone please tell me how to unsubscribe from this group! Thanks, - Subir -----Original Message----- From: news-gateway@lugnet.com [mailto:news-gateway...net.com]On Behalf Of Ed Manlove Sent: Wednesday, July 10, 2002 8:49 PM To: (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Re: Scheduler patch
|
|
Joseph, Not to add too much work load, if you have a chance could you give an overview of the proposals out there for the task scheduling and sensor modifications (if any). This could be simply a quick list of lugnet.robotics.rcx.legos threads which (...) (22 years ago, 11-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO Demo.c
|
|
(...) Well, that's much easier than all the crap I was going through. I guess it helps if you actually know what you're talking about. Thanks Steve (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | Re: HOWTO Demo.c
|
|
To solve your problems with demo.c, you sent me your source. There are some problems with it, but I think they are intresting enough to say something about them. The big problem you get with your program is caused by your main function: ---...--- (...) (22 years ago, 10-Jul-02, to lugnet.robotics.rcx.legos)
|
| |
| | ***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)
|
