Subject:
|
Re: Reading sensors at equal intervals.
|
Newsgroups:
|
lugnet.robotics
|
Date:
|
Sun, 25 Apr 1999 13:59:23 GMT
|
Viewed:
|
1350 times
|
| |
|
|
Dennis Clark <dlc@verinet.com> wrote:
> In lugnet.robotics, Kekoa Proudfoot writes:
> > By standard firmware, I assume you mean using the byte codes ala NQC or
> > something similar. If you only want semi-precise timing, you can use the
> > wait opcode to delay for approximately 100 ms between sensor samples. If
> > you want something more accurate, you can make use of a 1 ms timer to get a
> > better measurement of the actual delay incurred, or you can combine the
> > wait opcode with busy waiting on a timer to make the delay exactly 100 ms.
>
> I though that the four "Timer()" values read out in 100ms increments only.
> Is there a way to get a 1ms timer with NQC?
You are right, the timer values as seen by the firmware are in 1/10ths of a
second. I lost myself in H8-land, which has a 1 ms timer that gets divided
down before being seen by the firmware.
-Kekoa
|
|
Message has 1 Reply:
 | | Re: Reading sensors at equal intervals.
|
| (...) <snip> (...) That looks like a "no" then... How does the timing of tasks work? I seem to recall reading somewhere that the firmware executes the tasks in sequence - is there any timing element to this, or does it just do task 1, then (...) (26 years ago, 26-Apr-99, to lugnet.robotics)
|
Message is in Reply To:
25 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
Active threads in Robotics
|
|
|
|
|
|
