Subject:
|
Re: Multitasker test script
|
Newsgroups:
|
lugnet.robotics.rcx.pbforth
|
Date:
|
Thu, 13 May 1999 07:20:11 GMT
|
Reply-To:
|
robots@jpsc.co.SPAMLESSuk
|
Viewed:
|
1616 times
|
| |
|
|
Perhaps I should not have stripped all the comments for speed :)
\ The rationale for the delay above and the delay after the IR flash is
\ that the message is 77 bits of 417 microseconds each, a total
\ transmission time of 32 milliseconds, the first delay is to ensure
\ that the sample is taken in the middle of the flash, the second is
\ there to make sure the transmission has finished before firing again.
The NQC DEFCON code definately works with a 30ms delay after firing before
sampling, when I had figured out why it works I came up with the above to
be slightly more scientific about it. Once I have a non-blocking SedMessage
I can play about with FlashDelay to find the best time during the ping to
sample.
--
John Cooper, Wallington, UK
|
|
Message is in Reply To:
 | | RE: Multitasker test script
|
| John, I've been looking at your ping routine and note the following... Even if FF EMIT did not block, the wait makes things irrelevant. At 2400 baud, the FF is out the port within 4 msec. In fact, if EMIT did not block, you could probably wait jsut (...) (25 years ago, 13-May-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
|
|
|
|
