The TwoCameras.VI was created to simulate the use case of the two USB3 cameras I am using in my application. After anywhere from 500 to 5000 cycles I receive the following error for either one of my cameras:
-1074360304: Unable to set attribute.
Upon restarting my application in hopes to restore the camera session, I receive an error when trying to connect to the camera that previously faulted.
-1074360261: Unknown USB3 Vision error.
To restore use of the camera I cycle power to the faulted camera and the camera then can communicate with the IMAQdx drivers again.
Adding wait time between the IMAQdx steps did not affect this outcome.
For testing purposes, I modified the TwoCameras.VI to run only one camera. This program ran for 10,000 cycles with no error for each camera. Possibly not enough cycles to prove that one camera works, but still pretty convincing since it worked for 10,000 cycles on each camera.
I again modified TwoCameras.VI to only acquire images and not write settings as well as vise-versa (write settings, but not acquiring) for both cameras. This did not produce any errors after 10,000 cycles for each test.
Am I overlooking something about the IMAQdx VAS library?
Hardware
Basler Monochrome Camera (acA2500-14um)
Basler Color Camera (acA2500-14uc)
WIndows 8.1 PC, 64 bit
3 meter USB3 compliant cables away from High Voltage AC/DC power
Software
VAS - Aug 2013
LV 2013 13.0f2
Considerations
1. I have not updated the firmware of the Basler camera nor have I contacted Basler