ANNOUNCING: navX MXP Robotics Navigation Sensor

[slibert]

Originally Posted by Thad House

I know ours is 1.0.482, because I2C and SPI didnt work at all in the version that was preloaded, and looking at the flash drive we used to update it was 1.0.482. So at least on our end I don't think thats the issue. But I will double check.

And just to be clear, our issues over the past weekend were all seen on SPI. If it matters, we have the Update rate set to 60hz, The read is getting called once in the teleop loop, which is running every 20ms, and once in periodic tasks in a 20ms loop.

Thanks for clarifying, the details help; we've restarted the SPI longevity and brownout tests at 60Hz. They've been running for an hour now with no interruption, but it's a 24 hour test cycle.

Since you haven't sent any logs, I trust you've reviewed this and ruled out any other systemic issues including brownouts, Roborio CPU usage, loss of communication w/driver station, etc..

One other thing to check would be to look for any shorting between any of the pins on the navX MXP SPI connector header. These pins are electrically connected to the same MXP SPI bus pins used to communicate between the RoboRio and the navX MXP. If anything shorts the CS, SCK, MISO or MOSI pins (e.g., "swarf", or bent pins), that could cause bus communication failures. One other team encountered an issue where the Digital I/O pins on the navX MXP pin were accidentally shorted together (the pins were bent), so it's feasible this could be going on in your case.