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 sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 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.
| |||||
| 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 Trace 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
| |||||
| 281507 Return | Desktop Execution Trace Toolkit 2010 does dot 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
| |||||
| 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 development environment 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.
| |||||
| 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
| |||||
| 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
| |||||
| 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.
| |||||
| 380769 Return | Appending a one row table to a Word report causes an exception Appending a one row table to a Word report by wiring a 2D array with only one row to the Append Table to Report.vi causes the following error. Error -2146822347 occurred at Exception occurred in Microsoft Word: The requested member of the collection does not exist. Workaround: This issue was introduced in LabVIEW 2012, versions of the toolkit prior to 2012 do not reproduce the issue.
| |||||
| 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.
| |||||
| 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
| |||||
| 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.
| |||||
| 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.
| |||||
| 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/
| |||||
| 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
| |||||
| 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 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
| |||||
| 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.
| |||||
| 367888 Return | Hang when creating new test from specific VIs When creating a new unit test from certain VIs, the Unit Test Framework progress dialog may complete, but not disappear. This state causes LabVIEW to hang. Workaround: This issue was fixed in LabVIEW 2012 SP1. No changes to the Unit Test Framework were required.
| |||||
Document last updated on 1/28/2013