No Mentors..

[wendymom]

Also....our programming genius Skyler has been holding Skype sessions with our programmers. I'm sure if you wanted to join in he would be happy to fix it so you can. Just PM me for more info.

I bet you could set up the same kind of arrangement with Electrical and Mechanical people.

[Andrew Schreiber]

Originally Posted by JohnBoucher

There are many retired engineers out there, you just need to find them and not scare them off.
Letters to the editor for your local newspaper and contacting tv stations explaining your situation should get you some help. It worked for us.
You will need to keep it simple so you don't overwhelm the people helping you. FIRST , the FIRST engineering staff and Andymark will supply you with enough parts to make a running robot in the KOP. They do a great job with the rookie kit.

They don't always have to be engineers either. This year the acquisition I am most excited about is a retired millwright who loves to tinker.

I also bolded/underlined a section that always needs more emphasis. FRC is a competition. Don't forget this and build something because it will be cool, build something that is competitive. There is no shame in using the KOP stuff, it is there to be used.

[EricH]

If worse comes to worse and no local mentors can be found, by any or all of the methods suggested above, CD is a good place to ask some of those questions. Having access to several thousand mentors in one place, even if you aren't physically there, is a whole lot better than having zero mentors.

[synth3tk]

Originally Posted by wendymom

Also....our programming genius Skyler has been holding Skype sessions with our programmers. I'm sure if you wanted to join in he would be happy to fix it so you can. Just PM me for more info.

I bet you could set up the same kind of arrangement with Electrical and Mechanical people.

You just reminded me of something that the original poster should check into:
http://chiefdelphi.com/forums/showthread.php?t=87994

A network of FRC teams on Skype. So far there are 15 or so contacts on the list. And with the latest Skype, video conferencing is even possible.

[IndySam]

The one thing you need to have is somebody in charge. It's best if that is an adult but not mandatory.

Pure democracies just don't work well in the engineering process. Someone needs to have the final authority to make decisions. Somebody has to have as their #1 priority focus over the overall robot project or the project will be doomed for failure.

[Chris is me]

Originally Posted by maltz1881

1322 has never had an engineer and has won "Best in Engineering" a couple of times.

Best In Engineering isn't an award...

[dtengineering]

In our first year I was the only adult on the team of 12 students. We had NEVER seen an FRC event, had NEVER seen an FRC robot in person, and had only met one person with FRC experience, once, for an hour, the previous spring (before we even knew were were going to enter FRC.)

And we... well... we did about as well as you'd expect. We got our butts kicked! At least for the first day or so until we figured out what was going on. We were doing okay come Saturday, and then went on to win at least one FRC every award each year for the next six years. So don't panic. Where you are going is FAR more important than where you are right now.

Based on that experience, here is my advice:

1) Build simple. There are usually multiple ways to score. Pick the easiest one, and do it as well as you can.

2) Follow the instructions and build the kitbot as early as you can. You'll be given the parts and instructions to build a decent drivetrain. Use them. You can get fancy next year.

3) Don't be afraid to use wood. Baltic birch plywood is a wonderful building material.

4) Don't assume that engineers have some special knowledge that makes them better at building an FRC robot. If you've got a shop teacher at your school (maybe you ARE the shop teacher...) then you've got a technical expert. Maybe not an expert at labview programming, but surely there is a techno-geeky kid or two in your school who can follow some instructions and get the machine up and running. Our first programmer figured out how to write autonomous code on the plane to Toronto for our first tournament....

5) Machinists, millwrights, welders, mechanics, and any number of tradespeople can offer practical advice and often assitance beyond what you might get from many deskbound engineers. FRC is a hands on game... find some hands on people.

6) But whoever you get involved, don't let them talk you in to building a complex machine. Focus on sturdy, reliable and simple... start early, work hard and leave time to test.

And whatever you do... READ the RULE BOOK. ALL of it! Especially the tech inspection parts that give size and weight limits.... build under size and under weight.

Oh... and have fun. You'd be surpised how far you get by working hard and having fun.

Jason

[thefro526]

Originally Posted by Chris is me

Best In Engineering isn't an award...

Maybe "Engineering Excellence" is what they were referring to...?

Anyway, 816 has never had a true "Engineering" Mentor for as long as I've been on the team. (Since Fall of 2005) We've made due with some helpful parents, some brilliant students, and the right attitude. You don't NEED an Engineer or an army of them, it's just helpful if you do.

Come to think of it, this year we don't have any parents returning, so most of the Technical Mentoring is going to be Done by myself and another alumni.

[jspatz1]

As already mentioned, I definitely encourage you to join the new video collaboration network FRSee. This will put many experienced teams and mentors at your disposal to contact at any time. We anticipate a large influx of teams joining on and after kick-off day. Everything you need to know to get signed up is at the FRSee Website.

Also as Chris Fultz mentioned, be sure to sign up here with the new Virtual Technical Advisor program. Its purpose is to help teams in exactly your situation, by connecting you with technical mentors that can help you via phone and internet communication.

[raytexans]

We are working hard to make it happen here.

No rock is being left unturned and our partnership with our outside entities are being strengthened. The students learning successfully is my main goal and they are already excited and learning.

Every piece of advice and assistance that everyone has posted is very appreciated. The team is busy reading, researching, and talking up the program more than I thought possible at such an early stage. I had a parent call me tonight asking questions, but let me know her son hasn't stopped talking about robotics this week.

What our team hopes to inspire is the ideal that no matter what we can make it happen. Everything is a learning opportunity and as things happen they are accessing the changing situations, evaluating solutions, and solving problems.

Looking forward to kick off!

[rsisk]

Originally Posted by raytexans

our team hopes to inspire is the ideal that no matter what we can make it happen. Everything is a learning opportunity and as things happen they are accessing the changing situations, evaluating solutions, and solving problems.

I'm here to report that team 3778 is well on their way to becoming a FIRST Robotics team, congratulations.

[Josh Fox]

I'm going to echo Richard here.

My hat is off to you, because despite having never officially competed or having involvement before, you truly seem get what FIRST is really all about. Keep this mentality and set of ideals with you throughout the season and no matter what it will have been a success.

Good luck to you and your team in the rapidly approaching season.

[Carol]

Originally Posted by IndySam

The one thing you need to have is somebody in charge. It's best if that is an adult but not mandatory.

Pure democracies just don't work well in the engineering process. Someone needs to have the final authority to make decisions. Somebody has to have as their #1 priority focus over the overall robot project or the project will be doomed for failure.

I agree with this. Depending on the dynamics of your team, you need someone with authority to handle disputes. And don't forget the NEMO aspects of the team - an adult to handle (or at least oversee) the money, travel, paperwork., etc. can free up the students for robot building. Not that the students can't handle the NEMO aspects - this can be a good learning experience - but it is easy to miss details that can cause a lot of problems down the road.