NavX causing robot code to reboot

[tr6scott]

https://www.chiefdelphi.com/forums/s...d.php?t=154205

We are a labview team, we have also had strange issues with NAVX this year...

[slibert]

Originally Posted by tr6scott

https://www.chiefdelphi.com/forums/s...d.php?t=154205

We are a labview team, we have also had strange issues with NAVX this year...

Hmmm, missed that thread. So I'm curious also when your robot application is initializing the MXP IO (if any), and if that might be contributing to some sort of collision. The best hypothesis I can come up with is a race condition when allocating the MXP IO resources that in turn causes the allocation of SPI and other comm resources to fail (except the first time after loading the app after reimaging). Does this seem plausible to you?

[TylerHarmon]

If your code is crashing when you try to initialize the NavX, it probably is not properly communicating with the roboRIO. If you try to read from it before it is booted, you will also get a Null Pointer Exception. Just check if the value you want from the NavX != null before you try to do anything with it.

Most likely from what I have read here, you are not properly communicating with the NavX on an electrical side, or it is wired properly but you are trying to communicate with the wrong protocol.

[torzewsk]

We found it. PEBKAC
We had an obsolete version of AHRS.h in our include path, and it was not the right size. The adjacent memory allocation and the navx were wiping each other out. Thank you for your help, it got us thinking.

Tim T.