[Steve Warner]

The acquisition of the image is done in a seperate task just like the demo code. The code that searches for targets is also very much like the demo code but was not running. If you are talking about searching for targets in a separate task, that would be great. Is there any example code available?

The slow down I was referring to is both downloading code to the cRIO and the execution of the code. It is what Greg was writing about in a previous reply where loop times can get to be around 100ms. There are no other tasks running that I can think of. The gyro if that's considered a task.

We did some testing, which happened to be in a small room, to see how the camera setup affected loop speed and found it had a big effect. Last night I was in a much bigger room and, initially when the system was running normally, the camera was pointed toward some flourescent lights. After I repositioned the camera the image on the dashboard was much dimmer. Like I said my code change was very small and the only thing I can think of that would be chewing up CPU time is the camera task. Again, the target code was not running.

Steve