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 SoftMotion Module the issue was reported in. If you discover the issue appears in an earlier version of the NI SoftMotion 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 2017 and 2017 SP1 sorted by Category.
| 683310 | — | Vision Assistant installer is not currently supported through NIPM. Installation of Vision Assistant applications will need to be done through the existing WinMIF distribution. |
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| Vision FPGA | ||||||
| 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.
| |||||
| 464510 Return | Vision FPGA Filter VIs with a mask using a 9x9 kernel support image widths up to 2,000 pixels.
| |||||
| 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.
| |||||
| 634805 Return | The IMAQ FPGA Local Threshold VI does not correctly threshold the top of images when the kernel size is large.
| |||||
| 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.
| |||||
| 364804 Return | The IMAQ Overlay Multiple Lines 2 VI returns an error when Fill is the selected Drawing Mode.
| |||||
| 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.
| |||||
| 678540 Return | IMAQ Clamp Max returns incorrect calibrated distance after updating the calibration axis of the calibrated image (simple calibration)
| |||||
| 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.
| |||||
| Performance | ||||||
| 623193 Return | NI Vision allows a maximum of 1024 unique threads to access one image during the process lifetime. LabVIEW takes care of this by maintaining a threadpool. But for text-based (Eclipse, C, or CVI) users, it is recommended to use a threadpool architecture and reuse threads, if the number of accesses to any image exceeds 1024 unique threads. In the absence of a threadpool, there is a possibility of leak in memory during the imageCreateImage() and imaqDispose() calls in worker threads.
| |||||
| 569446 Return | A large number of open image references (in the order of thousands), can adversely impact the performance (processing time) of Vision APIs. It is recommended to dispose the reference when an image refnum is no longer in use.
| |||||
| C/.NET | ||||||
| 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.
| |||||
| Installation | ||||||
| 677373 Return | Additional requirements are needed to deploy LV_LineIntersection1 on NI Real Time targets with VxWorks and Linux OS. [Contact NI Support]
| |||||
| 683310 Return | Vision Assistant installer is not currently supported through NIPM. Installation of Vision Assistant applications will need to be done through the existing WinMIF distribution.
| |||||
Document last updated on 5/10/2018.