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.
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.
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.
The following items are known issues in LabVIEW 2009 Toolkits sorted by Category.
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
Document last updated on 8/2/2011