View Single Post
  #7   Spotlight this post!  
Unread 18-02-2010, 06:46
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: Camera Issues (we have tried practically everything!)

The default code is always looking for the target, in all modes. If you don't take advantage of this, you can turn off the button that enables the vision processing. You can also do this programmatically by turning off the global for different game modes, based on a button, etc.

If you want to process for targets, it definitely takes CPU, but shouldn't really affect the way the robot drives. Have you moved the vision code into teleop or something?

Greg McKaskle
Reply With Quote