| |
In lugnet.robotics.rcx.robolab, Dick Swan wrote:
> Unfortunately, it is very poorly documented and what
> it means is "set the task priority used for allocating
> and pre-empting devices (motors, sound) as part of the
> "acquire" opcode. A very obscure capability that I
> suspect is not well used.
It does allow some very interesting abilities too. I used it for a
line-follower, where three tasks could dynamicly alter their priority depending
on what was going on. Another use would be a multi-goal system. For instance,
one task could be trying to follow a lightsource, while another is responsible
for getting the robot ("animal") to rest. When it has been too long without
"sleep", the task raises its own priority and tries to acquire control of the
entire system. A lot of fun "behavioral" possibilities.
--
Brian Davis
|
|
Message is in Reply To:
 | | RE: true realtime event?
|
| It's not a true realtime interrupt. Some events may be recognized immediately (e.g. a new "mailbox" message, and some may be recognized on a 100 millisecond background scan (e.g. a "click" event). The event monitoring code does not put the task into (...) (20 years ago, 19-May-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
4 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
