Quote:
Originally Posted by Thad House
Has anybody had issues with their NavX's freezing the SPI and I2C Busses? We have been running it for a few days, and occasionally all reports will freeze and report nothing. Resetting the board does not fix this. The only fix is to reload the code on the roborio, which returns it to working condition. Has anybody else seen this yet? We are using LabVIEW.
|
Here at Kauailabs, we haven't heard of this issue before.
It's odd is that resetting the navX MXP doesn't clear the error, as this will reset all the navX MXP I2C/SPI circuitry. And from your description, it sounds like resetting/power-cycling the RoboRio doesn't clear the condition either, right? That's a very odd failure mode, indeed.
Here are a few questions that will hopefully lead closer to a diagnosis and solution:
Q1: When you said the only way to clear it is to "reload the code on the roborio", do you mean re-loading your robot application, or do you mean re-imaging the RoboRio?
Q2: Are you using the latest RoboRio firmware? There was apparently a I2C-related fix recently, and that the latest image v. is FRC_roboRIO_2015_v23 and the latest FPGA version is 2.1.0f3.
Q3: To help us reproduce what you're seeing, can you also please let us know more about your configuration? Specifically, are you using the I2C/SPI busses for any other communications to other devcies [we've heard of trouble communicating w/the LIDAR lite simultaneous w/other I2C devices, for instance], and which of the I2C/SPI interfaces are you currently using to communicate w/the navX MXP [did it fail on both the same way?]