CRIO ghosting

[Thad House]

Yesterday and today, the cRIO on our robot was acting very strangely. Last night, we plugged in to pressurize our air, and the robot automatically enabled itself. Which was really odd, and I thought should never happen.

Then in our match after that happened, Our auto did not act how it should have. It instantly started running our catapult and not responding to our limit switch that stops it. It was like it started running a different part of the code. When looking though our error logs for this match, normally the catapult motor sends MotorSafety errors to the driver station when it is running the loop correctly. In that match, it did not, and sent no errors at all to the driver station, not even the ping status ones that usually show up. So we re imaged the cRIO and hoped that worked.

It worked through most of today, but then it happened again. As soon as auto started the code started not responding correctly to the inputs. Because this was in the finals, we didnt have time to reflash, but we were able to get it to work correctly by entering teleop before connecting to the field, and not reboot the robot between doing this.

The same code worked great on our practice bot, and for the entire competition last time, so its really weird why it would do this. it just seemed really odd, and was wondering if anybody had any suggestions on what would cause something like this to happen?