@kiroture wrote:
Also, new problem that might be related?
I have on my front panel a button that opens a second VI in which I can view what the camera sees. I used exactly the same code as for the scan but without processing. It works very well. However, when I stop this VI (with a stop button, so without stopping the main VI), then I cannot make a scan without getting a timeout from the camera. What surprises me is that the contrary works: doing a scan then viewing what the camera sees.
The second VI in which I can view what the camera sees has "camera session" and "camera error" as input and as output. Can there be a problem if I use the same camera session many times in different VIs? Or what can be the problem?
Thanks again.
Without seeing your code it is hard to know for sure. I suspect all your issues stem from using the Ring acquistion model without properly releasing the images after you process each one, causing the acquisition to stall. I suggest you simplify things:
- If you're going to use the Ring VIs, do your processing in the same loop as the Extract Image call, and make the Extract VI always release pevious images.
- Or instead, just use the simpler Grab VIs which copy data out of the acquisition buffer instead, and thus don't have any way to stall the acqusition
- Don't try to use a producer/consumer model unless there is some benefit to your application (which I haven't seen in the code you have shown)
