Archived: LabVIEW 2009 Toolkits 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.

Overview



This document contains known issues for LabVIEW 2009 toolkits. The following toolkits are included:
  • Desktop Execution Trace Toolkit
  • Report Generation Toolkit for Microsoft Office
  • Unit Test Framework Toolkit
  • Adaptive Filter Toolkit
  • Digital Filter Design Toolkit
  • System Identification Toolkit
  • Simulation Interface Toolkit
  • PID and Fuzzy Logic Toolkit
  • Advanced Signal Processing Toolkit
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. If a particular LabVIEW toolkit is not listed below, it currently has no known issues.

The LabVIEW 2009 Platform Known Issues contains a full listing of known issues, including LabVIEW Development System and modules.

Contacting NI

You can contact us by phone, email, or the discussion forums. Visit the NI Website to contact us. If you are contacting NI in regards to a specific issue, be sure to reference the ID. If you have feedback on this document, please contact NI on this NI Developer Zone post.

Windows 7

National Instruments is committed to maintaining compatibility with Microsoft Windows technology changes. However, NI has become aware of a number of issues of potential significance regarding Microsoft Windows 7. To learn how Windows 7 affects your use of NI products, visit ni.com/info and enter the Info Code windows7.

Known Issues by Category

The following items are known issues in LabVIEW 2009 Toolkits sorted by Category.

Toolkit - Desktop Execution Trace Toolkit
144704 DETT can record "DeQueue Element Awake" - "Awoke with Data" events in the wrong thread
173669 Loading a trace doesn't work unless a new trace connection is added
224367 Desktop Execution Trace Toolkit does not trance a LabVIEW built DLL called from LabVIEW
Toolkit - Other
148996 The TSA MUSIC Spectrum VI returns incorrect results for a multiple-tone pure signal
173602 Incorrect example folder path in the Getting Started with the System Identification Assistant help
177698 [PID and Fuzzy Logic] Center of Sums, Center of Maximum, Mean of Maximum may give NaN result
173851 Context help of two options in the Rebuild Missing Data step shows broken links
183794 Cannot select .lvbitx files in SIT Connection Manager
Toolkit - Report Generation
188911 Control image alignment incorrect when "new report page" VI is used
176502 Excel Find and Replace VIs 'found' Boolean output give erroneous data.
Toolkit - Unit Test Framework
120941 Code Coverage analysis is not supported on LabVIEW Real-Time
129739 Code coverage for results include only those VIs that have tests defined for
136015 Code coverage analysis requires "Allow Debuging" to be set on VI under test
136421 Test configuration and test execution will cause a dirty dot on the project
160115 lvtest file can not be added to the LabVIEW project if it is in multi-level libraries
175831 Cannot create a test for an XY Graph
171553 File load conflict after dragging multiple LV Classes to another context



ID Known Issue
Toolkit - Desktop Execution Trace Toolkit
144704

Return
DETT can record "DeQueue Element Awake" - "Awoke with Data" events in the wrong thread
The code that records the particular event ("DeQueue Element Awake" - "Awoke with Data") can happen in such a way that we record it in the thread that enqueues the data. It does not mean that the primitive is actually waking up in the same thread.

Workaround: N/A

Reported Version: 1    Resolved Version: N/A    Added: 02/20/2009
173669

Return
Loading a trace doesn't work unless a new trace connection is added

Workaround: Add a new trace connection first by clicking on the New Trace button and then load the saved trace.

Reported Version: 2009    Resolved Version: 2010    Added: 08/05/2009
224367

Return
Desktop Execution Trace Toolkit does not trance a LabVIEW built DLL called from LabVIEW
Because of the way LabVIEW calls DLLs built in the same or different versions, DETT cannot trace a LabVIEW built DLL.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 08/02/2010
Toolkit - Other
148996

Return
The TSA MUSIC Spectrum VI returns incorrect results for a multiple-tone pure signal
If the input signal is composed of several pure tones, the resulting spectrum may contain only one peak.

Workaround: Changing the frequency or window length may reveal the peaks in the resulting spectrum. Increasing the value of the noise subspace may return ideal results.

Reported Version: 2009    Resolved Version: 2010    Added: 08/05/2009
173602

Return
Incorrect example folder path in the Getting Started with the System Identification Assistant help
In the Getting Started with the System Identification Assistant help, Step 3 asks user to "Navigate to the National Instruments\Express Workbench\System Identification Assistant\Examples\getting_started directory." In 2009, the Examples folder is moved to "National Instruments\System Identification Assistant".

Workaround: N/A

Reported Version: 2009    Resolved Version: 2010    Added: 08/05/2009
177698

Return
[PID and Fuzzy Logic] Center of Sums, Center of Maximum, Mean of Maximum may give NaN result
The Center of Sums, Center of Maximum, Mean of Maximum functions give a NaN result for an output variable if this variable contains a Gaussian or a Sigmoid membership function.

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 08/05/2009
173851

Return
Context help of two options in the Rebuild Missing Data step shows broken links
On the Configuration tab, the context help of Specify upper limit and Specify lower limit options under Stimulus shows broken links.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2011    Added: 10/01/2009
183794

Return
Cannot select .lvbitx files in SIT Connection Manager
When trying to select a bit file in SIT Connection Manager the dialog filters on .lvbit and you cannot select .lvbitx files.

Workaround: N/A

Reported Version: 2009    Resolved Version: 2010    Added: 10/01/2009
Toolkit - Report Generation
188911

Return
Control image alignment incorrect when "new report page" VI is used
When using the "append control image to report" VI, the alignment of some images is ignored when the "new report page" VI is used between appended images. This problem only exists with Office 2007. Other versions - Office 2003 and Office 2010 do not exhibit this behavior.

Workaround: Place a "new report line" VI between appending the image and the "new page" VI

Reported Version: 2009 32-bit    Resolved Version: N/A    Added: 06/16/2010
176502

Return
Excel Find and Replace VIs 'found' Boolean output give erroneous data.
The Excel Find and Replace VIs 'found' boolean output goes true even when the search string is cannot be found in the report.

Workaround: None.

Reported Version: 1.1.3    Resolved Version: 2010    Added: 06/30/2010
Toolkit - Unit Test Framework
120941

Return
Code Coverage analysis is not supported on LabVIEW Real-Time
The Unit Test Framework Toolkit cannot measure code coverage on real-time (RT) targets. The result will always be zero.

Workaround: N/A

Reported Version: 1    Resolved Version: N/A    Added: 02/06/2009
129739

Return
Code coverage for results include only those VIs that have tests defined for
Code coverage is calculated only during test execution. VIs that are not tested by the Unit Test Framework will not be included in the code coverage analysis. They will not influence the overall code coverage percentage for the project. They will also not be listed in the results window or in report files.

Workaround: N/A

Reported Version: 1    Resolved Version: 2010    Added: 02/06/2009
136015

Return
Code coverage analysis requires "Allow Debuging" to be set on VI under test
If the VI properties of a VI under test does not have a checkmark in the Allow debugging checkbox, code coverage result will always be zero.

Workaround: Check the "Allow debugging" option for VIs under test.

Reported Version: 1    Resolved Version: 2010    Added: 02/06/2009
136421

Return
Test configuration and test execution will cause a dirty dot on the project
Test configuration and test execution temporarily modifies the project in memory. None of this will affect the project information that is written to disk. However, it will prompt users to save the project when closing it in LabVIEW.

Workaround: N/A

Reported Version: 1    Resolved Version: 2010    Added: 02/06/2009
160115

Return
lvtest file can not be added to the LabVIEW project if it is in multi-level libraries
If lvtest file is in a library, and the library is the sublibrary of another library, the lvtest file can not be added to the LabVIEW project by draging&droping from disk to the project or by using popup menu "Add >> Files..."

Workaround: N/A

Reported Version: 2009    Resolved Version: N/A    Added: 06/16/2009
175831

Return
Cannot create a test for an XY Graph
If the VI has a XY Graph control as input or output, creating a test for this VI will fail (usually with the error "The following control name is not unique"). You will get an error saying that the control name is not unique.

Workaround: N/A

Reported Version: 1    Resolved Version: N/A    Added: 06/23/2009
171553

Return
File load conflict after dragging multiple LV Classes to another context
You will get loading conflict for lvtest files if you open a project which has multiple LV Classes and those classes have lvtest files of the same name. Loading any VI will also be very slow if you have this loading conflict in your project.

Workaround: Rename the lvtest files to different names. Or remove those lvtest files from the project and re-add them.

Reported Version: 2009    Resolved Version: N/A    Added: 08/05/2009

Document last updated on 8/2/2011

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).