View Single Post
  #2   Spotlight this post!  
Unread 16-01-2017, 12:29
aeastet aeastet is offline
Programming Mentor
AKA: Tim Easterling
FRC #6043 (Allegan Tigers Robotics)
Team Role: Coach
 
Join Date: Jan 2015
Rookie Year: 2011
Location: Holland, MI
Posts: 130
aeastet is an unknown quantity at this point
Re: Nav-X error - Cant get readings

It looks like you are getting CRC errors. I think the CRC errors are a red herring.

The clue here is that per your description the two green LEDs (S1 and S2) are not solid on (after the first second of startup).

The secondary clue is that I believe you are getting no data at all - a permanent failure. The CRC timing issue is a sporadic failure, not a permanent failure.

With a permanent failure (in which case the S1/S2 green leds are not both lit during normal operation), there will be no messages sent by the navX-MXP because it can't talk to the onboard MPU-9250 at all. And that means there's likely no response from the navX at all when an SPI request occurs. Which of course will be interpreted as a CRC error.

What you need to do is run the Factory Test Procedure (http://www.pdocs.kauailabs.com/navx-...est-procedure/. In particular, you need to confirm that the two green S1/S2 leds are working properly.

The other validation to perform is whether the navXUI (connected via USB to a PC) works. If the two green S1/S2 leds don't work, navXUI won't work either. At that point, we'll have confirmation of the problem.

It's possible something went south during the firmware update and you need to reattempt it. This can occur if the hex file is corrupt, or if the transmission of the complete hex file is interrupted during the firmwmare update process.

If after reflashing the firmware again the problem still persists, you should contact support@kauailabs.com for a replacement.

Thank you,

Tim

Last edited by aeastet : 17-01-2017 at 08:17. Reason: Better answer to the problem
Reply With Quote