View Single Post
  #3   Spotlight this post!  
Unread 22-02-2011, 13:49
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: Help altering camera video in Driver Station.

What the default code has done for the last couple years was to send the target info back numerically, and them overlay that on top of the original image that is sent to the dashboard. This is lightweight because it doesn't have to compress the image, and typically looks even better than the masked images because you have context to help identify what the camera is processing.

You can look at the game code for 2009, 2008, or you can even take the image from the robot and reprocess it on the laptop in the dashboard. Applying the same processing generally gives the same results, and your DS/Dashboard computer typically has plenty of CPU. So if using the LV dashboard, copy your robot vision VIs to the dashboard, reprocess, and display.

Greg McKaskle

Last edited by Greg McKaskle : 22-02-2011 at 13:49. Reason: spelling
Reply With Quote