Thread: ANNOUNCING: navX MXP Robotics Navigation Sensor
View Single Post
  #148   Spotlight this post!  
Unread 16-02-2015, 19:32
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 slibert View Post
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.
Follow-up questions: What update rate (in Hz) are you using w/the navX MXP - this'll help make sure our testing here is as close as possible to your situation. Also, what is your overall CPU % (average) when running your robot software?
Reply With Quote