 | | Re: decoding a message sent by an RCX
|
|
Dave Baum wrote: [snip] (...) Better yet, make it generate the code that I want it to generate, not what I tell it to generate. Thanks for giving us all such a great language ... without NQC I most likely would have an RCX collecting dust. - Nick - (25 years ago, 5-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: decoding a message sent by an RCX
|
|
(...) I wondered about that - hardly any traffic in the newsgroup despite numerous downloads of NQC. I hope its because people are just too busy building stuff and programming it with NQC and RcxCC. Perhaps I should add a few more bugs to NQC just (...) (25 years ago, 5-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: decoding a message sent by an RCX
|
|
(...) [...] I think something like this was already made by LEGO itself in the lab while creating the RCX/CyberMaster software. I say this because they seem to have forgot to remove the CABLE mode of transmission from the Spirit.ocx when deploying (...) (25 years ago, 4-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: decoding a message sent by an RCX
|
|
Woaw ! This could be great to have a full featured rcx expansion board... It should however be not too expensive, and in my opinion very basic to allow anything to be made. A "simple" (hehe :-) 8 bit Input / Output expander would be very, very nice. (...) (25 years ago, 4-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | RE: decoding a message sent by an RCX
|
|
Dave wrote... (...) Remember, you can send arbitrary ASCII data using pbFORTH. For example, to send "Hello World" you just use... : HELLO ." Hello World" CR ; Or to identify your RCX, you could use something like... : WHOAMI ." I am RCX number " (...) (25 years ago, 4-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: decoding a message sent by an RCX
|
|
(...) Yes, you are correct - 11 bits total per byte. And yes, this is very non-standard. I believe the signal is inverted - meaning that IR light is present for "0" bits, and no light for "1" bits. But I'm going from memory here and haven't looked (...) (25 years ago, 4-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | decoding a message sent by an RCX
|
|
hiya, I have been working on an idea to extend the number and type of devices that the RCX can control. I started with the idea of encoding serial data on one of the motor lines and decoding that in a PIC to do <stuff>. However, because working at (...) (25 years ago, 3-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
| | MacNQC in beta test
|
|
MacNQC is a GUI based version of NQC for the Macintosh. You can read more about it here: (URL) course, you can also find it from the main NQC site: (URL) Baum (25 years ago, 23-Aug-99, to lugnet.robotics, lugnet.robotics.rcx.nqc)
|
| |
| | Rcx Command Center version 3.0 beta avaialbe
|
|
Dear All, I am happy to announce that on the RcxCC web site there now is a beta release of RCX Command Center version 3.0 available. (URL) version uses NQC 2.0 (beta). Note that NQC 2.0 is not compatible with previous versions. RcxCC 3.0 includes a (...) (25 years ago, 16-Aug-99, to lugnet.robotics.rcx.nqc)
|
| |
| | Re: NQC floating point library?
|
|
(...) Sorry, the standard RCX firmware doesn't support anything other than signed 16 bit integer math, so NQC doesn't do floating point. Depending upon the problem, you may still be able to convert the operation into appropriate integer math. If you (...) (25 years ago, 15-Aug-99, to lugnet.robotics.rcx.nqc)
|
