To LUGNET HomepageTo LUGNET News HomepageTo LUGNET Guide Homepage
 Help on Searching
 
Post new message to lugnet.roboticsOpen lugnet.robotics in your NNTP NewsreaderTo LUGNET News Traffic PageSign In (Members)
 Robotics / *36214 (-20)
  Re: Interesting BrickOS Timing Results
 
From the second scope screen capture here : (URL) you can see that the analog settling time is about 10 microseconds for the rotation sensor. Philo www.philohome.com (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: Interesting BrickOS Timing Results
 
(...) I've found that any interrupt on the RCX has a minimum overhead of 101 to 113 states (or about 7 us). This is the time taken by the CPU to recognize and dispatch the interrupt plus the time the ROM routine takes to dispatch the interrupt to (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: Interesting BrickOS Timing Results
 
Joe, That's definitely an improvement! So, that would be a 250 Hz sample rate for any given sensor. I just tried a modification similar to yours that did all 4 conversions every OCRA/B interrupt (or 1 KHz sample rate) and got: IDLE: 82 2ROT: 77 (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: Interesting BrickOS Timing Results
 
I did some "real world" tests with this update. I was Astounded at what a difference it makes. The bot I was testing with is a killough platform; which I had tried for hours previously, to get it to follow a line smoothly. I think BrickOS was giving (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Spybotics to RCX message
 
The following NQC code will define a routine to send a message to the RCX or Scout: // Sends an RCX PBMessage to RCX or Scout // nMessage = 1 - 255 __nolist void SendRCXMessage (const int nMessage) { asm { 0xe3, &nMessage }; asm { 0x17, 37 }; } I'm (...) (24 years ago, 15-Jan-03, to lugnet.robotics.spybotics)
 
  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)
 
  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)

Next Page:  5 more | 10 more | 20 more
Redisplay Messages:  All | Compact

©2005 LUGNET. All rights reserved. - hosted by steinbruch.info GbR