Thread: LabVIEW dashboard works in the pits but not on the field
View Single Post
  #1   Spotlight this post!  
Unread 22-03-2015, 21:57
forbes's Avatar
forbes forbes is offline
Software developer
AKA: Evan Forbes
FRC #3507 (Ubotics), 694 (StuyPulse)
Team Role: Mentor
  
Join Date: Apr 2013
Rookie Year: 2012
Location: New York City
Posts: 154
forbes is a splendid one to beholdforbes is a splendid one to beholdforbes is a splendid one to beholdforbes is a splendid one to beholdforbes is a splendid one to beholdforbes is a splendid one to beholdforbes is a splendid one to beholdforbes is a splendid one to behold
LabVIEW dashboard works in the pits but not on the field
At the Central Illinois Regional my team ran into a problem that put our tote manipulator out of order for about 4 matches.

We read values from a modified version of the LabVIEW dashboard to be able to update parameters on the fly (such as our elevator speed). This worked fine during the build season and worked when tethered in the pit. It also worked in the first 2 matches, but then in subsequent matches we were not receiving some values from the dashboard, causing two of our mechanisms to completely stop working. (I'm not sure if we were getting any data at all, but we were at least not getting two boolean arrays)

We worked with a CSA, but were unable to identify the root cause for several matches. Once we figured out it was the dashboard, we just scrapped using it completely and hard coded all of our values.

I didn't get to talk to the CSA after we figured it out to discuss why this might be happening.

Any ideas?