| |
mattdm@mattdm.org (Matthew Miller) wrote:
> Kekoa Proudfoot <kekoa@pixel.Stanford.EDU> wrote:
> > A common workaround is to have the PC occasionally poll the RCX to see if
> > it has anything new to send. This way the PC starts all conversations, and
> > the RCX still gets to send messages (close to) when it needs them sent.
>
> Yeah, that would work great. Does anyone have code that does this? (Don't
> want to reinvent the wheel...) I know of your send program, and Paul Haas's
> perl stuff. Is there anything else I should be looking into? (And Dave,
> wouldn't this be a great NQC 2.1 feature? *grin*)
FWIW, I did something similar to this using NQC and the Datalog.
It uses variable0 for polling and letting the PC know
the Datalog has some "stuff" it wants to send.
http://www.cs.tamu.edu/people/jkp2866/cpsc643/explorerbot.html
jack
j-perdue@tamu.edu
|
|
Message is in Reply To:
 | | Re: Listening to IR via NQC
|
| (...) Yes, that is what I'm looking for. Unless anyone else knows of anything, I guess it's time to dive into the coding. :) (...) Yeah, that would work great. Does anyone have code that does this? (Don't want to reinvent the wheel...) I know of (...) (25 years ago, 24-Sep-99, to lugnet.robotics.rcx, lugnet.robotics.rcx.nqc)
|
6 Messages in This Thread:
  
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
