| |
> I'm nearly done with my NQC to pbFORTH port of the IR proximity detector,
> but I'm stuck where I have at present got a 30ms delay (Sleep(3) in NQC).
> I expect it isn't critical but the current detector works so well I am
> loath to change any of the parameters. The timers in pbFORTH only count in
> 100ms steps, so how can I get a 30ms or better timer? Do you know how NQCs
> Sleep is implemented?
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 through the RCX tasks and firmware, so it should
be possible in FORTH.
Cheers,
Ralph Hempel - P.Eng
--------------------------------------------------------
Check out pbFORTH for LEGO Mindstorms at:
<http://www.bmts.com/~rhempel/lego/pbFORTH/default.html>
--------------------------------------------------------
Reply to: rhempel at bmts dot com
------------------------------------------------------
|
|
Message has 1 Reply:
 | | Re: Ir transmission
|
| (...) 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 (...) (25 years ago, 16-Apr-99, to lugnet.robotics.rcx.pbforth)
|
Message is in Reply To:
| | Re: Ir transmission
|
| (...) Perhaps EMIT? would do (...) I'm nearly done with my NQC to pbFORTH port of the IR proximity detector, but I'm stuck where I have at present got a 30ms delay (Sleep(3) in NQC). I expect it isn't critical but the current detector works so well (...) (25 years ago, 14-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
|
|
|
|
