NavX causing robot code to reboot

[Poseidon5817]

We've had issues with a NullPointerException getting thrown for the NavX not being detected when the robot code loads. Restarting the code or roborio usually fixes it.

[slibert]

Originally Posted by Poseidon5817

We've had issues with a NullPointerException getting thrown for the NavX not being detected when the robot code loads. Restarting the code or roborio usually fixes it.

Please post the stack trace for the exception next time you encounter it.

[Ginger Power]

We have had somewhat related problems with our NavX as well. We've been battling a communication issue for a really long time and we just figured it out.

We had the NavX in our C++ code and we didn't have it on our practice bot. Because of this, we could only connect to our Roborio 1 time. After the power was shut off and turned back on we could no longer connect. The only way we could connect was by reimaging the Roborio. After reimaging we could connect 1 more time.

The people on our team who actually know the details behind the problem are contacting NI and FIRST and making them aware of the problem. I believe they will also be posting their findings to CD.

[Jonathan L.]

In 2015 we used the nav6 (predecessor of the navX). It used a serial connection to the roboRIO. We had issues with the roboRIO not working (not connecting or something like that). It seemed like we had to re-install the roboRIO firmware and re-image. Removing the nav6 from the robot fixed the issue. Anyway, we found that unchecking the "Console Out" checkbox in the roboRIO imaging tool allowed us to use the nav6 normally.