| | Re: dll problems
|
|
(...) I had this same problem yesterday when I had the IR tower in long range mode and had the RCX quite close to the tower. If its not in long range mode sometimes I have to turn the RCX off and then turn it back on again before dll will (...) (25 years ago, 8-Dec-99, to lugnet.robotics.rcx.legos)
|
|
| | RIS 1.0 vs 1.5: which more "desirable"?
|
|
pardon my newbie-ness. i am researching mindstorms, as i am getting myself a set for xmas. now i am confused about the fact everyone seems to want RIS with the v 1.0 RCX. is this true? i guess i am just caught up in the details and new (to me) (...) (25 years ago, 8-Dec-99, to lugnet.robotics.rcx.nqc)
|
|
| | dll problems
|
|
Hi, guys. I've got legOS compiled and running pretty happily on a redhat 6.0 and a 6.1 machine, after some fussing with settings, i've figured out that it wants to use /dev/ttyS1 for the serial port... however, once the firmware is downloaded, i (...) (25 years ago, 8-Dec-99, to lugnet.robotics.rcx.legos)
|
|
| | LNP collision detection Bug found and fixed
|
|
Hi there, i just found an evil little bug in lnp ( or maybe it's actually a bug in gcc ). The problem is the definition of tx_state as char, and compare operations like if (tx_state < TX_ACTIVE) . The compiler generates wrong code for this (...) (25 years ago, 8-Dec-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: firmdl3 problem? - Tower not responding
|
|
(...) "Tower not responding" really means that it can't write to the tower. Check batteries and the range. (...) Weird. As far as I can tell, exit is called correctly in all circumstances where "tower not responding" could be generated. (...) Again, (...) (25 years ago, 7-Dec-99, to lugnet.robotics.rcx.legos)
|