Subject:
|
Re: Communicatin between NQC and legOS
|
Newsgroups:
|
lugnet.robotics.rcx
|
Date:
|
Tue, 26 Sep 2000 11:28:27 GMT
|
Viewed:
|
1662 times
|
| |
|
|
In lugnet.robotics.rcx, Dave Baum writes:
> The protocol used by the standard firmware (which is what NQC relies on)
> is described on these sites:
>
> http://graphics.stanford.edu/~kekoa/rcx/
> http://www.crynwr.com/lego-robotics/
very good hint !!
> the opcode of interest is F7 (thats what gets sent as a transmitted
> message). The entire packet would look like this:
>
> 55 ff 00 f7 08 x ~x s ~s
>
> where x is the message you want to send
> ~x is the one's complement of x
> s is the checksum (f7 + x)
> ~s is the one's complement of the checksum
OK, but do i have to create this frame using legos ??
I tried but it doesn't work.
(thank you so far dave baum !
I received your book today, hope this will help me.)
|
|
Message has 1 Reply:
 | | Re: Communicatin between NQC and legOS
|
| (...) you won't be able to use LNP - those packets are completely different from the Lego firmware ones. You'll need to write bytes directly to the serial port (I'm not sure what support there is for this in legOS since once you start munging the (...) (24 years ago, 27-Sep-00, to lugnet.robotics.rcx)
|
Message is in Reply To:
| | Re: Communicatin between NQC and legOS
|
| (...) The protocol used by the standard firmware (which is what NQC relies on) is described on these sites: (URL) opcode of interest is F7 (thats what gets sent as a transmitted message). The entire packet would look like this: 55 ff 00 f7 08 x ~x s (...) (24 years ago, 23-Sep-00, to lugnet.robotics.rcx)
|
6 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
|
|
|
|
