Go to Post Yes ONE blue banner would be nice one of these days, but I've never lost focus of why we as mentors do what we do. It's about preparing the students for "defense" in life, and laugh when your robot gets scored into a goal. - Chris_Elston [more]
Home
Go Back   Chief Delphi > Technical > Technical Discussion
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Closed Thread
 
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 30-05-2015, 12:37
msigalov msigalov is offline
Registered User
FRC #4096
 
Join Date: Jan 2015
Location: Champaign, IL
Posts: 7
msigalov is an unknown quantity at this point
Re: Team 4096 Grasshopper Drive design

Quote:
Originally Posted by GeeTwo View Post
It depends on how high you lift the omnis, or more likely push the traction wheels down. If the omnis aren't above the line between the bottom of the traction wheel and the bottom of the rear frame or bumper, then yes, you can be pushed onto the omni. Many (most?) butterfly/grasshopper designs do not articulate this far. With the traction wheels on the corners, you have a longer wheelbase, making it harder for another robot to lift your traction wheels through pushing. You also reduce turning ability while in tank mode, which is probably why most butterfly and grasshopper designs I've seen have the traction wheels near the center and the holonomic wheels on the corners.
The problem I see with having the omnis in the middle is that it requires having a piston on the center wheel to keep it level with the omnis. As it is the current Square-I pistton is $80 and all the load is going onto the thread.

Another idea is to push the tank wheels just far down enough so that the drivetrain has all 9 wheels touching the ground instead of resting on just the 4 tanks. The omnis wouldn't reduce maneuverability compared to 4 tank and it would have the longer wheelbase and stability of having the tanks on the outside.

Personally, I'm more worried about the way I mounted the gearboxes. I'm afraid that the weight will bend inside plate of the drivetrain. That's why there's a plate attached to the 8020 that supports the CIM. Same worry goes for the strafe gearbox and CIM. Another worry is that the 8020 crossbars aren't enough support for the chassis.

This entire project was worked on by 3 students, no mentors have helped yet. We want it as a relatively low budget drivetrain for the off season to prepare for a strong start next build season.
  #2   Spotlight this post!  
Unread 30-05-2015, 13:19
Abhishek R Abhishek R is offline
Registered User
FRC #0624
Team Role: Alumni
 
Join Date: Mar 2013
Rookie Year: 2012
Location: Texas
Posts: 892
Abhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond repute
Re: Team 4096 Grasshopper Drive design

I recommend you check out this document. 624 actually tried to make a simpler version of nonadrive/butterfly a few years back, and we dubbed the result the "Grasshopper" drive.

http://www.chiefdelphi.com/media/papers/2968?

The experiment was pretty successful, achieving all the strengths of the standard nonadrive setup while being relatively simple and light.

On the idea of the static strafe wheel - we ran that setup in the original iteration. It worked generally fine most of the season, but every now and then we would find a rough spot in the field where we couldn't strafe. In the offseason, when we made it actuate up and down pneumatically, we realized the static version had actually been causing a lot of friction in the drive. As soon as it was lifted up off the ground, we saw significant speed/acceleration improvements and increased battery life. Someone at one of our offseason events even asked if we added another CIM to our drive!
__________________
2012 - 2015 : 624 CRyptonite
Team Website
  #3   Spotlight this post!  
Unread 30-05-2015, 14:31
msigalov msigalov is offline
Registered User
FRC #4096
 
Join Date: Jan 2015
Location: Champaign, IL
Posts: 7
msigalov is an unknown quantity at this point
Re: Team 4096 Grasshopper Drive design

Quote:
Originally Posted by Abhishek R View Post
I recommend you check out this document. 624 actually tried to make a simpler version of nonadrive/butterfly a few years back, and we dubbed the result the "Grasshopper" drive.

http://www.chiefdelphi.com/media/papers/2968?

The experiment was pretty successful, achieving all the strengths of the standard nonadrive setup while being relatively simple and light.

On the idea of the static strafe wheel - we ran that setup in the original iteration. It worked generally fine most of the season, but every now and then we would find a rough spot in the field where we couldn't strafe. In the offseason, when we made it actuate up and down pneumatically, we realized the static version had actually been causing a lot of friction in the drive. As soon as it was lifted up off the ground, we saw significant speed/acceleration improvements and increased battery life. Someone at one of our offseason events even asked if we added another CIM to our drive!
Your drivetrain was the inspiration for our design, hence the most likely incorrect grasshopper name. We wanted to avoid tensioning, but we will try to figure out how to vertically actuate the strafe wheel. Would it need to be actuated when we are strafing, or whenever it is in h drive?
  #4   Spotlight this post!  
Unread 30-05-2015, 19:04
Abhishek R Abhishek R is offline
Registered User
FRC #0624
Team Role: Alumni
 
Join Date: Mar 2013
Rookie Year: 2012
Location: Texas
Posts: 892
Abhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond reputeAbhishek R has a reputation beyond repute
Re: Team 4096 Grasshopper Drive design

Quote:
Originally Posted by msigalov View Post
Your drivetrain was the inspiration for our design, hence the most likely incorrect grasshopper name. We wanted to avoid tensioning, but we will try to figure out how to vertically actuate the strafe wheel. Would it need to be actuated when we are strafing, or whenever it is in h drive?
We only actuated it when we were strafing. I'll try and post a pic if I can. There's a bit of lag between the time the driver hits the button and the robot actually starts strafing. If you can, the 148 method of actuation via the torque of the gearbox itself is probably better. I saw 987 used that system this year too, maybe someone from one of their teams may chime in on how it worked in more detail. (They may have posted elsewhere on CD about it too.) Either way, it doesn't need to be actuated when you're in H drive all the time, only when you're strafing.
__________________
2012 - 2015 : 624 CRyptonite
Team Website
Closed Thread


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 03:17.

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