| |
In article <FKvK6J.MH7@lugnet.com>, "Vlad Dumitrescu"
<vladdu@nospam.hotmail.com> wrote:
> > As for libraries, I'm not sure what qualifies as "cute", but within NQC,
> > all of the RCX communication is containd within its own set of classes
> > (which I call rcxlib). Compile and link against these classes to add RCX
> > functionality to your own C++ programs. The access is robust, but not
> > "high level". For example, there isn't a method to turn on a motor.
> >
> > Dave Baum
>
> Thanks for the explanation. So, it's back to the basics! ;-)
>
> I did not explain my question very well, I think. What I would like to do is to
> steer the RCX from the PC, by querying its state and send it high-level
> commands (for example to make another maze-walker-thingie). It can be done wirh
> SendMessage, but it would be much nicer to be able to send more than a byte at
> a time...
Could you be more specific on "querying its state" and "high-level
commands"? If you're willing to write custom C++ code, you can pretty
much do whatever you want on top of the rcxlib stuff from the NQC source
base. Its pretty easy to send messages to control motors, read
variable/sensors, etc. You could also send commands to start individual
tasks, read the datalog, or send messages (which would then be interpreted
by an NQC program on the RCX).
Does any of this answer your question?
Dave Baum
--
reply to: dbaum at enteract dot com
|
|
Message has 1 Reply:
Message is in Reply To:
7 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
|
|
|
|
