![]() |
Issues with Drivebase
After competing at the Australia regional, my team realised how difficult it is to get over the scoring platforms with the kit drivebase in the long configuration. As a result, we have now replaced our six 4" wheels with four 6" wheels on the ends. However, our robot now struggles to turn on the spot. At this point, we're pretty sure that the fault isn't in the code or electronics, but we've seen plenty of other teams use this setup with no problems. Has anyone else had the same issue? How did you solve it?
|
Re: Issues with Drivebase
Your wheels are creating too much friction when you try to turn. Replacing two or four wheels with omni wheels will help greatly.
|
Re: Issues with Drivebase
Quote:
|
Re: Issues with Drivebase
If you only replace one pair, replace the one with less weight (away from the center of gravity). For most robots this year with a convex rectangular base, this would be the rear wheels. We used this configuration for Ultimate Ascent, and we had the two solid wheels in the front and two (idle) omni wheels in the rear. Our CoG was quite near the center of volume. We did have a bit of fishtailing at high speed going forward, but at low to moderate speed, we were fine; I don't imagine you'll be doing much sprinting in Recycle Rush. Interestingly, we had less fishtailing in reverse. This was presumably because more of the weight was over our solid driven wheels.
A better solution is to use six solid 6" wheels as the chassis was designed to use. The center wheels are dropped by 1/8", so the wheelbase is only one half or the other for purposes of "tank mode" turns, but full length for purposes of not falling over forwards or backwards. |
Re: Issues with Drivebase
Quote:
|
Re: Issues with Drivebase
Opening with some quotes from another thread...
Quote:
Quote:
Quote:
Quote:
Quote:
|
Re: Issues with Drivebase
Quote:
|
Re: Issues with Drivebase
Quote:
|
Re: Issues with Drivebase
Quote:
|
Re: Issues with Drivebase
If I might make a suggestion:
You're a little worried about fishtailing, so why not NOT put omnis on only one end, or traction wheels only on one end? Why not put one omni on one end, and one omni on the opposite corner, and do the same with the traction wheels? See: FRC494 in 2006. This gives less fishtailing than two omnis on one end, similar stability to a 4WD with all traction wheels, and easier turning than said 4WD all-traction. |
Re: Issues with Drivebase
We might all be overthinking this? Our team used the kit chassis, long configuration, with 6" wheels that are just like the 4" kit wheels. We notched the ends of the chassis for wheel clearance, so we could use the normal length belts. We competed in two regionals, and were semifinalists in one, and finalists in the other. No issues with driving. The rocking is a feature, not a problem, it allows the robot to turn easily on carpet. The 6" wheels let us go over the scoring platforms ok.
|
Re: Issues with Drivebase
Quote:
|
Re: Issues with Drivebase
Quote:
|
Re: Issues with Drivebase
Quote:
And oh, yes - what was the aspect ratio (track to wheelbase ratio) of that robot? Where was the CoG? Well, now I've got a nice problem to work on in the evenings as I travel this week, If I actually have any spare time. |
Re: Issues with Drivebase
The design of the rest of the robot may make it so that some specific type of drivetrain is more better than another. Having a robot that cannot carry a stack of totes without dropping them seems to be a common problem this year...I don't know if modifying the drivetrain is enough to overcome this? Driver practice is helpful, and making changes to the control system can help, too. It could be that using omni wheels is a good way to deal with it. We did have some problems with dropping totes, but I really can't blame the drivetrain, since we didn't design our robot to restrain the totes. For our RC operations, the 6wd kit chassis worked just fine. We were able to move and place stacks of two totes successfully many times, with the top tote just resting on the bottom one.
|
| All times are GMT -5. The time now is 16:31. |
Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi