Thread: ANNOUNCING: navX MXP Robotics Navigation Sensor
View Single Post
  #232   Spotlight this post!  
Unread 01-04-2015, 11:26
marshall's Avatar
marshall marshall is offline
My pants are louder than yours.
FRC #0900 (The Zebracorns)
Team Role: Mentor
  
Join Date: Jan 2012
Rookie Year: 2003
Location: North Carolina
Posts: 1,256
marshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond reputemarshall has a reputation beyond repute
Re: ANNOUNCING: navX MXP Robotics Navigation Sensor
Quote:
Originally Posted by randantor View Post
We are also having issues with reading the NavX at times. We are using LabVIEW with the SPI bus. Sometimes the data is all 0 with the 'Data Valid' output false. In every case, restarting the robot code from the driver station gets it working again. Before, I had only seen it on our comepetition robot while connected to the FMS, and I thought it was related to the clock issue mentioned earlier, but yesterday it happened twice on the practice bot, which has a diffferent roborio and NavX board. I would say it happens about 1 in every 10-12 robot starts.

I haven't tried I2C or UART, but we may switch protocols for Lone Star and see what happens.
Check your battery voltage levels. This sounds like a brownout related issue. What version of the firmware are you running on the NavX?
Reply With Quote