Go to Post Remind me again. Why do we let the GDC hold us captive to these hints year after year? - jholman [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 Rating: Thread Rating: 3 votes, 5.00 average. Display Modes
  #16   Spotlight this post!  
Unread 13-11-2003, 08:25
Joe Matt's Avatar
Joe Matt Joe Matt is offline
Wake Up Get Up Get Out There
no team
 
Join Date: Dec 2001
Rookie Year: 2001
Location: CAK
Posts: 5,067
Joe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond reputeJoe Matt has a reputation beyond repute
Quote:
Originally posted by nuggetsyl
weapon i think you are in the wrong competition for that
Notice the parentheses? It's what we call our accessories, but more aptly describe it. Accessories sounds like we're making a purse and some nice shoes to go along with it.
__________________
Reply With Quote
  #17   Spotlight this post!  
Unread 13-11-2003, 12:15
nuggetsyl's Avatar
nuggetsyl nuggetsyl is offline
Registered User
FRC #0025
Team Role: Coach
 
Join Date: Sep 2001
Location: north brunswick
Posts: 869
nuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond reputenuggetsyl has a reputation beyond repute
lol
Reply With Quote
  #18   Spotlight this post!  
Unread 13-11-2003, 13:13
Sachiel7's Avatar
Sachiel7 Sachiel7 is offline
<Yes I managed to flip it
AKA: Shayne Helms
FRC #1132 (RAPTAR Robotics)
 
Join Date: Sep 2002
Rookie Year: 2002
Location: Richmond, VA
Posts: 541
Sachiel7 is just really niceSachiel7 is just really niceSachiel7 is just really niceSachiel7 is just really niceSachiel7 is just really nice
Send a message via AIM to Sachiel7
Hmm...Robots with Purses....
Heh, just a funny thought.
Funny post JosephM...
__________________
-=Sachiel7=-

There's no such thing as being too simple!
Look for Team #1132, RAPTAR Robotics at the VCU Regional this year!
Reply With Quote
  #19   Spotlight this post!  
Unread 13-11-2003, 13:51
Madison's Avatar
Madison Madison is offline
Dancing through life...
FRC #0488 (Xbot)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1999
Location: Seattle, WA
Posts: 5,246
Madison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond reputeMadison has a reputation beyond repute
I've just been taught about a number of different design processes and philosophies, but rather than reiterate them here, I'll just give you a link or two.

I don't really like democracy in robotics teams because I think it's limiting to what the team can accomplish when a leader emerges and directs people's efforts efficiently. That said, I usually prefer to be the one who's leading, too, so that may give you some idea about why I feel that way.

It's a balancing act and there's no right solution. If students aren't given enough involvement or input in the design process, they may begin to resent that or feel unneeded. If a single person has the organizational skill and time available to them to oversee the entire design themselves, with criticism taken and considered, the team may build a robot that far exceeds their expectations.

At least, so I think.
__________________
--Madison--

...down at the Ozdust!

Like a grand and miraculous spaceship, our planet has sailed through the universe of time. And for a brief moment, we have been among its many passengers.
Reply With Quote
  #20   Spotlight this post!  
Unread 13-11-2003, 15:07
ChrisH's Avatar Unsung FIRST Hero
ChrisH ChrisH is offline
Generally Useless
FRC #0330 (Beach 'Bots)
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1998
Location: Hermosa Beach, CA
Posts: 1,230
ChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond reputeChrisH has a reputation beyond repute
Ken did a great job of explaining the basics of the engineering process. I would have said the same things but didn't have time at that moment. But I think he missed a key point, budgets. He probably left it out in the interest of brevity.

When we are ready to move from the What stage to the How stage we set budgets for weight and sometimes cost before we get to the design. We also set aside "overhead weight" for those minor items like the RC, battery, and light. The budget reflects somewhat the relative importance of the subsystem in our game strategy.

Last year's budget was something like this:
Overhead 30lbs
Frame 20 lbs (includes sidewalls)
Drive 20 lbs
Wedges (small arms to grip ramp) 30lbs (includes most pnuematics and compressor)
Arm and gripper 25 lbs

Notice: we have only budgeted 125 lbs in this example. Systems NEVER come in under budget so allow for "growth". Actually we usually budget to 115 lbs, but in this example I stayed closer to actual weights.

We also start our subsytem designs from the interface to the next system. (Remember "He who designs the interface first wins!") So if we have a lifting arm joined to the frame, the first thing is to define how the arm interfaces and "fix" that. The frame and arm are then designed around the interface. The frame doesn't care much what the gripper end of the arm looks like. This way the frame builders can get busy and build the robot while the arm guys flail around trying to get their gripper to work. This way, even if the arm guys fail entirely we can still drive.

Budgeting also provides something of a reality check. If you can't figure out a design that stays within budget then maybe you shouldn't be doing that function.

Finally we have a System Engineering function that ensures that ALL the interface requirements are defined and communicated to the relevant groups. (System Engineer: "No, we can't add that limit switch, it's not on the list and besides we have to ship tomorrow"). The Systems Engineers also track weight and cost to ensure that each system stays within budget, both cost and weight. They also monitor progress. If a subsystem isn't done a week before ship we will either funnel a massive effort towards finishing it or scrap it.

We usually have a mentor and a student who are dedicated to this vital function. They have other jobs in the team and participate in building the robot, but their PRIMARY responsibility is making sure we finish on time and within budget.

It's not necessarily fun, but it is important. Properly executed, a Systems Engineering approach enables many more people to participate in the design process while still staying co-ordinated. It lowers the individual work load, so that people have more time to think about what they are doing and do it right the first time. It is also how most major systems (ie aircraft, satellites, etc) are designed today. Such systems are far too complex for a single person to comprehend in detail, let alone design.
__________________
Christopher H Husmann, PE

"Who is John Galt?"
Reply With Quote
  #21   Spotlight this post!  
Unread 13-11-2003, 15:13
skrussel skrussel is offline
Registered User
no team (000)
 
Join Date: Jun 2001
Location: Michigan
Posts: 156
skrussel has a spectacular aura aboutskrussel has a spectacular aura aboutskrussel has a spectacular aura about
Yeah, this is a good thread....happened last year, too!

Regarding comments about fewer than 10 kids doing most of the robot construction.........after 7 years in FIRST, I find that happens regularly, and I believe that it is okay. Kids seem to find their niches on the team, some participating more than others, some contributing more than others, some spending more time than others. That's okay, too.

Actually, more than 7-10 kids who actually have their hands on the robot can be too many.

I totally agree with Ken that the PROBLEM needs to be worked out first, then figure out how to construct the robot to solve the problem. One of the best pieces of advice ever. Learned this one the hard way!
__________________
[
Reply With Quote
  #22   Spotlight this post!  
Unread 14-11-2003, 09:32
Steve Shade Steve Shade is offline
Registered User
no team
Team Role: Engineer
 
Join Date: Jun 2001
Rookie Year: 1999
Location: Pasadena, MD
Posts: 78
Steve Shade has much to be proud ofSteve Shade has much to be proud ofSteve Shade has much to be proud ofSteve Shade has much to be proud ofSteve Shade has much to be proud ofSteve Shade has much to be proud ofSteve Shade has much to be proud ofSteve Shade has much to be proud ofSteve Shade has much to be proud of
I'll try to keep this short because Ken and Chris have stated most of my process.

Ken's team uses something similar to what i have been doing for about 3-4 years now with my teams. To extend Ken's line of thinking to link Chris' line, you have to go form asking WHAT are we going to do, to HOW are we going to do WHAT we said, and then ask HOW MUCH will each function/system cost and benefit WHAT we are doing? By cost I mean things like weight, time, personnel resources to design and manufacture, etc. You can also use some of these costs as a way to figure out the trade-offs between which systems you choose to build. For example, if you have 20 people on the team, and your drive system will take 3 weeks to design and build with 10 people working on it, then you have to cut back somewhere else.

My only other additional comment is let the numbers guide your decisions. Ken gave a good example of this. You can find many ways to play the game by breaking down the scoring at the beginning and trying to compare the bets points combination to the most realistic combination of systems on your robot. This doesn't mean to go conservative, but to select something that is realistic.

There are plenty of great engineering tools out there. A great source for these tools is form a company called GOAL/QPC. They produce a number of little books for under $10 that are just filled with useful tools. I would recommend the Memory Jogger II as a good place to start getting acquainted with the tools. The Teams Memory Jogger, the Creativity Tools Memory Jogger and the Project Management Memory Jogger ams also be useful depending on what your team needs are. Their website is here. If anyone wants to know what is in these books I have or have read many of them. The books are also available on CD.

Steve
Reply With Quote
  #23   Spotlight this post!  
Unread 14-11-2003, 11:07
KenWittlief KenWittlief is offline
.
no team
Team Role: Engineer
 
Join Date: Mar 2003
Location: Rochester, NY
Posts: 4,213
KenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond reputeKenWittlief has a reputation beyond repute
good point. Using numbers to drive your decision is called Data Driven Analysis.

simply, you calculate the results of the different options you have, and then let the numbers determine your best option.

Take last years game again. If the only thing you do is park on top of the ramp, you get 25 points.

if the only thing you do is push half the boxes into your scoring zone, you get (how many boxes were there again?) 26 points?

if you get half the boxes on your side, and maintain a stack of 4, you get 88 points

if you build a bot that stay in the starting box and knocks half the wall over, you get 0 points

let the data show you the most productive tasks your bot can do

same thing for tradeoffs in the design process. If you use the stock transmissions and two drill motors in the kit, your robot will have a certain top speed, a certain amount of pushing force, and you can bolt it all together in one day

if you build a custom transmission, the performance will be different, but it will take you many weeks to design and fabricate.

This is another area that separates engineers from basement inventors. Inventors get an idea that seems cool to them, and they run off and start building it.

Engineers look at the data, and let it tell them where to focus their life-energy to get the most bang for the buck.

In FIRST you only get 6 weeks - its not much time

if life, you only get to be an engineer for 40 to 50 years - its not much time either (when you are trying to change the world :c)
Reply With Quote
  #24   Spotlight this post!  
Unread 16-11-2003, 18:33
Aignam's Avatar
Aignam Aignam is offline
This Space For Sale
AKA: Anthony Mangia
#1257 (Parallel Universe)
Team Role: Scout
 
Join Date: Oct 2002
Rookie Year: 2003
Location: North Brunswick, New Jersey
Posts: 877
Aignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant futureAignam has a brilliant future
Send a message via AIM to Aignam Send a message via Yahoo to Aignam
Group brainstorming sessions. Figure out what works, what'll win the matches. Make things only as complex as they need to be in order to be efficient. Then do it.
__________________
Some Thoughts to Ponder
How does a sign turn into a lady friend? Don't optional stop signs ruin the purpose? What are pneumatics? Am I really banned from 229 for life? Can walls get bigger?

Aignam. Pronounced A-Num. Mangia backwards.

NJFIRST.org | Best Thread. Ever.

AIM: Aignam | ICQ: 265237569 | E-mail: AnthonyMangia@aol.com | HTTP: www.aignam.com
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

Similar Threads
Thread Thread Starter Forum Replies Last Post
How much planning goes into your robot? Jnadke General Forum 41 29-01-2006 21:29
Team 131 'C.H.A.O.S.' robot design archiver 1999 0 23-06-2002 22:37
WASH Palm scouting at the Championship Mike Soukup Scouting 2 19-04-2002 15:14
Index of team's post about their robot... Ken Leung Robot Showcase 1 20-03-2002 17:10
about how Drive Train push the robot... shouldn't the force accelerate the robot? Ken Leung Technical Discussion 12 26-11-2001 09:39


All times are GMT -5. The time now is 15: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