Impact Acquire SDK Java
BVS CA-SF or other USB3 Vision™ devices connected to the system are not detected by Impact Acquire or cannot be initialised

Symptoms

Tools like ImpactControlCenter list mvBlueFOX devices connected to the system but their state is set to Unreachable or trying to open the device fails. In rare cases devices are not even displayed.

Cause

A "USB3 Vision" camera is part of the bus or system to which it is connected. Like other devices (e.g. PCIe card, mouse, etc.) a "USB3 Vision" device is bound to the system via a driver. Because a device can only be bound to one driver in the system, it is possible that the device driver is bound to another "USB3 Vision" driver which is available on the system.

In this case it is possible that you cannot see the BVS CA-SF or third party USB3 Vision™ device using Balluff tools like ImpactControlCenter or you can see it but you cannot use it. A dialog like the following might appear:

Figure 1: Unreachable devices

Resolution

The driver binding can be changed using the Windows "Device Manager":

Note
Please be sure, that you have already installed the Impact Acquire package with USB3 Vision™ support.
  • Open the "Device Manager" from "Control Panel → System → Device Manager".
    For example on this system, an BVS CA-SF is bound to the "NI Acquisition Device" driver
Figure 2: BVS CA-SF as a NI Acquisition Device
  • Right-click the device and select "Update Driver Software...".
  • Click on "Browse my computer for driver software":
Figure 3: Browse my computer for driver software
  • Click on "Let me pick from a list of device drivers on my computer":
Figure 4: Let me pick from a list of device drivers on my computer
  • Select the USB3 Vision™ driver called "USB3 Vision Device(Bound to MATRIX VISION GmbH driver using libusbK)" and click on "Next":
Figure 5: Select the Balluff/MATRIX VISION driver

Afterwards, the driver binding will be changed.

  • Finally, click on "Close":
Figure 6: Driver update was successful
  • Now the BVS CA-SF (mvBlueFOX3) device should be bound to the Balluff/MATRIX VISION driver via libusbK.
Figure 7: mvBlueFOX3 is bound to the Balluff/MATRIX VISION driver via libusbK