|
|
|
![]() |
|
|||||||
|
||||||||
|
|
Thread Tools |
Rating:
|
Display Modes |
|
#12
|
|||||
|
|||||
|
Kevin A wrote:
Quote:
Sanddrag wrote: Quote:
If you're standing beside a railroad track, not moving, and a train goes by at 50 mph -- well, it looks like the train is passing at 50 mph, right? Now, if you're in another train, heading in the opposite direction of the first, but also at 50 mph -- well, then that first train looks like it's traveling at 100 mph. Think of things the opposite way as well. If you're on a train that's running parallel to the first at 50 mph, it appears as if the other train isn't moving at all. If the first train speed up to 60 mph, it would appear to us as if it's going 10 mph. See? Imagine both sides of the clutch are now spinning at 300 RPM. It appears as if they're not moving. Speed one side up to 1000 RPM and then it appears as if it's spinning 700 RPM when your frame of reference is moving at 300. I'm not sure if this is helping. The real point is that "relative clockwise" motion never requires the motors to spin clockwise. It just requires that the left end spin faster than the right end such that the clutch slips. After a certain point, you could actually turn the drill off altogether. generalbrando wrote: Quote:
George wrote: Quote:
Turning is an interesting issue, I think, and something I'm still investigating. It seems that the gearboxes would behave very differently depending on how the robot turned. If it were to steer like a car, the gearboxes, together, could be used as a "differential" and the speed differences between the motors do not seem like they'd pose any real problem -- much like many robots. With a zero turning radius, however, things get a little stickier. For that, one side is going in reverse -- using the Chiaphua motor -- while the other goes forward using whichever motor is most appropriate for the speed at which it's turning. It may be that there's an easy solution, a programming solution, or that a zero turning radius is impossible to achieve. Again, I'm just not sure. Frank wrote: Quote:
I agree that there are better solutions if you want to couple two motors together and run them all the time. You'll get more power at a given speed that way. Most of those solutions rely on averages -- as does the differential. This solution does not. This design is explicitly for maintaining separation of your motors and taking advantage of the unique characteristics of each. The additional performance range possible via this solution means that your robot could simultaneously have the ability to output more torque and more speed than any other robot -- especially middle-of-the-road, average robots using a two motor drivetrain. Again, thank you everyone for taking the time to read through that very long post and ask questions. You're raising issues that I haven't thought of yet or don't have satisfactory answers to and I really appreciate that. I understand that the design in its first iteration isn't close to perfect and so I'm seeking your feedback so I (and others) can make improvements before testing and using it -- if it's worth using at all. |
| Thread Tools | |
| Display Modes | Rate This Thread |
|
|