Thread: Camera Tracking
View Single Post
  #2   Spotlight this post!  
Unread 31-01-2009, 18:38
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 Tracking

You don't mention which dev environment, but some of my comment will be similar either way.

If using LV, beware that open panels add overhead. Great for debugging, but that is the price you pay.

Probe the output from the camera, and within the PID area where you are consuming that data and acting on it, probe again.

The better type of probe would be a chart so that you have history and can see how much of a lag is there or if you are indeed skipping values.

If you can't get them probed, just add indicators here and there.

If not using LV, trace values in C by dumping to an array of printing to a file.

Again, what you are looking for is the way the values interleave, and whether they lag.

Greg McKaskle
Reply With Quote