Go to Post Not that I'm doubting you, but where is it bugged? The exterminators are in the house. - Greg McKaskle [more]
Home
Go Back   Chief Delphi > ChiefDelphi.com Website > Extra Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #16   Spotlight this post!  
Unread 01-12-2014, 19:11
Dunngeon Dunngeon is offline
Pumped
AKA: Ryan
FRC #0973 (Greybots)
Team Role: College Student
 
Join Date: Mar 2014
Rookie Year: 2012
Location: Cal Poly San Luis Obispo
Posts: 299
Dunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond reputeDunngeon has a reputation beyond repute
Re: pic: 8WD CONCEPT DRIVETRAIN

Quote:
Originally Posted by Kevin Ainsworth View Post
Two topics:
1) Encoder Vex Chain
I don't really like this myself but we haven't had time to change it. It should work but could be a pain. Any slop would result in inaccurate positioning for low speed maneuvers. I personally would like to see gears, thanks for the input.

2) 8WD Chassis Wheel Lift
We ran the same configuration in 2013 and the thing was a beast. Where your center of gravity is positioned does matter. You would ideally want it to be located central to the six wheels touching the ground, so between the gearboxes. If you made the front and back wheels both raised your robot would be tipping forward and backwards every time you accelerated or decelerated. It would also make your robot unstable during dynamic moves. It would make your contact patch width to length ratio way to high and your robot would be extremely unstable and twitchy at speed. Your width would be about 28" and length would be around 9" so your ratio would be 3:1. Way too high. We modified our 2013 practice robot to test the ideal ratio by making the side rails slide in and out on extrusion and I can tell you the current ratio is about ideal for high speed stability and low speed maneuverability. There was no perfect ratio but too long and it took too much motor energy to overcome the scrubbing wheels, too wide and it became too twitchy. I would like to know what Team 67 had on their wide 2012 robot. From their tech notes it looks like none of the wheels were raised but that's from looking at the pixelated AutoCad drawing. I can tell you from actual testing that with six wheels touching we can go full speed, throw one stick the opposite direction and pinwheel to go the opposite direction, at full speed. I see no issues with maneuverability, low speed scrub is minimal and it doesn't take much power at all to pinwheel with no forward motion. The wheel contact patch is still wider than it is long so you get the best of both worlds.
That's what I was thinking, so the raised set is just there to prevent the robot tipping.
__________________
(2015-?): 973
(2012-2015): 955
Reply With Quote
  #17   Spotlight this post!  
Unread 02-12-2014, 18:16
Adrian Clark Adrian Clark is offline
Registered User
FRC #1678 (Citrus Circuits)
Team Role: Mentor
 
Join Date: Apr 2012
Rookie Year: 2009
Location: United States
Posts: 79
Adrian Clark is a jewel in the roughAdrian Clark is a jewel in the roughAdrian Clark is a jewel in the roughAdrian Clark is a jewel in the rough
Re: pic: 8WD CONCEPT DRIVETRAIN

I like the idea of using larger bearings and shafts to minimize losses, but I'm curious how much of a difference it would actually make.

I could be wrong, but it looks like the rational behind this design is higher efficiency by eliminating any losses from the standard hex shaft approach.

On a standard WCD, there is no space between the wheel and the bearing. So the bending of the shaft is almost nonexistent. Because of this I think your bearing setup will make very negligible difference.

Last season during a meeting in which we discussed what we wanted to accomplish with our off season drive train design, a very respected mentor offered a great piece of advice. That advice was to go after low hanging fruit. This means to go after the small problems that can be easily solved, and as many as you can. I say this because I think you're tackling a very small and possibly nonexistent problem with a solution that demands a lot of resources. I think those resources could be better spent, a lot could be accomplished in the time it takes to design and fabricate your bearing configuration. My suggestion is to identify that low hanging fruit, and to allocate your resources accordingly. In my eyes it's better to tackle several small problems that fix one with a complex solution.

This is just my 2 cents. All that being said, kudos to all involved in this design. You guys identified a problem and came up with a very elegant solution.

Best of luck rumbling in 2015's ultimate assist

-Adrian
Reply With Quote
Reply


Thread Tools
Display Modes Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Forum Jump


All times are GMT -5. The time now is 11:53.

The Chief Delphi Forums are sponsored by Innovation First International, Inc.


Powered by vBulletin® Version 3.6.4
Copyright ©2000 - 2017, Jelsoft Enterprises Ltd.
Copyright © Chief Delphi