Jump Start Build - Control System Startup Suggestions

[RyanN]

For everyone that doesn't know, my name is Ryan Nazaretian. I've been the lead programming mentor for Team Fusion 364 for the past 2 years. I've been involved with Team Fusion since 2003; all the way from their summer camp program in 7th grade, to being a mentor now. I'm going to Mississippi State University for Computer Engineering, and I'm a senior this year.

Team Combustion 1912 holds the annual Jump Start Build at Northshore High School on the first Saturday after Kickoff with the help of Team Chaos 1421, and Team Fusion 364.

For the past few years I have been going to help with the control system startup. This year, I want some feedback of some mentors, students, anyone involved with FIRST Robotics.

At competition, what are some things that you see that team poorly execute? Should they have put in a potentiometer to help with control? Are they failing inspections (control system specific)?

If you are attending Jump Start Building, what would you like me to cover? Do you want to use the compressor but don't know how? Would you like to control the position of an arm using some form of closed loop control? Otherwise, I'll go straight to the point:

1. Software Updates
2. Software Installation <- This first because it takes ssssssoooooo lllooonnnggg... We'll skip ahead while everyone installs the software.
3. System Integration - Putting it all together (hardware)
4. Dlink Router Setup (Firmware Update, IP Configuration)
5. Formatting your Compact RIO
6. Intro to Robot Framework - Making your first cRIO Program
7. Running your first cRIO program
8. 'Burning' your first cRIO Program

But yea, let me hear it! I'm excited!

[Alan Anderson]

What do I often see poorly executed? Wiring.

There's really only one way to connect power to everything and have it work properly. Apparently the power distribution diagram isn't obvious enough for some teams to get it right.

[RyanN]

Originally Posted by Alan Anderson

What do I often see poorly executed? Wiring.

There's really only one way to connect power to everything and have it work properly. Apparently the power distribution diagram isn't obvious enough for some teams to get it right.

Good one!

I take good wiring for granted with our team. Neatness, labeling, correct size, and make sure it goes to the correct place (Dlink to converter to boosted 12V, cRIO (8-slot & 4-slot) to the 24V output, camera to 5V output, 20A breakers for all control system components.

[Jimmy Nichols]

Is this the same as the RQBS?

[3132MentorMike]

Originally Posted by Alan Anderson

What do I often see poorly executed? Wiring.

There's really only one way to connect power to everything and have it work properly. Apparently the power distribution diagram isn't obvious enough for some teams to get it right.

Ryan - to go one step further, you should teach a proper technique on preparing the wires (Anderson's, spade connectors, etc.) as well as proper strain relief. A great mentor in NH on 2342, "Mr. T", teaches a technique (where applicable, depending on the connector) of crimp, solder, and shrink tube that I've never seen fail on robot in 5 years.

Also caution teams on long runs of unshielded PWM cables. A discussion on EMI/EMC/signal integrity is probably going to go over their heads, but "too long" needs to be something in their vocabulary.

[RyanN]

Originally Posted by Jimmy Nichols

Is this the same as the RQBS?

I believe it's very much the same. The goal is to have a running kitbot at the end of the day.