 | | Re: LNP problem
|
|
(...) You need to compile remote.c for the RCX, that's the part running on the RCX. rcx.c and rcx.h define an interface for your application to use the functions provided in remote.h. Namely to turn on/of/break/reverse the motor ports and to read (...) (24 years ago, 2-Feb-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Is there a NQC HowTo out there someplace?
|
|
(...) Well there are books called "Teach yourself C in 5 days", 21 days and so on... try amazon books. NQC is not actually a full C compiler, it has been simplified a great deal and if you learn the basics from a book, you'd be ready to go with NQC (...) (24 years ago, 2-Feb-03, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: IR header how optional
|
|
(...) I doubt anything (short of a 2MV Lightning Flash) will warm anything in 1 msec. ;) Also, the receiver won't warm up until the header has been read in completion and decoded. So I doubt it's used for that. Normally, in any communication, you'd (...) (24 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
 | | IR header how optional
|
|
(...) Yep. But via our solid new reply framing code, thanks again, now I can see ... (...) Nope. At least not here: now that I look, I see my RCX often doesn't require the PC to send x 55:FF:00. IR command packets like x 10:FE 10:FE PBAliveOrNot and (...) (24 years ago, 2-Feb-03, to lugnet.robotics.rcx)
|
| |
 | | Re: command framing as seen from kernel/program.lrkey_handler
|
|
(...) Just to be more certain we're understanding each other, if that's ok, I'll mention that ... 1) Newbie that I am, I have no clue how frequently brickos switches on bit masks. I wonder if only to decode xD2 RemoteCommand. 2) Using log2(xx & -xx) (...) (24 years ago, 2-Feb-03, to lugnet.robotics.rcx.legos)
|