 | | Re: What is "Stop Event Monitoring" for?
|
|
Don't know specifically about Robolab, but usage might be. "I want to monitor a bump sensor for the next 100 milliseconds for an event; if the event doesn't happen in this time, then stop monitoring for the event." One way to program this is define (...) (22 years ago, 28-Dec-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Maximum Subroutine numbers?
|
|
I don't use Robolab, but I can offer some insight into how the RCX firwmare operates with subroutines (and events) that may partially explain your problems. RCX firmware supports 8 (eight) subroutines per slot. Internally they are numbers 0 to 7. (...) (22 years ago, 28-Dec-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Is there a bug database?
|
|
Is there a bug database for Robolab? Unless it's the first perfect program ever written, there have to be bugs. Is there a procedure in place to report suspected bugs? Are they being cataloged, hopefully in a searchable database? (22 years ago, 28-Dec-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Events in Robolab
|
|
After dozens of hours of experimentation, it is my conclusion that event-driven programming in Robolab is unreliable. Eventually, the RCX stops responding to events. This does not always happen at the same point in a given program, nor is it (...) (22 years ago, 28-Dec-03, to lugnet.robotics.rcx.robolab)
|
| |
| | Re: Maximum Subroutine numbers?
|
|
Following up my own post with more information: I found in the Minnesota FIRST League's Software Training Manual the statement: "Local subroutines are identified and called by number (1-8)." This suggests that unlike containers and most other (...) (22 years ago, 28-Dec-03, to lugnet.robotics.rcx.robolab)
|
