Troubleshoot NI Vision: Hardware - USB3 Vision

The focus of this guide is to help start troubleshooting Vision Hardware communication and bus issues with a focus on USB3 Vision. This is part of a collection of guides aimed at troubleshooting NI Vision. If "USB3 Troubleshooting" is not the problem being experienced head back to the Troubleshooting NI Vision Guide.

Also named USB 3.1 Gen 1 (not compatible with Gen 2), the USB3 Vision standard draws on the GenICam standard (XML file). The transfer bandwidth is up to 350 MB/s (use the USB 3.0 interface). With a low latency and jitter, has high stability (good error handling), and is completely plug and play ready.

This guide is split into general troubleshooting steps and a number of more specific examples of potential issues. The specific examples should not be treated as a list of steps to work through, but rather as a set of examples that can help you in your troubleshooting process.

By the end of this article, you can expect to have been through the generalized troubleshooting steps common to this topic area. By reading through the specific examples, you will know more search terms related to "NI Vision hardware" and "USB3 Vision" that can help inspire questions and different ways to look at the problem.

Generic Troubleshooting:

For USB3 Vision, the most common issues are due to communication or compatibility. Listed below are generic troubleshooting steps from a low level of effort to high:

1. Check the Hardware Compatibility and compliance of the camera
2. Check and update the camera to the last Firmware (from the manufacturer third party tools)
3. Check the Installation and compatibility of drivers
4. Reinstall Vision Acquisition Software (VAS) software and check the activation and licensing
5. Repair NI-IMAQdx by the NI Package Manager
6. Check the hardware driver through Windows Device manager
7. Remove the description files (.iid, .icd, .xml) loaded when the camera is connected for the first time. The location of these files is below, and reconnect the camera to reload them
   • The .icd file has all the attributes of the camera. Usually placed at <Users>\Public\Public Documents\National Instruments\NI-IMAQ\Data
   • The .iid file saves the name of the .icd file and additional information from the device, like the serial number. <Users>\Public\Documents\National Instruments\NI-IMAQdx\Data

Specific Troubleshooting Examples:

The following list of examples is not intended to be a comprehensive list of all potential problems. However, it can be used to help identify useful search terms by introducing keywords important to the troubleshooting of this topic.
Other possible solutions and troubleshooting steps:

• Error 0x80070015, 0xBFFF801D, or Code 52 When Detecting USB3 Camera on Windows 10
• LabVIEW Reports "Attribute Value Is out of Range" for a USB 3 Camera (A difference in attribute range is mainly a difference of characteristics provided by the manufacturer)
• USB 3.0 Camera Detected in NI-MAX but Can't Acquire Images
• Ring API doesn’t work with LabVIEW Examples. With USB 3.0, we cannot use Ring API examples with LabVIEW because Ring API is low level. Ring API as limitations when used with USB 3.0 Vision usage. Few cameras with firmware that supports setting an arbitrary image can use Ring API. And with specific pixel formats U8, I16, U16, RGB32, and RGB64.

Next Steps

If you are still experiencing a problem please head back to the Troubleshooting NI Vision Guide