NI Vision Development Module 2019 and 2019 SP1 Bug Fixes

Overview

The following items are the CAR IDs of issues fixed between the release of NI Vision Development Module 2018 SP1 and NI Vision Development Module 2019 SP1. If you have a CAR ID, you can search this list to validate that the issue has been fixed. This is not an exhaustive list of issues fixed in the current version of NI Vision Development Module.

Vision Development Module 2019

IDFixed Issue
727204IMAQ Extract HOG outputs different Feature vector at every call.
726462Vision examples are not linked correctly through CVI Example Finder.
724647Deep Learning Examples were not searchable through LabVIEW Example Finder.
720366In some cases, IMAQ Match Pattern 4 can crash due to a race condition.
719026Find Edge VI does not have an output that returns whether an edge was found.
696276Calling 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..
428570Writing to AVI files is limited to a 2GB size.

 

Vision Development Module 2019 SP1

IDFixed Issue
123490/733365Optimized parallel code generation in Vision Assistant can sometime generate code that contains a race condition in foreign LabVIEWs (Chinese, French, German, Japanese, Korean)
197652/741989Vision Assistant does not launch when LabVIEW FPGA is not installed on the machine.
200507/743965In Vision Assistant, Real-word measurements cannot be selected when configuring the measurements to display from the Particle Analysis Step.
105913/729857On foreign OSes, Vision Assistant may not generate LabVIEW NXG code if you select a VI name that contains multibyte characters.
111307/731009When editing a pattern maching step, the template may be found at a different location that when you first configured the step.
179080/738319Depending on image content and ROI, IMAQ Fit Contour can sometimes hang.
145516/734982Calling IMAQ AutoBThreshold on U16 images can cause an Access Violation crash in LabVIEW.
179217/739730Pattern Matching template learned with IMAQ Learn Pattern in Vision Development Module 2015 crashes when being opened with Vision Development Module 2018

 

Documentation CARs Fixed in 2019 SP1:

88676/459981
88657/707882
165200/735151
165203/733830
165206/724645
165211/727211
165214/727210
165217/704363
165219/714231
165221/692126
165223/674511
165226/670433
165228/661538
165232/637563
165234/618351
120256/724647

Glossary of Terms

 

  • Bug ID - When an issue is reported to NI, you may be given this ID or find it on ni.com.  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).