Go to Post [Programming a swerve drive] It's really really simple, unless you actually do it. - Ether [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
  #11   Spotlight this post!  
Unread 18-02-2012, 01:43
frasnow's Avatar
frasnow frasnow is offline
Software
no team
Team Role: Mentor
 
Join Date: Jun 2010
Rookie Year: 2010
Location: Oregon
Posts: 83
frasnow is a splendid one to beholdfrasnow is a splendid one to beholdfrasnow is a splendid one to beholdfrasnow is a splendid one to beholdfrasnow is a splendid one to beholdfrasnow is a splendid one to beholdfrasnow is a splendid one to behold
Re: [DFTF] The Classic Blunder...

I have a question for all the people talking about the 30 pounds and how great it is. How can a robot truly be competitive if the electrical team doesn’t have time to test their wiring, the software team doesn’t have time to test autonomous routines, and the drivers don’t have time to practice? I’ve seen this type of thing occur many times at work, and it always delays projects. Mechanical engineers sometimes think the deadline for the project is their deadline and don’t leave any time for integration and debug.

Say you have a hypothetical team with very few resources, so they can only go to one regional and they can’t afford to build two robots. Let’s say the mechanical part of the team decides the shooter doesn’t need to be completed prior to bag-and-tag. They build a prototype shooter, but they never put it on a robot. The plan is to work on the shooter for a few weeks and attach it at the regional. It won’t go onto a robot until practice day, and the team will miss much of the practice session working on the build.

System integration is the hardest part of engineering. In the real world the game balls have different densities, so your precisely controlled mechanical system is not so precise. In the real world things rarely work the first time and you have to study the problem to decide if it is mechanical, electrical, or software. This is why teams should be doing system integration throughout the season. Don’t wait until the end to test the system or you may quickly run out of time.

I don’t believe a team with low resources can decide to just finish 30 pounds of the robot after bag-and-tag and truly be successful (OK, a low percentage will). These types of teams need to finish early giving the electrical team time to work out wiring issues, the software team time to test code and write autonomous modes, and the entire team time to make an objective decision about the drivers. You can build the most perfect mechanical system in the world, but without electronics, software, and drivers it will just sit there. Yes, we couldn't do it without the mechanical team either.

Remember there are 3 robots on every alliance. Many alliances will likely pick one defender/feeder robot, and many will look for a good balancer. You don’t have to have a way to score balls. Make a basic feeder before bag-and-tag. Give your drivers plenty of time to practice. If you show yourself to be a great defender that doesn’t get penalties at the regional, you will likely get picked.
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 23:09.

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