Motor declarations break analog module

[nathanww]

In which team 1678 continues our saga of stumbling across every frustrating bug that exists:

Today I finished tracking down an error that was causing the analog module on our robot to not function correctly(about 90% of the time when you booted the robot, the analog inputs would be unreadable and it would spew "invalid parameter" errors from low-level analog functions). After replacing the hardware(didn't help), testing with sample code(made the errors go away), cutting out various functions(didn't help), reimaging the cRIO(didn't help), and finally going through and commenting/uncommenting everything line-by-line, I discovered that the cause was actually the declarations of the speed controller classes(victors and jaguars) that we were using to control our kicker and climbing mechanisms.


I really have no idea how this could be causing low-level errors in the analog code, but tests confirmed that this is indeed the case. Even more bizzarrely, the RobotDrive class that we have configured for 4-motor tank drive doesn't interfere with the analog system at all!

Does anyone know what might be going on? Right now, we have to choose between using sensors and using motors.