 | | Re: light sensor problem?
|
|
(...) Oh! So readings are more stable, and it isn't just my imagination. That's good to know :) (...) Those values used to pretty cleanly define max and min- or at least, they must have, since I consistently got 15-105 values (or roughly what he (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) To achive scaling of light sensor reading from 0..100 the following theoretical formula should be used: light = 146 - scaled / 7, where scaled is the reading of AD_X >> 6. I found this at (URL) this page contains a lot of electrical (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: Possible bug with bss allocation
|
|
(...) Paolo and others: Eddie and I have talked about this, and we both agree that this is a big change- so I think we are aiming for this for 0.2.5. Since it has already been seven months since 0.2.3, I think we'll aim for getting 0.2.4 out the (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) I looked through the dsensor stuff, and it looks quite bad to me... We execute a delay loop inside an interrupt handler. We issue the command to start the next read from that same handler. This will read the sensors very quickly, for the cost (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
| | Re: light sensor problem?
|
|
(...) I'm the one that fixed active sensor reading... :-) Settle time is one of mine... Kekoa msg about this problem (a very old one in this ng if I remember) helped me to solve things. (...) I patched the reading routine in ds_handler to fix a vary (...) (24 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
