 | | Re: Wire communication
|
| (...) I think all you really need to do is switch the motor port between "float" and "brake". That's the same as opening and closing a touch sensor. I've used that for simple signals, and it seems to work fine, but I haven't tried more complex (...) (22 years ago, 9-Dec-04, to lugnet.robotics.rcx.legos)
| | |  | | Re: The Great Ball Contraption (was Re: Rolling ball clock revisited)
|
| (...) There will be a minimum throuhgput to solve that. Right now, we're testing with 1 ball/second. So, the very first module will be regulated to run somewhere just below that speed. As long as everyone else can meet the minimum, there will be no (...) (22 years ago, 9-Dec-04, to lugnet.technic, lugnet.robotics)
| | |  | | Re: The Great Ball Contraption (was Re: Rolling ball clock revisited)
|
| (...) Looks fun ;o) One of my goals when building Bob's clock was to get my feet wet in ball moving... One foreseeable issue: if an upstream unit has more throughput than a downstream one, we shall get ball overflows! Philo (22 years ago, 9-Dec-04, to lugnet.technic, lugnet.robotics)
| | |  | | Wire communication
|
| Hello, I am currently trying to implement a communication protocol between two bricks using just one of the copper wire given with the brick. The protocol is based on manchester encoding, using a well-timed alternation of up and low signals. My (...) (22 years ago, 9-Dec-04, to lugnet.robotics.rcx.legos)
| | |  | | Re: input used as output
|
| well I've decided to go with 2 RCX's anyway. Later I may switch to a non-lego controller ala handyboard, brainstem, etc. Anyway, for the record, the current is also pulsed in order to get the reading from the photoreceptor. I still suspect I could (...) (22 years ago, 9-Dec-04, to lugnet.robotics)
| |