LabVIEW 2015 Toolkits Known Issues

Panoramica

This document contains known issues for LabVIEW 2015 toolkits. The following toolkits are included:
  • Advanced Signal Processing Toolkit
  • Biomedical Toolkit
  • Database Connectivity Toolkit
  • Desktop Execution Trace Toolkit
  • Digital Filter Design Toolkit
  • GPU Analysis Toolkit
  • Multicore Analysis and Sparse Matrix Toolkit
  • Report Generation Toolkit for Microsoft Office
  • Simulation Interface Toolkit
  • Unit Test Framework Toolkit
  • VI Analyzer Toolkit
  • Electric Motor Simulation 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 2015 Platform Known Issues contains a full listing of known issues, including LabVIEW Development System and modules.

Refer to the Third Party Licensing & Activation Toolkit group on the NI Community website for questions or information about any known issues in the Third Party Licensing & Activation Toolkit.

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 2015 Toolkits sorted by Category.

Toolkit - Advanced Signal Processing
431453 TSA Principal Component Analysis (Array).vi does not correctly calculate the covariance matrix when the "unified?" input is sent to False.
Toolkit - Database Connectivity
347325 DB Tools Insert Data.vi does not write dates correctly when OS language is set to French date format
389996 Error 1 Returned from DB Tools Insert Data.vi
Toolkit - Other
356420 Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name
412822 Issues with the Biomedical Workbench when you downgrade the Biomedical Toolkit from 2013 to 2012
510649 Changing an indicator into a constant within a Control & Simulation Loop breaks the VI
Toolkit - PID and Fuzzy Logic
514789 Autotuning PID Online.VI Example Reads Proportional Gain 'NaN' with the Relay Technique.
Toolkit - Report Generation
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
382455 Microsoft Excel Template named cell range font size is overwritten
391394 Dates are Reversed by Excel Easy Table.vi on Non-US Languages
463584 Append Horizontal Line to Report VI generates incorrect HTML code with width units in percent and decimal separator is set to ","
472835 The Save Report to File.vi requires the "report file path" terminal to be wired, but is not set as a required input
Toolkit - Simulation Interface
125072 Applications using only the SIT Scheduler VI will hang
257100 Deleting an indicator in SIT 2010 VI breaks VI and does not recompile automatically
276747 Large arrays are grayed out and will not map to a Simulink model using the Simulation Interface Toolkit
301408 SIT fails to create correct path for replay file on PXI controllers
367752 Model with Custom S-Function Returns Null Pointer Exception on Pharlap OS
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
420795 When creating a custom LV project template with the Unit Test Framework .lvtest file, the new project will overwrite the original template when saving instead of creating a new instance with new files.
466818 Error 1527 will occur when running the example "Programmatically Run Tests from Projects.vi" referencing the example project "LV Class.lvproj."
475037 Enabling loop iteration parallelism in For Loops results lower code coverage than expected
471993 Cannot create Unit Test for VI with control connected to the terminal and inside a tab control



ID Known Issue
Toolkit - Advanced Signal Processing
431453

Return
TSA Principal Component Analysis (Array).vi does not correctly calculate the covariance matrix when the "unified?" input is sent to False.
N/A

Workaround: Use the TSA Covariance (Array).vi which is located at "vi.lib\addons\Time Series Analysis\Statistical Analysis.llb\TSA Covariance (Array).vi"

Reported Version: 2013    Resolved Version: N/A    Added: 03/25/2014
Toolkit - Database Connectivity
347325

Return
DB Tools Insert Data.vi does not write dates correctly when OS language is set to French date format
When Windows language format is set to French with the short date to dd/MM/yyyy, the DB Tools Insert Data.vi writes incorrect values to database files.

Workaround: Convert timestamp data into strings before inserting into the database with the DB Tools Insert Data.vi.

Reported Version: 2011    Resolved Version: N/A    Added: 11/16/2012
389996

Return
Error 1 Returned from DB Tools Insert Data.vi
Error will be returned when writing array data to MS Access database, and column values are provided despite the database already having column values.

Workaround: N/A

Reported Version: 2011    Resolved Version: N/A    Added: 08/02/2013
Toolkit - Other
356420

Return
Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name
Robotics Wizard cannot load a manifest file in a folder with a Chinese character in the name

Workaround: Move the manifest file to a new location

Reported Version: 2012    Resolved Version: N/A    Added: 07/13/2012
412822

Return
Issues with the Biomedical Workbench when you downgrade the Biomedical Toolkit from 2013 to 2012
If you downgrade the Biomedical Toolkit from the 2013 release to the 2012 release, the Biomedical Workbench reports an error, and the positions of the application icons are incorrect.

Workaround: Delete the following files from the Biomedical Toolkit\Workbench\data directory to solve this problem:
Applications.dat, IconsData.dat, and SeekBtnData.dat.
This restores the Biomedical Workbench to the default setting. However, the Biomedical Workbench loses all application icons that you added to the Biomedical Workbench.

Reported Version: 2013    Resolved Version: N/A    Added: 07/09/2014
510649

Return
Changing an indicator into a constant within a Control & Simulation Loop breaks the VI
If you have an indicator within a Control & Simulation loop, changing that specific indicator into a constant can break the VI.

Workaround: Create a new constant instead of changing an indicator into a constant.

Reported Version: 2012    Resolved Version: N/A    Added: 08/03/2015
Toolkit - PID and Fuzzy Logic
514789

Return
Autotuning PID Online.VI Example Reads Proportional Gain 'NaN' with the Relay Technique.
When running the Autotuning PID Online.vi example, with the Relay Technique the "Tuned PID gains" output of proportional gain (Kc) shows "NaN" when the program believes tuning is completed by flashing "tuning completed?".

Workaround: Tune the individual terms first. Start by first tuning for P until the response is stable. Then continue to tune by switching to PI. Lastly, repeat the process for PID.

Reported Version: 2014    Resolved Version: N/A    Added: 02/04/2015
Toolkit - Report Generation
188911

Return
Control image alignment incorrect when "new report page" VI is used
When using Append Control Image to Report.vi, the alignment of some images are ignored when 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: Use 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)
Macro-Enabled Word or Excel templates (.dotm) file types are not handled by the Word and Excel implementations of the New Report.vi

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 Report Generation Toolkit 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
382455

Return
Microsoft Excel Template named cell range font size is overwritten
When appending cell data to named cell ranges from Microsoft Excel Templates, font size is always size 10pt.

Workaround: Use Excel Set Cell Font.vi to manually set the desired font for each named range.

Reported Version: 2012    Resolved Version: N/A    Added: 01/25/2013
391394

Return
Dates are Reversed by Excel Easy Table.vi on Non-US Languages
The month and day are reversed when exporting data to Excel for languages other than US-English. For example 03/02/2013 (3rd of February 2013) in LabVIEW is exported as 02/03/2013 and considered as 2nd of March 2013 by Excel.

Workaround: After investigations, we found that the problem was coming from NI_ReportGenerationToolkit.lvlib:Excel_Insert_Table.vi

Indeed in this VI, there are three followed Range property nodes for "Value2". When desactivated the last two, the issue is not here anymore.
However, when using this workaround, there are then problem with colors (??).

Reported Version: 2012    Resolved Version: N/A    Added: 08/02/2013
463584

Return
Append Horizontal Line to Report VI generates incorrect HTML code with width units in percent and decimal separator is set to ","

Workaround: Set ". "as decimal separator, or change the string format in the vi to '%.;%f%%'

Reported Version: 2014    Resolved Version: N/A    Added: 07/09/2014
472835

Return
The Save Report to File.vi requires the "report file path" terminal to be wired, but is not set as a required input
The VI will return Error -41003 when running the VI if the path is not wired or empty. This requirement is enforced in the VI itself, so it will not break the run arrow.

Workaround: Wire the file path of the report to the VI.

Reported Version: 2013    Resolved Version: N/A    Added: 07/09/2014
Toolkit - Simulation Interface
125072

Return
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
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
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 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
367752

Return
Model with Custom S-Function Returns Null Pointer Exception on Pharlap OS
If structs are defined inside a function on a Pharlap target the model will return a null pointer exception.

Workaround: Structs should be defined in static memory when using a Pharlap target

Reported Version: 2011    Resolved Version: N/A    Added: 11/16/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
420795

Return
When creating a custom LV project template with the Unit Test Framework .lvtest file, the new project will overwrite the original template when saving instead of creating a new instance with new files.

Workaround: N/A

Reported Version: 2012    Resolved Version: N/A    Added: 05/07/2014
466818

Return
Error 1527 will occur when running the example "Programmatically Run Tests from Projects.vi" referencing the example project "LV Class.lvproj."

Workaround: 1. Open LV Class.lvproj
2. Open by double clicking in Windows Explorer "Programmatically Run Tests from Projects.vi" (Now the VI will be in the LV Class.lvproj LabVIEW instance)
3. Modify "Programmatically Run Tests from Projects.vi" to run LV Class.lvproj
4. Run the VI

Reported Version: 2013    Resolved Version: N/A    Added: 05/07/2014
475037

Return
Enabling loop iteration parallelism in For Loops results lower code coverage than expected
A For Loop configured for parallelism is incorrectly counted as an uncovered diagram when calculating code coverage

Workaround: Turn off parallelism or set the for loop to "Allow debugging" for the code coverage test

Reported Version: 2011 SP1    Resolved Version: N/A    Added: 06/02/2014
471993

Return
Cannot create Unit Test for VI with control connected to the terminal and inside a tab control
This result in an error:
LabVIEW: Type Mismatch: Object cannot be cast into the specified type.

Workaround: If possible, do not have a control connected to the VI's terminal and inside a tab control.

Reported Version: 2010    Resolved Version: N/A    Added: 07/09/2014

Document last updated on 7/29/2015

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