Subject:
|
Re: Ir transmission
|
Newsgroups:
|
lugnet.robotics.rcx.pbforth
|
Date:
|
Fri, 16 Apr 1999 06:31:17 GMT
|
Reply-To:
|
robots@jpsc.co.#antispam#uk
|
Viewed:
|
1983 times
|
| |
|
|
> In general, NQC hooks in through the RCX tasks and firmware, so it should
> be possible in FORTH.
The bytecode interpreter does it, which is what NQC maps to (opcode 43).
I'd prefer a timer (or access to a clock) with millisecond resolution rather
than a delay because things will get interesting whan multitasking.
What is the CPU clock frequency of the RCX?
--
John Cooper, Wallington, UK
|
|
Message has 1 Reply:
 | | RE: Ir transmission
|
| (...) I think its around 16 Mhz for the crystal and 4 MHz for the cycle time. I think there is a msec timer buried in the OC1A handler (see Kekoa's disassembly) I agree that we want something to trigger a run flag instead of having to check the (...) (26 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
Message is in Reply To:
| | RE: Ir transmission
|
| (...) Alas, I only used the firmware timers available as core RCX firmware calls. I can look through Kekoa's disassembly to see if there are higher resolution timers available ( I think the motor timers might be useful ) In general, NQC hooks in (...) (26 years ago, 15-Apr-99, to lugnet.robotics.rcx.pbforth)
|
9 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
|
|
|
|
