 | | Re: makelx issues
|
|
Kajim schrieb: (...) Depending on your configuration, there may or may not be certain error messages when building the compiler. They mostly deal with missing system libraries, which doesn't avail to much - legOS has its own libraries. (...) This (...) (25 years ago, 31-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | makelx issues
|
|
Sorry to post configuration issues again; however, I have I beleive sucessfully compiled the new egcs 1.1.2[altho the self tests at the end fail...] and can begin to compile legOS 0.2.3 but makelx segfaults every time it is run... The only guess I (...) (25 years ago, 31-Mar-00, to lugnet.robotics.rcx.legos)
|
| |
| | controling two motors with only one output?
|
|
Hi guys, I was thinking about multiplexing motors, and it came to me that it should be easy to control two motors (only one at a time though) using one output of the RCX. Below, I describe my general idea, but I would like to know if you tackle this (...) (25 years ago, 31-Mar-00, to lugnet.robotics.rcx)
|
| |
| | Re: Modulo operator in NQC
|
|
(...) The limitation is more historical than anything else. Originally expressions were all evaluated at compile time, which is why I have a bunch of operators (%, >>, <<) that have no corresponding bytecodes in the firmware. Over the last few (...) (25 years ago, 31-Mar-00, to lugnet.robotics.rcx.nqc)
|
| |
| | Problems reading active sensors with legos? Is there a solution?
|
|
I'm a bit confused with the reading of my light sensor with legOS. I'm getting values with a lot of "noise"... For example, reading the value for white, I'm getting values with a "noise" from 36 to 24 (raw) around the right value. Reading some post (...) (25 years ago, 30-Mar-00, to lugnet.robotics.rcx.legos)
|
