 | | Why do it? Was: multi-device output controller —Ralph Hempel
|
| | | (...) I have checked this out, and if you use the standard RCX firmware (or other firmware that uses the RCX ROM, then you get the waveforms you are talking about at 125Hz 1/(1ms x 8). You also get polarity information - oh no, I've said too much. (...) (26 years ago, 26-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| | | |
| | | | | Re: Why do it? Was: multi-device output controller —Wes Matchett
|
| | | | | Ralph, Thanks for reigning in the rabbit chase! As the originator of this thread I'd like to respond to the 'why'... I keep running out of ports on my creations. I see 5 or 6 as a practical limit. My criteria for a solution: 1. Entirely compliant (...) (26 years ago, 26-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| | | | | |
| | | | | | | RE: Why do it? Was: multi-device output controller —Ralph Hempel
|
| | | | | | (...) Measuring PWM is not difficult, but it would involve a micro (PIC12C508 anyone?) dedicated to the task and then you would have to get it to drive the RCX, which means motor drivers, etc. If you are willing to spend $50 and LOTS of time, then (...) (26 years ago, 27-Mar-99, to lugnet.robotics, lugnet.robotics.rcx.pbforth)
|
| | | | | | |
| | | | | Re: Why do it? Was: multi-device output controller —Joel Shafer
|
| | | | I think that the solution should also be flexible enough to allow the power to be plugged into either an RCX output port or a battery pack. That way if you didn't want to lug around another battery pack, or if you didn't want to use up another (...) (26 years ago, 26-Mar-99, to lugnet.robotics)
|
| | | | |
| | | | | | Re: Why do it? Was: multi-device output controller —Wes Matchett
|
| | | | My original message described the controller with two inputs, one for device selection and one for device power. This could easily be connected to whatever power source the user desires. (...) (26 years ago, 26-Mar-99, to lugnet.robotics)
|
| | | | |
