|
|
 | | Re: 4095 Record and Play
|
| To add some further information, I popped the unit open last night and observed that, as I had hoped, mechanically the unit should be capable of operating correctly. Each motor channel has a mouse style slotted wheel and sensor, so the firmware (...) (22 years ago, 12-Nov-03, to lugnet.robotics)
| | | | | Motors on Sensor ports
|
| I'm just curious if there's any harm in connecting motors to active sensor ports... I know you don't get very much voltage/speed/torque, but you do get interesting readings that can be used to detect when the motor stalls. This is potentially a very (...) (22 years ago, 12-Nov-03, to lugnet.robotics.rcx)
| | | | | Re: One Input - Two Outputs?
|
| (...) That's one of the links I was trying to find the other day! Thanks. I'm not sure if it will do what I want, but I'll have to stare at it a while to find out. Keep the ideas coming, if there are more. -Duane (22 years ago, 12-Nov-03, to lugnet.technic, lugnet.robotics)
| | | | | Re: One Input - Two Outputs?
|
| (...) You also might check out a construct called a Directional Transmission. This is a simple setup using a sliding worm gear that does pretty much what you are describing. Michael Powell has a web page describing his design that I used (...) (22 years ago, 12-Nov-03, to lugnet.technic, lugnet.robotics)
| | | | | Re: One Input - Two Outputs?
|
| (...) One way to do that is to have a rubber-band/spring/shock holding "Output B" in it's starting position. Then, you can use a differential to move both A and B. Going forward, A will be easier to drive, so it will push A to it's limit, then B (...) (22 years ago, 12-Nov-03, to lugnet.technic, lugnet.robotics)
|
|
