Team 237 would like to know how to join the Chiaphua and drill motors into one for the drive system. Can anyone help us on this feat and tell us in exact detail how you can do this? Pictures, diagrams, anything that can help us out post it here or email it to me at [email protected] . Thanks alot! :ahh:
p.s. even joining any other 2 motors post it here also thanks 
Are you saying use a chiaphua and a drill for each of the 4 wheels? or like 2 sets of that in the back and FPâs in the front?
If you can describe exactly what you are trying to do I will look through all my downloaded stuff and archives to see if I can find something like it.
-Greg The Great
ok cool umm we are trying to use tank steering with a drill and chiaphua motor on each side of the robot. meaning 1 chiaphua and drill motor on one side and aanother set on the other side.
Oh boy⌠do I have something for you.
As part of the FIRST college course that I taught this semester, I have some rather comprehensize data on combining both the chips and drills⌠from a number crunching standpoint, itâs very complete.
There arenât any sprocket sizes, CAD drawings, or the like⌠but theory wise⌠this is (fundamentally) very strong material. I will be publishing a white paper along these lines soon on www.boilerinvasion.org.
Hereâs the PowerPoint. If you have questions, please ask. If someone has corrections, comments, or concerns, please ask.
http://web.ics.purdue.edu/~mjadams/motorsinfirst.ppt
Matt
I avnât read the whitepaper listed above, it might say what iâm about to say but anyway⌠Donât match the moters at free speed. I have seen many teams do this. This is the quickest way i know to mismatch them. Match them under some typical load. Further matching can be accomplished through software.
thanks for the info guys keep replying to this post! we need everyones input 
Search⌠there are 1000000000000000000 threads on this topic (well, not that many, but there are certainly more than I care to count) download a white paper such as the Technokatâs transmission, or Team 116âs, or Team 716âs They all offer complete prints and hints/tips etc.
From the best of my understanding, nothing is wrong with matching at free speeds. If you donât, at higher RPMs you will have back EMF occur, reducing efficiency if you have one motor trying to go faster than the otherâs free speed.
Take a look at the following figure for a Drill in low gear and Atwood coupled together at the drillâs free speed:
http://web.ics.purdue.edu/~mjadams/couplefreespeed.gif
Letâs say that you have 200 in-lbs of torque applied to the shaft. In this case, the motors coupled at free speed will spin at about 225 RPM. The atwood motor will be contributing more torque to the system than the drill. I do not see a problem with this. I admit that thereâs uneven load sharing between the motors⌠but there is nothing fundamentally wrong with this from a mechanics standpoint.
I think that some people believe that if motors arenât sharing equal load, then thereâs a âproblemâ or the motors are âfightingâ each other. This is not the case, and isnât âbad.â You donât have an even current draw from each motor⌠but your motors arenât being ruined, and your efficiency is constant. Theyâre pretty happy. One is working harder, but they donât get jealous of each other! The only time problems arise is if thereâs a situation with little torque, and theyâre coupled at a non-free speed. One motor (higher free speed) says, âWoo hoo! letâs go really really fast!â and the other says, âBut my max speed is slower than yours. Iâll try to do what I can to keep up, but we wonât be able to go as fast as you combined!â
Now with the above illustration⌠donât think of motors as people rowing a boat, where if one is rowing harder the boat will turn. Think of the motors as a bicycle with two riders. If one works harder, thatâs fine. But if someoneâs legs just canât physically move fast enough, itâs bad news!
Now, you could optimize your motors such that theyâre intersecting at a low torque that your robot could never achieve due to friction, slightly below the free speed. This could help have the amount of torque (and current) distributed between the motors be more even. But having the load sharing imperfect is not a âbadâ thing if youâre careful about analyzing the situation to make sure the load isnât so uneven that a breaker on one motor will trip before the other can effectively contribute.
Letâs take a look at this:
http://web.ics.purdue.edu/~mjadams/coupleotherspeed.gif
NOTICE: As you can see, the free speed of a combined motors in low torque conditions (to the left of their intersection point) I made to be the geometric mean of the two speeds. This is not completely correct, (neither is the fact that these show all linear relationships between torque and RPM, this is simplified). There are coefficients that determines the ratio between the two motors free speed which sets what the RPM the motors will have at low torque values. However, the RPM in low torque conditions is NOT the fastest motorâs speed, nor is it the slowest. The reason for this is unique to DC motors, and refers to the back-EMF, which occurs when a DC motor is spinning faster above itâs free speed. You run this risk of this occuring if you do not match them at free speed.
However, will you ever have motors truly reach free speed in a robot? Nope. So can you adjust the ratios by a little so that theyâre share the toque more evenly? Of course. Even matching free speeds is impossible since the free speed varies from motor to motor of the same type.
However, keep in mind that if you have low torque conditions that yield RPMs above the slower motorâs free speed, you loose efficiency.
And this is going to bring up one heck of a hail storm⌠I know it.
Please, letâs keep this at a technical level, and be as specific if you can. Disagree with facts. Graphs help out. Hack away at mine if you wish. Just keep it legit and not hunches. Weâll settle this.
Input welcome, could a EE out there explain back EMF for me a little better?
Matt
In fact, sometimes you will want to do something similar to this. For 2002 my team designed the gearbox so the bosch would be moving the robot almost to the point where the atwood was not adding any power under normal movement to keep current draw down. Then when we had goals or if we were pushing another robot weâd slow down about .5ft/s but then the torque would increase greatly while not drawing too much extra current. I wouldnât suggest doing something with that big of a difference in normal load rpmâs of the shafts but if you wanted to keep current draw down on normal conditions you could do something similar. Also, I would suggest combining the two motors together as soon as possible in the gearbox to use less gears and keep weight down.
bosch 307 Watts @37.4A
CIM 300 Watts @40 (estamate)
300+300=600
600W=one gearbox
600+600=1200
1200W 2gearboxes
1 HorsePower=746 Watts
1200/746.7=1.6
1.6 Horsepower
Rob-
How did you âslow downâ? Via the joystick or by some sort of a shifting device? Iâd have to do some thinking about it, but initially Iâd say that that just âslowing downâ via a joystick wouldnât let one motor kick in more torque than the other since the amount of torque needed would be constant at any moving speed, and presumably, the joystick would control both motorâs input voltage.
Matt
Sorry if i repeat what someone else is sayingâŚim short of time and didnt read the entire postâŚbut you can simply use the drill motor alone(no clutch) and gear the two into a 1:1 ratio. From this point you can decide upon the rest of your gearing, etc.
If my memory is correct:
Drill no clutch:about 19000
Chip:about 5000
so its close to a 4 to 1 ratio
this means that the gear on the chip needs to be 4x bigger that the drill for a 1:1 ratio.
Hope this was helpful
-Pat
Bosch normal load speed is 19670 and the Atwood normal load speed is 4967
There was no option to slow down, the robot slowed itself down when the additional load of the goals was added to the robot. The drills couldnât fully handle the extra 362 pounds and so the motor slowed down and then the Atwood picked up for it, drawing less current than running the Atwood at a slower rpm. We also had a âsoftware shifterâ which took the joystick feedback and divided it by 1.5 so the operator could switch the speed down when latching onto goals.
This is incorrect.
Atwood at normal load (from 2003 spec sheet) is 4378 RPM.
Free speed is 5,500.
Free speed on Bosch is 19,670 RPM as Sarah stated for normal load speed.
Just wanted to make sure that the right data is out there.
Check it out here:
http://www.usfirst.org/robotics/2003/specsheets.htm
Matt
Matt and Rob are both on the same page with this one.
Basically it is possible to design a gearbox to emphasize different motors depending on the torque-load on the gearbox (which determines motor performance⌠speed, efficiency, current draw, etc).
This means: your gearbox is designed with 2 motors. When the robot is moving across the field unimpeded, the torque load on the motors is such that one motor is carrying most of the load, and the other is somewhat dragging within the gearbox. When the robot is under a high-load condition (like towing goals, or pushing against another robot), there is more torque loading on the motors, and now the other motorâs output is greater.
I donât like this method.
What we use on 229, (and many other teams have used, with great success) is simply matching the free speeds of the motors. This means, that if the robot is opperating under a no-load condition, both motors will be spinning the same speed. Will this ever happen: No! But⌠it works out pretty well. Essentially you get a nice balance of torque output from each motor at all different load conditions. Itâs not perfect, but it works well.
We also couple this with a 2-speed shifter. This allows the designer to provide 2 different torque output conditions, depending on torque loading. (Need to tow a goal? Just downshift!)
shrug This is all a matter of preference. There has actually been quite a bit of debate on this subject within the past year (Tytusâ differential combiner concept). I think for now weâll stick with matching free-speed, simply because itâs easy, and it works well enough for our applications.
Good luck,
John
PS - As always, for more information about the theory and physics involved in this stuff, look for other posts on this forum (There are plenty!), contact your friendly neighborhood FIRST mentor/enginerd. (Or drop me an IM.)
Advice to the rookies:
Donât sweat the numbers TOO much⌠(you still need to calculate!)
These values vary so much from motor to motor, and the specs arenât 100% accurate anywaysâŚ
Using a free speed of ~5,500 for the Chip, and ~20,000 for the Bosch is fine. Any more detail than that and youâre wasting your time. (Motor performance will change over time as well).
Donât believe me? Perform some tests⌠youâll be surprised by what you find.
If you get a 90% speed match between combined motors, youâre probably doing okay.
John is right on.
I just wanted to make sure that the right information is out there. You gotta be close, but it helps to start with the most accurate numbers available.
Matt
In regards to the speeds on the new Bosch motor, the spec sheet on the FIRST site gives the numbers at 11v, not 12v or 13.2v when the battery is fully charged. So the 19670 works as a normal load speed at 12v. As for the Atwood speed that was my bad, I posted under her name and I didnât have my papers handy, thanks for catching it.
thanx alot guys! all this info i feel so luved as for the fighting and arguing calm down lol anyway keep up the info this is really helping alot! :yikes: