 | | Re: Interesting BrickOS Timing Results
|
|
This was a terrific analysis. It's not surprizing that current implementation hogs so much CPU time. If all four A/D channels are scanned every 150 us then the A/D interrupt is occuring every 37.5 us since each A/D channel generates its own (...) (24 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Interesting BrickOS Timing Results
|
|
(...) This would be my favourites. If one builds a fast moving robot, main concern will be how fast the robot reacts to light sensor changes or how small the structures could be that the light sensor will "see". If one builds a thinking robot, for (...) (24 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Hi, I'm new
|
|
(...) (24 years ago, 14-Jan-03, to lugnet.robotics)
|
| |
 | | Re: I2C device for the RCX
|
|
Dick Swan wrote: >I don't understand your references to clock pulses. The I2C protocol >is edge triggered with a data bit transferred as the clock signal >transitions from a LOW to HIGH value. Where do clock pulses come into >play? OK, as a (...) (24 years ago, 14-Jan-03, to lugnet.robotics)
|
| |
 | | Re: New Parts
|
|
(...) Oh, these new sets also have a nice new tire (unfortunately only one per set) in them. It says 36.8x14 ZR on the side. They have the rubber permanently attached, and are 3 2/3 bricks tall. -- David Schilling (24 years ago, 14-Jan-03, to lugnet.technic, lugnet.robotics, lugnet.modelteam)
|