 | | Re: Interesting BrickOS Timing Results
|
|
Mark, I retrieved the latest BrickOS from CVS, made clean and made the cpu test program you listed. I then made two small changes (to see what would happen); first the results, then the changes: IDLE: 89 2ROT: 87 NOAD: 91 (see below) NIRQ: 98 (see (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Land mine robot
|
|
(...) Or make your own. "Passive" sensors have a 5V constant current, and the raw value is the resistance, scaled so infinite resistance is 1023. "Active" sensors can draw more power, but I don't know anything about them. (24 years ago, 15-Jan-03, to lugnet.robotics)
|
| |
 | | Re: Interesting BrickOS Timing Results
|
|
(...) The delay was added a long time ago after a bit of discussion on this newsgroup/list. A search through old newsgroup posts will turn up a brief series of three posts with subject "Rom sensor read routine" from Apr/May 1999. The explanation (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Patches on SourceForge? A good/bad way to get changes into brickOS?
|
|
I've just posted (URL) note that there are 4 other patches lingering from as far back as September. Will my patch be looked at because it has been posted there? For info, here is the patch description The last version of binutils that brickOS works (...) (24 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: I2C device for the RCX
|
|
(...) Lepomux works with a serial protocol (5 bit preamble, 8 bit data, parity) based on a halfbit-clockspeed of 1 kHz. So compared to your I2C-driver it is dead slow (about 33ms/byte = 30 bytes/s). This slow speed has two reasons: - it's possible (...) (24 years ago, 14-Jan-03, to lugnet.robotics)
|
| |
 | | 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)
|