 | | Re: Interesting BrickOS Timing Results
|
|
(...) I forgot to mention... This is *almost* the same as moving some of the subsystem code into a seperate high priority task. For example, LCD refresh code is executed in the 1ms timer ISR. It really doesn't need to be in the ISR. It can do it's (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Interesting BrickOS Timing Results
|
|
(...) 250msec? Not blocked entirely, but delayed. That's what I meant by "stutter". I've measured the general interrupt handler to take anywhere from 70-150us. So, the higher the sample rate the more significant the disruption. Anything faster than (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | RE: Interesting BrickOS Timing Results
|
|
(...) I have been following this thread in my peripheral vision for a while now. All of the talk is very interesting and appears to be leading to a general question about how and why the drivers are the way they are.... As a point of interest, some (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos, lugnet.robotics.rcx.pbforth)
|
| |
 | | Re: DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
|
|
Hi there, did some worh with rcx/legos/DSM in my thesis which can be found at www.cs.uit.no/~kenne.../Thesis.ps Although i didnt share the memory of each rcx, i installed a dsm server(created at the local university) on a notebook which each rcx (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: Interesting BrickOS Timing Results
|
|
Mark Riley wrote: > Actually, if we move the sys_time > handler back to OCRA (instead of the watchdog NMI), > then we could just check if bit 0 of sys_time is zero to > determine if the subsystem handler should be called (plus > this will get (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Inverted Pendulum
|
|
Hi, I just stumbled over this site (URL) thought that may be nice pet project for myself to work on. To build and program a robot balancing an inverted pendulum. First single, then double... :) Looking at the videos there is seems the bot needs (...) (24 years ago, 15-Jan-03, to lugnet.robotics)
|
| |
 | | MOC: RCKillough Mk III
|
|
Hellu! Another RCKillough I made to a Swedish LEGO fest, this is the third Killough I've built. Someday I'll have to make a fourth version with some real function :) (URL) me know what you think! Notice that follow-ups should go to lugnet.technic. (...) (24 years ago, 15-Jan-03, to lugnet.announce.moc, lugnet.robotics, lugnet.technic)
|
| |
 | | Re: DISTRIBUTED/PARALLEL CLUSTER for legOS through n*RCX
|
|
Yes Kekoa it's a bottle neck, as I wrote on the original message, the main idea is to distribute the load, with the MINIMUM amount of network traffic. I think that all the RCX should be connected through fibre optics, in order to implement the (...) (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | Re: I2C device for the RCX
|
|
(...) We'll first check it out before boasting about it ;) The whole thing won't work without some hardware modifications on the lepomux - so I'll tell you about it in two or three weeks. Gunther (24 years ago, 15-Jan-03, to lugnet.robotics)
|
| |
 | | Re: Interesting BrickOS Timing Results
|
|
Hi Marc, (...) Nice idea, but wouldn't that result in at least one of four cycles beeing blocked by OCRA? or is our system interrupt finished within less than 250msec? (...) Right, that was what I did for my Lepomux patch - works fine. Gunther (24 years ago, 15-Jan-03, to lugnet.robotics.rcx.legos)
|
| |
 | | 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)
|