 | | Re: MindStorms at Robot Store (Hacking Lego Compatible Parts)
|
|
In message <36493BCF.8BE4F5A8@projo.com>, Brian Stormont <brian@projo.com> writes (...) Has anyone taken apart the small yellow 2x2 connectors yet on the Cybermaster? It looks as if you might not be able to repair them. On my old 1092 TC-II, it was (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: RCX Programming Questions and Sensor Ideas
|
|
In message <3648D155.FF4306@alu...ucsc.edu>, Joshua Delahunty <lugnet.robotics@lugnet.com> writes (...) RECEIVED is spelt wrong in the Spirit.OCX software too. :-) I would like to add though that I was impressed with the high quality of the manual. (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: MindStorms at Robot Store (Hacking Lego Compatible Parts)
|
|
In article <QqqhbWADlXS2EwhF@mk...on.co.uk>, CyberUser <CyberUser @mksftwre.demon.co.uk> writes (...) Dunno about the cybermaster, but the wire links with black 4x4 connectors are very bad. Anyone who has visited Legoland Windsor will know a very (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: RCX Programming Questions and Sensor Ideas
|
|
(...) Oops. I don't know how the scheduler in the RCX works. It might execute 1 opcode from each task in order. If 2 tasks get in sync, then they will never leave the semaphore code as written. Here's a fixed version. I added a random backoff. (...) (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: RCX Programming Questions and Sensor Ideas
|
|
(...) Paul, Are you sure you want to sleep before decrementing r31? As written, r31 is always >= 1 during the sleep -- which prevents any other tasks from obtaining a lock on the resource during this sleep time. In other words, once any two tasks (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: RCX Programming Questions and Sensor Ideas
|
|
(...) I think "oops" applies in this case. Your fix looks correct. (...) It doesn't have to be random, just each task needs a different delay. This is easy, since each task has to run its own version of the code. For task 3 insert 3 noops, for task (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: Ultrasonic Radar
|
|
(...) Polaroid manufactures the 6500 series ultrasonic ranging system that can be purchased in single quantities for less than $50 US, but it can't be directly connected to the RCX. (See (URL) for ordering. See ftp://wirz.com/Polar...r/6500.PDF for (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | What about multiplexing sensors?
|
|
Has anyone attempted to mux the three sensor connections to expand the RCX's sensor capability? Think this is possible? I don't have an RCX of my own [yet] nor the EE capacity to pull this off, so I'm counting on the geniuses out there! --Steve (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: MindStorms at Robot Store (Hacking Lego Compatible Parts)
|
|
I have some black ones as well, I think its for colour coding - yellow for sensors, black for third motor. I think I prefer the old grey cable as its more flexible. Perhaps the stiff thin black cable is supposed to last longer. On the Cybermaster (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: RCX Programming Questions and Sensor Ideas
|
|
(...) Does that support an arbitrary number of tasks? If there are n tasks numbered 1 to n, and task k delays for k cycles on failure, I think you still have to be careful to make sure that the number of tasks n is smaller than the loop overhead h (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Tachocount
|
|
According to the Technical Reference, Tachocount counts the number of revolutions of the motor shafts (of the two built-in Cybermaster motors ONLY). I fiddled a liitle with it, but it doesn't seem too useful, first of all because the internal motors (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: Tachocount
|
|
At least there's one thing that CyberMaster proved - That 3 inputs is not the limit of the H8 or even all the LEGO PBricks. Clearly CyberMaster have 5 inputs, although 2 of them are fixed just like the 2 fixed motors (which is not as bad as it (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | RE: MindStorms at Robot Store (Hacking Lego Compatible Parts)
|
|
Here's a piece I could use: a touch sensor (switch) that is normally closed, with a diode in it. The diode could also be separate, in a brick with contacts on the top and the bottom, so you can stack the sensor, the diode, and your hookup wire. It (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: What about multiplexing sensors?
|
|
You can: 1. Put multiple Touch sensors on the same input but you can't tell which one was hit. 2. Put a Light and Touch sensor on the same input and read normal light levels except when the Touch is hit it the input will read 100. 3. There are a (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | RE: What about multiplexing sensors?
|
|
I'm thinking more along the lines of using all three outputs and all three inputs to code a multi (read "more than three of each input and/or output") I/O multiplexor? This inherently reduces the possible sample rate on each input or output (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: What about multiplexing sensors?
|
|
(...) I've done it using an output port to control a MUX. I've been able to control up to three sensors through one input port. This could be extended to nine sensors through all three sensor ports. I'm working on ways to control more sensors both (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Sensor inputs (more than three)
|
|
Has anyone noticed that each sensor input block has four connectors? If you connect one sensor to two connectors and another sensor to the other two, you essentially read both sensors simultaneously. If this could be munipulated somehow then you (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: What about multiplexing sensors?
|
|
(...) I do. I only have two motors! 8^) But I'm looking at ways to use either the inputs to control the MUX or have an external control that the RCX can query to determine which sensor is currently active. ---Larry +---...---+ Larry Coffin (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: What about multiplexing sensors?
|
|
(...) I guess I've lurked long enough...pardon my ignorance, but what's a MUX? --Andy (28 years ago, 11-Nov-98, to lugnet.robotics)
|
| |
 | | Re: What about multiplexing sensors?
|
|
MUX is short for multiplexer. Just a switch that lets you hook multiple things to one input. (...) (28 years ago, 11-Nov-98, to lugnet.robotics)
|