NI does not actively maintain this document.
This content provides support for older products and technology, so you may notice outdated links or obsolete information about operating systems or other relevant products.
Each Issue appears as a row in the table and includes these fields:
Issue ID—Contains the number in at the top of each of the cells in the first column. When you report an issue to NI, you may be given this ID, you can also find IDs posted by NI on the discussion forums or in Knowledge Base articles.
Issue Title —Describes the issue in one sentence or less.
Problem Description (optional)—Describes the problem in further detail. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI (contact information below) and reference the ID number given in the document.
Reported Version—Contains the earliest version of the NI Vision Acquisition Software driver the issue was reported in. If you discover the issue appears in an earlier version of the Vision Acquisition Software driver than is reported in this field, you can report that to NI (contact information below) to have the field updated.
Resolved Version—Contains the version the issue was resolved or was no longer applicable. If an issue has not been resolved "N/A" will be reported.
Date Added—Contains the date the issue was added to the document (not the reported date).
Feel free to contact NI regarding this document or issues in the document. If you are contacting NI in regards to a specific issue, be sure to reference the ID number given in the document to the NI representative. The ID number contains the current issue ID number as well as the legacy ID number (use the current ID number when contacting National Instruments). You can contact us through any of the normal support channels including phone, email, or the discussion forums. Visit the NI Website to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The following items are known issues in NI Vision Acquisition Software 18.0 and 18.5 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Installation | ||||||
| 623854 Return | Installing or reinstalling certain drivers, including NI-IMAQdx or Vision-RIO, on top of previous installations on a Linux Real-Time target can put the target in an unreachable state unless you force it into safe mode using the reset button or manually reassociate driver dependencies on the target. To avoid this issue, format the target prior to installing or reinstalling software, or only perform reinstallations using a Recommended Software Set. To learn more about this issue and additional recovery options, visit ni.com/info and enter the Info Code nikalEmbeddedReinstall.
| |||||
| 684897 Return | In NXG 2.1, upgrading either DAQmx or NI-IMAQdx from 17.5 to 18.0 will create an incompatibility in a shared dependency. As a workaround, if you have both drivers installed make sure to upgrade both drivers.
| |||||
| 591562 Return | Upgrading and then downgrading the NI-IMAQdx driver might not revert back completely to the correct version. As workaround, manually delete the niimaqdx.dll from System 32 and SysWOW64 after uninstalling the new version and then force reinstall the old one.
| |||||
| NI-IMAQdx | ||||||
| 414065 Return | Volume License Manager attempts to check out available NI Vision Development Module licenses before trying NI Vision Acquisition Software licenses.
| |||||
| 474860 Return | Renaming a camera on some real-time targets may take a long time to complete.
| |||||
| 682085 Return | AXIS Q1765-LE cameras are not enumerated in NI-MAX on Windows 10 computers. Possible workaround is to use a Windows 7 computer and port over the generated .icd and .iid files (located under C:\Users\Public\Documents\National Instruments\NI-IMAQdx\Data) of the camera to the Windows 10 computer.
| |||||
| 690945 Return | If selecting a camera file in NI-MAX results in an error, there will be no way to switch to a different camera file. As a workaround, either delete the IMAQ .iid file on disk or change the .icd file it points to.
| |||||
| 714802 Return | In the Triggered Grab example, the Timeout input is overwritten by the default five second timeout of the Grab2.vi. In order to use the Timeout property, wire a -2 as the timeout input of the Grab2.vi
| |||||
| 708625 Return | Changing the source of a Camera Link camera control line doesn't take effect until the session is closed and reopened.
| |||||
| 706600 Return | Quickly switching a camera from one NIC to another will sometimes prevent the user from opening a session to the camera.
| |||||
| 705508 Return | When a GigE camera has a UserDefinedName with a special character ('\"', '*', '/', ':', '<', '>', '?', '\\', '|') in it, the .iid file is not created properly. Removing the character or manually creating the .iid file on disk and pointing to the serial number of the camera can be used as workarounds.
| |||||
| 699992 Return | When acquiring from the Windows ISC-178x Smart Cameras, it is possible to see a high CPU utilization. This is due to limited CPU resources on the device. Disabling image display should help reduce the utilization.
| |||||
| 692125 Return | In some circumstances, Camera Link boards will not enumerate correctly. Rebooting the computer usually solves the issue.
| |||||
| 690944 Return | After renaming a Camera Link board in NI-MAX, you must close and re-open MAX before it will show up again.
| |||||
| 691432 Return | It is possible in some cases to get a "Camera already in use" error when first opening a session to the a Camera Link board through NI-IMAQdx. To workaround this issue, disable and then re-enable the card in Device Manager.
| |||||
| NI-IMAQ I/O | ||||||
| 427019 Return | Only one NI PCIe-1473R framegrabber can use the virtual serial port at a time.
| |||||
Document last updated on 10/19/2018.