Camera Tracking

[Tanner]

Originally Posted by Greg McKaskle

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

Thought posting in the Labview forum would be a hint towards what I was using.

Er, I must be lost or confused. Probe / indicate what? I've got a graph on my Track Trailer.vi (with the PID loop) that displays my set point (0.5 the width of the image) and the process variable (x value from Image Processing.vi). When it runs, the graph clearly shows the process variable as a "square wave" - all square, not smooth like a Sine wave. The "smooth-ness" of the wave can be affected by the frame rate and other things from the image processing, but not by much.

So, I'm not sure what else there is to probe...

Thanks
-Tanner