 | | Re: Monitor() and Event()
|
|
(...) I decided to write a small sample program showing how to configure events. Check out events.nqc at (URL) reply to: dbaum at enteract dot com (26 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: Announce: October NRB Meeting
|
|
(...) Wish I could come, but we have a Legofest planned for The Construction Site at 3 - that would be too much driving. Regrets, -Tim (26 years ago, 24-Oct-00, to lugnet.robotics)
|
| |
 | | Re: Monitor() and Event()
|
|
(...) Monitoring is automatic (done by the firmware). Monitoring stops when control leaves the monitor statement, so something like this: while(true) { monitor(EVENTS) { } catch { } } will miss a lot of events. You need to configure the events using (...) (26 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: Timing of RCX statements
|
|
(...) I wouldn't expect Wait() to be very precise. I haven't looked at the firmware in great detail, but generally when writing this sort of thing you set up timing chains. Imagine a function that gets called every 1ms for bookkeeping... void (...) (26 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: single motor pneumatic pump and switch
|
|
Yes we do... but that's why we play with LEGO(R) too : ) "John Barnes" <lego-robotics@crynwr.com> wrote in message news:4.2.0.58.200010...lserver... (...) (26 years ago, 24-Oct-00, to lugnet.robotics)
|