 | | Re: Timing of RCX statements
|
|
(...) Thanky Dave for your reflections concerning the timing. The thing that caused some astonishment and a little bit of frustration is that the RCX is so slow. O.K. - the code sent to the RCX is interpreted and this needs some time. However, I was (...) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | 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 (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | 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 (...) (24 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 (...) (24 years ago, 24-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Timing of RCX statements
|
|
I was trying to simulate a serial link by using an output of the RCX. I didn't work and when I analyzed the timing, I found out that the RCX's execution of statements is far too slow for the protocol I wanted to simulate. So I made some measurements (...) (24 years ago, 23-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Monitor() and Event()
|
|
Can someone teach me more on Monitor() and Event()? Does the Monitor() check the event status repeatly or we have to make a repeat task to activate the monitoring job? If it is not checking the event status repeatly, why we cannot just read the (...) (24 years ago, 23-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC 2.2 r2 released
|
|
A few minor bug fixes from r1 (URL) reply to: dbaum at enteract dot com (24 years ago, 22-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: RCX Code tutorial or better program all together?
|
|
(...) There sure is.... NQC, a program of the gods. (URL) the news group lugnet.robotics.rcx.nqc is where you discuss NQC. -- Coin-Op's For Sale!: (URL) Lego Workshop: (URL) Lego Club: (URL) (24 years ago, 19-Oct-00, to lugnet.robotics, lugnet.robotics.rcx.nqc)
|
| |
| | Re: Connecting 2 RCXs
|
|
(...) Hook up the output of RCX.A to the Input of RCX.B. Set the RCX.B's input to Touch. Now toggle the RCX.A's output from OFF and float. This will turn the ground 'short' on and off and work Exactly like a switch. No power runs though the Input (...) (24 years ago, 19-Oct-00, to lugnet.robotics.rcx.nqc)
|
| |
| | NQC and RCXCC
|
|
Using NQC together with RCXCC (by Mark Overmars) is a fine combination that fulfills my demands for writing software, debugging and testing. Unfortunately, Mark Overmars, the author of RCXCC will not do any further development for this product. (...) (24 years ago, 19-Oct-00, to lugnet.robotics.rcx.nqc)
|
