For a vision application in an industrial setting we are using USB3 cameras via CVB. This works as intended however because the PCs aren’t properly shut down by the larger machine (it just cuts the power) and the application has the cameras locked at that time they stay locked when the PCs start up.
As a workaround, deleting the %CVBDATA%\Genicam folder and starting the GenICam Browser application makes the cameras available again but this requires remotely logging in to the PC which is undesirable.
I’ve automated the part of deleting the %CVBDATA%\Genicam folder but after this the camera is discovered with access status NOACCESS which means loading the camera fails (LoadImageFileW using the camera’s access token as found via discovery (DoDiscoverW and DoEntryGetInfoW). Discovery does find the camera but indicates its access status is NOACCESS.
Apparently the GenICam browser application has a means of ‘resetting’ the camera which makes access possible. When I start the GenICam Browser it also creates the %CVBDATA%\Genicam folder and subfolders\files (starting my application and running discovery does not).
Obviously the GenICam browser application does something during it’s initialization which unblocks the camera which my own application does not but I have not been able to find what that is (neither on this forum nor in the sample applications).
Has anyone experienced this problem and found a non-manual way to solve it?