Go to Post I think FIRST is probably close to the farthest you can get from 'gangsta', outscored only by the math team. - Tom Bottiglieri [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

 
 
 
Thread Tools Rating: Thread Rating: 4 votes, 5.00 average. Display Modes
Prev Previous Post   Next Post Next
  #15   Spotlight this post!  
Unread 14-01-2014, 08:38
Bongle's Avatar
Bongle Bongle is offline
Registered User
FRC #2702 (REBotics)
Team Role: Mentor
 
Join Date: Feb 2004
Rookie Year: 2002
Location: Waterloo
Posts: 1,069
Bongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond reputeBongle has a reputation beyond repute
Send a message via MSN to Bongle
Re: Aerial Assist--Perspective from a low-resource team

This should keep your mechanical team happy:
1) Drive it like you stole it until it breaks*
2) Do a failure analysis, redesign/remanufacture the broken component, or put into place a procedure that will detect the failure pre-match.
3) Goto 1.

You're probably correct that many other teams are at the same spot you are, and will now be iterating their designs to make them faster, more reliable, and more effective. Simply having a robot that can do the game task won't be enough. You've got a fantastic chance to build a 6th or 7th version of your bot by ship day. That should keep your mechanical guys busy.


*"Breaks" and the associated fixes can mean many things:
1) Did the driver screw up? Maybe your control software is too confusing and needs adjustment.
2) Did the robot munch its own part? Maybe you need sensors to prevent that from happening, or you should design the part to be less likely to wreck itself
3) Did a part simply break? Time for a redesign or beefing-up of that part.
4) And of course, you can simply redefine success. Can your robot pick the ball up 10 times in a minute? Change your requirement to 15, and see what needs to be done (driver training? pickup redesign? different ball-approach tactics?) to get your effectiveness up to that level.
5) Did a normal wear component break? How easy was it to replace? Could you design the robot to have greater access to that part?
6) Was something forgotten before a test session and delayed the start of the driving? Make some checklists or maybe even have the robot software self-check that everything is present and working.
7) Are there areas of the field that your robot won't be able to pick up the ball, like corners or in the open field? You could change the pickup to make it more effective in those areas. Also, see [4].
8) Can your catcher catch a ball thrown blindly (a human could throw it backwards over their head) 100% of the time?

Last edited by Bongle : 14-01-2014 at 08:44.
Reply With Quote
 


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 15:47.

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