engineer bots
 

prenote: I'll make cliffs later if enough ppl want them.

This was team 1549's rookie year and though we had some FIRST vets (one was on his 5'th year. he is a college student now) most of us, including myself, were rookies to FIRST. Anyways, moving on...

A little about our team: there is a charter high school at Washtenaw community college that i am in and that is the home of team 1549. Our team consists of high school and college students. The college students are mostly majoring in industrial robotics, fluid power and machining. Most of them are not engineers.

The point?
At GLR this year we saw teams who's bots were obviously totally designed by the engineers. While this is legal i do not think it is with the spirit of FIRST. There were 4 builders (including myself) and 1 programmer who did 70% of the work on team 1549's robot. A few more guys jumped in in the last 2 weeks. Except for our passive gripper and the winch drum everything was designed, made and put together by high school and college students.

Our bot, while very good (when the drive program isn't screwed up and I'm not getting ramming penalties), cant measure up to these superbots.

There is nothing that can really be done so i guess i am just ranting for my own sanity. I just wanted to point out the unfair advantage that many teams have.

Also, i cannot conclude a post about building the bot without thanking the mentors, particularly Kieth and Gary. Without your guidance, passing on the wisdom of past experience and teaching the team how to be a team we could never have gotten this done. Thanks guys!

Re: engineer bots
 

This subject has been debated over and over for years. Please search out some of the posts regarding this.

Summary in my words and my opinions:
There are many types of FIRST teams with their own unique way of organization, building, engineering, fund-raising and yes participation levels of students and engineers.

The true focus must remain the I in FIRST - Inspiration. How a team desires to inspire can run the full range from 100% student designed robots to the robots that have significant professional engineering. In both cases the Inspiration can be either weak or strong. It is how the team leadership decides to make their team run.

Dean has said many times that Engineers and Teachers Inspiring youth to get involved in careers involving Science Engineering and math is the real mission. How it is done is up to the team. There are no magic formulas for we are all from different schools, different socio economic situations and have different levels of engineering/corp support.

Is this unfair - YES. Would it not be great if we were all from wealthy communities and had corporate partners that could support teams without budget restrictions and all had students that were all college bound with scores of 35 on the ACT. And all students getting a free ride to a college of their choice.

That (above) is not true and yet can be unfair.

Is it unfair for a student not to know where their next meal is coming from - YES
Is it unfair for a student to have a terminal illness - YES
Is it unfair for a team to make their robot from used metal - YES
Is it unfair for a team not to have an engineer on their team - YES

Look, life is not fair. FIRST competitions are not fair. This is life. We make the best path we can and do everything possible to stay on it.

Instead of focusing on what other teams have look at the INSPIRATION. Were you inspired by the experience. If so, FIRST has accomplished its mission as well as your team mentor. If you are NOT inspired take a close look at why. Please do not use the lack of resources as the excuse....I am sure there are others.

Sorry for the long answer but I hold the INSPIRATION in FIRST as the most important mission. As a team leader if I do not INSPIRE I have failed, and I do not like to fail.

Mike Martus Team #47
I have been with FIRST for 10 years and see the inspiration.

Re: engineer bots
 

I am 100% with Mike on this one.

Every team and every situation is different, and they can change from year to year. The true measure of a successful team is the Inspiration part -
and that can come in a lot of different ways. Each team and each team member has an opinion about what is best.

Re: engineer bots
 

i agree with both opinions in this discussion

we are a rookie team and had minimal help as well as funding
we worked so hard to get our robot going and then to see it work was awesome

but then to get to the regional and see another rookie team with a machined robot that looked to be built by others

i mean we did good but we were unable to get to nationals and a team that couldn't even control their robot could

thats just where everything in my opinion comes into question :confused:

Re: engineer bots
 

some people would point fingers at team 1549 and say "what? you let college students help build your bot? we only let HS students build ours"

every team has their own approach - some teams take a few years to find their balance.

but in the end, its all good.

Re: engineer bots
 

Please, everyone, before you post in this thread, read what you're about to say. Heck, even have someone else read it.

This is one of those sensitive topics where people have a knee jerk reaction and immediately post their thoughts. This is also one of those topics that we've never been able to have an intelligent, mature discussion on. It quickly degenerates into name calling, and finger pointing.

Also, unless you have some insight into the day to day runnings of another team, please do not insinuate that the students on such teams do not do any of the work. Maybe they do, maybe they don't, but fact of the matter is, you really don't know.

As a warning, please keep discussion civil and on topic, or this thread will have to be closed.

Re: engineer bots
 

Personally, I really don't care if there is a team whose robot was built by the engineers. What I get out of FIRST is the satisfaction of working with the team. I love my team, I like it how all the personal problems go away when all of us come together to make this possible and show what SigmaC@T can do. Mentors are always there to help us. If they weren't there to help us, FIRST wouldn't be where it is now. The engineers never give up even after taking times off from work, getting yelled at by their wife, even putting themselves into jeopardy.

... I can also understand the problem with a team (with a student built robot) saying its not fair for another team to have a robot which is engineer built. But think positive. Put your mind together and take on the challenge.

Welcome to the real world.

Re: engineer bots
 

You are right, inspiration is king. I also know that there would not have been the inspiration if i would not have been a serious part in building the robot. I learned about all sorts of stuff, i learned about materials, hot to lathe, mill and even how to weld. I was also very saddened and disappointed when we got our tail tanned by a few teams who's high school members never even touched the bot in the pits. the veteran *insert big 3 sponsor here* engineers did all the stuff.

It isn't about money, we had a huge machine shop at our disposal (community college has a machining program) complete with good CNCs and everything. we even had a high schooler who was in the CNC programming associates degree. We also had money, the college said they would pay for everything. What we didn't have was lots of engineers who have what only time can give... experience.

I am glad we didn't, i am very proud of our bot. I wish that every FIRST team could feel such pride in THEIR work.

No, I'm not going to resort to name calling like some of these threads do. I am not angry, i just feel cheated. I also feel for other high schoolers who may have been cheated. *EDITED OUT for lack of clarity* In many ways FIRST is becoming commercialized. but sponsors are a necessary evil.

It is reasons like that that i am against having a big 3 company sponsor us.

Re: engineer bots
 

The point?
At GLR this year we saw teams who's bots were obviously totally designed by the engineers. While this is legal i do not think it is with the spirit of FIRST. There were 4 builders (including myself) and 1 programmer who did 70% of the work on team 1549's robot. A few more guys jumped in in the last 2 weeks. Except for our passive gripper and the winch drum everything was designed, made and put together by high school and college students.

Our bot, while very good (when the drive program isn't screwed up and I'm not getting ramming penalties), cant measure up to these superbots.

There is nothing that can really be done so i guess i am just ranting for my own sanity. I just wanted to point out the unfair advantage that many teams have.

Also, i cannot conclude a post about building the bot without thanking the mentors, particularly Kieth and Gary. Without your guidance, passing on the wisdom of past experience and teaching the team how to be a team we could never have gotten this done. Thanks guys!

Hi Validius!

I can sincerely understand your frustration. The only thing that I can suggest is that you change your perspective just a little. It sounds like you had a good experience with your team and mentors this year and I'm sure learned a lot and hopefully developed some new relationships. You should be rightfully proud of your accomplishments and of the product you and your team produced. That is what FIRST is really about. You certainly sound "inspired" and that is the most important aspect of FIRST (IMO). Focus on your teams accomplishments. Every team is different. Just try to make yours the most excellent it can be and I assure you that your experience with FIRST will be of great value and satisfaction to you.

I can understand how easy it is for it to seem like people are "cheating" when it looks as though professional engineers built the robot with little participation from students. When this does happen, the people who are shortchanged the most are the students who didn't have the opportunity to participate in building the robot.

I am an engineer so I know how hard it is to not jump in and "build" the robot by insisting on what I think is best. I also know that we end up with a better robot because I don't! Seriously! You don't have to be an engineer to have great ideas. I see my role as trying to help the students implement THEIR ideas. Sometimes they work, and sometimes they don't. Finding solutions is what engineering is about. I also know that the best way to learn is by trying and, sometimes failing. I remember and learned a whole lot more from the mistakes I made as a young engineer than the things that worked out right out of the box. You know what? I still make mistakes (though I like to think not as many) and I still learn from them.

Don't let your frustration impact your "sanity". Be the very best you can be and inspire your team to seek the same goal. Make the maximum use of whatever resources you have at your disposal. There will always be teams with more and teams with less. Try to focus on getting the maximum amount out of all the resources you and your team have. If you do that, you can be very proud of your accomplishments, no matter what another team does or does not do.

Best of luck to you! (sorry for the long winded reply!)

Re: engineer bots
 

This year we had no (literally no) engineering help, we were competitive and won a judges award for this. There were 9 students and 2 teachers who worked on this bot. These mentors hardly ever touched the bot not only because they didnt want to but because students didnt want them to. Many people commented on the fact that when ever they were walking by our pit there were students programming, repairing and inspecting. We didnt even have a mentor who knew how to program in C. When Mentors did help out they didnt do it them selves they taught us how. I loved This year, The bot was designed by students built by students an operated by students.

However Next year we will have engineering help because that is the ideal of FIRST. When we were in our Chairmans interview they said to think about that for next year. What I want next year is engieers teaching the students so at the end of the build season there are a bunch of experts (high school students) who can fix anything on the bot.

Team 195 is the best example I have ever seen. When we were in the practice area at UTC there were multiple teams with adults working on the bot. However The Cyber nights at 20 or so students working on their bot and 5 mentors (or atleast adults) with their feet up sitting at the top of the stairs. Their complex gripper and What appeared to be a shift on the fly transmission obviosly had atleast some engineering influence. However Tom and the rest of the guys from 195 did all or atleast the majority of the work I saw done on the Robot.

Re: engineer bots
 

Just as a side note before I start, I know a lot of machines do look like they were engineer built, but a lot of them were just built by fantastic students. I know 67 was that way when I was on it and people often confused it for being engineer built.

Onto what I really wanted to say. I have actually just recently had this conversation with a fellow mentor. While I believe (personally) that students should be the ones building their machines and doing everything, he pointed out that the initial purpose of this competition was not a science fair, it was for students to be inspired to be engineers, to place engineers on a sort of pedestal and make students want to do it themselves. Whether this objective is accomplished by the engineers building the robot or the students was not the point, so long as the students were inspired.

Personally, I feel that the best way to inspire students is to allow them to experience the entire process first hand. I also realize, however, that there are a lot of people unable to take that risk. Small machine shops can't take the liability risks of a child being injured. Can you imagine the lawsuit if a student got injured and sued a small machine shop? Not only would they go out of business with bad publicity, but they would be bankrupt from the suit. That's not a risk that many small businesses are willing to take. These days, people are just looking to make it rich on lawsuits and courts are more than willing to help them out it seems. While I'd rather things were different, they aren't and I understand why some teams are forced to have engineer built robots.

Moderators, feel free to delete this post if you feel that it's not appropriate, but I said what I feel needed to be said in the best way I could think of to say it. Thanks!

Re: engineer bots
 

Our team has a few engineers to help out, some equipment, and a small amount of money. We use parts that are used. Our drills have 1 speed. And the students do the work. It's the way we decided to run as a team. We could change it, but we don't want to.
And now for the good part...

One of the new students was scouting during GLR, and was watching some of the "well engineered" machines. She vented some frustration about them. I explained that it didn't matter - it was the inspiration part that matter, not the score at the end of the day...

But then she said she wasn't upset about the fancy robots... she felt sorry for the students who, she assumed, didn't get to work on the robots. So we had to have to whole "different ways to inspire" talk that y'all are doing right now. I was just happy as a mentor to have a student who PREFERRED to be on a team like ours, and DIDN'T want to be on a "super team". It felt good. Don't get that allot.

Re: engineer bots
 

I can certainly understand your frustration but would hope that you would keep a positive attitude. We were also one of those new small teams once with no money and only two mentors. It was tough competing with the “big” teams, but starting off is always tough.

As far as who should be building the robot, I frequently use the analogy of teaching someone to cook.
1) If the students were told to sit outside the kitchen and just watch the cook, the end product would be great to eat, but most students wouldn’t learn much.
2) If the students were sent to the kitchen to experiment freely with no direction, they might have fun for a bit, but the results would not be very good to eat.
3) If the students were right there side by side with the cook in the kitchen learning step by step and getting their hands dirty, the product would be pretty good and the students would have learned how to cook.

Taking this analogy further: Some people learn to cook from their mothers or grandmothers in small kitchens with old equipment. Some learn “on the job” at restaurants, and some study at large institutions. All can be very effective.

So, what does all this mean? Every team’s situation is different and we all need to do the best we can with what we have to work with. Some of the most impressive students I have had the pleasure of meeting through FIRST have been from very small and very frugal teams. These students had been inspired and were inspiring to me.

On our robot I have the students do as much as they personally can and teach them to do more. For some, this means cutting, filing, drilling, and assembling. Others have learned how to use a lathe and milling machine. The same is true for the programming.

On a practical note, if you need help, please ask. Most teams would love to help out in any way they can, during the design/build period or at a competition.

Jay

Re: engineer bots
 

I understand how you feel. It's not much fun when you realize that everything you worked so hard for lies in the shadow of these "superbots". The game is always much easier for Veteran teams; they know how to "play the game". They spend each year coming up with some new, better method of doing something (transmissions, cleaner wiring, more advanced programming, different drive mechanisms), and are able to create a new robot each year with a little of each of these great things.

I, personally, am against a robot being designed and built with minimal student assistance. I have seen it too much, and grew to dislike it. For me, it is and should remain a "high school robotics competition". This is the exact reason that i created my team this year. I wanted to show that a successful team can be made without the assistance of professional engineers. No teachers, no engineers, no corporate sponsor demanding a victory in exchange for it's sponsorship. For the record, we have done just fine.

However, these "superbots" do (as has been stated above) serve a very good purpose. We look up to and admire these teams. The best example i can think of comes from one of my own students. We, as a rookie (and a team whose robot was built exclusively by high school students) obviously did not have one of these "superbots". We server our purpose, and we able to be competitive, but we stood in the shadow of these giants.

One of my students who designed our arm mechanism was utterly dumbfounded by the presence of these other teams. He has no previous exposure to FIRST, and was basically lost for words at seeing these amazing robots. And you know what? I could see the excitement in his eyes. I could tell by the way he looked at how they had "done it" that the wheels in his head were turning. He was flooded with ideas (which he shared with me) about how we could improve our tactics for next year. He's hooked, and his enthusiasm inspires me to keep at it. As we all know, this competition is about inspiring high school students. Consider him inspired.

I love this organization. I love seeing my students lives changing. I love seeing how the veterans improve each year. It is truly inspiring.

Re: engineer bots
 

Hear Hear

By far the best way to inspire the students in FIRST is for them to be working side by side with mentors.

There is another aspect to this question that many people who are new to FIRST don't understand. I will try to explain in the best way that I can.

I genuinely care for the students on my teams. I want to see them as successful as possible. But if I limit the inspiration that I have given to just the students on my teams I would have affected about 20 students per year for 7 years. I am not satisfied with having that level of influence. By contributing to the excellence of the FIRST robotics competition we have the ability to inspire 10s of thousands and soon 100s of thousands of students.

How many students from other teams have been inspired over the years by the amazing creations of teams like 33, 45, 47, 67, 71, and so many others? I can only be one more voice insisting that these teams are doing the right thing by their students as well as all of the students in FIRST. As a mentor, these teams are my inspiration.

Matt B.

(ps I apologize to all the great teams I didn't add to the above list)

Re: engineer bots
 

I 100% agree with Jay, back in 1999 and 2000 we showed up definitely outgunned for the competition but we did our best with what we had and each year tried to do better. Now after being part of the team for 6 years I have seen many a student come and go and you have to work your team based on the level of talent, pride, and skills of the people on the team. Some years we have had students that either wanted to machine or already knew how to and they did their thing, other years none of them showed interest in the build phase but they wanted to assemble it and maintain it at the competition. Each team is different and actually each year is different. Heck this year neither the engineers nor the students made a bunch of the plates for the robot, they were laser cut by our sponsor. Keep in mind that 99.9% of the mentors and engineers don't build robots for a living or anything even close to robots, except for those guys on 217 and 469 :p. Our whole team is electrical engineers that are learning as much about gearboxes and mechanisms as the students.
Don't get down, use your drive that got you this far to propel your team to the next level. I have to believe that any of the rookie teams that go out and come up with a super duper mechanism that toasts a many year veteran team get some sort of extra satisfaction.

My only word of caution, don't go to the extreme of not looking for any help from mentors just to say you did it yourself, IMHO you WILL be missing one of the biggest parts of FIRST and that is to be working with people out there in the real world. It starts the ball rolling from a networking perspective when you are in college looking for a job or just being more comfortable in an interview after college. It may even tell you that engineering or science is the right path for you or even which discipline. This kind of experience is very valuable for most students and they wouldn't have this kind of access without FIRST.

The level of competition has certainly advanced this year. This is the first year where I can say I didn't see any robots at the regionals that went out 5' and fell apart. Nearly every year in the past you could write off 20% of the teams as being totally non-functional, NO-LONGER.

Congratulations FIRST and all of the students, mentors, and teachers that make it all happen

Re: engineer bots
 

I'm sure she's not the only one that would rather do all the work and fail, than do no work and win. It's a great feeling knowing a month ago you were banging your head on a table because you couldn't pickup a vision tetra, but now your robot that you programmed is the 2nd robot to cap a vision tetra in autonomous. I couldn't get that kind of feeling if I knew that a mentor programmed it.


EDIT: I'm not meaning to say that I didn't need a mentor, the programming/electrical mentor was always there for me, but instead of doing the work for me he was acting as a safety net. If I fall into trouble with the code, he would bail me out, tell me what I did wrong, how to fix it, and send me on my way. That's what a true mentor should do.

Re: engineer bots
 

[/b]What I think?

I agree on both parts. I mean INSPIRATION means different for everyone and their team. Is it okay for someone else building their team robot, NO. Is it fair to the other teams to compete in competitions with no engineers and limited budget and go against teams with super bots. NO. But its OK. Like a previous poster above said "Welcome to the real world" This is true, in life its not fair. I mean our robot is made totally by my team, just regular students, NO OUTSIDE HELP. Our school board and local sponsors are our only means of funding. But again, its OK. Yeah, I wish that our robot got some help from engineers and we had more money. But we have the greatest of times and when our robot hits the field, it realllys shows. I am proud of "Sweet FEEET" and my team.

Don't be discourage and just have fun.

Re: engineer bots
 

wow this thread is holding together surprizingly well.

Build a man a fire and he will be warm for a day
but set a man on fire and he will be warm for the rest of his life (sorry, couldnt resist :^)

Some things to think about. Ive been an electrical engineer for 21 years now. Ive designed many digital systems, and I have never had to

1. layout a printed circuit board
2. fabricate (etch) a circuit board
3. assemble a circuit board (solder the parts on)
4. assemble a prototype
5. build a test fixture

I should point out, I have worked for several different corporations in my career.

Generally speaking, engineers dont build or fabricate anything. We design things. We get the fun part, coming up with new stuff, detailing how it works, creating the drawings and schematics, then we hand those off to people who specialize in the fabrication, assembly, building.... and they give the prototypes to us for testing

If you have a small team and you build a fairly simple robot, and fabricate and assemble the parts yourself, thats awesome

and if you have access to a state of the art automated machine shop, and you create drawings and put a block of aluminum in a CNC machine, and finished parts are in your 'in basket' the next morning, that is awesome too.

FIRST is not intended to be a crash course in engineering. Its intended to be a peek at the light that beams from the end of the tunnel.

In the end engineering is what happens between your ears, not what you build with your hands, not what a machine spits out.

Somebody has to put the robot together, and you learn alot about physics and mechanics and electronics by doing that, but dont confuse that with engineering. In the real world very few engineers spend any significant time on a lathe, drill press, welder, grinder, PCB pick and place machine, CNC machine, soldering...

in fact, if I spent a lot of time on the factory floor, soldering or machining parts, my manager would be upset "thats not what we pay engineers to do" - hand that off to a machinist or assembly person, and get back to design and development.

something else, it takes 4 or 5 years of college to become an entry level engineer. We cannot teach HS students to be engineers in 6 weeks, even if we do have pre-kickoff meetings. There are so many things that students would never be able to do, if we had to teach them first and then let them do it on their own.

Engineers have a lot of tricks up their sleeves. If your sponsor is a major engineering house, it would be a crime if they were not allowed to work their magic for your team, and let you see some of the high end stuff that is possible.

Re: engineer bots
 

Engineers are a great resource but I don't think they should be the ones 'on the front lines' building the robot. Sure they can help and offer their expertise, but they shouldn't be the ones making the final decisions. On our team, yah, we have engineers that help and offer their advice, but students make the final decisions.

The ultimate "test" is to watch at a competition. Go into the pits or watch when a robot breaks down and see who immediately works on it. We have seen some teams with adults working on it and fixing it and students sitting back doing nothing and I don't think that teams should operate like that. Our team is one of the FEW that doesn't have an adult as a coach. I think because students are making the final decisions, they don't want to be 'bossed around' by an adult. They would rather listen to a student their own age. I am wondering how everyone else feels about the adults as coaches situation?

Re: engineer bots
 

This has been discussed in other threads, please search :)

Re: engineer bots
 

To me this thread reveals why I always disliked those "popularity thread" that appear every year ("WHo has the best robot" , ect.). Not every team has the resources that other teams do so when they see Uber team X roll out thier super fabricated machine and run circles around every body else and get fawned over every second on Cheifdelphi while these other teams who worked just as hard on their robot struggle year in and year out to just survive often without fanfare or trophies and kindly phrases from FIRST veterans do not make them feel any better.
It would be nice if FIRST had everybody perform on a level playing field but that just isn't going to happen (FIRST just doesn't have the manpower to make sure all teams work within the realms of what is legal). It's like major league baseball. The Yankees have more money than everybody else that allows them to build a virtual all-star team while whole division have a smaller payroll than the team. But did the Yankees do wrong for doing what they do? It's not agianst the rules so it's not wrong.
What I offer to the teams that do not have the resources: keep on keeping on. The rewards await your efforts if you persevere. All we ask is you don't give up.

Re: engineer bots
 

We used to brag that our robot was 100% student built, but over the years what I've found to be the case is that isn't really what FIRST is looking for in this. The end goal I believe is to get high school students working side by side with industry professionals.

Re: engineer bots
 

couple things Dean has said in the past at the kickoff meetings:
__________________________________________________ _____________
"In a couple weeks you might start to feel you are involved in a robot building contest. Then you are in serious trouble!"

"The game is not fair. The competition is not fair. Its not meant to be fair."
__________________________________________________ _____________

The competition / game part of this program has never been intended to be a contest to see which highschool or sponsor team can build the best robot. Thats not what we are here for.

Re: engineer bots
 

so true, however there must be a balance!

Re: engineer bots
 

I have been reading through this thread and i finial decided to post.
My team MOE 365 has a very strong mentor support, We are very very very lucky to have mentors and parents support from many different industry's and fields, By having those mentors our students are able to see a glimpse into what kind of careers they might want to go into. Yes we are very lucky to have a great group of support.
Is our robot built by our mentors? NO even though we have a strong engineer base, our bot is designed, built and programed by students. Our mentors work with us to help us learn what we are doing. Our bot has always been student designed engineer refined, that means we design it and then guide us to what can and cant work, With out our great mentors I know that I would have never learned how to work on a drive train or pneumatics system. Working with them has been the best experience of my life.
It was said before that this is not a science fair, that means that kids can work with mentors to help them and that is what happens, they help them.
I do not see any problem with those teams that get help from or build/machine parts of the bot for them, as long as the students learn something. That is what FIRST is all about teaching Kids, about life and some science stuff to.
It is sad that some teams do not have any mentors beyond a parents or a teacher, but just remember that those people are still teaching you a lesion just like everyone else's mentors are.
I am sorry about the wording of this post, This topic was really hard for me to express my feelings in words, So I am going to end it here.

Re: engineer bots
 

I read a lot about people seeing teams that look like they were build by engineers. Go and talk to them, and you might be surprised by what you find out. Maybe not, but at least then you have better data on who built what then how the robot looks.

Be civil in all things and you will get far.

Wetzel

Re: engineer bots
 

It does make it all the better when the Red Sox win, though.

Re: engineer bots
 

Yeah but technically the Soxs spend just a little less than the Stankees.
But I do enjoy it when they win. ;)

Re: engineer bots
 

I've only skimmed this thread because there are alot of lengthy posts, and i just want to put my 2 cents in... maybe 3 cents.

I think whoever said it was about the inspiration is 100% correct. FIRST is meant to give a group of kids to work alongside with engineers, not nesecerrily to win. You want to come up with the best solution to the problem, and as in the real world, if you're coming up with a solution, you are pit up against people with more resources than you.

Our team for instance, both years, has had a very good mix of engineering and student support. This year, we lost all of our funding, so we had to work on a considerably smaller budget than we had last year, but we still, I think (we'll find out in 10 days), came up with a very good bot. Our engineers were there to teach us, and at the same time, we taught them. I think that working WITH the engineers is a huge part of the experience. I don't think students doing it all, or engineers doing it all is the answer, you have to be somewhere in the middle. I've learned an amazing ammount of things from my 2 mentors on the team (electrical/programming mentor and programming mentor), and I really have been inspired. And I think thats more what you need to get. A trophy is nice, going to nationals is nice, but in the end, it boils down to what you got out of it, did you get something from it... I know I did, and that to me, is worth getting myself beaten by a team who may have lost sight of that goal, who is just in it for the sake of winning. Because at the end of the day, I know that what we did was a huge accomplishment for a group of kids and engineers in 6 weeks, and I think that everyone should get that satisfaction, instead of focusing on the winning.

Re: engineer bots
 

All the points made about inspiration and assistance from mentors being important are certainly true.

However, having been a student and college mentor with three different teams with varying degrees of mentor involvement vs. student involvement when it comes to designing and building the robot, I've noticed that students learn the most when they are ones doing the designing and building. On team 53, the students are the ones coming up with designs, building the robot, doing the programming, and performing the administrative tasks. Of course there are parents and mentors for guidance and suggestions, but really the students are the ones getting it done, and it's really impressive. They have learned some of the basic fundamentals of engineering design, have some machining and technical experience, and most importantly have a realistic sense of the engineering process (i.e. oh my god, it doesn't work, what do I do now?!). These are all extremely helpful skills for college and working.

So if you are a powerhouse team and being inspired and learning about engineering, that's pretty cool. And if you're a small team where your students are doing most of the work but not necessarily winning competitions, you get your due when you head off to college or the workforce with skills that your peers may not have developed and experiences that your peers may not have had.

Either way, FIRST works. You just have to keep the big picture in mind.

Re: engineer bots
 

These threads always surface at this time of year, as dedicated students see the types of robots and teams they are up against. This discussion has been great in this thread, and I would like to add some brief additions.

1. Many people assume that "great looking 'bots" which perform great are all done by adults. While this does happen in FIRST at times, it is much rarer than you think. Many people have accused our team of doing this over the years, as this thread did. While it is true that we have very involved adults, we also have students design, build, debug, and fix the 'bot right along side of these professionals.

2. There are many college students who are acting as mentors who have had this same opinion of "it's not fair when adults design/build/etc.!!!" It takes them about a year or two of experiencing the uniqueness of FIRST before they realize the benefit of the adult mentors in this program.

Andy B.

Re: engineer bots
 

Memories.....I do remember when 85 would brag about being 100% student built. We would have problems, the engineers would feel like "what should we do?" and the kids didn't feel like they could compete. Then one day we asked the mentors "Do you build every part of your product? The answer was "No we can't if we want to be competitive". Talk about real world right in your face. Just like the real world is a balancing act so is FIRST robotics.

My best advise is to use your situation to make your team better. Team 85 is about 80% student built. For us that is a good balance. Maybe next year it will be 90% or 40%. Inspiration comes from the kids working with the mentors and from having a competitive robot.


Good luck to all of you.

Steve Yasick

Re: engineer bots
 

You'd better be very sure you know these machines were engineer designed and built. Because you could be hurting alot of peoples feelings. So machines that look this good could have been designed by the students and then final designed and engineered by the adults.

You have to watch the term engineer robots.
There are many things that go into a finished product.

1. design of the robots features
2. engineering running numbers for stress, strain, and weight.
3. making the prints for fabrication.
4. making the parts
5. assembly of the robot

If you are a team that does not make prints for fabrication or run calculations and just starts assembly and fabrication your missing the largest part of being an engineer.

Students can do a great job of designing features, making parts, and assembling parts together. But they really need to see the process of making correct ANSI or ISO standard prints. They also need to see the calculations that are run to predict material choice and size. The whole point of taking math classes that extent up to Calculus 5 is to predict and size parts before you make a giant mess. This is a Design Engineer's JOB. You can get a little bit out of making an "as built robot" but not as much as running through all the steps.

These steps are why team 173 Rage can build 2 robots in 6 weeks and include spare parts in the shipping crate. The engineers on rage smooth out the students designs. The students first make an as built machine from old parts to try different ideas". Then the engineers smooth out the design, engineering, and then produce documentation for fabrication. Parts of the machine are fabricated by the students i.e. cnc parts (sprockets, gripper arms,) others are sub'd out to sponsors. In the end students assemble the machine together with the engineers at the high school.

Re: engineer bots
 

The posts in this thread have meant a lot to me as a student team leader. I've noticed that this year, team 343 has had a LOT more student involvement than in the past. Despite having fewer students on the actual team itself, the level of their involvement was outstanding. So many factors of this years robot were designed, built and improved by Metal-In-Motion students.

A few years ago... I began to ponder across the meaning of FIRST. Did our team really have it? After winning the very first National Engineering Inspiration award I began to look deeper. I asked myself so many questions like "Are our engineers doing too much work on the robot?" (Nobody quickly answered my question with a NO.) "Are the students getting the true value of the educational aspect of FIRST" I analyzed my thoughts and feelings on many different parts of our team. "What did this all mean to me?" "Since I don't want to be an engineer, does that leave me at fault for not letting this experience change my mind?" ABSOLUTELY NOT... The memories of the team will forever be with me... The real life lessons I've gotten will continue to be a part of who I am, and who I'll become. "What is the significance in this post?" It's to understand that the importance of FIRST lies within the hands of the leaders of every team. As we go through life we understand that everyone is different. Therefore, every team has a different approach to designing a machine to perform the tasks we're given. Some teams emphasize the hands on approach of student participation. Other's stand by and watch as the engineers do the work. I've found over the past year that I've answered my own questions. "Absolutely not. The engineers don't do too much work on our robot." I've found that the most important thing is to have a good mixture of both student design and engineering inspiration. (honestly) I truly believe that our engineers have provided us the basis of what this FIRST is all about. That students and engineers can work TOGETHER as a team. I truly believe that students need to be taught how to do something before they participate in a long trial and error runoff. From AutodeskInventor creations to tapping parts... students can value the participation of engineers as long as it's in the right way. But yes... Life is unfair. FIRST is Life. After using the transitive property of algebra applied to simple basics. We understand that sometimes... FIRST can be unfair. But as long as YOU value the educational aspects.. I suppose that's the important thing... It all starts with one! :)

Re: engineer bots
 

I think this a great analogy. I would prefer to have students working along side me as we learn and master the art of robot electrical together. I learn from students and they learn from me. By our second regional or by nationals, they are able to perform every task needed except some weird problem that may pop up. Some years there is more student involvement and sometimes it goes the other way. Our students free us up so that we can help other teams at the events we attend. Our motto has been "If you come to play, we will assist in any way we can to make that happen." I am sure this is true of any of the teams in question, we are bound to help when we can.

And to add my twist to Ken's "build a man a fire"...Build a student a robot and it will keep him/her busy for a few days in the spring. Teach a student how to build(design, wire, program) a robot and they will stay away from home, use some really strange language and wear funny clothes the whole year long.

Re: engineer bots
 

Personally, if someone came up to me and said our teams robot was too well made to be made by us, i think it would be a complement. I know for a fact our robot was student made, i watched them make it! The only thing that really wasn't student done was welding some of the major frame components together, and that wasn't because they didn't want to try, but because our adviser didn't feel comfortable with any students or even himself welding the critical parts.

Also, dint think a team with a college student or students means they do all the work. My team mainly used me as a soundboard and another source of suggestions for designs. Design and engineering was a very collaborative processes between the mentors and the students. Any work i did to the robot was being an extra set of hands or doing stuff like helping drill holes or do other small stuff. Biggest single part i did on the whole bot was a 2 axis camera mount that no one had a clue on how to build. So please don't stereotype us college students as primary builders :D
Ive been dieing to do something in FIRST for about 7 years now, and this is the first chance ive gotten. So for as much thanks from my team for helping them, i thank them twice as much for giving me the chance!

Re: engineer bots
 

Personally, I don't really care how much student involvement is on another team; it's not my problem to tell other teams how to run.

However on a BCR note:

I am on a team that has about 10 students and 20 mentors. The balance may be pretty heavy, but all of the mentors are supplying inspiration, so it doesn't really matter. All mentors have different styles, so on different projects there are different styles. On design, there is not much student involvement in the actual pysical design, but all students have input on the conceptual design. If a student comes up with an idea, it will be heard; in fact our 6WD kitbot frame was mostly student designed. Actual building is probably 95% or so. Being on the team for my third year, I am noticing progression/inspiration in myself and others during this process. Programming is a bit mentor-heavy, unfortunately, but without them we'd probably have no code. Don't get me wrong, they are definately teaching the students, but some people learn faster than others. The concept for our autonomous (have tetra leaning on back of robot, have arm swing over the top, nudge that back under the center driver goal and then whack the hanging tetra) was from a student.

Overall, I like our balance. But heck, I wouldn't mind being on a 100% student built team. I also wouldn't mind being on a team with high engineer participation. As long as it gets across the message of FIRST, I could care less.

-Daniel

Re: engineer bots
 

I agree you guys had an amazing robot, but rookie all-star is not all about what you do on the field and this year it was won in the pits. I agree we did not perform that great on the field. We shipped out our robot with minimal driving time which was our rookie mistake. But to say we didn't build it is ubsurd. Team 1676's robot was completly student designed and built. The engineers just guided us along. I think you should rethink posting something like this before you get all the facts.

Re: engineer bots
 

I myself would have to take a neutral side in this discussion. I have participated in both atmospheres. My first year on team 703 there was a core of about 5 students and 2 mentors that built,wired,programmed,and drove the robot. It was a very tight nit group of individuals that worked together very well. In fact we placed 5th out of 75 teams at the canadian regional last year. Then there was this year when we took in team 902 that had been disbanded by its home school. They had a group of 8 engineers that came with them when they joined our team. At first I felt the same way that most of you feel. I didnt want any engineers telling me how to build our robot, but now i wouldnt have it any other way. Not that the Engineers were the sole designers of our robot, Bill had us helping him design components whenever possible. I along with the rest of our team has developed a great relationship with some of these guys that we were weary about to begin with. Some of them are just like us, Kids in grownups bodies just wanting to have fun (no offense Matt we wouldnt have it any other way). The point i am tring to make is that there are points to both sides of the story and what a team decides is up to them. They both have there strengths along with there weaknesses. But i do know one thing. We started FIRST to achieve a common goal and not only will we leave with more knowledge and wisdom, we will leave as friends and thats what really counts if you ask me. And one final thing i would like to thank all the mentors for teaching me so much. Thanks alot guys. :cool:

Re: engineer bots
 

personally i learned most in the area of teamwork because the mentors STAYED OUT to a large extent. In fact, i think they did a perfect job. They made sure we worked on the stuff we wernt so interested in. They made a few things, stuff that we had no idea about and could have never made (like a nifty design for our passive gripper). We decided to modify it quite a bit later, on our own and it worked out great. There certainly was a balance.

Re: engineer bots
 

I think 1676 made a very smart move. For their rookie year, they build their robot based on our 2004's robot because they saw it worked. It wouldn't matter if their robot was 100% engineer built as long as the kids on their team were getting inspired. I can tell you this team more than deserved the Rookie All Star. Go look at the website, their chairmans/rookie all star submission[Holy God its amazing], the character of the students on the team. They are an awesome team. Great job 1676.

-Bharat

Re: engineer bots
 

When I was on the Fairport team last year, we tried to show the students how to do everything. During the first few weeks we found we had to start all the tasks ourselves (the mentors) until the students could see how it was done. Then one by one we handed the tasks off, stepped in only when someone was stuck, and then only to get things going again.

I found this message I posted last year. I think it sums up my opinion on this matter perfectly:

Re: engineer bots
 

I once started a thread like this when i was a rookie. Since then i have relized many things about mentors and engineers. You may think that these bots are engineer bots but they are actually student bots. Students dream up the ideas for bots, it is than up to the mentors and engineers to make these dreams a reality. This is why it may look as if these bots are engineer bots but, they are actually a product of experienced students and hard working adult leaders. Don't worry your time will come when you have a "Super Bot" as you call them, which years of competition you gain experience to build a great bot. A great team you may want to look at and speak to are teams 135, 71, 48, 47, 45 and many more. Most teams will be glad to help you become competitive to, JUST ASK FOR HELP!

This is all i have to say, i am not trying to talk down to you, or scould you, just make you rethink your toughts