View Single Post
  #13   Spotlight this post!  
Unread 01-04-2015, 11:33
cjl2625's Avatar
cjl2625 cjl2625 is offline
apel py
AKA: Cory Lynch
FRC #2067 (Apple Pi)
Team Role: Programmer
 
Join Date: Jan 2013
Rookie Year: 2013
Location: Guilford, CT
Posts: 412
cjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to beholdcjl2625 is a splendid one to behold
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.
This is precisely what happens for us.
I don't think it's a brownout issue, because it happens with a fresh battery upon booting up.
__________________
Head Programmer / Driver
Reply With Quote