LabVIEW 8.5.x Known Issues
PrintOverview
This document contains the LabVIEW 8.5.x known issues. It includes the set of known issues that were included in the LabVIEW 8.5 readme as well as issues discovered since the release of LabVIEW 8.5 and 8.5.1. 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. Each Issue appears as a row in the table and includes an issue title, a brief description of the problem, any workarounds that might help resolve the issue, and the date the issue was added to the document (not the reported date).
The issues appear in two tables which each contain the same information:
- Known Issues by Category - This table sorts the issues by category. This table is recommended for use in helping determine if an issue has been reported to us, and is also recommended for users wanting to skim the document to learn of potential issues they may face with LabVIEW 8.5 during development.
- Known Issues by Date - This table is a flattened list of all issues sorted only by the date the issue was added to the document. Use this table to quickly locate the most recently reported issues.
The workarounds that appear in the document are not always tested by NI and are not guaranteed to resolve the issue. If a workaround refers you to the NI KnowledgeBase, please visit www.ni.com/kb/ and enter that KB number in the search field to locate the specific document. The brief description given does not necessarily describe the problem in full detail, and it is expected that you might want more information on an issue. If you would like more information on an issue feel free to contact NI and referencing the ID number given in the document. The ID number contains the current issue ID number as well as the legacy ID number (maintained for search ability). Use the current ID number when contacting National Instruments. You can contact us through any of the normal support channels including phone, email, or the discussion forums. See www.ni.com/ask to contact us. Also consider contacting us if you find a workaround for an issue that is not listed in the document so that we can add the workaround to the document.
The issues reported on this page are for all 8.5.x LabVIEW versions. Unless noted otherwise in the problem description, issues reported in this document apply to the 8.5 release. If an issue was fixed in a later release (such as 8.5.1) it will be noted in the workaround field of the issue. Please visit the NI webpage for more information on the latest LabVIEW 8.5.1 maintenance release, and the LabVIEW 8.5.1 Readme for a list of other issues fixed in this release. For other LabVIEW versions, see the LabVIEW page on ni.com for information.
Known Issues by Category
The following items are known issues in LabVIEW 8.5.x sorted by Category.
| ID | Known Issue |
|---|---|
| ActiveX and .NET | |
| 47857 3NHFKMSU |
ActiveX event unregistration did not execute properly after the VI goes idle If you register an ActiveX event, you must unregister the event explicitly. Otherwise, memory leaks might occur because the ActiveX control does not know that the client has disconnected. Workaround—Always unregister event using "Unregister For Events" node. Date Added—09/01/2007 Return to top |
| 66867 4D6EI7XX |
LabVIEW Throws ActiveX Error 3005 LabVIEW throws ActiveX error 3005 when executing property and invoke nodes that are passed an automation refnum. This is commonly seen in the Database Connectivity Toolset Execute Query VI. Workaround—Use the forward-only cursor type This issue has been fixed in LabVIEW 8.5.1. Date Added—09/12/2007 Return to top |
| 68471 4E485CF2 |
Loading VIs Containing References To .NET Assemblies in the GAC Results In Irresolvable Assembly Load Warnings In rare cases, you may receive warnings when loading a VI that calls .NET assemblies in the Global Assembly Cache (GAC): The .NET assembly expected to be at "C:\[PATH]\[VINAME].vi\<GAC>\[Assembly Name]" was loaded from "<GAC>\[Assembly Name]". You may also receive error 1003 when building an application with VIs that call .NET assemblies in the GAC, indicating "The VI is not executable." Opening the VIs will produce the load warnings mentioned above. Neither saving the VI nor reconfiguring the .NET nodes will resolve this. Workaround—1. Open the VI. 2. Delete all .NET nodes that reference the specified assembly(s). Also, delete any .NET refnum controls or indictors that reference the specified assembly(s). Note, this will break the VI. 3. Save and close the VI. 4. Reopen the VI and verify you do not get the GAC warning message. 5. Close and restart LabVIEW. 6. Open the VI. 7. Recreate the VI components you deleted in step 4. 8. Save and close the VI. 9. Open the VI (and if applicable, build the application) and verify you do not get the .NET load warnings. 10. Repeat this for all VIs and controls that contain .NET nodes or .NET refnums that reference the specified assembly(s). Note: When loading a VI that calls other VIs that you have already fixed, they will be re-broken in memory. Therefore, do not save the subVIs upon saving and closing the top-level VI. Doing so will re-break those subVIs. To be safe, apply your workaround with a top-down approach starting with the top-level VI and working down towards the subVIs. This issue has been fixed in LabVIEW 8.5.1. Date Added—12/05/2007 Return to top |
| 53386 4G51T2U1 |
VI saved without diagram breaks when it contains .NET reference Distributing a VI which contains .NET functionality (especially a callback function) fails when the option "Remove Block Diagram" is enabled. Workaround—Do not save the VI without a block diagram. This issue has been fixed in LabVIEW 8.6 Date Added—01/23/2008 Return to top |
| 105336 | Using an ActiveX Document control can crash LabVIEW Wiring an Activex Document Control (a special type of ActiveX control not commonly used with LabVIEW) with the 'create document' option to a property node, it crashes LabVIEW without any error notice. Workaround—This issue has been fixed in LabVIEW 8.6 Date Added—05/02/2008 Return to top |
| Building and Distributing LabVIEW Applications | |
| 65977 4CM921LJ |
Shortcuts Added in Installers Are Not Created Properly When creating an installer in LabVIEW 8.5 and creating shortcuts to files included in extra project folders, the shortcuts do not populate correctly in Application Builder, and if a file is selected, it may be linked to the wrong file on the install target. Workaround—More information on this problem, and the National Instruments recommended workaround can be found in KB 4EGEL6HY available on ni.com. If you need an alternative to the workaround presented in the KnowledgeBase, you can create separate folders for each file you need to have a shortcut created for instead of putting them all in one. This issue has been fixed in LabVIEW 8.5.1. Date Added—09/12/2007 Return to top |
| 66547 4D3CTJLV |
Cannot register DLL as a COM file in LabVIEW 8.5 when building an installer In the LabVIEW 8.5 Application Builder when building an installer, "Register COM" cannot be selected for a DLL in order to register it with Windows. Workaround—More information on this problem, and the National Instruments recommended workaround can be found in KB 4EGEL6HY available on ni.com. If you need an alternative to the workaround presented in the KnowledgeBase, you can build an installer which runs a bat file after installing to register your COM object (see the LabVIEW help for further information) or use System Exec.vi to register the DLL in the code This issue has been fixed in LabVIEW 8.5.1. Date Added—09/13/2007 Return to top |
| 65891 4CKERKC3 |
Building an application that contains a VI that has a static VI reference to itself throws Error 7 Building an application that contains a VI that has a static VI reference to itself fails throwing the following errors: "LabVIEW cannot find a file that is a dependency of a Startup, Exported, or Always Included VI. File Not Found: The missing file might be referenced by one of the libraries included in the build or by the file - test.vi." or "Error 7 LabVIEW: File not found. The file might have been moved or deleted, or the file path might be incorrectly formatted for the operating system. For example, use \ as path separators on Windows, : on Mac OS, and / on Linux. Verify that the path is correct using the command prompt or file explorer." Workaround—Don't use static VI referece, instead use the Open VI ref prim, passing it the the Current VI path constant. This issue has been fixed in LabVIEW 8.5.1. Date Added—09/27/2007 Return to top |
| 58644 4E9DE968 |
Application Builder does not allow Startup VIs to Use VI Setting for the Run When Opened option When configuring the Source File Settings for an executable build specification, checking Use VI Setting for the Run When Opened option and then saving the build specification does not retain the change. When opening the build specification, the Use VI Setting checkbox will be unchecked. Workaround—Configure whether or not the Startup VI will Run When Opened in the build specification (leave Use VI Setting unchecked). This issue has been fixed in LabVIEW 8.6 Date Added—10/17/2007 Return to top |
| 67286 4DH8D5QK |
Duplicate Files Displayed Within the Installer Properties in 8.5 When adding support files to an installer (build specs), files can appear to be duplicated within the Destination View Workaround—More information on this problem, and the National Instruments recommended workaround can be found in KB 4EGEL6HY available on ni.com. If you need an alternative to the workaround presented in the KnowledgeBase, you can use an auto-populating folder that points to the data folder (after building the executable). This issue has been fixed in LabVIEW 8.5.1. Date Added—10/18/2007 Return to top |
| 68528 4E2BHO5U |
Installer builder source files page shows wrong file names for class members When including override VIs from LabVIEW classes in an installer, the wrong file names are added to the Destination View. This issue also affects build specifications created in previous versions of LabVIEW imported to 8.5 (but not 8.5.1 or later). Workaround—More information on this problem, and the National Instruments recommended workaround can be found in KB 4EGEL6HY available on ni.com. This issue has been fixed in LabVIEW 8.5.1. Date Added—10/18/2007 Return to top |
| 99475 | Error 1 on first build of application when using custom error codes When you create custom error codes and select the "Copy error code files" when building an executable, the build may fail on the first attempt with an Error 1. Workaround—After seeing the error, build the application again for a successful build. This issue has been fixed in LabVIEW 8.5.1. Date Added—04/01/2008 Return to top |
| 112751 | Build Errors when VI Names are Identical but Capitalized Differently A build error occurs when building applications (executables) with VIs (including Dependencies) that have identical names and only differ in their capitalizations. The build ends up being unsuccessful with the Possible Reasons being "Error Copying Files". The VI listed in the error window is the VI which has the similar name. Workaround—Use LabVIEW Search (Edit Menu»Find Project Items) to find the VIs which have the same name and rename them to make the capitalization identical. Date Added—07/29/2008 Return to top |
| Controls and Indicators | |
| 50061 42NAR8SA |
Center justified tables display improperly when overlapping with the front panel origin When you add a table control to the front panel so that it overlaps with the vertical origin of the front panel, LabVIEW displays center justified columns off center when you type text. The cells appear to float or move horizontally until aligned with the vertical origin. Workaround—Move the table away from the front panel's vertical origin. Date Added—09/01/2007 Return to top |
| 51311 477DKPBQ |
LabVIEW does not maintain child-only item setting when dragging an item within a tree If you have a tree item with the child-only setting, and then drag it within the tree, LabVIEW loses the child-only setting. Workaround—Use tree events to (1) get the child-only flag setting when the user begins a drag, and (2) reset the child-only flag after completing a drop. Date Added—09/01/2007 Return to top |
| 52297 4AIFC0R0 |
Internal error related to locked tab control at fpsane.cpp line 369 and line 367. If you lock a tab control that is already locked using Group»Lock, you might see two internal errors and LabVIEW may crash. Workaround—Do not lock a control that is already locked. Date Added—09/01/2007 Return to top |
| 88787 3J0A89J1 |
Zero element clusters not reported as an error for Type Defs/Custom Controls Type Defs should not contain zero element clusters, but LabVIEW does not report an error if you have a type def with zero elements. Workaround—Do not save a zero element cluster. Date Added—09/01/2007 Return to top |
| 91672 477M7K00 |
Large amounts of data in combo box can appear to hang LabVIEW. If you place a large amount of data in a combo box, on the order of megabytes, LabVIEW appears to hang by taking a long time to calculate wrapping. Workaround—N/A Date Added—09/01/2007 Return to top |
| 66461 4CUGA5RK |
Programatically Increasing Stacked Plot Chart Legend at Run-Time Crashes LabVIEW If you programmatically increase the size of the plot legend through the property LegNumRows when using the stacked plot option of a waveform chart, often times, LabVIEW will crash with a DWARN in alloc.cpp line 655 or a DABORT in ThEvent.cpp line 190. Workaround—Two potential workarounds: 1. If you write to the plot before you change the number of plots visible, then LabVIEW crashes less often. It appears to crash most often when you try to increase the number of plots before LabVIEW has allocated memory for the additional plots. If you are changing the number of plots while LabVIEW is writing to the indicator in a loop, it appears that it still crashes pretty often. This is only a partially viable solution, and only works if you can stop updating the chart while it resizes. 2. Place the stacked plot in another VI and show it on the front panel via a sub-panel. Then use VI server to programmatically update the chart. Another workaround from a customer: Since it is ok to reduce the number of displayed plots on a chart (but not ok to incrrease it), initialize the program with maximum expected number of plots and then allow the user to reduce from there. If the user wants to increase the number of plots, they must restart the program. This issue has been fixed in LabVIEW 8.5.1. Date Added—09/10/2007 Return to top |
| 66776 4CUDBIVB |
Cannot Save Variant Data Returned by the LabVIEW ActiveX Server as a Control/Indicator's Default Value. Cannot save variant data returned by the LabVIEW ActiveX Server as a control or indicator's default data. Saving the VI returns LabVIEW: Memory is full. Cannot save VI "[name of VI]". LabVIEW Save error code 10: Default data space.Workaround—Use the VI Server interface instead. This issue has been fixed in LabVIEW 8.5.1. Date Added—09/10/2007 Return to top |
| 64101 4B1CC3V9 |
Scrolling graph's cursor legend corrupts front panel redrawing. Controls and Indicators on front panel have become either totally invisible, distorted, or corrupt. This can happen if your front panel has a waveform graph with the cursor legend visible. If your graph has multiple cursors and a scroll bar in the legend the front panel image can become corrupt if you have scrolled to the very bottom of the cursor legend's list of cursors. Workaround—Because this problem is due to the cursor legend, to fix the problem, replace any waveform graphs with another waveform graph (right click graph and click replace), then minimize and restore the LabVIEW front panel window and repeat for any waveform graphs which had a visible cursor legend. After your controls are restored, expand the cursor legend such that there is enough room to display your cursors without a scroll-bar. This issue has been fixed in LabVIEW 8.5.1. Date Added—09/11/2007 Return to top |
| 66538 4CU3C5QW |
Updating a Typedef that Contains a Refnum that Contains a Cluster can Make LabVIEW Crash Updating a typedef that contains a refnum to a cluster can make LabVIEW crash. Workaround—This issue has been fixed in LabVIEW 8.5.1. Date Added—09/11/2007 Return to top |
| 41148 4D1JQKJ7 |
Unable to change the Display Format for Y-axis in a dynamic data type Waveform Chart/Graph The display format for the y-axis cannot be changed in a waveform chart/graph if it is configured to receive the dynamic datatype (i.e. it will be blue on the block diagram). Workaround—Configure the y-axis formatting when the graph is not in dynamic datatype mode by deleting any dynamic data wires and rewiring with a waveform. Then you can rewire with the dynamic data. Date Added—09/13/2007 Return to top |
| 67199 4D97A7ST |
LabVIEW crashes when deleting a scale that has a cursor attached to the last scale in the scale list With two scales on a waveform graph, when you delete a scale that has a cursor attached to it, LV crashes. Workaround—To avoid this problem, retarget a cursor to the appropriate plot before deleting the scale. This issue has been fixed in LabVIEW 8.5.1. Date Added—09/13/2007 Return to top |
| 41224 4DA24FXR |
Cannot display extended types on intensity plots In LabVIEW 8.0 and newer, when you wire extended precision type numbers to an intensity graph or chart you get a different looking plot than with the same double-precision numbers. Workaround—Use the data type conversion functions to convert your data to double precision representation. Date Added—09/26/2007 Return to top |
| 41596 4DK867QQ |
Right-Clicking on Intensity Chart/Graph Scale Legend Crashes LabVIEW Righ-Clicking on Intensity Chart/Graph Scale Legend Crashes LabVIEW. Workaround—This issue was resolved in LabVIEW 8.5.1. Date Added—09/26/2007 Return to top |
| 67400 4DHETOCB |
Enum Property Node RingText.Text Crashes LabVIEW Writing a value to the RingText.Text property of an enum control causes LabVIEW to crash in either fpsane.cpp line 367 or FPDCO.cpp line 1838. Workaround—Use a text ring control instead of an enum. This issue has been fixed in LabVIEW 8.5.1. Date Added—10/02/2007 Return to top |
| 68620 4E3I4TVB |
Digital Waveform Graph Cursor Legend Does Not Show Correct Y-Values Digital Waveform Graph Cursor Legend Does Not Show Correct Y-Values Workaround—This issue has been fixed in LabVIEW 8.5.1. Date Added—10/22/2007 Return to top |
| 43116 4FQ6JR1G |
Duplicate Case Crashes with "Delete/Copy panel terminals from diagram" Disabled The Block Diagram option "Delete/Copy panel terminals from diagram" allows front panel terminals to be copied/created by copying the block diagram terminal. If you disable this and ask LabVIEW to duplicate a case that has a terminal, LabVIEW crashes. Workaround—Enable the "Delete/Copy panel terminals from diagram", duplicate your diagram then delete the undesired terminals or use the Add Case instead. This issue has been fixed in LabVIEW 8.6 Date Added—12/03/2007 Return to top |
| 70707 4FF2R30G |
Crash When Passing a True to a SubVI Boolean with "Latch Until Released" Mechanical Action LabVIEW 8.5 crashes when you pass a boolean value to a SubVI where the receiving control is set to mechanical action "Latch Until Released". Workaround—Set mechanical action in SubVI control to anything but "Latch Until Released" This issue has been fixed in LabVIEW 8.5.1. Date Added—12/03/2007 Return to top |
| 37476 44H8J3ZP |
Digital Display Legend Doesn't Adjust for Number of Plots in Executable In the LV Development environment, when the number of plots are changed dynamically, the Digital Display for each plot is dynamically added or removed from the legend. However, when run in an executable, the plot glyph is updated correctly, but the digital displays is not added or removed when the number of plots is changed dynamically. Workaround—Please refer to NI KB 2I6H445F for more information about this problem and workaround. Date Added—12/12/2007 Return to top |
| 59242 4GB6DJ0G |
LabVIEW 8.5 crash when replacing modern waveform chart or graph with visible scrollbar to classic waveform chart or graph When you enable the visible scrollbar in the graph or chart's plot legend, and then replace the chart or graph with a classic control or indicator through the right-click menu LabVIEW crashes. Workaround—Disable the scrollbar before replacing the chart or graph. This issue has been fixed in LabVIEW 8.6 Date Added—12/17/2007 Return to top |
| 43109 4FRF0826 |
Cannot customize plot legend with background image in LabVIEW 8.6 You cannot configure a plot legend with a custom background image in LabVIEW 8.6. Workaround—Make the color of the plot legend transparent, and place the image behind it. This only works if your plot legend remains a fixed size in a fixed location. Date Added—01/23/2008 Return to top |
| 59426 4GQA4KNO |
Sweep Chart with Large History Length Crashes LabVIEW Sweep charts configured with a large history length (multiple thousands of points) and an autoscaling X axis will cause LabVIEW to crash after the first sweep. Decreasing the chart history length afterwards does not prevent the crash from occurring. A new chart must be created and configured. Workaround—Use either the Strip or Scope Chart update methods or use a smaller Chart History Length. This issue has been fixed in LabVIEW 8.6 Date Added—01/23/2008 Return to top |
| 45133 4I0976O4 |
The coercion of an enum through its digital display behaves differently in the development environment than in a LabVIEW executable. The coercion of an enum through its digital display behaves differently in the development environment than in a LabVIEW executable. Neither produce an out of range value, but one coerces to the last entry in the enum, the other leaves the enum unchanged. Workaround—Use an event structure to capture value change filter events and restore the enum to the value you choose. You can also disable the digital display for the enum. Date Added—02/22/2008 Return to top |
| 103297 | Changing a Text Ring Control to Fixed Point Representation Crashes LabVIEW Changing a Text Ring Control to Fixed Point Representation Crashes LabVIEW. Workaround—This issue has been fixed in LabVIEW 8.6 Date Added—06/30/2008 Return to top |
| 100580 | Dropping control references may cause Data Change event for XControl Dropping a control/indicator reference onto a VI that is hosting an XControl, whose data type is an array, will cause a Data Change event to be handled by the facade VI of the XControl. Workaround—N/A Date Added—07/09/2008 Return to top |
| 118949 | Tab control local variables generate value change events when you use a multi-column listBox A value change event is generated when a Tab Control local variable's value is changed in an Event Structure that was triggered by a double-click/ value Change on a multi-column listBox.. Workaround—Use Value Property Node for the Tab Control instead of Local Variable to change the Tabs. Date Added—07/10/2008 Return to top |
| 119444 | Mulicolumn listbox format lost on upgrade A Multicolumn listbox created in LV 7.1 may lose its format when opened in LV 8.5 or later. Column headers lose their 3D appearance and font formatting might be lost. Workaround—Replace the Listbox and recreate all customizations Date Added—07/12/2008 Return to top |
| DataSocket | |
| 37020 4A37JOV9 |
DataSocket functions do not handle Domain security correctly. The DataSocket Open function returns error 1179 for any attempt to connect to a shared variable that has security enabled, even if the correct user is logged in. Workaround—Drop a shared variable node on the block diagram and run the VI once; you can delete the variable node and DataSocket security will continue to work. Date Added—09/01/2007 Return to top |
| 46630 2VO0SF00 |
DataSocket/OPC Leaks Memory when repeatedly using ActiveX VIs to perform open-write-close If you call the DataSocket Open, DataSocket Write, and DataSocket Close functions in succession repeatedly, LabVIEW leaks memory. Workaround—To correct this problem, call the DataSocket Open function once, use the DataSocket Write function to write multiple times, and then use the DataSocket Close function. Date Added—09/01/2007 Return to top |
| 46965 38ECIGX3 |
DataSocket HTTP protocol does not work in a LabVIEW built DLL You cannot use the http protocol with the DataSocket VI and functions in LabVIEW-built shared libraries. Workaround—This issue has been fixed in LabVIEW 8.6 Date Added—09/01/2007 Return to top |
| 47103 3BS49JS8 |
dialog box and open datasocket conflict If a dialog box is already open, you cannot use the DataSocket Open function. Workaround—N/A Date Added—09/01/2007 Return to top |
| 47977 3OLE2573 |
DataSocket and Fixed Size Array Do Not Work You cannot use front panel DataSocket data binding with fixed-sized arrays. Workaround—Uncheck autopreallocate arrays and strings in the VI properties execution category for all VIs not intended to run on an FPGA. Date Added—09/01/2007 Return to top |
| Documentation | |
| 118200 | Discrepancy in TCP Read help There is a problem with the documetation about operating a native LabVIEW TCP Read function in CRLF mode. The LabVIEW help says if you request n bytes and there is no CRLF in the n bytes, the function should timeout, return no bytes, and return an error. This is not what happens - if there are at least n bytes available at the port, the function returns the n bytes and no error regardless of whether there is a CRLF in the string. If there is a CRLF in the string, it just returns the string up to and including the CRLF as advertised. If there are less bytes at the port than the bytes requested, it times out and returns an error. Workaround—N/A Date Added—07/07/2008 Return to top |
| External Code | |
| 56773 3ZJCNQMQ |
Dynamically loading LabVIEW-built DLL in UI thread hangs LabVIEW If you configure a Call Library Function Node to dynamically load a LabVIEW DLL (place a checkmark in the Specify Path on Diagram checkbox on the Function page of the Call Library Node configuration dialog box) and you select Run in UI thread in the Thread control, LabVIEW hangs when the node executes and attempts to load the library. If you configure the Call Library Function Node to call a DLL written in C with these same settings, LabVIEW works correctly. Workaround—This issue has been fixed in LabVIEW 8.6 Date Added—09/01/2007 Return to top |
| 59247 4GBEB2V9 |
LabVIEW crash when calling DLL using Maximum Error Detection When maximum error detection is enabled in your Call Library Function Node, if you pass a string to a DLL and you don't specify a minimum size, LabVIEW can crash, return bad data, and/or an error message. Workaround—Use no error checking or default error checking on your DLL, or set a minimum string size through the Call Library Function configuration dialog. This issue has been fixed in LabVIEW 8.6 Date Added—12/19/2007 Return to top |
| File I/O | |
| 47436 3IKBUP99 |
Zip build provider and Zip VIs do not support multi-byte character encodings. The Zip build provider and the underlying Zip API provided in the File I/O palette do not support paths with multibyte character encodings. Some upper or lower bytes of multi-byte characters decode into disallowed ASCII characters when not configured correctly. Workaround—Ensure that the full filepath to zipped files does not contain multi-byte characters. Date Added—09/01/2007 Return to top |
| 47819 3N68LE00 |
2GB file size limit of datalog files The maximum size of datalog files is 2 GB. Workaround—N/A Date Added—09/01/2007 Return to top |
| 53421 4G9A4D00 |
Calling TDMS Read Multiple to Read String Data Causes Memory Leak A memory leak will occur when calling TDMS Read multiple times to read string data. This can happen if calling multiple instances of TDMS Read or are calling TDMS Read in a loop. Workaround—Create a property for each data value and store the string value as the property value. This issue has been fixed in LabVIEW 8.6 Date Added—10/25/2007 Return to top |
| 69273 4EM9CC70 |
Calling TDMS Read Multiple Times to Read String Data Causes Memory Leak A memory leak will occur when calling TDMS Read multiple times to read string data. This can happen if calling multiple instances of TDMS Read or are calling TDMS Read in a loop. Workaround—Create a property for each data value and store the string value as the property value. This issue has been fixed in LabVIEW 8.5.1. Date Added—10/25/2007 Return to top |
| 58848 4F5HD99A |
Open/Create/Replace Datalog.vi does not show confirmation message when "replace or create with confirmation" is selected Open/Create/Replace Datalog.vi does not show confirmation message when "replace or create with confirmation" is selected Workaround—Write custom code to first detect whether or not the file exists and give a custom dialog. This issue has been fixed in LabVIEW 8.6 Date Added—12/17/2007 Return to top |
| Functions, VIs, and Express VIs | |
| 37575 3PD8N0M8 |
LabVIEW uses large amounts of memory when reading an entire wave file at once The Sound File Read VI uses large amounts of memory to read an entire .wav file. Workaround—Read the data from the .wav file in sections rather than in one large file. Date Added—09/01/2007 Return to top |
| 39161 401FEQTL |
The device ID input of the Play Sound File VI does not work on Windows On Windows, LabVIEW ignores the device ID input of the Play Sound File VI. This VI plays sound only on the default sound card. Workaround—Use the Sound Output Configure VI and the Sound Output Write VI with the Sound File Open VI and the Sound File Read VI or the Sound File Simple Read VI. Refer to the Sound File to Sound Output example VI for an example of this workaround. Date Added—09/01/2007 Return to top |
| 41530 4DJFJM00 |
Advanced Storage VIs Do Not Work in a LabVIEW Development System with a Different Language If you move the Advanced Storage VIs to a LabVIEW development system with a different language, the VIs do not work because the object types and property names do not match the names in other languages. Workaround—To correct this problem, use the internal, language-independent object types and property names. Refer to KnowledgeBase 377C3NHB at ni.com for more information about correcting this problem. Date Added—09/01/2007 Return to top |
| 41531 4DJFK100 |
If you create a new, untitled VI while using the Storage VIs, the numbering of the untitled VI might be inconsistent. If you create a new, untitled VI while using the Storage VIs, the numbering of the untitled VI might be inconsistent. Workaround—N/A Date Added—09/01/2007 Return to top |
| 47891 3NRGJTI7 |
Sound Output Set Volume VI doesn't set the volume on a per-channel basis The Array instance of the Sound Output Set Volume VI does not use the volume input to set the volume on a per-channel basis. Instead, this VI uses the first element of the volume input as the sound level for all channels. Workaround—N/A Date Added—09/01/2007 Return to top |
| 48016 3P7CBB4Q |
Unsigned int32 loses value in formula node when you write to the most significant bit If you wire a hex value greater than x7FFFFFFF as an unsigned, 32-bit integer to a Formula Node, LabVIEW coerces the value to 0. Workaround—Use signed 32-bit integers instead of unsigned 32-bit integers in the formula node. Date Added—09/01/2007 Return to top |
| 50420 44CG88SN |
Update the Pulse Transition Measurement Express VI The terminology and measurement definitions for the Transition Measurements VI comply with IEEE Standard 181-2003, IEEE Standard on Transitions, Pulses, and Related Waveforms. However, the Timing and Transition Measurements Express VI does not comply with this IEEE Standard. Workaround—The Slew rate refers to the transition slope. The Preshoot refers to the pre-transition undershoot (rising pulse) or the pre-transition overshoot (falling pulse). The Overshoot refers to the post-transition undershoot (rising pulse) or the post-transition overshoot (falling pulse). Date Added—09/01/2007 Return to top |
| 51084 4709CDDV |
Match Regular Expression function might cause stack overflow with some inputs Certain regular expressions might cause a stack overflow on large input strings. Some regular expressions might recurse repeatedly while LabVIEW attempts to match a large string that might overflow the stack eventually. For example, the regular expression (.|\n)*A and a large input string might cause LabVIEW to crash. Workaround—Rewrite the regular expression to avoid recursion. For example, to avoid recursion you can rewrite the regular expression (.|\n)*A as (?s).*A. The (?s) notation indicates that a period (.) matches new lines. You also could rewrite the expression more efficiently as [^A]*A. Date Added—09/01/2007 Return to top |
| 52263 4AJA41TQ |
Some operations on integer waveforms lose dt value Some functions, such as Absolute Value and Logarithm Base 10 operate as you expect with DBL Waveforms, but when you apply the same functions to an I16 waveform, for example, the Absolute Value function works as you expect while the Logarithm Base 10 function loses the sampling interval dt value. LabVIEW resets the sampling interval dt value to 1.00. Workaround—Extract the Y-array of the waveform and perform the needed operations on Y before re-building the waveform. Date Added—09/01/2007 Return to top |
| 54942 41CE6I39 |
Storage VIs do not recognize DIAdem date/time channels The Storage VIs do not recognize the date/time format used in DIAdem date/time channels. When you use the Storage VIs to read data from a DIAdem date/time channel, LabVIEW converts the date/time data to a double-precision, floating-point number that represents the number of seconds since 01/01/0000. Workaround—After LabVIEW converts the DIAdem date/time data to a double-precision, floating-point number, you can convert the double-precision, floating-point number to a more meaningful value. Date Added—09/01/2007 Return to top |
| 90497 3YJ87JCM |
Write to Clipboard Method takes minutes and a lot of CPU If you try to copy a large amount of data from LabVIEW to the clipboard, LabVIEW slows significantly and might become unresponsive. Workaround—N/A Date Added—09/01/2007 Return to top |
| 92298 4AOEJ5F2 |
FP:Get Image, FP:Get Image Scaled, Print:VI to HTML, Print:VI to RTF, and Print:VI to Printer methods do not properly generate off-screen cluster images These methods generate an incorrect image of the front panel when it contains off-screen clusters and the contents of all off-screen clusters appear blank in the generated image. This issue only affects the FP:Get Image and FP:Get Image Scaled methods when the Visible Area Only parameter is set to False. Workaround—This issue has been fixed in LabVIEW 8.6 Date Added—09/01/2007 Return to top |
| 65534 4CFADPDX |
Replace Array Subset Broken for 3D (or Higher) Arrays Replacing a subset of an array with more than 2 dimensions (i.e. a 3D array) causes a broken wire and the VI to break. 1D and 2D arrays do not have this problem. Workaround— This issue has been fixed in LabVIEW 8.5.1. Date Added—09/11/2007 Return to top |
| 65723 4CKGJ6Q7 |
UDP Write Hangs LabVIEW When Called in a Loop with a High Loop Rate Writing data at high rates using the UDP Write function within a loop can cause LabVIEW to hang and display a Resetting VI dialog. The rate at which UDP Write can be called in a loop is dependent upon the size of the data being written during each call to the function. Workaround—Use the Wait until next second multiple function to control the loop rate and therefore how fast UDP packets are written. This issue has been fixed in LabVIEW 8.5.1. Date Added—09/11/2007 Return to top |
| 67753 4DO78989 |
Compiler error when using some strings with Max & Min When using sub-strings (string output of some string functions such as "Match Pattern") with the Max & Min function, compiler error "copy cvt, csrc=0x3F" is generated and the VI fails to compile with broken run arrow and message "VI Failed to Compile." Workaround—Insert an always copy primitive between the wire between the "before substring" output of the Match Pattern function and the input of the Max & Min function This issue has been fixed in LabVIEW 8.5.1. Date Added—10/04/2007 Return to top |
| 67948 4DP855N3 |
Write to Binary File function writes incorrect data when writing manipulated arrays When an array of data is written to a binary file, if the array is manipulated in a way that produces sub-arrays to be written to the file (such as through transposing the array or through indexing sub-arrays out of a multidimensional array) the data written to file can be incorrect. Workaround—If you do any array operations such as index array or transpose array, before writing the new array to the write binary file primitive, insert an Always Copy primitive on the wire. A copy will be made, but it will write the correct values to the file. Alternatively, you can use Flatten to String function to flatten data into a string before writing to file. This issue has been fixed in LabVIEW 8.5.1. Date Added—10/04/2007 Return to top |
| 68695 4E4ERDTP |
Compiler Error in VI with compound arithmetic primitive taking array and float inputs A VI containing a compound arithmetic function with 4 or more inputs will cause LabVIEW to be unable to compile with "VI Failed to Compile" error if the inputs to the compound arithmetic function are a branched floating point number, and a branched array wire that has been manipulated (such as through a mathematical function like Cos). Workaround—Use an always copy primitive on one of the wires branching from the floating point input (as opposed to an array input). This issue has been fixed in LabVIEW 8.5.1. Date Added—10/05/2007 Return to top |
| 68217 4DPRHHV |
Write To Measurement File Express VI in a loop always resets each iteration causing multiple channels to be written Writing data to a TDM file with the Write To Measurement File VI in a loop resets the file each loop iteration creating multiple channels of data in LabVIEW 8.5. Workaround—This issue has been fixed in LabVIEW 8.5.1. Date Added—10/11/2007 Return to top |
| 58548 4E78KBXE |
The Split Signals function does not properly generate output terminals When expanding the Split Signals function to allow for multiple output signals, the Split Signals function does not properly generate output terminals to allow for wire connections to those output signals. Workaround—Grow the Split Signals function up from the top instead of down from the bottom. This issue has been fixed in LabVIEW 8.6 Date Added—10/15/2007 Return to top |
| 68979 4EFEMMWB |
Non-Functional Formula Express VI for Base Development System In the base development system for LabVIEW 8.5 the Formula Express VI appears as a empty icon and is non-functional. This Express VI is functional in the full and professional Development systems. This can also result in LabVIEW load error code 37 if attempting to open a VI with the Formula Express VI that is saved in a previous LabVIEW version. Workaround—Use LabVIEW in evaluation mode for 30 days or use the following work around: In the Functions Palette select "Select a VI..." and choose the function found at: "C:\Program Files\National Instruments\LabVIEW 8.5\vi.lib\express\express arith-compare\FormulaBlock.llb\Ex_Inst_Formula.vi" In order to permanently add this to the Functions Palette, point the user to the LabVIEW Help Topic Editing a Palette Set. Note: Users should be aware that if they migrate to using the different version of the Express VI, they may not get the improved behavior on a future upgrade as we continue to improve this VI. This issue has been fixed in LabVIEW 8.5.1. Date Added—10/17/2007 Return to top |
| 68232 4E1B60P2 |
Unzip.vi returns "Error code 2, System Exec.vi." when trying to unzip The Unzip.vi located in the Zip palette of Labview 8.5 throws an error when trying to extract the content of some zip files. Workaround—This issue has been fixed in LabVIEW 8.5.1. Date Added—10/22/2007 Return to top |
| 68790 4EB7N9NK |
Compiler error when constant wired to TCP write connection ID LabVIEW gives the compiler error "bad dsoffset, dso=-1" when a connection id constant is wired to the connection ID terminal of the TCP write primitive. Workaround—This issue has been fixed in LabVIEW 8.5.1. Date Added—10/22/2007 Return to top |
| 68872 4EBC79AG |
Dabort crash in MemoryManager.cpp error 406 when feedback node handles subarray or substring types When an array of data or string is wired to a feedback node, if the array or string is manipulated in a way that produces sub-arrays (such as through transposing the array or through indexing sub-arrays out of a multidimensional array) or substrings (such as through Split/Search String) LabVIEW crashes with an error in MemoryManager.cpp line 406. Workaround—Replace feedback nodes with shift registers, or insert always copy function between transpose array and feedback node terminal. This issue has been fixed in LabVIEW 8.5.1. Date Added—10/22/2007 Return to top |
| 69463 4EH5G5TQ |
LabVIEW crashes when exporting a graph or chart as BMP or EMF image to clipboard in a LabVIEW executable. A LabVIEW Executable will crash when exporting an image of an XY graph, waveform graph, or waveform chart, as a BMP or EMF format. VIs doing the same thing in the development system do not crash. Workaround—This issue has been fixed in LabVIEW 8.5.1. Date Added—10/29/2007 Return to top |
| 53130 4EM7J8WQ |
The Formula Express VI Can Produce Incorrect Results When All Inputs Are Integers The numeric representation of a Formula Express VI's 'Result' output terminal is dependant on the representation of the inputs, regardless of the mathematical operations used. For example, if the inputs to the Formula Express VI are all integers and the mathematical operation is division, the result will also be an integer. This is inconvenient when using divisions, logs, etc. as LabVIEW normally coerces inputs in numerical operations when necessary. Workaround—Insert a 'To DBL Precision Float' in the wire of any of the formula inputs to change the 'Result' representation to DBL. This issue has been fixed in LabVIEW 8.6 Date Added—11/16/2007 Return to top |
| 69820 4ETCLK2A |
LabVIEW 8.5 can crash due to out of range values wired to the DisabledItems[] property node for rings and enums The DisabledItems[] property for named numeric types (Rings and Enums) accepts an array of integers which represent indices to disable. If this array is empty or contains negative numbers LabVIEW memory can be corrupted which can cause either an immediate crash, a delayed crash, or undefined behavior. Workaround—Instead of wiring in an empty array or an array with a negative number to the disabled items (which can cause a crash), wire in an array with an element larger than the highest index of the ring whose disablesitems[ ] is being set. This will enable all the ring items, but since there is no valid disable index, it will leave the ring enabled. This issue has been fixed in LabVIEW 8.5.1. Date Added—11/19/2007 Return to top |
| 70577 4FFFDF7U |
Number To Fractional String Uses Incorrect Precision With Doubles When passing a double (DBL) number to the precision input of the Number To Fractional String, it appears the output string uses a precision of 0. When coercing the double to an I32 before passing it to the precision input, the output string uses the specified precision. Workaround—Coerce the DBL value to an integer, using a To Long Integer function, before passing it to the precision input terminal. This issue has been fixed in LabVIEW 8.5.1. Date Added—11/19/2007 Return to top |
| 59547 4H6HORHZ |
"Quotient and Remainder" function improperly coerces to I64 and can return incorrect value "Quotient and Remainder" function coerces values to highest bit width. If you are dividing an I64 by an I32 the 32 bit number shows a coercion but the quotient returned is incorrect. If you convert using the To Quad Integer the quotient is computed correctly. Workaround—Convert non 64-bit integers to the I64 type using the "to quad integer" function before wiring to the "quotient and remainder" function. This issue has been fixed in LabVIEW 8.6 Date Added—02/22/2008 Return to top |
| 50327 4436ATN3 |
To More Specific Class to an XControl returns an error in built applications To More Specific Class to an XControl returns an error in built applications even when the cast is valid. Workaround—Use a generic Typecast node instead. This issue has been fixed in LabVIEW 8.6 Date Added—06/20/2008 Return to top |
| 94566 | Probes on a cluster containing an IMAQ image always fail to load Right-clicking to create a probe on a cluster that contains an image returns error "Failed to load or create probe". This worked in LabVIEW 8.0 and 8.2. Workaround—Create custom probe without IMAQ image. Date Added—06/20/2008 Return to top |
| 96735 | Wiring Invalid File Refnum to Deny Access function crashes LabVIEW When using the Deny Access primitive, if an invalid reference number (including a null reference constant) is passed to this reference input of the function, it will crash LabVIEW. Workaround—Ensure an invalid reference number isn't passed to this VI. Date Added—06/26/2008 Return to top |
| 101959 | LabVIEW crash when comparing string to a control refnum of a sub-vi LabVIEW crash when comparing string to a control refnum of a sub-vi using an equal or not equal primitive for the comparison. In previous versions the VI would give a broken arrow for this operation. Workaround—Use the property node to get the Label.Text instead of comparing the control refnum directly. This issue has been fixed in LabVIEW 8.6 Date Added—07/08/2008 Return to top |
| 118373 | Subtraction and subsequent Add or Subtract operations using 2D array types might produce incorrect results with 64-bit integer data types Adding or subtracting 2D arrays when using array controls (as opposed to constants) with I64 or U64 representation can return incorrect results. This also affects any other add/subtract operation that maybe wired to one of the array controls. However, independently the add function is not affected. This occurs in LabVIEW 8.0 and 8.2 as well. Workaround—This does not happen in all cases; if the 2D array is wired through functions or if other operations occur before the initial subtraction the problem may not exist. If you test the code and discover the problem, multiply the second input to the subtract by -1 and replace your subtract with an add primitive. Add a note to your code where this operation is done so that future reviewers of you code understand why you implemented this workaround. Date Added—07/08/2008 Return to top |
| 118106 | Variant To Flattened String and Flattened String To Variant Do Not Support Fixed Point Data Type The Fixed Point data type is not supported by the Variant To Flattened String and Flattened String to Variant functions. You may see a crash when trying to unflatten this datatype in conjunction with an empty fixed point array. Workaround—Either use a supported datatype or do not use the Variant. Date Added—07/11/2008 Return to top |
| Import Shared Library Wizard | |
| 36889 4999TKGI |
Import Shared Library wizard cannot recognize a function if the function declaration contains a default value In the Import Shared Library wizard, LabVIEW cannot recognize a function in a header (.h) file if the function declaration contains a default value for a function parameter. Workaround—Remove the default values of parameters in the header file. Instead, add the default values to the Configure VIs and Controls page of the Import Shared Library wizard. Date Added—09/01/2007 Return to top |
| 37271 45I650CI |
The Import Shared Library wizard does not support macros inside of function declarations The Import Shared Library wizard does not support macros inside of function declarations in the header (.h) file. Workaround—Move any macros outside of function declarations in the header file. Date Added—09/01/2007 Return to top |
| 37448 44CEN7MQ |
Import Shared Library wizard cannot recognize multiple function declarations in a row If you have a header (.h) file that contains multiple function declarations in a row, the Import Shared Library wizard recognizes only the first function declaration. Workaround—Separate the function declarations in the header file. Date Added—09/01/2007 Return to top |
| 39823 4AIGSL00 |
The progress bar in the Import Shared Library wizard appears to hang When you use the Import Shared Library wizard, LabVIEW displays a progress bar. This progress bar might appear to hang, even though the tool is working correctly. Workaround—Wait until the generation finishes. Date Added—09/01/2007 Return to top |
| 64258 4B9MOUMX |
Import Web Service wizard fails to expand the .NET reference when the reference is in an array The Import Web Service wizard expands the .NET reference and returns all its properties. However, when the .NET reference is in an array, it returns only the reference, not its properties. Workaround—Use the Index Array function and a Property Node to get the properties of the .NET reference. Date Added—09/01/2007 Return to top |
| Installation and Activation | |
| 67845 4DJE9C3A |
LV attempts to repair itself after a later version of LabVIEW is uninstalled If you uninstall LabVIEW 8.5 and a previous version of LabVIEW remains on the system, the previous version of LabVIEW might try to repair itself the next time you open it. The repair process might remove any patches you installed for that version of LabVIEW. Make sure to reinstall any patches you have on the system after the repair finishes. Workaround—Refer to KnowledgeBase 36ICL128 at ni.com for more information about correcting this problem. Date Added—09/01/2007 Return to top |
| 67931 4DJEJ200 |
Windows Explorer crash when opening LLB If you install LabVIEW and then install a previous version of LabVIEW on the same computer, Windows Explorer crashes if you use Windows Explorer to perform an operation on an LLB. Workaround—In the previous LabVIEW version installed, select Tools»Options, select Environment from the Category list, remove the checkmark from the Enable Windows Explorer for LLB files checkbox, and click the OK button. Display the same Environment Options page again, place a checkmark in the Enable Windows Explorer for LLB files checkbox, click the OK button, and restart the computer. Date Added—09/01/2007 Return to top |
| LabVIEW Environment | |
| 46449 2JQ91R6I |
LabVIEW's Hierarchy Window does not show the labels of the VI's for print out When you print the VI Hierarchy window, LabVIEW does not print the VI labels. Workaround—N/A Date Added—09/01/2007 Return to top |
| 47212 3EIB4MS5 |
No prompt to add a comment in the revision history on close If you select the Prompt for a comment when the VI is closed option on the Revision History Properties page, LabVIEW does not prompt you to add a comment to the History window when you close the VI. Workaround—Select the Prompt for a comment when the VI is saved option on the Revision History Properties page Date Added—09/01/2007 Return to top |