 | | 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)
|