NavX Error

[protectvariable]

Our team has recently been using a NavX-MXP Robotics Navigation Sensor by kauai labs. After using it for a bit we noticed that instantiating the sensor and reseting yaw, (see below picture) then using the reference in periodic tasks yielded an error like, "This SPI port is already in use", in the driverStation console. When we removed the yaw reset it worked fine. Any reasons to why this may be?

[Caboose]

Originally Posted by protectvariable

Our team has recently been using a NavX-MXP Robotics Navigation Sensor by kauai labs. After using it for a bit we noticed that instantiating the sensor and reseting yaw, (see below picture) then using the reference in periodic tasks yielded an error like, "This SPI port is already in use", in the driverStation console. When we removed the yaw reset it worked fine. Any reasons to why this may be?

Hmm...this is odd. I'll look at it tomorrow.

[Greg McKaskle]

I made a change to Open to register the VI refnum and our crashing issue is resolved. If anyone else using LV and navX has an every-other-time crash during development, there should be a fix up shortly, and I could tell you the edit to make if need be.

Greg McKaskle

[tr6scott]

Greg,

can you send or post the fix, we were attributing this every other crash to mDNS... we are using the navx too.

PM here is fine.
Thanks.

[Caboose]

I will be posting a fix for this error tonight.

[Caboose]

Updated Library. This should fix the mentioned issue by OP and the later mentioned issue by Greg.
https://github.com/FRC900/navX-MXP-L...s/tag/v2.0.5.0

[Greg McKaskle]

We verified the fix. Thanks for pushing the update.

Greg McKaskle

[Caboose]

Originally Posted by Greg McKaskle

We verified the fix. Thanks for pushing the update.

Greg McKaskle

Thank you for help with the fix.

[tr6scott]

Thank You!
No more every other crashes yesterday... great time saver.