(13.02.002 .Net Sdk)
I’m encountering a bug which seems strange to me, and thought I’d stick it up here to see if anyone else has had a similar issue and how was it resolved:
I have a windows service that connects to a camera and captures images from a stream in a fairly typical way [timeout set to 200ms] when triggered from an external source:
StreamImage image = imageStream.WaitFor(cvbTimeout, out WaitStatus result)
This has been generally working fine, except I have recently started to notice that occasionally when I start the service, the driver gets loaded fine and everything appears to be set up and ready except that no images are ever captured (it is not a trigger issue, as this has been working reliably for years).
Once one of my machines encounters this error, it doesn’t go away until I manually open the CVB management console, grab a stream and capture an image. Once this has been performed, and I restart the service, images are then captured as normal.
Can anyone offer any insights into this behaviour? Why would attempts to capture images start timing out and then stop timing out once I manually take an image?