VAS - Unknown USB3 Vision error

Question

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
Attachments:
USB3 Error.zip ‏79 KB

Answer 1

Alejandro,
Thanks for the response.
1. I am curious what the article means by, "IMAQdx driver goes through the camera driver". I have selected in MAX to use the 'NI-IMAQdx USB3 Vision Device' Driver. This is the only option as I have not installed a Basler driver. So how does the IMAQdx driver use an underlying Basler driver?
2. This is good example for my use case. It does not write settings while the acquisition is stopped, which is the core difference, as well as only one camera session being open at a time (hence the non-simultaneity). I am able to grab over 500 images before error which suggests to me that the driver does support simultaneity; however, the issue may occur infrequently and may be caused by the simultaneity. Once I have the hardware again, i will try the following:
a. Remove the WriteSettings.VI. This will isolate whether it is the writing of the settings or the starting/stopping of the camera session.
b. Remove simultaneity. I will make sure I only have one camera session open at a time. I am curious if this will cause any other issues since I am repeating this many times at a fast rate...opening and closing camera sessions that is.
3. Again good examples. The most applicable is probably the IMAQdx - Four Cameras. Again though, I have tried running just acquisitions and I do not get errors. One difference I spotted is that the buffer size is 10. So the other test I will run would be to:
a. Increase buffer size to 10
Any other info is appreciated.