Subject:
|
Re: Interesting BrickOS Timing Results
|
Newsgroups:
|
lugnet.robotics.rcx.legos
|
Date:
|
Tue, 14 Jan 2003 04:07:03 GMT
|
Viewed:
|
2914 times
|
| |
|
|
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 (23%)
cputs("2rot"); msleep(100);
ds_rotation_on(&SENSOR_1);
ds_rotation_on(&SENSOR_2);
cpu();
ds_rotation_off(&SENSOR_1);
ds_rotation_off(&SENSOR_2);
sleep(3);
Mark
|
|
Message has 2 Replies:
 | | 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 (...) (21 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
| | | 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 (...) (21 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
Message is in Reply To:
| | 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 (...) (21 years ago, 14-Jan-03, to lugnet.robotics.rcx.legos)
|
19 Messages in This Thread:
  
 
- Entire Thread on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
This Message and its Replies on One Page:
- Nested:
All | Brief | Compact | Dots
Linear:
All | Brief | Compact
|
|
|
|
