[Ivan Helmrich]

The problems I had with the vision code was frame rate and repeatable performance. Sometimes one color would be picked up, sometimes both. I tried the various changes in values that were suggested in a couple of threads here on CD but never got anything stable enough to rely on.

To be honest, we ended up bailing on trying to use vision for any automation about half way through the build. There were other, non-control issues that needed more attention. I had followed a couple of discussions on the camera but I couldn't dedicate the time to try all of the suggestions. Part of the reason for my original question was that I couldn't find anything in the LV implementation that that would have lead me to some of the methods people seemed to be talking about and so assumed, apparently wrongly, that the C++ code or perhaps comments was more descriptive of the process, less black box like, and that was part of the success some were having.

I was looking for a frame rate somewhere in the 20 fps range. I don't think we got out of single digits. The things I remember reading that should have helped are:
More light
Lower resolution
Turning off some things in the 2 color vi.
There was also some LV specific issue where the code would only process every other frame, I forget the specifics.

The purpose of the thread was to ask the question. If it will be instructive for many of us to change it to a discussion of how to get good camera performance, great. Since many teams are probably starting back up with the new school year, perhaps it is a good time to do this.

So, what really has to change in the 2 color demo to get the frame rate up? Once I can get that working, then I'll work on the reliability.

Thanks,

Ivan