IMAQdx USB3 camera errors on computer only using run-time

[cbl-jnj]

A Windows 10 computer with the LabVIEW 2015 SP1 development environment installed, was used to create an executable and an installer, for some functioning code which includes the use of a IMAQdx USB3 camera. The executable works on this development computer. The installer includes the following additional installers:

Running the installer on a new Windows 10 computer to install the executable completes, and when the executable is run, one the following three errors is reported at the IMAQdx Open Camera VI:

• (-52005) - The parameter received by the function is not valid.
• (-52023) - No transfer is in progress because the transfer was aborted by the client. The operation could not be completed as specified.
• (-52024) - An unknown or unexpected communication fault occurred while attempting to read data from or write data to a device.

The following simple VI, that repeats how the camera is opened in the larger program, was turned into an executable and run. It shows the camera is enumerated, but the IMAQdx Open Camera VI returns an error, which is one of the three above.

What is causing these IMAQdx errors? What needs to be done to not have them?

The help for IMAQdx Open Camera VI indicates this VI does a number of things (opens a camera, queries the camera for its capabilities, loads a camera configuration file, and creates a unique reference to the camera). The "loads a camera configuration file" is a bit concerning because it is not clear how that file is created or where it is loaded from on the Windows 10 computer with just the run-times installed. No MAX and no LabVIEW development are on this computer.

[Hatef.fouladi]

usb3 camera driver 

[cbl-jnj]

---

@Hatef.fouladi wrote:

usb3 camera driver 

---

Is there a specific concern with the usb3 camera driver?

The Windows Device Manager has the camera listed with the NI-IMAQdx USB3 driver:

and as mentioned and shown previously, the IMAQdx Enumerate Cameras VI lists the camera.

The error is reported when the camera is opened with IMAQdx Open Camera VI. And a fourth error was reported at this VI, at one point yesterday, during testing:

• (-52022) - IO processing is not active.

[udka]

Suggestion:

-Use cam0 as constant to your Session in instead of getting from IMAQdx Enumerate Cameras and see if it works in EXE.

-If above works, then you should look into this link: What is NI-IMAQdx Runtime and Why is My Session In Control Disabled in My Executable?http://digital.ni.com/public.nsf/allkb/4A096593E2BD63BE86257D49007A5B30

[cbl-jnj · Accepted solution]

Thanks for all the input.

It turns out the system that was being upgraded to a new PC with Windows 10 had a USB cable issue.

While the USB cabling worked for the previous PC with Windows 7, it needed to be changed in order for the camera to work with the new Windows 10 PC.

The cabling was a 3m USB extender with a 6 inch USB cable and was replaced with a 2m extender with a 6 inch USB cable. The maximum cable length for USB3.x is 3m, so it was luck it worked in the old setup.

A take away from all this may be that if the IMAQdx Enumerate Camera VI succeeds, but the IMAQdx Open Camera VI fails, check the USB cabling and lengths.

This was all finally determined using the camera vendor's software, which behaved the same as the NI IMAQdx USB3 driver.