 | | 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)
|
| |
 | | Re: New Parts
|
|
(...) One new part that I'm happy to finally see is a 7-long axle! There's a light gray one in <set:8355>, and perhaps some of the other new racers as well. -- David Schilling (24 years ago, 14-Jan-03, to lugnet.technic, lugnet.robotics, lugnet.modelteam)
|
| |
 | | Re: New Parts
|
|
(...) parts to see if they can solve a particular problem. However they tend to create $$ problems instead :) (...) I will! /Tobbe (24 years ago, 14-Jan-03, to lugnet.technic, lugnet.robotics, lugnet.modelteam)
|
| |
 | | Re: Interesting BrickOS Timing Results
|
|
Mark, ANOTHER great find! You are pushing BrickOS to new heights! Ok, so what can we do about this? 1) Provide a constant to set the update frequency at compile time. 2) Provide a variable to set the update frequency at run time. 3) Optimize the (...) (24 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Interesting BrickOS Timing Results
|
|
Oops, found a little bug. ;-) Forgot to turn off the rotation sensors. Caused a wrong reading if you let the program run through the readings more than once. The rotation sensor section should read like this: // with two rotation sensors enabled (...) (24 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Interesting BrickOS Timing Results
|
|
Hi All, The recent posts about interfacing an i2c device to an RCX sensor port (in .robotics) got me interested in looking at the kernel code that handles the sensors. So, I did and found myself looking at the ds_handler function. This function is (...) (24 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
|