Go to Post Our prototypes are good and running, now just need to do some magic to transform all that wood to aluminum. :eek: - FIRSTMa2104 [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 Rate Thread Display Modes
Prev Previous Post   Next Post Next
  #2   Spotlight this post!  
Unread 27-09-2011, 22:32
DonRotolo's Avatar
DonRotolo DonRotolo is offline
Back to humble
FRC #0832
Team Role: Mentor
 
Join Date: Jan 2005
Rookie Year: 2005
Location: Atlanta GA
Posts: 7,011
DonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond reputeDonRotolo has a reputation beyond repute
Re: Reverse Engineering, experiences, advice

Somewhat related comments:

I think deconstructing your last bot is a great idea, but add the goal of reassembling it again. It will make a dandy test mule for ideas.

As for mentor overload in the design arena: Instead, teach the kids how to follow a prioritized and iterative design process. By that I mean the should...

First, understand the Game and what it takes to win it, including nuances of strategy. Maybe only one or three kids will understand these nuances, so let them explain to everyone else. (We all know what it takes to win a baseball game, the game's been here for years. But think of some of the strategies that are used: Would a bunt be an obvious play or a nuance? Think of the Game in those terms)

Second, decide what Tasks the robot must be able to perform to win the Game. This is a great brainstorming activity. No mechanisms (you have to control that with an iron fist) just capabilities.

Third, once "everyone agrees" (or at least there's a majority) on the Capabilities, then determine which ones are most important, and list them in order. This is important, as it determines which Capabilities are lost when design tradeoffs must happen (e.g., Crunch Time).

Fourth, brainstorm Mechanisms to perform those Capabilities. This is the fun stuff, go wild for a day or two. (For 1676, this happens on the first Tuesday & Wednesday of Build Season).

Then, let the proponents of a Mechanism go prototype it. Cardboard, styrofoam, wood, whatever - "Proof of Concept". 2 Days.

Friday or Saturday is Design Review, where the Mechanisms are selected.

Them for the next 5 weeks, everyone is fabricating Mechanisms they know a lot about. If you get some kids well-trained, assembly can happen in week 3-1/2, with furious re-fabrication and final assembly in week 4-1/2.

Then the drivers get it to break it, and if they are successful, you build the better, stronger mechanism part in week 5-1/2, slap it together and crate (or bag) it.

(Programmers start in Week 2 BTW because the mechanisms are defined already).

Hope this stimulates some discussion.
__________________

I am N2IRZ - What's your callsign?
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 02:58.

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