| | 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 (...) (22 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 (22 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 (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
|
| | 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 (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
|
| | 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 (...) (22 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|