View Single Post
  #147   Spotlight this post!  
Unread 16-02-2015, 18:28
slibert slibert is offline
Software Mentor
AKA: Scott Libert
FRC #2465 (Kauaibots)
Team Role: Mentor
 
Join Date: Oct 2011
Rookie Year: 2005
Location: Kauai, Hawaii
Posts: 359
slibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud ofslibert has much to be proud of
Re: ANNOUNCING: navX MXP Robotics Navigation Sensor

Quote:
Originally Posted by Thad House View Post
Powercycling the RoboRIO, or hitting the Restart Robot Code button on the DS does make it work again. Also, the DS reports that there is no valid device at the address when this happens. Resetting just the Gyro board does not change anything.

Also, we are using the newest firmware on the newest firmware on both devices. And there are no other devices on the busses. This error happens on both SPI and I2C.
After doing some checking, another navX MXP customer has indicated they've seen a similar issue w/SPI, and their thinking is there's an issue in the LabView WPI Library component. This seems plausible, since the navX MXP is a slave on both buses, and resetting the navX MXP(which completely releases the busses) doesn't clear the issue. But it's a bit early in the investigation process to tell.

We've setup a LabView SPI longevity test here at Kauai Labs, and will try to reproduce the issue - and if we can reproduce it, we'll gather as much info as we can and inform National Instruments of the details - and post what we know on this thread.

Until we find out where the problem lies and how to resolve it, you might consider using the TTL UART or USB interfaces instead.
Reply With Quote