Archived: LabVIEW 2011 and 2011 SP1 Toolkits Known Issues

Publish Date: Jul 22, 2018 | 4 Ratings | 1.50 out of 5 | Print

Overview

This document has been archived and is no longer updated by National Instruments.

This document contains known issues for LabVIEW 2011 toolkits. The following toolkits are included:
  • Adaptive Filter Toolkit
  • Advanced Signal Processing Toolkit
  • Database Connectivity Toolkit
  • Desktop Execution Trace Toolkit
  • Digital Filter Design Toolkit
  • Multicore Analysis and Sparse Matrix Toolkit
  • PID and Fuzzy Logic Toolkit
  • Report Generation Toolkit for Microsoft Office
  • Simulation Interface Toolkit
  • System Identification Toolkit
  • Unit Test Framework 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 2011 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.

Known Issues by Category

The following items are known issues in LabVIEW 2011 and 2011 SP1 sorted by Category.

Toolkit - Desktop Execution Trace Toolkit
127647 Save All Traces asks for a file name but does not use it
144704 DETT can record "DeQueue Element Awake" - "Awoke with Data" events in the wrong thread
224367 Desktop Execution Trace Toolkit does not trance a LabVIEW built DLL called from LabVIEW
281507 Desktop Execution Trace Toolkit 2010 Does Not Highlight the Traced Items Under LabVIEW 2010 Japanese
328834 DETT doesn't correctly trace application if launched outside of LabVIEW Tools » Profile menu
Toolkit - Other
177698 [PID and Fuzzy Logic] Center of Sums, Center of Maximum, Mean of Maximum may give NaN result
125072 [SIT] Applications using only the SIT Scheduler VI will hang
257100 [SIT] Deleting an indicator in SIT 2010 VI breaks VI and does not recompile automatically
276747 [SIT] Large arrays are grayed out and will not map to a Simulink model using the Simulation Interface Toolkit
301408 [SIT] SIT fails to create correct path for replay file on PXI controllers
294984 System Identification Toolkit Returns non-sensible error when input sizes are different
325714 [MASM] Unexpected behaviour when using FFT VIs or Linear Algebra VIs in a timed loop
358379 [MASM] Incorrect results are returned if FFT VIs or Linear Algebra VIs are used in a timed loop
Toolkit - Report Generation
200345 The "Append Table to Report" VI displays incorrect values in MS Word 2010 and Report Generation Toolkit 2010.
188911 Control image alignment incorrect when "new report page" VI is used
249185 Unable to Create Report from Macro-Enabled Word or Excel Template (.dotm file)
312071 Error 7 when using Report Generation Toolkit VIs in a DLL
313610 Excel ActiveX methods lead to an error in Report Generation Toolkit 2011.
Toolkit - Unit Test Framework
120941 Code Coverage analysis is not supported on LabVIEW Real-Time
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
127647

Return
Save All Traces asks for a file name but does not use it
When you right-click an application instance and select "Save All Traces", or select File»Save All Traces, the file name that is entered is not used. The files are instead named according to the date and time the traces were started. File name format: month_day_year _ hour_minute_second_fractionalsecond.ttd. For example, a traced started on January 1, 1904 at 01:22:33.444444 would be saved as 1_1_1904 _ 01_22_33_444444.ttd

Workaround: Use Windows Explorer to manually rename the files once it's saved.

Reported Version: 1.0    Resolved Version: Unknown    Added: 02/06/2009
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.0    Resolved Version: N/A    Added: 02/20/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
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

Reported Version: 2010    Resolved Version: N/A    Added: 08/02/2011
328834

Return
DETT doesn't correctly trace application if launched outside of LabVIEW Tools » Profile menu
If Desktop Execution Trace toolkit is launched from Windows Explorer, and attempts to trace the execution of an instance of LabVIEW that doesn't have the default VI Server port (3364), no events will appear in the event log.

Workaround: Launch DETT via LabVIEW's Tools » Profile » Trace Execution menu or change LabVIEW to use the default VI Server port.

Reported Version: 2011    Resolved Version: N/A    Added: 03/28/2012
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

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

Return
[SIT] Applications using only the SIT Scheduler VI will hang
An application just using the SIT Scheduler VI will hang on the second iteration when calling the model DLL.

Workaround: The SIT Model Update VI needs to be called directly after the SIT Scheduler VI. Or replace the SIT Schedule VI with the SIT Take Model Time Step VI

Reported Version: 5.0    Resolved Version: N/A    Added: 07/25/2011
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: Manually change the mapping in the Connection Manager and then click OK.

Reported Version: 2010    Resolved Version: N/A    Added: 08/02/2011
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.

Reported Version: 2010    Resolved Version: N/A    Added: 08/02/2011
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/

Reported Version: 2010    Resolved Version: N/A    Added: 08/02/2011
294984

Return
System Identification Toolkit Returns non-sensible error when input sizes are different
SI Estimate Partially Known State-Space Model VI can incorrectly report error -20002 even when the input sequences are in fact the same size. Instead the error should be -41528 "The matrix exponential calculation overflowed."

Workaround: N/A

Reported Version: 2010 SP1    Resolved Version: N/A    Added: 03/28/2012
325714

Return
[MASM] Unexpected behaviour when using FFT VIs or Linear Algebra VIs in a timed loop
On a desktop computer, unexpected results are returned on first iteration when FFT VIs or Linear Algebra VIs are placed inside of a timed loop.

Workaround: Use a while loop instead.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 03/28/2012
358379

Return
[MASM] Incorrect results are returned if FFT VIs or Linear Algebra VIs are used in a timed loop
On a desktop computer, an incorrect result is returned on first iteration when FFT VIs or Linear Algebra VIs are placed inside of a timed loop on LabVIEW 2011 SP1 32-bit.

Workaround: Use a while loop instead.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 03/28/2012
Toolkit - Report Generation
200345

Return
The "Append Table to Report" VI displays incorrect values in MS Word 2010 and Report Generation Toolkit 2010.
Using the "Append Table to Report" VI to add strings of Cyrillic font to a table in an MS Word report results in gibberish being added to the report.

Workaround: N/A

Reported Version: 2010    Resolved Version: N/A    Added: 03/09/2010
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
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

Reported Version: 2010 32-bit    Resolved Version: N/A    Added: 10/29/2010
312071

Return
Error 7 when using Report Generation Toolkit VIs in a DLL
By default RGT VI's are compiled into the DLL, but can't be executed from within the DLL.

Workaround: The DLL will run correctly if you include the Report Generation toolkit lvclass dependencies in a separate support directory and specify that they are always included in a data directory.

Reported Version: 2011 32-bit    Resolved Version: N/A    Added: 03/28/2012
313610

Return
Excel ActiveX methods lead to an error in Report Generation Toolkit 2011.
When the examples are opened the VI has a broken run arrow and the error list says the SubVI's are not executable. SubVI's contain invoke nodes that are calling Active X methods that are not linked properly.

Workaround: Right click on reference wire into broken invoke node and select Create » Create method for 'broken invoke node' to recreate the invoke node. Then rewire and VI is fixed.

Reported Version: 2011 32-bit    Resolved Version: 2012 32-bit    Added: 04/27/2012
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.0    Resolved Version: N/A    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 child of another library, the lvtest file can not be added to the LabVIEW project by dragging & dropping from disk to the project or by using context 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.0    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/3/2012

Back to Top

Bookmark & Share


Ratings

Rate this document

Answered Your Question?
Yes No

Submit