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 / *36224 (-20)
  Re: Interesting BrickOS Timing Results
 
(...) My thought was that the OCRA interrupt could be used as the general 1ms interrupt and the subsystem handler (which is currently using OCRB) could be called every other time from the OCRA handler by using a flag (toggled every 1ms). Actually, (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
 
Last year I built a robot which used multiple RCXs in the way you mention. I was building a sumo wrestling battle bot, and at some point ran out of sensor ports. For my sumo bot I'd built up some small abstraction layers around the sensors and (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
 
Just a question about this. Won't the IR airwaves will be a major bottleneck for most parallel applications? -Kekoa (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: Interesting BrickOS Timing Results
 
OCRA and OCRB are output interrupts for the 16 bit timer. They can be programmed to fire at specific points along the timers run. So, technically, they cannot be used independently of each other. If OCRA resets the timer value back to zero, then (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: Spybotics to RCX message
 
Hey cool, Mark, this is really going to be useful! I've noticed that when MindScript generates a call to the SendRCXMessage subroutine, it always pops the calling parameters off the stack. For example, this MindScript code: SendRCXMessage(5) (...) (24 years ago, 15-Jan-03, to lugnet.robotics.spybotics)
 
  DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
 
Hi all. I'm taking a course on parallel/distributed operating systems. So this post attempts to find out if someone has thought, or has implemented some kind of distributed application over BrickOS/legOS (from now legOS, for this post). I know (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: I2C device for the RCX
 
(...) Well, one reason for this is that I2C doesn't need a precise clocksignal (thanks to Dick Swan for telling me, I totally forgot about it). All the timer stuff shouldn't matter for the I2C device, so there should be even higher speeds possible, (...) (24 years ago, 15-Jan-03, to lugnet.robotics)
 
  Re: Interesting BrickOS Timing Results
 
(...) Timer B is usually unused but has a lower priority than Timer A. If you do a lot of stuff in the timer A routine, this will block timer B interrupts (especially if timer B generates more interrupts than timer A). The mean thing is that those (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
 
  Re: RCX Motor Controller
 
(...) The RCX is equipped with MLX10402 H-bridge drivers (take a look at www.melexis.com). These drivers have two inputs to control the H-bridge: IN_1 IN_2 0 0 -> motor off 1 0 -> forward 0 1 -> backward 1 1 -> both motorpins switched to ground The (...) (24 years ago, 15-Jan-03, to lugnet.robotics)
 
  Re: Land mine robot
 
Metal detectors are subtle things. Good ones can distinguish between an aluminium ringpull and a gold coin; bad ones get confused by damp soil. The simplest and cheapest design I've seen used a PIC12C508, a hand-wound coil, a resistor and a couple (...) (24 years ago, 15-Jan-03, to lugnet.robotics)
 
  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)

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

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