Navx Mxp no longer working

[brubakbd]

I'll definitely check that tomorrow.

[AustinShalit]

I sent Kauailabs an email and got this response:

Once the RoboRIO firmware got updated to the 2016 firmware version, the USB connectivity to the navX-MXP stopped working. We still don't have any word on a resolution to this issue, and unfortunately I've been informed that this isn't a high priority issue from the WPI/National Instruments perspective (since the serial over USB support is not 'official').

For that reason, we're encouraging teams to use the SPI interface, or if that isn't feasible to use the I2C or TTL UART interfaces.

We do still recommend that the USB cable between the RoboRIO and the navX-MXP be left connected, because this will ensure that the navX-MXP power is maintained even if a RoboRIO stage 2 brownout occurs. More info on that is discussed in item #2 in the navX-MXP Best Practices page.

- scott

[brubakbd]

Alright, we got it working. Turns out it was something stupid we did. We were using a setref vi in begin and get ref where we wanted to use it. Turns out you should just alter begin and where you want to use it and make the output of the open vi an output of begin and an input of the vi you want to use it in.

[Alan Anderson]

Modifying the project framework (e.g. by adding an output to Begin) is usually a bad idea. Using the Refnum Set/Get functions is preferred.

The -44007 error you were getting suggests that you had spelled the name of your NavX reference differently in the two places.

[MrRoboSteve]

It's too bad about the USB not working. We used that to get the navX into a good location on the robot, where we could not fit the roboRIO.