Go to Post A good robot with great strategy beats a great robot with good strategy. - Brian Maher [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Media   CD-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #46   Spotlight this post!  
Unread 28-06-2011, 17:28
thefro526's Avatar
thefro526 thefro526 is offline
Mentor for Hire.
AKA: Dustin Benedict
no team (EWCP, MAR, FRC 708)
Team Role: Mentor
 
Join Date: Aug 2006
Rookie Year: 2005
Location: New Jersey
Posts: 2,599
thefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond repute
Send a message via AIM to thefro526 Send a message via MSN to thefro526
Re: Driver Selection: A Discussion

Quote:
Originally Posted by Chris is me View Post
Seriously, do you guys really tell drivers to "go easy on the robot"? That's just prolonging a failure that WILL happen.
This reminds me of something that was told to me when I first learned how to drive a robot.

'A robot can always be fixed - but a match can never be replayed'.

Ever since then I've designed, built, driven and coached with that in mind.
__________________
-Dustin Benedict
2005-2012 - Student & Mentor FRC 816
2012-2014 - Technical Mentor, 2014 Drive Coach FRC 341
Current - Mentor FRC 2729, FRC 708
Reply With Quote
  #47   Spotlight this post!  
Unread 28-06-2011, 17:50
Duke461's Avatar
Duke461 Duke461 is offline
Boiler Strong.
AKA: Ben Carson
FRC #0461 (Westside Boiler Invasion)
Team Role: Alumni
 
Join Date: Dec 2010
Rookie Year: 2010
Location: West Lafayette, Indiana
Posts: 864
Duke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond repute
Re: Driver Selection: A Discussion

Quote:
Originally Posted by Chris is me View Post
I don't mean that literally any action a driver can do should be unable to break the robot, though that's obviously ideal. But a robot isn't something that should require constant thought to its safety to drive.

It's funny that you mention Breakaway, because that seems like the best example. Barring deploying the hanger and intentionally tipping, how exactly could you break a good robot that year? If your robot could be damaged by anything other than an unusual circumstance like getting chain caught in your wheels, it simply was not robust.

Seriously, do you guys really tell drivers to "go easy on the robot"? That's just prolonging a failure that WILL happen.
I see your point, and i agree you shouldnt go easy on the robot, but there were times where robots were hit, or were going too fast over the hump and flipped over. I'm definitely not saying you should be really cautious; im just saying that all of these robots could have catastrophic breakdowns.
But even a year like this, aggressiveness could be bad. Lets say you're farther away from a tube than the opponent, and you're both driving full speed. The only way you have a chance of getting that tube is by putting your arm to the ground way before you get there. Now theres a good chance you'll smack the arm/wrist, and high speed side loads can harm basically any arm/wrist/lift.
Quote:
Originally Posted by thefro526 View Post
This reminds me of something that was told to me when I first learned how to drive a robot.

'A robot can always be fixed - but a match can never be replayed'.

Ever since then I've designed, built, driven and coached with that in mind.
Thats not always the best way to look at it. In my example above, i'd rather decrease my chances of winning that match by a little bit as opposed to having to play defense or sit out 2-5 matches because your arm was smashed.
__________________

The opposite of excellence is good enough.
2012-2013 President; 2011-2012 Vice President
2011-offseason FRC Student Drive Coach; 2010-11, 2011-2012 VEX Drive Coach
2011, 2010-offseason FRC Driver/Operator
2012, 2011-offseason, 2010-offseason FRC Human Player
Find me on: Facebook, Gmail, Twitter, Tumblr, Blogger/Blogspot
Reply With Quote
  #48   Spotlight this post!  
Unread 28-06-2011, 18:00
thefro526's Avatar
thefro526 thefro526 is offline
Mentor for Hire.
AKA: Dustin Benedict
no team (EWCP, MAR, FRC 708)
Team Role: Mentor
 
Join Date: Aug 2006
Rookie Year: 2005
Location: New Jersey
Posts: 2,599
thefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond reputethefro526 has a reputation beyond repute
Send a message via AIM to thefro526 Send a message via MSN to thefro526
Re: Driver Selection: A Discussion

Quote:
Originally Posted by Duke461 View Post
.
Thats not always the best way to look at it. In my example above, i'd rather decrease my chances of winning that match by a little bit as opposed to having to play defense or sit out 2-5 matches because your arm was smashed.
If something on your machine can be broken during normal game play and it takes 2-5 matches to fix, then it's a design flaw - or at least that's how I see it.
__________________
-Dustin Benedict
2005-2012 - Student & Mentor FRC 816
2012-2014 - Technical Mentor, 2014 Drive Coach FRC 341
Current - Mentor FRC 2729, FRC 708
Reply With Quote
  #49   Spotlight this post!  
Unread 28-06-2011, 18:18
Chris is me's Avatar
Chris is me Chris is me is offline
no bag, vex only, final destination
AKA: Pinecone
FRC #0228 (GUS Robotics); FRC #2170 (Titanium Tomahawks)
Team Role: Mentor
 
Join Date: Dec 2008
Rookie Year: 2006
Location: Glastonbury, CT
Posts: 7,766
Chris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond reputeChris is me has a reputation beyond repute
Send a message via AIM to Chris is me
Re: Driver Selection: A Discussion

Quote:
Originally Posted by Duke461 View Post
I see your point, and i agree you shouldnt go easy on the robot, but there were times where robots were hit, or were going too fast over the hump and flipped over.
If a robot's hit and something broke, especially bumper to bumper contact, bad design.

If your robot can't go over the hump past a certain speed without flipping, design issues aside, you should probably have some kind of software limit rather than something as subjective as "don't go too fast man"

Quote:
But even a year like this, aggressiveness could be bad. Lets say you're farther away from a tube than the opponent, and you're both driving full speed. The only way you have a chance of getting that tube is by putting your arm to the ground way before you get there. Now theres a good chance you'll smack the arm/wrist, and high speed side loads can harm basically any arm/wrist/lift.
We designed for that exact situation, and it showed. Our robot's arm was snagged on another at Battlecry. They drove forward and yanked us around by our arm, with absolutely no damage. Obviously that's a worst case scenario, and arms should definitely NOT be used that way, but robust design should be something that is always emphasized.

Quote:
Thats not always the best way to look at it. In my example above, i'd rather decrease my chances of winning that match by a little bit as opposed to having to play defense or sit out 2-5 matches because your arm was smashed.
You really need to be able to make nearly any repair in one match cycle.

Losing just one match can kill your chances at the Top 8. Do you really want your driver to wasting precious brain cells doubting himself and his robot? No, you have split second decisions to make, there's no time to think.
__________________
Mentor / Drive Coach: 228 (2016-?)
--2016 Waterbury SFs (with 3314, 3719), RIDE #2 Seed / Winners (with 1058, 6153), Carver QFs (with 503, 359, 4607)
Mentor / Consultant Person: 2170 (2017-?)
.
College Mentor: 2791 (2010-2015)
-- 2015 TVR Motorola Quality, FLR GM Industrial Design -- 2014 FLR Motorola Quality / SFs (with 341, 4930)
-- 2013 BAE Motorola Quality, WPI Regional #1 Seed / Delphi Excellence in Engineering / Finalists (with 20, 3182)
-- 2012 BAE Imagery / Finalists (with 1519, 885), CT Xerox Creativity / SFs (with 2168, 118)
Student: 1714 (2009) - 2009 MN 10K Lakes Regional Winners (with 2826, 2470)
2791 Build Season Photo Gallery - Look here for mechanism photos My Robotics Blog (Updated April 11 2014)
Reply With Quote
  #50   Spotlight this post!  
Unread 28-06-2011, 19:48
Duke461's Avatar
Duke461 Duke461 is offline
Boiler Strong.
AKA: Ben Carson
FRC #0461 (Westside Boiler Invasion)
Team Role: Alumni
 
Join Date: Dec 2010
Rookie Year: 2010
Location: West Lafayette, Indiana
Posts: 864
Duke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond reputeDuke461 has a reputation beyond repute
Re: Driver Selection: A Discussion

Quote:
Originally Posted by Chris is me View Post
If a robot's hit and something broke, especially bumper to bumper contact, bad design.

If your robot can't go over the hump past a certain speed without flipping, design issues aside, you should probably have some kind of software limit rather than something as subjective as "don't go too fast man"



We designed for that exact situation, and it showed. Our robot's arm was snagged on another at Battlecry. They drove forward and yanked us around by our arm, with absolutely no damage. Obviously that's a worst case scenario, and arms should definitely NOT be used that way, but robust design should be something that is always emphasized.



You really need to be able to make nearly any repair in one match cycle.

Losing just one match can kill your chances at the Top 8. Do you really want your driver to wasting precious brain cells doubting himself and his robot? No, you have split second decisions to make, there's no time to think.
While i understand your points, this is a general discussion for driver choice. and in an ideal situation, the average robot WILL have design flaws that will make the driver need to be smarter about how he/she drives it.
__________________

The opposite of excellence is good enough.
2012-2013 President; 2011-2012 Vice President
2011-offseason FRC Student Drive Coach; 2010-11, 2011-2012 VEX Drive Coach
2011, 2010-offseason FRC Driver/Operator
2012, 2011-offseason, 2010-offseason FRC Human Player
Find me on: Facebook, Gmail, Twitter, Tumblr, Blogger/Blogspot
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 20:43.

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