| | Re: LNP collision detection Bug found and fixed
|
|
(...) it is already defined this way... indeed it looks like egcs for h8300 treats char as unsigned by default. look at the following test proggy... char ch; void showbug(void) { if (ch < 1) ch=-2; } ... and the disassembled code (...) (...) (25 years ago, 10-Dec-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: rotation sensors in legOS 0.2.2
|
|
(...) I'm pretty sure that the battery-power thing is not legOS specific- over the summer, I noticed that at low battery the raw values themselves increase (weird- I'd expect a decrease) and that throws off the sensor detection. Presumably (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: LNP collision detection Bug found and fixed
|
|
(...) It shouldn't matter if it does. More likely, it seems to me, is that TX_COLL is defined like this: #define TX_COLL -1 in which case, the offending statement becomes: tx_state=-1; which is old-style for: tx_state-=1; (should generate a (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|
|
| | Re: rotation sensors in legOS 0.2.2
|
|
(...) Hi Michael, i also tried the new sensor code and it seems to work for me. I noticed the rotation sensor to stop working properly with nearly exhausted batteries, but i think that's a minor issue, maybe it's not legOS specific. (...) well, most (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|
|
| | rotation sensors in legOS 0.2.2
|
|
Has anyone out there successfully had a rotation sensor running in legOS 0.2.2 I have had a quick look through the last few posts I could find on lugnet and we have recompiled legOS to include the updated dsensor.c and dsensor.h code found on the (...) (25 years ago, 9-Dec-99, to lugnet.robotics.rcx.legos)
|