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 Development Module the issue was reported in. If you discover the issue appears in an earlier version of the NI Vision Development Module 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 Development Module 2018 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Vision FPGA | ||||||
| 634805 Return | The IMAQ FPGA Local Threshold VI does not correctly threshold the top of images when the kernel size is large.
| |||||
| 691538 Return | Unable to create IPINs for some Vision algorithms using IP Builder in LabVIEW 2018, use 2015 instead.
| |||||
| Algorithm | ||||||
| 572114 Return | The IMAQ Learn Distortion Model VI with the Distortion Model set to Polynomial generates an inconsistent calibration template if the X Step and Y Step values from the IMAQ Calibration Target to Points - Circular Dots 2 VI are less than 0.0001.
| |||||
| 341924 Return | The IMAQ Read Data Matrix Barcode 3 VI may hang on some I16 images.
| |||||
| 323970 Return | 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.
| |||||
| 569844 Return | The IMAQ Compare Golden Template VI returns different defect image results for LabVIEW 32-bit and LabVIEW 64-bit versions.
| |||||
| 411635 Return | The AVI2 VIs do not support writing extra data to AVIs.
| |||||
| 429210 Return | The IMAQ AVI2 Open and Close VIs leak when opening and closing a session with Built-in Codecs.
| |||||
| 564897 Return | Reading a frame from an AVI compressed using the codec "Cinepak Codec by Radius" with the IMAQ AVI Read Frame VI corrupts memory, and prevents LabVIEW from displaying a file dialog.
| |||||
| 698352 Return | Pattern Matching "In-Depth Discussion" topic links to Deep Learning instead of Pattern Matching in the NI Vision Concepts Help. Refer to the updated NI Vision Concepts Help for the "In-Depth Discussion" on Pattern Matching.
| |||||
| 716660 Return | IMAQ Calculate Defect Map returns error -1074396109 when the input image is calibrated with an old calibration.
| |||||
| 714960 Return | Vision vi.lib VIs do not have "separate compiled code from source file" enabled. This results in recompiles every time the target is switched.
| |||||
| 704363 Return | The LabVIEW help for IMAQ FFT is incorrect. The description of the VI should be: The FFT creates a complex image in which LOW frequencies are grouped at the center, while HIGH frequencies are located at the edges.”
| |||||
| 703071 Return | Using the Merge Overlay and Write Custom Data functions in parallel can cause a LabVIEW crash. As a workaround, call both functions sequentially.
| |||||
| 697946 Return | The IMAQ AVI2 Create VI does not support non-integer frame rates.
| |||||
| 697023 Return | When using the IMAQ Fit Line VI, if the resulting line is either vertical or horizontal it is possible to get error: "-1074395315 IMAQ Vision: You supplied an inefficient set of points to match the minimum score". As a workaround, rotate the set of points to a 45 degree angle to find the fitted line.
| |||||
| 696276 Return | Calling a VI that has Vision functions in a TestStand sequence with Adapter Run-Time engine mode with Auto detect using VI version selected will sometimes cause the UI to close and LabVIEW to silently crash if there are multiple LabVIEW Run-Time engines installed. As a workaround, use the 32-bit version of TestStand and Vision Development Module.
| |||||
| Display Control | ||||||
| 509996 Return | The snapshot property node for the Image Display Control on NI Linux Real-Time targets returns an error even though the control is functioning properly. This issue is present only when the target is connected to the host.
| |||||
| 510277 Return | When zoom factors above 30 are used, the Image Display Control on NI Linux Real-Time targets leaves black-colored border space.
| |||||
| 512425 Return | The Image Display Control on NI Linux Real-Time targets may not work properly when an image is set using a property node value and the target is connected to the host. The property node value works properly when the target is disconnected from the host.
| |||||
| 414069 Return | Japanese and Simplified Chinese for text overlays are not supported on NI Linux Real-Time targets.
| |||||
| 683846 Return | LabVIEW NXG code generated is incorrect when the user decides to expose the Overlay parameters as a control on the front panel.
| |||||
| C/.NET/TestStand | ||||||
| 589566 Return | Vision Development Module examples for LabWindows/CVI 2015 or later can give null pointer dereference crashes if Vision development or runtime licenses are not activated.
| |||||
| 696276 Return | Calling a VI that has Vision functions in a TestStand sequence with Adapter Run-Time engine mode with Auto detect using VI version selected will sometimes cause the UI to close and LabVIEW to silently crash if there are multiple LabVIEW Run-Time engines installed. As a workaround, use the 32-bit version of TestStand and Vision Development Module.
| |||||
| Vision Assistant | ||||||
| 510164 Return | When an FPGA target is active in a LabVIEW project, the Vision Assistant executable cannot generate code for a non-FPGA LabVIEW target into that same instance of LabVIEW.
| |||||
| 683310 Return | Vision Assistant installer is not currently supported through NIPM. Installation of Vision Assistant applications will need to be done via download from the web, or from physical media.
| |||||
| 484419 Return | The Local Threshold step in Vision Assistant does not warn that multi-pixel (x8) FPGA code generation is not implemented for the step, and instead generates broken LabVIEW FPGA code.
| |||||
| 685743 Return | Loading images with IMAQ Load Image Dialog or Vision Assistant, results in error -1074395995 or "Selected Invalid Image" if the image files contain multiple-byte character that include "0x7C". Use path control or Vision Acquisition Express VI as workaround.
| |||||
| 692355 Return | Having two instances of the Pattern Matching step pointing to the same template but using different algorithms results in the template not being found in one of the steps. As a workaround, have a different copy of the template for each instance of the Pattern Matching step.
| |||||
| 693530 Return | In the Pattern matching step, parameters are not saved when switching from one pattern matching algorithm to another.
| |||||
| 699277 Return | Using the Pattern Matching step with Geometric Pattern Matching and a calibrated image does not return calibrated results. To get calibrated results, set the Enable Calibration advanced parameter to True in the Advanced View, under the Matching section.
| |||||
Document last updated on 10/23/2018.