OCCRA
Go to Post Just to be clear, NOTHING anyone says here is a confirmation. The ONLY source for official answers to questions like this is the FIRST Q&A system. - dlavery [more]
Home
Go Back   Chief Delphi > FIRST > General Forum
CD-Events   CD-Media   CD-Spy   FRC-Spy  
portal register members calendar search Today's Posts Mark Forums Read FAQ rules

 
Reply
Thread Tools Rate Thread Display Modes
  #1   Spotlight this post!  
Unread 05-06-2012, 06:33 PM
thenomnivore's Avatar
thenomnivore thenomnivore is offline
Registered User
AKA: Ramirez
FRC #1212 (The Sentinels)
Team Role: Engineer
 
Join Date: Mar 2011
Rookie Year: 2010
Location: Arizona
Posts: 23
thenomnivore is an unknown quantity at this point
Plans for the future

For next year's robotics season, the team decided to change almost everything entirely about the team. Our showmanship, that way we dress, etc. One of the most important and most talked about issues we face is the design process. For the last couple years, what we have done this process was we would have 2 teams making 2 robots, choose which one is the best, go from their but by the end of the season, it seems like a waste of time because of the amount of time we spent of each robot and not one. I'm asking any team for advice or how their team does their design process and how well does it work. Also, we are trying to get our mentors to have less say in the final robot because usually, the most important task almost 100% becomes a project of the mentors.
Any input and ideas are helpful. Thanks
__________________
A sandwich only gets tastier when defeated.
Reply With Quote
  #2   Spotlight this post!  
Unread 05-06-2012, 07:11 PM
Michael Blake's Avatar
Michael Blake Michael Blake is offline
Head Coach
FRC #3481 (Bronc Botz)
Team Role: Coach
 
Join Date: Jan 2011
Rookie Year: 2011
Location: Helotes, TX
Posts: 249
Michael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant future
Re: Plans for the future

Quote:
Originally Posted by thenomnivore View Post
For next year's robotics season, the team decided to change almost everything entirely about the team. Our showmanship, that way we dress, etc. One of the most important and most talked about issues we face is the design process. For the last couple years, what we have done this process was we would have 2 teams making 2 robots, choose which one is the best, go from their but by the end of the season, it seems like a waste of time because of the amount of time we spent of each robot and not one. I'm asking any team for advice or how their team does their design process and how well does it work. Also, we are trying to get our mentors to have less say in the final robot because usually, the most important task almost 100% becomes a project of the mentors.
Any input and ideas are helpful. Thanks
You may want to start with John V-Neun's (148 Robowranglers) white-paper on the Design Process...

http://people.clarkson.edu/~jcarroll...R.20091204.pdf

We're a 2nd year FRC team who won the Engineering Inspiration award and seeded in the Top 8 at our two regionals. Plus, we seeded 5th/Captain on Archimedes and made it to the Semi-Finals... 15 months ago, we didn't know a "Digital Sidecar from a Railway Car!"

Our entire approach/process is based on this document...

EXPERIENCE, HARD WORK, recruitment, combined with this _invaluable_ knowledge that JVN has shared is what has enabled our team to progress rapidly...

Hope this is helpful to you and your team...
__________________
Founder - FRC 3481 - Bronc Botz (2011) // 2012, 2013, 2014, and 2015 Beta Test Team - C++
Founder - San Antonio Competition Robotics Alliance, Inc. (SACRA) [501(c)(3) pending] (2012)
Co-Founder w/Matt Blake - VEX VRC 3481Z - Wonder Botz (2011) [for Physically or Mentally Challenged Teens]
Co-Founder - FTC 4008 - Bronc Botz-Orange (2010) and FTC 4602 - Bronc Botz-Blue (2011) and FTC #6976 - Bronc Botz-Nano (2013 - middle-schoolers)

Last edited by Michael Blake : 05-06-2012 at 07:15 PM.
Reply With Quote
  #3   Spotlight this post!  
Unread 05-06-2012, 07:11 PM
Garrett.d.w's Avatar
Garrett.d.w Garrett.d.w is offline
Build Lead
FRC #2733 (The Pigmice)
Team Role: Engineer
 
Join Date: Jul 2011
Rookie Year: 2010
Location: Portland
Posts: 318
Garrett.d.w is a splendid one to beholdGarrett.d.w is a splendid one to beholdGarrett.d.w is a splendid one to beholdGarrett.d.w is a splendid one to beholdGarrett.d.w is a splendid one to beholdGarrett.d.w is a splendid one to beholdGarrett.d.w is a splendid one to behold
Re: Plans for the future

We do something that we call the 7 ways. It works great for us because it gives everyone, even the mentors (though they generally opt out) an equal opportunity to present and comment ideas.

I like to break this down into a few simple steps.

1). Individual brainstorm.
Each person goes off and draws or describes a solution to a problem.

2). Presentation
Each person gets a brief slot of time to present their ideas and then a slot of time to answer questions.

3). Listing of pro's and cons
The team brainstorms the pro's and cons of all of the solutions, normally we have already axed 3/4 of the ideas at this point, so we are not overworking ourselves.

4). Vote!
The team votes for their favorite solutions. From here we take two or three solutions and mock them up in plywood, just as a proof of concept.

This process can take our team about a full day to complete. We generally only have to do it once per season to figure out our general build strategy.
__________________
"A mind once stretched by a thought will never regain it's original dimensions."

Optimists think the glass is half full.
Pessimists think the glass is half empty.
Engineers realize it's twice as big as it needs to be.

Last edited by Garrett.d.w : 05-06-2012 at 07:18 PM.
Reply With Quote
  #4   Spotlight this post!  
Unread 05-06-2012, 07:12 PM
LeelandS's Avatar
LeelandS LeelandS is offline
Robots don't quit, and neither do I
AKA: Leeland
FRC #1405 (Finney Falcons)
Team Role: Tactician
 
Join Date: Nov 2007
Rookie Year: 2005
Location: Webster, NY
Posts: 518
LeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond reputeLeelandS has a reputation beyond repute
Re: Plans for the future

Hi! First off, I congratulate you on taking this step. A lot of teams I've talked with are not willing to do a total overhaul of their process and team in general. It can be a great way to get a team to reinvent themselves and start down a different path if they're not liking their current one.

First off, I wouldn't advocate the "two teams, two robots" deal. It's in interesting thing to consider if you have a very large team and an insane amount of resources, but otherwise, you're going to have two robots that are half as good as one could be. So I'd recommend having your entire team come together and work on one robot.

Here are a few notes I remember when considering how I'd run a team and designing a robot:
- Break into groups. Put students and mentors into assigned sub-groups that focus on a single aspect of the robot (drive system, game piece manipulator, end game device, etc.). It's easier to facilitate design and production on a smaller group, so long as they're not TOO small. Make sure all students on the team are able to suggest designs.
- K.I.S.S. "Keep it simple, stupid." Don't over complicate things. The process I follow most is start with your design. Then iterate it, making it more robust and effective each time, without adding too much complexity.
- Built within your resources. In addition to K.I.S.S., don't build a design your team can't support. Unless you have the manpower, time, experience and resources to design, build, manufacture and maintain a system, don't do it. I've seen a lot of teams try and build something beyond their resources, and the result is not terribly pretty. This includes both physical systems and anything related to programming. Don't overburden your programmers.
- Play for the game. Consider everything you want to do in this game. From drive system to game piece manipulator, make sure your system plays the game. If you're designing for this game, you may want a drive system with high traction for bridge traversal. Things like that are what you want to consider.

These are the basic points I consider. I'll post more later when my laptop battery isn't on the verge of death.
__________________
My heart will forever lie with SparX
1126: 2008 - 2011; Where it All Began.
1405: 2013 - Present; A Wanderer is Born.

I want to change everything. I want to revolutionize FIRST. If only, one team, and one day, at a time.
Reply With Quote
  #5   Spotlight this post!  
Unread 05-06-2012, 07:47 PM
thenomnivore's Avatar
thenomnivore thenomnivore is offline
Registered User
AKA: Ramirez
FRC #1212 (The Sentinels)
Team Role: Engineer
 
Join Date: Mar 2011
Rookie Year: 2010
Location: Arizona
Posts: 23
thenomnivore is an unknown quantity at this point
Re: Plans for the future

This has been a lot of help THANKS!!
__________________
A sandwich only gets tastier when defeated.
Reply With Quote
  #6   Spotlight this post!  
Unread 05-06-2012, 07:52 PM
Andrew Lawrence's Avatar
Andrew Lawrence Andrew Lawrence is offline
Work it harder, make it better.
AKA: SuperNerd256
FRC #1323 (Madtown Robotics)
Team Role: College Student
 
Join Date: Jan 2011
Rookie Year: 2011
Location: Merced, California
Posts: 3,378
Andrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond reputeAndrew Lawrence has a reputation beyond repute
Send a message via Skype™ to Andrew Lawrence
Re: Plans for the future

I'd like to start this post by saying thank you for making this thread. I've been meaning to redo how our team does design for a while, and this gave me the initiative to start it. So, thank you.

Anywho, this is what I came up with:

Saturday (kickoff day):
-Discuss game
-Objectives
-Ways of scoring
-Possible Strategies
-Get the general game strategy locked in
-Make a strategy for both offense and defense
-Have people decide which subgroup they want to work in during the design period

Sunday:
-No team meeting
-Have team members brainstorm different designs for their subsystem

Monday (may go on to Tuesday):
-Whole team meets
-Break up into system subgroups, and start making a list of designs and details for each subsystem part
-Subgroups draw out and list the details of each mechanism, and pick their top 3
-Each subgroup presents their top 3 ideas to the entire team
-The whole team goes over the pros/cons of each design presented
-After a detailed pro/con of each part, the team does one of two things:
-1: Choose the best design out of 3 for each subgroup
-2: Eliminate one of each subgroup design and vote again on the remaining two
-By the end of Monday/Tuesday, there is 1 remaining design for each subsystem of the robot. The team then finalizes those designs with the more intricate details (how, what), and the design is semi-locked.

Semi-locked means that for the most part, you won't change anything, but you can if you need to.
__________________
Team 256: 2011-2014
Team 1323: 2014-Present

"The greats weren't great because at birth they could paint, the greats were great because they paint a lot" -Macklemore
Reply With Quote
  #7   Spotlight this post!  
Unread 05-06-2012, 07:53 PM
LedLover96's Avatar
LedLover96 LedLover96 is offline
That dude in the Golden Hat
AKA: Walter Deitzler
FRC #3397 (Robolions)
Team Role: Leadership
 
Join Date: Jul 2011
Rookie Year: 2010
Location: University City, MO
Posts: 755
LedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond reputeLedLover96 has a reputation beyond repute
Re: Plans for the future

Also, check out Kartik's presentation, once it is posted online. Definitely a thing to see, and a great help.
__________________

(Hanging out with my buddies at 610)
Robotics, it's not just a club, it's a career.
FLL Referee (2012-Present)

2014 Gateway Robotics Challenge winners (With 2481 and 1985)
2011 St. Louis Regional Winners (With 1985 and 3284)
2010 Highest Rookie Seed
Reply With Quote
  #8   Spotlight this post!  
Unread 05-06-2012, 08:03 PM
thenomnivore's Avatar
thenomnivore thenomnivore is offline
Registered User
AKA: Ramirez
FRC #1212 (The Sentinels)
Team Role: Engineer
 
Join Date: Mar 2011
Rookie Year: 2010
Location: Arizona
Posts: 23
thenomnivore is an unknown quantity at this point
Re: Plans for the future

again, i thank thee!
__________________
A sandwich only gets tastier when defeated.
Reply With Quote
  #9   Spotlight this post!  
Unread 05-06-2012, 08:20 PM
Alex.q Alex.q is offline
Registered User
FRC #2220 (Blue Twilight)
Team Role: Alumni
 
Join Date: Jan 2011
Rookie Year: 2008
Location: Eagan, Minnesota
Posts: 157
Alex.q is on a distinguished road
Re: Plans for the future

I know almost nothing about your team, so I can't give comments directly to your situation, but I will describe ours this past year. We are one of if not the largwest FRC team in Minnesota with about 50 kids that show up on a regular basis. Every year it seems we have re-structured our build plan and leadership. This past year, we considered the same idea with two different robots, and decided it would be a lot of wasted effort because much of the work would be redundant and it would not create any opportunity to iterate. The idea then became 1 chassis with two competing manipulator teams to see who could design the best manipulator. (While we did not use this approach, I think it would have worked well for a subsystem like the shooter, but I'm not sure if it would have meant a catapult and a wheeled shooter or two different but similar designs.) Anyway, we decided that it could be hard to decide which one was better (at what point do you decide, and at the deadline point the truly better manipulator is still waiting to get its essential part in the mail) and could also create hard feelings within the team. We also considered employing large number of students to build more prototypes. I'm not exactly sure of the approach we chose, because as soon as we started the build season, the approach changed to create our traditional build subteams (chassis, manipulator 1, manipulator 2). (As a sidenote here, I remembering vehemently opposing this, having experienced in lunacy compartmentalized subteams who failed to properly integrate their subsystems. Beware of this.)

In short, instead of 2 robots, build 1 chassis 2 different yet similar subsystems that will employ the same game strategy. (It would be hard to compare good ball collector to a mediocre shooter). OR Build 2 robots and iterate upon the first version to improve it. This is probably the more popular method.

I have been thinking about how to once again restructure the build process, and this is what I am currently considering. Everyone as a team decides what strategy they want to employ. Then groups break out into subgroups (chassis and manipulator) to brainstorm possible ideas for the sub-assembly on which they will specialize. Ideas are presented to the whole team, some shot down; a select few will be prototyped. A smaller group of students will work as the design team to do the detailed design work. As they do this, they will assign build tasks to the builders (prototype what amount compression will be needed on the ball). Once an iteration of the robot is designed, everyone works to build it. Its tested, evaluated to see waht could be improved. Re-design flawed systems, continue to test v1.0 while designing and building 2.0.

*Keep in mind I am accustomed to a large team, with a smaller team, I am sure you would adapt this structure.
Reply With Quote
  #10   Spotlight this post!  
Unread 05-06-2012, 08:37 PM
Michael Blake's Avatar
Michael Blake Michael Blake is offline
Head Coach
FRC #3481 (Bronc Botz)
Team Role: Coach
 
Join Date: Jan 2011
Rookie Year: 2011
Location: Helotes, TX
Posts: 249
Michael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant futureMichael Blake has a brilliant future
Re: Plans for the future

Quote:
Originally Posted by LedLover96 View Post
Also, check out Kartik's presentation, once it is posted online. Definitely a thing to see, and a great help.
Without even seeing this yet, I would agree...

We were deep in fixing our bot Wednesday and didn't get the opportunity to go to Karthik's presentation...

Anxious to see the presentation soon to see how we can fuse/merge it with JVN's Design Process approach:

http://people.clarkson.edu/~jcarroll...R.20091204.pdf
__________________
Founder - FRC 3481 - Bronc Botz (2011) // 2012, 2013, 2014, and 2015 Beta Test Team - C++
Founder - San Antonio Competition Robotics Alliance, Inc. (SACRA) [501(c)(3) pending] (2012)
Co-Founder w/Matt Blake - VEX VRC 3481Z - Wonder Botz (2011) [for Physically or Mentally Challenged Teens]
Co-Founder - FTC 4008 - Bronc Botz-Orange (2010) and FTC 4602 - Bronc Botz-Blue (2011) and FTC #6976 - Bronc Botz-Nano (2013 - middle-schoolers)
Reply With Quote
  #11   Spotlight this post!  
Unread 05-06-2012, 09:34 PM
nlknauss's Avatar
nlknauss nlknauss is offline
STechnologyEM Teacher, Alumni
AKA: Nate Knauss
FRC #2729 (LC Storm Robotics Team)
Team Role: Teacher
 
Join Date: Feb 2003
Rookie Year: 2000
Location: New Jersey/Philadelphia
Posts: 291
nlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond reputenlknauss has a reputation beyond repute
Re: Plans for the future

There are a wide number of engineering design processes you can follow to design and build your solution. Pick one that will work within your system and the resources you have available to your team. Also remember that you have to run that design process. Look ahead and schedule where you should be on exact days of your timeline and make those goals happen. I've seen many people pick a process to follow and not use the process to see the design out because the end of build sneaks up on them.
__________________

Nate Knauss
FRC 2729 Teacher-Drive Coach 2009-?, FTC 4390, FTC 7433

FRC 87 Student 2000-2002 and Mentor 2003-2006, FRC 1647 Mentor 2006-2008, FIRST Senior Mentor 2009-2013
2014 - Hatboro-Horsham Innovation in Control Award, Lenape-Seneca Gracious Professionalism Award
2013 - Lenape-Seneca District Winners (w/ 316 & 2495), Chairman's Award, Mid-Atlantic Region Champions (w/ 2590 & 1640)


"We can't change the cards we are dealt, just how we play the hand." -Randy Pausch

Reply With Quote
  #12   Spotlight this post!  
Unread 05-07-2012, 07:37 AM
Anupam Goli's Avatar
Anupam Goli Anupam Goli is offline
Still 0 blue banners...
AKA: Wing
FRC #1648 (G3 Robotics)
Team Role: Mentor
 
Join Date: Dec 2010
Rookie Year: 2008
Location: Atlanta, Georgia
Posts: 895
Anupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond reputeAnupam Goli has a reputation beyond repute
Send a message via Skype™ to Anupam Goli
Re: Plans for the future

Quote:
Originally Posted by SuperNerd256 View Post
I'd like to start this post by saying thank you for making this thread. I've been meaning to redo how our team does design for a while, and this gave me the initiative to start it. So, thank you.

Anywho, this is what I came up with:

Saturday (kickoff day):
-Discuss game
-Objectives
-Ways of scoring
-Possible Strategies
-Get the general game strategy locked in
-Make a strategy for both offense and defense
-Have people decide which subgroup they want to work in during the design period

Sunday:
-No team meeting
-Have team members brainstorm different designs for their subsystem

Monday (may go on to Tuesday):
-Whole team meets
-Break up into system subgroups, and start making a list of designs and details for each subsystem part
-Subgroups draw out and list the details of each mechanism, and pick their top 3
-Each subgroup presents their top 3 ideas to the entire team
-The whole team goes over the pros/cons of each design presented
-After a detailed pro/con of each part, the team does one of two things:
-1: Choose the best design out of 3 for each subgroup
-2: Eliminate one of each subgroup design and vote again on the remaining two
-By the end of Monday/Tuesday, there is 1 remaining design for each subsystem of the robot. The team then finalizes those designs with the more intricate details (how, what), and the design is semi-locked.

Semi-locked means that for the most part, you won't change anything, but you can if you need to.
Your schedule is nice, but seems a tad bit rushed. An alternative to yours would be something like this;

On Saturday, concentrate on kickoff, and READ THE RULES. Do not discuss anything until reading the rules. Know your limitations. Know the game. Once that is done, start coming up with strategies. Make a priority list of what game elements you want to manipulate. There is a good example of this in HOT's technical documents; http://frcteam67.dyndns.org/hot_Engi...Tech_Notes.pdf

On Sunday or Monday, make sure everyone is agreeing with the strategy. Vote is only a four letter word. You have to make sure everyone is unanimous with the decision on strategy. Voting is a last resort to come to a decision, never the first. Once that is done, you can divide people into subgroups and have them come up with concepts for each of the subsystems. The Drive Train should be decided first, as this is usually the easiest to decide and biggest hurdle.

Each concept should have a proof of concept or prototype, though with drivetrains, there are enough resources where a proof of concept isn't needed, and active prototyping would only be fore frame structure. The other subsystems should go through rapid prototyping in order to test the concept and to find an optimal efficiency of manipulating the game element. I like to refer to 118's 2006 week 3 video as an example of what I'm talking about: http://www.youtube.com/watch?v=UV_d1ChpyLg
__________________
Team 1002: 2008-2012
Team 1648: 2012-????
Facebook
Georgia Institute of Technology Class of 2016
I wish everyone a great season, and good luck!
Reply With Quote
  #13   Spotlight this post!  
Unread 05-07-2012, 07:51 AM
Unsung FIRST Hero
Al Skierkiewicz Al Skierkiewicz is offline
Broadcast Eng/Chief Robot Inspector
AKA: Big Al
FRC #0111 (WildStang)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1996
Location: Wheeling, IL
Posts: 10,031
Al Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond reputeAl Skierkiewicz has a reputation beyond repute
Re: Plans for the future

I suggest you read "Behind the Design". I question your decision to change the team marketing and look. We did that one year and no one could find us. We are tie dye forever now. We start brainstorming after we take a break when the kickoff ends. We don't stop for the next several days. We play the game, work on strategy, play the game some more, finalize strategy and then make a lost of what it will take to win the game. Then and only then do we start to design the robot. We take input from everyone during this phase, students mentors and parents. No idea is turned down. Each year we do this part a little different depending on who is leading. We often break into small groups and then report back when all the groups get together. Then we build a prototype and start testing. We modify the design throughout the build and sometime right up to Champs.
__________________
Good Luck All. Learn something new, everyday!
Al
WB9UVJ
www.wildstang.org
________________________
All is better now, NOS parts are working fine. Why does this year's game remind me of Violet in Willie Wonka? Hmmmm, I see blueberries!
Reply With Quote
  #14   Spotlight this post!  
Unread 05-07-2012, 07:57 AM
Unsung FIRST Hero Woodie Flowers Award
Chris Fultz Chris Fultz is offline
My Other Car is a 500 HP Turbine
FRC #0234 (Cyber Blue)
Team Role: Engineer
 
Join Date: Jan 2002
Rookie Year: 1942
Location: Indianapolis, IN
Posts: 2,630
Chris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond reputeChris Fultz has a reputation beyond repute
Re: Plans for the future

http://www.chiefdelphi.com/media/papers/2485
__________________
Chris Fultz
Cyber Blue - Team 234
2014! IRI Planning Committee - Co-Lead (yes, already planning).
2010 - Woodie Flowers Award - Championship
Reply With Quote
  #15   Spotlight this post!  
Unread 05-07-2012, 09:14 AM
aja747 aja747 is offline
lead stratagist.
AKA: mcfly
FRC #0228 (Gus Robotics)
Team Role: Scout
 
Join Date: May 2012
Rookie Year: 2008
Location: meriden, ct
Posts: 1
aja747 is an unknown quantity at this point
Send a message via Skype™ to aja747
Thumbs up Re: Plans for the future

thanks for all the advise ill send this stuff to the head honcho. def alot of teams should be thinking this way because personnaly i think team 148 has alot of fun during build season
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 10:31 PM.

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


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