 | | Re: IRPD revisited
|
|
(...) Very nice! Although I think your statement about robots breaking apart when they hit a wall is a bit over-dramatic. Lego creations stick together pretty well -- I've built a large number of robots with mechanical bump sensors. That's not to (...) (27 years ago, 18-Sep-99, to lugnet.robotics)
|
| |
 | | Re: Decoding the LEGO IR remote control
|
|
(...) The Lego IR protocol is pretty simple. If you have demodulated output, why not dump some samples here so we can see if they make sense? The encoding is straight serial, but inverted - a pulse of light indicates a zero or a low voltage on a (...) (27 years ago, 18-Sep-99, to lugnet.robotics.rcx)
|
| |
 | | Re: color sensor: was ( Light sensor values)
|
|
Stephen P. Gibbons <lego-robotics@crynwr.com> wrote in message news:37E361B0.6CA5FE...ech.net... (...) of the (...) sensor can (...) given (...) You have a good idea, but the LEGO light sensor is a silicon photo transistor which is mostly sensitive (...) (27 years ago, 18-Sep-99, to lugnet.robotics)
|
| |
 | | Q:#include and RCXCC 3.0 beta help requested
|
|
Hello. I have two questions about #include. I am using RCXcc Beta 3.0. 1. How do you specify the default include path. Is there an environment var? 2. When I use the full path (E:\lego\application...\file.nqh) I get an error that says there is no (...) (27 years ago, 19-Sep-99, to lugnet.robotics.rcx.nqc)
|
| |
 | | Re: Q:#include and RCXCC 3.0 beta help requested
|
|
There was a bug with #include for files using MSDOS line endings in NQC 1.0b1. I'm pretty sure RcxCC beta 3.0 used this version of NQC. The bug was fixed in NQC 1.0b2, which is available from (URL) for an include path, try setting the environment (...) (27 years ago, 19-Sep-99, to lugnet.robotics.rcx.nqc)
|