 | | Re: Waiting for more than one event
|
|
(...) You could setup two concurrent events or do something like : Loop until 5 seconds is up If Touched, exit loop (20 years ago, 29-Aug-04, to lugnet.robotics.rcx.robolab)
|
| |
| | Waiting for more than one event
|
|
What is the best way of waiting for more than one type of event? I want to turn on a motor and run it for 5 seconds or until the tough sensor is pressed, whichever comes first. This seems like such a basic problem that I'm quite sure there must be a (...) (20 years ago, 29-Aug-04, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Understanding Event Register Container
|
|
(...) Container defaulted to the Red Container. The actual question was raised by one of my students. He couldn't understand why Variable 0 was assigned a 0. I suspect that the 0 means "the event register". The designation is sure confusing. To (...) (20 years ago, 27-Aug-04, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Understanding Event Register Container
|
|
(...) Are you zeroing out the container in this step? I'm not used to reading a robolab program like this. How did you output the text? I would be interested in see the vi. Could you post it or send it to me? James (URL) (20 years ago, 27-Aug-04, to lugnet.robotics.rcx.robolab)
|
| |
| | Understanding Event Register Container
|
|
Below is text output of a Robolab 2.5 program using two concurrent events. What exactly does "Variable 0 = 0" mean? It's right under the EventLand label. This line represent the default Red Container being assigned the Event Register Container. (...) (20 years ago, 27-Aug-04, to lugnet.robotics.rcx.robolab)
|
