 | | Multitasking
|
| I removed the multitasking features from my cruise and avoid code last night and discovered the robot runs smoother, using less code, and less RCX variables. David Leeper (just wanted to pass this along to those thinking about multitasking) (25 years ago, 13-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| From: "David Leeper" <david.leeper@destiny.com> (...) night (...) Cruise and avoid is a pretty simple type of program, and multitasking really isn't necessary. I wrote a sublimation version of it mostly to play with the concepts of sublimation. Two (...) (25 years ago, 13-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| Hi Alex, I was thinking this over last night and was wondering about how sleeping a task would affect an application that requires precise timing. In the bicycle example, what would happen if the balancing task was asleep when the bicycle began to (...) (25 years ago, 14-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| (...) Actually, this is precisely the case where multitasking works best. A single-threaded application has to poll for events that it is interested in. Regardless of the priority of a particular event, that event has to wait until the application (...) (25 years ago, 14-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| Hi John, I agree that on an interupt-driven system, multitasking is very useful for problems that require precise timing. As soon as the problem occurs, an interupt is fired and the appropriate code handles the problem. But, as you noted, the RCX (...) (25 years ago, 14-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| (...) That isn't the RCX, but rather then standard Lego firmware. legOS avoids most of the limitations of the standard firmware, and there is still room for more interrupt-driven approaches. (...) The difference is that if your bot hits something (...) (25 years ago, 14-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| Hi Alex, I was thinking this over last night and was wondering about how sleeping a task would affect an application that requires precise timing. In the bicycle example, what would happen if the balancing task was asleep when the bicycle began to (...) (25 years ago, 14-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| Hi John, Thanks for for clarifying the differences between the RCX capabilites and the default firmaware capabilities. LegOS sounds like thge right to for true multitasking. But while I'm using the default firmware, it sounds like the sleep task (...) (25 years ago, 14-Jan-00, to lugnet.robotics)
| | | | | Re: Multitasking
|
| From: "David Leeper" <david.leeper@destiny.com> (...) the (...) I was planning on doing this with LegOS, which uses a different scheduler (and John said). With the standard firmware it might work as well, it really depends on how slow the thread (...) (25 years ago, 14-Jan-00, to lugnet.robotics)
| |
