|
Re: How many days do your programmers get with a fully built robot before stop build
I can't speak for other years, but I think this year was the best year for the programming team (for multiple reasons).
We got a spare control system through FIRST Choice and Andymark, and let our programming team use those on a dummy board. They actually used the board from last year's robot to program it in Java (while we used the new one to program in LabView, the language we have used for multiple years). Once the robot was ready for the electrical components, we disassembled the Java board and decided to use Java for the robot. The LabView board was repurposed for Java, and the team kept working. Once the robot was completely finished (last weekend of build), they just needed to check some values for the potentiometer that was used for our arm. We didn't have anything too complex (like vision tracking), only the potentiometer. And they only needed to read the values on the smart dashboard while we were practicing driving to get their readings.
__________________
As a senior that will be leaving the team, I have to teach others how to:
1. Know the manual extremely well
2. Wire the robot
3. Organize the shop
4. Help people find parts when they need them
5. Find parts to order and give the detailed list to the coach in charge of buying the parts
6. Keep track of team updates, Q & A responses and FIRST blog posts
7. Be active on CD
8. Plan and execute drive team strategy
And more that won't fit on this list...
|