View Single Post
  #10   Spotlight this post!  
Unread 14-02-2014, 17:39
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,751
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: Compressor code kills our drive system

Hopefully you are just running interactively and not deployed. All you do is open the teleop subVI from the project or from the RobotMain block diagram. When the subVI is called, the arrow looks like the right sample. If not being called it looks like the left one. When called in a loop, it will flicker back and forth. Or if you probe a wire like the joystick output, it will show the values.

The dashboard shows joysticks and robot motor value on its Drive tab. The values are written in the teleop, so you will know it is running and whether it is updating the motors.

One nonSW thing to check is to see that all three LEDs are brightly lit on the digital breakout board. If not, the 12V power is likely missing. The device will power a few motors with the current from the digital cable, but will fail somewhat mysteriously as more things are connected.

Greg McKaskle
Attached Thumbnails
Click image for larger version

Name:	From Clipboard.png
Views:	9
Size:	8.2 KB
ID:	16234  
Reply With Quote