[~Cory~]

I was in your position last year. I decided to do a "mini" build season with an old robot. I gave myself 6 weeks to program a crab drive robot from scratch. From their I learned some of my weaknesses and fixed them before this years build season.

I also strongly recommend doing a complete (with notes) read through of WPIlib documentation and examples. It will help you know what is there and the library in its entirety rather than the snippets you need and use.

Another recommendation is understand to a point that you could teach the following to a new student: (I hadn't) The cRIO and how it works, Controller Area Networks, PID loops, Traction Controll, I2C, TCP/IP, and traction controll. This is important because you will have to explain things to the mechanical sub teams if something doesnt work, or you need it a part of the robot physically changed.

My last and final recommendation is tell your team the position you are in. You need to make it known that you need AT LEAST A WEEK of debugging time with the robot. The robot was put together and I was left with three days to do all of the testing and autonomous.