Quote:
Originally Posted by swaglord2000
We actually found our issue! The modules on the cRIO were opposite what they needed to be so when we put them in the right order we were able to get a response.
|
Did the imaging tool indicate that they were in the correct location before fixing it, though? My team's off-season robot is having unexplainable issues similar to the ones mentioned here in this thread, except the robot shows absolutely no indication of functionality other than printing button states (not axis states) from the controller to the DriverStation. The imaging tool says that all of the modules are green (in the correct location, I assume), and reformatting / re-imaging it doesn't help in the slightest. We've reduced our code down to the absolute minimum, but nothing has worked...