I’ve a very similar problem to this one:
However, since the other topic has been closed in between, and I’m using a much newer Version: 18.104.22.168.
So, just as in the other case, the grabbing is active (with the RingBuffer active - if that makes any difference), but when I try to make a Device Discovery again:
Driver.DeviceDiscovery.Flags.IgnoreVins | Driver.DeviceDiscovery.Flags.IgnoreAccessStatus,
out SharedATList deviceList);
System.Runtime.InteropServices.SEHException: 'External component has thrown an exception.'
at Stemmer.Cvb.DriverLib.DODiscover(String seed, Int64 flags, Int64 reserved, IntPtr& list, IntPtr timeout)
at Cvb.Driver.DeviceDiscovery.Discover(String seed, Flags flags, Int64 reserved, Int32 timeoutMs, SharedATList& list)
at Cvb.Driver.DeviceDiscovery.Discover(Flags flags, SharedATList& list)
I’ve connected to the active camera from an Access Token of a previous discovery.
I’ve two (Allied Vision GT1930L) cameras connected to my computer using a switch.
It doesn’t make any difference, whether I dispose the ATList from the previous discovery, or don’t. (I’ve tried not to dispose it - for just in case)
The acquisition runs on also on an error.
If the acqusition is stopped before the discovery and then restarted, there is no problem.
Is this a bug, or per design so?
Thank you for your help!