Subject:
|
Timing of RCX statements
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Mon, 23 Oct 2000 12:30:44 GMT
|
Viewed:
|
1948 times
|
| |
|
|
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 of statements (e.g. wait, off/on, if-then-else,
etc.). There are some things I don't understand like the following.
An execution of a motor-on command needs something around 3.4 ms. I did the
measurement (NQC) by putting 100 (and 1000) of this statement in a sequence,
measured the time with the FastTimer and divided by 100 (1000). A Wait (1),
i.e. a 10 ms wait needs a bit more than 10 ms.
When I tested
On (OUT_B);
Wait (1); /* 10 ms delay */
The result was between 10 and 11 ms. I expected approx. 14 ms.
In general it seems that each simple command needs around 3 to 4 ms (also a
WAIT (0) ).
My question: has anybody done some measurements of the above kind? What about
the above example (10..11 vs. 14 ms)?
|
|
Message has 1 Reply:
 | | 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)
|
3 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
