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.
The following items are known issues in LabVIEW 2010 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
| |||||
| 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
| |||||
| 280872 Return | Desktop Execution Trace Toolkit 2010 Does Not Trace VI Executions Under LabVIEW 2010 Japanese When Destop Execution Trace Toolkit 2010 (DETT) is installed and used under LabVIEW 2010 Japanese, it launches but does not show any tracing behaviors at all. Workaround: N/A
| |||||
| 281507 Return | Desktop Execution Trace Toolkit 2010 Does Not Highlight the Traced Items Under LabVIEW 2010 Japanese Double-clicking a trace item does not highlight the item in question in the block diagram. Instead Error Code 1510 is returned. Workaround: N/A
| |||||
| Toolkit - Other | ||||||
| 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
| |||||
| 287441 Return | [PID and Fuzzy Logic] Fuzzy System Designer missing is keyboard shortcuts in menu The Fuzzy System Designer main user interface is missing the keyboard shortcut associations in the menu file. Workaround: N/A
| |||||
| 211954 Return | [SysID] Estimate Frequeny Response Step in System Identification Assistant does not save settings The value of "Frequency in log" and "Magnitude in dB" are not saved when you save a project. If the project is reopened, these two controls have been reset. Workaround: N/A
| |||||
| 249413 Return | [SysID] "a" is not supported as a symbolic variable If you use "a" as a symbolic variable in System Identification Toolkit, you might encounter unexpected results since "a" is used as a variable internally in the System Identification Toolkit. Workaround: N/A
| |||||
| 257100 Return | [SIT] Deleting an indicator in SIT 2010 VI breaks VI and does not recompile automatically Deleting an indicator from a compiled VI results in a broken error because of a blank event structure inside the SIT portion of the block diagram. Opening the SIT Connection Manager and clicking OK to recompile the SIT portion of the block diagram does not recompile the code and the VI remains broken. Workaround: Manualy change the mapping in the Connection Manager and then click ok.
| |||||
| 276747 Return | [SIT] Large arrays are grayed out and will not map to a Simulink model using the Simulation Interface Toolkit The Simulation Interface Toolkit cannot map an array larger than 10 elements to a Simulink model. If an array larger than 10 elements is mapped in the SIT Connection Manager, the array will become grayed out on the front panel. Workaround: Break up larger arrays into several smaller arrays with 10 or less elements. Re-combine the elements in Simulink by using the "Mux" block.
| |||||
| 301408 Return | [SIT] SIT fails to create correct path for replay file on PXI controllers Error 14112 when using a replay file with SIT with some PXI controls. 8101 and 8108 models have shown this behavior. Workaround: Change Filename = "/1.tdms" to Filename = "1.tdms" in the ini file located at / replay config/
| |||||
| 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
| |||||
| 249185 Return | Unable to Create Report from Macro-Enabled Word or Excel Template (.dotm file) Workaround: Add "mtod" to the case containing Word_Create_Document.vi to properly handle these templates. This case structure can be found within the NI_Word:lvclass:new report subVI.vi
| |||||
| 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
| |||||
| 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.
| |||||
| 254858 Return | ATML/XML Report Causes HTML Report to Generate an Incomplete Report When generating an HTML report of a Unit Test, selecting to also generate an ATML/XML report will result in losing the Test Details section of the HTML report. Workaround: N/A
| |||||
| 300593 Return | LabVIEW Unit Test Framework cannot find base LabVIEW Class If you have a VI that contains the LabVIEW base Class you will receive a message "Class type Not Found" when trying to load a .lvtest file. Workaround: Create your own parent class and make Class 1 inherit from it. Use that parent class object as indicator in test VI. Don't use the built-in LabVIEW Object.
| |||||
Document last updated on 8/2/2011