Archived: NI Vision Development Module 2012 Known Issues

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.


This document contains the NI Vision Development Module 2012 known issues that were discovered before and since the release of the NI Vision Development Module 2012. Not every issue known to NI will appear on this list; it is intended to only show the severe and more common issues that can be encountered.

Known Issues

The following items are known issues in the NI Vision Development Module.

  • The IMAQ Read QR Code VI may hang when the QR Code Cell Size has a minimum size of 2 or less. Setting the minimum size to 3 or higher will prevent this issue.
  • The IMAQ Read Data Matrix Barcode 3 VI may hang on some I16 images.
  • Zooming out on a large, 32-bit image in the Image Display in LabVIEW will cause the image to black out.
  • To store error statistics on corrected images, you must run the IMAQ Get Calibration Info2 VI before correcting the calibration template image. The Return Error Information input must be set to TRUE.
  • The IMAQ Get Calibration Info2 VI returns 0 for the X Step and Y Step subparameters of the Grid Descriptor output if the calibration template image was not learned using simple calibration.
  • When installing software to a newly formatted Compact Vision System with MAX 4.7, files may be improperly installed. Refer to Timeout Received When Installing Software on CVS in MAX 4.7.x for information about addressing this issue.
  • Vision Assistant cannot generate C code if a double-byte character exists in the path to Vision Assistant or in the destination path for the generated code.
  • Some Vision Development Module .NET examples only work if Measurement Studio 8.6 is installed.
  • The Visual Basic .NET Label example does not compile.
  • There is no 64-bit Vision API for C or .NET.
  • Installing the Vision Development Module on a Windows Vista 64-bit computer where Visual Studio 2005 has been recently installed causes compatibility warnings.
  • The Vision Development Module cannot open two of the installed AVI files, SideCrash1.avi and SideCrash2.avi, when running as a 64-bit application.
  • AVI functionality requires Microsoft DirectX 8.1 or later.
  • On Windows XP computers with Service Pack 2 installed, NI Vision does not support reading AVI files located in the Local Settings folder, or any subfolders of this folder, when the AVI file uses any of the following compression filters:
    • Indeo Video 5.10 Compression Filter
    • Intel Indeo Video R3.2
    • Intel Indeo Video 4.5
    • Indeo Video 5.10

      Copying the AVI file to another folder resolves this problem.
  • Using NI Vision with LabWindows/CVI on a machine that does not support the MMX instruction set may cause an Illegal Operation exception to occur within the LabWindows/CVI environment. This error occurs when DirectX checks for the availability of the MMX instruction set on the machine.
  • The Vision Assistant Express VI image caching feature is available in LabVIEW 8.2 or later.

Glossary of Terms


  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on  You may also find IDs posted by NI on the discussion forums or in KnowledgeBase articles.
  • Legacy ID – An older issue ID that refers to the same issue.  You may instead find this issue ID in older known issues documents.
  • Description - A few sentences which describe the problem. The brief description given does not necessarily describe the problem in full detail.
  • Workaround - Possible ways to work around the problem.
  • Reported Version - The earliest version in which the issue was reported.
  • Resolved Version - Version in which the issue was resolved or was no longer applicable. "N/A" indicates that the issue has not been resolved.
  • Date Added - The date the issue was added to the document (not the reported date).