[JABot67]

I guess I could post for my team, though I really don't know all the details. I'll answer what I can. Most of my answers will be quick.

Programming:

What language did they use?
LabVIEW at Kettering and MSC, C++ at Wayne State and the Championship.
That's right, we had two completely different, functional codes from different programming environments. We decided to try something different this year with such a huge programming team.

Threaded code or just poll in the teleop loop?
I have no idea what this means, though I wrote basically all of the LabVIEW code. Sorry...

Did they do something in autonomous? If so, what worked?
We had many autonomous modes. We have scored from all three zones, and have started out in all three zones in eliminations. It really helped out to have so many autonomous modes. There were major differences between the autonomous modes in C++ and in LabVIEW, but they were meant to do the same thing.

What problems did you encounter, if any, with WPILib?
No problems.

Did you download the sources and rebuild WPILib/CanJaguarLib?
No.

CAN or PWM control?
PWM control.

Did you use the Classmate for programming your robot or student/school supplied computers?
We used our own computers. Using the classmate would have been just terrible.

Robot Design:

NOTE: I was not involved with the robot build. I am a programmer, and definitely not an expert. I'll try to answer these questions based on what I know, which was gathered from working in the pits or with the practice robot.

What sensors were used?
Encoders on the left and right drive, and potentiometers on the kicker and the arm. One yaw rate gyro that was especially useful in auton. No limit switches. We had a camera that we never used.

Did you use the vision system?
No.

If so, what modifications did you have to make to the code?
N/A

What drive system? Wheels?
8 wheel tank, front and back four wheels were smaller and raised.

How many motors?
4 CIM Drive
2 FP motors for the kicker and arm
2 Window - one for the roller and the other for the shifter, to kick and to shift into arm mode.

What material was used for the frame (Aluminum, steel, unobtanium)?
Water-jetted sheet aluminum. Don't know the specs.

How did they control the ball?
Pincher, with a static bottom bar and a top roller attached to a belt that slips when a ball is being possessed, but still applies torque to the ball.

Energy storage for kicker (elastic, pneumatic, motor driven, etc.)?
Tempered garage door spring.

How did you cut your parts (water jet, LASER, mill, hand tools,etc.)?
Our frame is waterjetted.

Did you hang?
Yes.

If so, what wenching approach did you use?
We used four 200 pound gas struts, and a block and tackle. We wound up the mechanism before every match and used the stored energy to elevate the robot.

The Driver Station

Did you reprogram your dashboard code?
Yes. However, we never ended up using the new dashboard.

Did you use external controls beyond your joysticks?
No.

Any problems in getting the USB to behave?
Yes. Eventually we decided to plug our controllers directly into the Classmate, as there were enough USB ports to do so.

Did you use any unusual controls like WiiMotes, XBox controllers, etc.?
Well we have used only Logitech gamepads for the last couple years. No fancy controllers. We don't even use joysticks anymore.

Did you feel that the Classmate was fast enough?
We hated the Classmate. The one FIRST gave us decided to crash during two matches at Wayne State, disabling us for the rest of those matches. And the bootup time was way too slow.

Anything else?
We had a lot of problems this year. There were a whole lot of issues we had to face in order to come out on top. But those problem solving steps were part of what makes FIRST Robotics so fun.

Any techniques that you feel might be beneficial to others in the future?
Well we scouted a lot. Our scouting team is huge and that definitely impacted how we did at our competitions.

I'm sorry that my answers were so short, but hopefully this gives some insight into Team 67.