 | | 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 - (26 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 (...) (26 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 (...) (26 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. (...) (26 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 " (...) (26 years ago, 4-Sep-99, to lugnet.robotics.rcx.nqc)
|
