 | | true realtime event? —Elizabeth Mabrey
|
| | | Hi I am trying to find out whether the event in Robolab is a truly realtime interrupt. Once the event is triggered, does it truly preempt the current running process? Input or suggestion to reading material will be appreciated. ---...--- -------- (...) (19 years ago, 19-May-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| | | |
| | | | | RE: true realtime event? —Dick Swan
|
| | | | | 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 (...) (19 years ago, 19-May-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| | | | | |
| | | | | | | Re: true realtime event? —Brian Davis
|
| | | | | | (...) 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 (...) (19 years ago, 19-May-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| | | | | | |
| | | | | Re: true realtime event? —Ralph Hempel
|
| | | | I can't answer your actual question, but have a close look at the way your tagline comes across. It looks (unintentionally, I'm sure) like you are closely affiliated with the LEGO company. I googled for your name and found a link to a post where you (...) (19 years ago, 19-May-05, to lugnet.robotics.rcx.robolab, lugnet.robotics.rcx)
|
| | | | |
