 | | Re: light sensor problem?
|
|
(...) That should be great! :-) (...) use (...) Absolutely True!!!! :-) (...) I'm quite sure that you can do it!!!! :-) And this should be a real step forward!!!! What a beautiful thing to have some time to spend in this section of code... :-) I'm (...) (26 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: light sensor problem?
|
|
(...) Let me think about how to uncouple this from sys_time, so the code can get higher resolutions. (...) Yes, but even if all active sensors are turned of we are running with a lot of CPU power due to the high sampling speed. If you lower the (...) (26 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Rotation Sensor Values
|
|
(...) That's a good question. Is this the latest tarball? If so, there have been some modifications to the refresh loop, and this may indicate a bug in them. In other words, it could be the double sets of lcd_refresh() and not the actual reading (...) (26 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Rotation Sensor Values
|
|
I added back in the display code, and left out the lcd_refreshes. Then I got a proper counter. I wonder why the refresh was throwing the reading off. Thanks for all your help, Andy (...) (26 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|
| |
 | | RE: light sensor problem?
|
|
(...) I've used the OC1B interrupt for my servo driver code in pbForth. You could use the OC1B to set the settle time for each reading, and then actually read the results when the interrupt expires. Having a structure to tell you which A/D to read (...) (26 years ago, 24-Jul-00, to lugnet.robotics.rcx.legos)
|