View Single Post
  #2   Spotlight this post!  
Unread 04-03-2014, 06:34
Greg McKaskle Greg McKaskle is offline
Registered User
FRC #2468 (Team NI & Appreciate)
 
Join Date: Apr 2008
Rookie Year: 2008
Location: Austin, TX
Posts: 4,748
Greg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond reputeGreg McKaskle has a reputation beyond repute
Re: Dashboard display

Have you caused it to crash doing this before?

My suggestion is that you place the indicator in one of the binding tabs. The Operation and Auto tabs will automatically bind anything placed into them to a SD variable of the same name.

The next step is to publish the spike value on the robot using the same name. So find a place on the robot that makes sense, perhaps periodic tasks, and call the GetEnabledState VI. Write that value to the SD variable. That function tells you whether the compressor control loop is telling the spike to run the compressor. If it is different than what is actually happening on the robot, you may want to check the electrical connections, LEDs, make sure the robot is enabled, etc.

Greg McKaskle
Reply With Quote