Subject:
|
Re: Scout programming
|
Newsgroups:
|
lugnet.robotics.rcx.nqc
|
Date:
|
Thu, 28 Mar 2002 01:05:50 GMT
|
Viewed:
|
3606 times
|
| |
|
|
In article <GtLp4p.BAJ@lugnet.com>, "Bill" <rcairflyer@hotmail.com>
wrote:
> I used BricXCC and the USB tower to program the Scout. I was wondering how
> the programming was done by NQC. Are the Scout and RCX command sets
> compatible? How so? Or does NQC translate and assemble differently
> depending on target brick?
>
> There are many programs written for the RCX. Are those programs compatible
> with the Scout (ignoring motor/sensor hardware differences)?
>
> For the RCX and the Scout, how similar are the processors and command sets?
> The Scout SDK documents the assembly code and subroutines. Is there a
> similar document for the RCX?
There's a lot of overlap between Scout and RCX, but they aren't
identical. Most of the stuff that NQC has to generate (math, control
structures, etc) is common. The system calls tend to be very different,
but this is all defined in an API file that is processed by NQC before
compiling your program. You can view the api file by typing "nqc -api".
If an NQC program only uses features that are present on both Scout and
RCX, then the program will compile for either target.
The RCX 2.0 SDK includes a document that explains the RCX bytecodes (I
know the beta version included it, I'm not sure about the final version
but I don't see why it wouldn't).
Dave Baum
|
|
Message is in Reply To:
 | | Scout programming
|
| I used BricXCC and the USB tower to program the Scout. I was wondering how the programming was done by NQC. Are the Scout and RCX command sets compatible? How so? Or does NQC translate and assemble differently depending on target brick? There are (...) (23 years ago, 26-Mar-02, to lugnet.robotics.rcx.nqc)
|
2 Messages in This Thread:
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
