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.
This document contains the LabVIEW 8.6.x known issues that were discovered before and since the release of LabVIEW 8.6. 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.
The Known Issues for toolkits can be found in the LabVIEW 8.6.x Toolkits Known Issues document.
The Known Issues Document is divided into two separate tables appearing in two separate Developer Zone documents. The following document displays the issues by issue category.
Known Issues by Category
The known issues in this document are organized by the category of issue. Please refer to Developer Zone Article " LabVIEW Known Issues Categories Defined" for an explanation of the categories and what types of issues are in each category.
Known Issues by Date
For those who wish to locate the newly reported issues, we have also published another version of the known issues table sorted only by date the issue was added to the document.
You can contact us by phone, email, or the discussion forums. If you are contacting NI in regards to a specific issue, be sure to reference the ID.
The following items are known issues in LabVIEW 8.6.x sorted by Category.
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| ActiveX and .NET | ||||||
| 137557 Return | LabVIEW 8.6 project using certain .NET assemblies opens with dirty dot If you create a project in LabVIEW 8.6.x and add a VI that uses certain .NET assemblies, every time you open the "project", it will appear with a doc mod, or dirty dot, requiring a save even though nothing has changed. The assemblies include (but may not be limited to) System, Accessibility, IEHost, IIEHost, WindowsBase, and WindowsFormsIntegration. Workaround: N/A
| |||||
| 221992 Return | LabVIEW Constructor node cannot load dlls written in .net 4.0 LabVIEW supports the .NET Framework 2.0. It does not support the new features of .NET past 2.0. Many applications built with the .NET Framework 3.0 or 3.5 would still use mscorlib 2.0 which hadn't changed versions since .NET 2.0. With Visual Studio 2010 and .NET 4.0, Microsoft replaced mscorlib 2.0 with mscorlib 4.0. Because of this LabVIEW cannot load assemblies compile for the .NET Framework 4.0 Workaround: N/A
| |||||
| Analysis and Math | ||||||
| 125525 Return | The Interpolate 2D VI requires a square Z array The Interpolate 2D array incorrectly requires a square 2D array as an input for the Z array, it did not require this in previous versions and now returns an error number of -20145 when executed with a non-square array. Workaround: Workaround is to pad your input array out to square, then trim the result.
| |||||
| Building and Distributing LabVIEW Applications | ||||||
| 53817 4I6CKJ00 Return | Adding password protected VI to a library while building an application causes a password dialog to appear When building an application with "Add files to new project library" selected on the Destinations page, if the application includes any password protected vi.lib subVIs you will be prompted to enter these passwords. Workaround: You can cancel the prompt for the password, which may produce a Load Warning dialog. You can also cancel the Load Warning dialog and the operation will complete.
| |||||
| 112751 Return | 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.
| |||||
| 119615 4EI92JAI Return | Application created after converting a build script is missing menu bar. Application created after converting a build script is missing menu bar. When updating a .bld file to the current LabVIEW version, the value of some VI properties are incorrectly set. This problem exists in LabVIEW 8.5 and 8.6 but not 8.5.1. Workaround: In the Source File Settings page of the build specification, select the VI and press the "VI Settings" button. Verify the settings are as expected.
| |||||
| 122079 Return | Build Specification Ignores Remove Front Panel and Block Diagram Flags for the Dependencies Node The Application Builder Build Specification ignores the remove front panel and block diagram flags at build time. The build always uses the default values of this flag whereby it removes the front panel and block diagram. The problem and workaround apply for both executable and source distributions. Workaround: To change the Settings to not remove front panel and/or block diagram, do the following. 1) Uncheck or Check "Remove front panel" and/or "Remove block diagram" in the Source File Settings page of the Build Specification 2) Change one common VI Property (example: "Allow debugging" is a good one to change since debugging requires a block diagram which you intend to remove anyway) that can be changed for every dependency (all contained items). Change it using the "Customize VI Properties" Dialog Box which is also found in the Source File Settings page of the Build Specification
| |||||
| 51179 47B12U5U Return | Error 6 occurred at Create Folder in Create Directory Recursive.vi when building an application (EXE), shared library (DLL), source distribution or web service When building a Build Specification, the build process fails with Error 6 at Create Folder in Create Directory Recursive.vi. This usually happens if the path one of the files generated by the build (temporarily during the build process or as part of the output) is too long. The operating system requires paths for files to be less than 255 characters. Workaround: 1. Use a shorter path for your build destination (i.e. c:\build\) and if necessary copy the output to the final location you need. 2. A. For application (EXE) and shared library (DLL) build specifications, place a checkmark in the Use LabVIEW 8.x file layout checkbox on the Advanced page of the Properties dialog box. 2. B. For source distribution or web service build specifications, uncheck the Preserve disk hierarchy checkbox on the problem Destination on the Destinations page of the Properties dialog box.
| |||||
| 117382 Return | Application builder requests password for dynamic VI for a project that was created from a .bld file. Application builder requests password for dynamic VI for a project that was created from a .bld file. When updating a .bld file to the current LabVIEW version, the value of some VI properties are incorrectly set. This problem exists in LabVIEW 8.5 and 8.6 but not 8.5.1. Workaround: Once project is created from bld file, verify and update VI properties manually in Source File Settings page.
| |||||
| 154568 Return | Minimum Version Required Dialog Text on Built Installer Incorrect When building an installer, the advanced tab from the installer properties contains a check box labled "Require the LabVIEW 8.6 development system or later". When this box is checked, and you try to install the built application on a machine without LabVIEW, a dialog comes up stating "You must install LabVIEW 8.5 or later on the system before you can run this setup". Workaround: If you need this requirement, document that 8.6 is needed for your customers.
| |||||
| 136989 Return | Executable can't find some VIs due to the General Error Handler On upgrading to LabVIEW 8.6, some executables do not run because they are missing VIs. These VIs include vi.lib\Utility\error.llb\Not Found Dialog.vi vi.lib\Utility\miscctls.llb\LVBoundsTypeDef.ctl vi.lib\picture\picture.llb\Get Text Rect.vi vi.lib\event_ctls.llb\eventvkey.ctl The missing VIs can be traced to the General Error Handler. Workaround: Perform a Force Compile (CTRL + Shift + Run Button) on the Top Level VI to recompile the entire hierarchy. If you still experience the problem, open the VIs which call the missing subVIs (e.g. General error Handler CORE.vi) and force compile those VIs.
| |||||
| 124673 Return | Not all development .ini file settings are replicated to executable .ini file Workaround: Add the needed lines manually to the exe's ini file, or make your own custom INI file and choose that file in the Advanced page of Build Specifications.
| |||||
| 134147 Return | Cluster of Refnum Type Defined Crashes Executable Workaround: N/A
| |||||
| 90672 400C2N00 Return | The server.tcp.acl Config Token is not copied to build application's ini file Workaround: Programatically set the VI Server TCP/IP Access using the application property Server:VI Access List. Or, in the LabVIEW development system, set the TCP/IP Access list how you would like it using Tools>>Options. Then, copy the config token "server.tcp.acl" from LabVIEW.INI to your EXEs INI file.
| |||||
| 208364 Return | LabVIEW built installers created on a 32-bit machine will not install most drivers when run on a 64-bit machine If you build an installer using LabVIEW on a 32-bit machine that contains National Instruments drivers, the corresponding drivers will not be installed if the installer is run on a 64-bit machine. Drivers such as NI-DAQ, NI-Sync etc. are affected by this issue. Installation on 32-bit machines are not affected by this bug. Workaround: On the deployment 64-bit machine, download and install the missing drivers from the ni.com Drivers and Updates page.
| |||||
| 227609 Return | Statically linking a LabVIEW built DLL in a C++ project results in error 998 if the DLL is not added to the Delay Loaded DLLs list Workaround: Go to the Project Property Pages, Configuration Properties»Linker»Input and add the name of your DLL to the Delay Loaded DLLs list.
| |||||
| 242600 Return | A search dialog can appear when building a source distribution where the main destination is a library Building a source distribution with the following options set will display a dialog searching for unused VIs in libraries in the original project: - Remove unused library members - Main destination is a library Workaround: N/A
| |||||
| 255617 Return | Error 1502 can occur if dependencies are placed in non executing case structures In previous versions of LabVIEW you could place VIs in a case structure with a constant wired the the case selector. This would load the VIs at runtime. If you have this pattern and attempt to build an executable you could receive error 1502 Workaround: Don't use unreachable code
| |||||
| Controls and Indicators | ||||||
| 219819 Return | 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. Formerly tracked as 50061 and 42NAR8SA Workaround: Move the table away from the front panel's vertical origin.
| |||||
| 51311 477DKPBQ Return | 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.
| |||||
| 52297 4AIFC0R0 Return | 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. After the fact: copy the Tab Control from the block diagram into a new VI. It will show up unlocked in the new VI.
| |||||
| 88787 3J0A89J1 Return | 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: This behavior has existed in LabVIEW for a very long time; this issue will be removed from the Known Issues Document in future versions. Please contact NI if you have questions on this issue.
| |||||
| 91672 477M7K00 Return | 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
| |||||
| 41148 4D1JQKJ7 Return | 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.
| |||||
| 37476 44H8J3ZP Return | 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: N/A
| |||||
| 43109 4FRF0826 Return | Cannot customize plot legend with background image in LabVIEW You cannot configure a plot legend with a custom background image in LabVIEW. 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.
| |||||
| 45133 4I0976O4 Return | 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.
| |||||
| 100580 Return | 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
| |||||
| 118949 Return | 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.
| |||||
| 122856 Return | The XControl Facade does not get the Panel Resize event when the XControl is inside a re-entrant clone The XControl Facade does not get the Panel Resize event when the XControl is inside a re-entrant clone. All other initializations happen as expected. Workaround: Read and Write the "Container Bounds" (using Property Nodes) of the XControl in the re-entrant VI to force the panel resize to occur. The read and write operation should be performed only once in the re-entrant VI
| |||||
| 122857 Return | Bundle by Name does not work for XControls which contain Cluster Typedefs XControls which contain Cluster Typedefs cannot have their values modified by using the Bundle by Name option. Workaround: Use the Value Property Node for the Control/Indicator in the Cluster to change it's value directly.
| |||||
| 57016 44DLSS7Q Return | Major grids disappear on waveform graphs under certain circumstances The major grids on waveform graph disappear for some X-scale values when the graph width is between 415 and 703, and the X axis is set to relative time Workaround: Adjust the Plot Area Size to an appropriate width so that the grids show again. OR Do not use relative time.
| |||||
| 123651 Return | Changing the group name of a plot area in a mixed signal graph crashes LabVIEW If you change the name of a plot area in a mixed signal graph, LabVIEW crashes. Workaround: N/A
| |||||
| 124118 Return | Can't resize legend area of a mixed signal graph having multiple plot areas If you have a mixed signal graph, with multiple plot areas, you cannot resize the legend area (the section on the left labeling your plot areas). If you resize, the Y axis labels stay in place while the graph changes location. Workaround: Start this after the legend area has been hidden: 1) Adjust the width of the indicator on the LEFT side making the graph smaller. 2) This will make the Y-axis labels come back in view. 3) Adjust the width of the indicator on the RIGHT side from here on out. -- or -- Remove all plot areas except for one, size the graph as you would like, add the additional plot areas back in the graph.
| |||||
| 45360 4I0EE2BQ Return | Localization Codes do not Function for Timestamp Controls According to the help, localization codes are available for format strings. They allow to specify the decimal separator and override the system decimal separator. However, this doesn't work for the Timestamp "advanced format" option. Workaround: If you would like to discuss this issue and possible workarounds, please visit the NI Discussion Forums
| |||||
| 128407 Return | TestStand UI Built in LabVIEW Freezes When Moving Splitter Bars While a Sequence is Executing When you try and move a splitter bar while a sequence is executing, everything on the UI (built in LabVIEW) freezes, except from the TS ActiveX Controls. Workaround: The splitter bars can be moved at any other point, only when the sequence is executing dis this a problem. When the UI freezes, a window can be brought on top of the UI to force a redraw; this will return to UI to the correct behavior.
| |||||
| 132432 Return | 3D Graph Changes from Perspective to Orthographic Mode While in "perspective" mode, when the 3D indicator size is changed the graph switches to "orthographic" mode. Workaround: Open the 3D Graph Properties window to set mode to Perspective mode.
| |||||
| 96243 Return | Replacing XY Graph Changes Data Type of References When an XY Graph of data type 1-D array of clusters of arrays is replaced on the front panel, any references to this graph will change data type to 1-D array of doubles. Workaround: Click on the reference, link to any other object, then relink it to the original graph. This will restore the data type.
| |||||
| 147779 Return | "Data Entry" tab of Numeric Controls does not update properly "Data Entry" tab of properties dialog only applies to the first numeric control for which the dialog is opened per launch of LabVIEW. This issue exists in LabVIEW 8.6.1. Workaround: The LabVIEW 8.6.1f1 Patch has been released for this issue.
| |||||
| 152732 Return | plotsupp.cpp line 4051 or scalesup.cpp line 2847 errors and crashes These errors or crashes could occur in certain cases when charts are set to update in the "sweep" mode. Workaround: One possible workaround would be to change the chart to update in "scope" mode instead of "sweep". Right click the chart on the Front Panel to open the short cut menu. Then navigate to Advanced >> Update Mode and select Scope Chart. Repeat the procedure for all charts present on the VI.
| |||||
| 160722 Return | Fixed Point Array Constant Does Not Allow "Adapt To Entered Data" Option Editing a fixed point array constant does not work as expected. The values get reset as soon as you finish entering them. Workaround: Create a control and then convert it to a constant. If you want to modify it, convert it back to a control, make the modifications and convert it to a constant again.
| |||||
| 163678 Return | VI Crashes When Displaying Variants With Null Attributes When displaying a variant that contains one or more attributes that has a null value, LabVIEW will crash. This crash occurs when displaying on the front panel or on a probe Workaround: Before displaying, check if any attributes are null. If so, give them a non-null value.
| |||||
| 164268 Return | Tab control incorrectly displays ComponentWorks 3D Graph when other tabs are selected "Page Labels Display" Tab Controls display remnants of ComponentWorks 3D graph when toggling through the pages using Page Labels Display. The issue does not occur when manually clicking on the Page names, or when changing the value of the tab with the tab's terminal, a local variable, or a Value property node. Workaround: Change the value of the tab directly on the terminal, with a local variable, or a Value property node.
| |||||
| 122321 Return | Mixed Signal Graph does not resize plot legend when in executable Moving the bar separating the plot legend and the mixed signal graph does not work when the graph is used in an executable. The cursor changes to the resize tool, but the bar does not move. Workaround: N/A
| |||||
| 164804 Return | Waveform Chart CPU usage is higher in 8.2 than 8.0 if X scale major markers are hidden Workaround: N/A
| |||||
| 167056 Return | Wiring cluster of fixed point values to waveform chart causes a broken arrow Workaround: Change the representation of the number wired into the cluster to something like I64, then back to FXP
| |||||
| 174973 Return | Event mouse down for Tree Control Scrollbar returns coordinates for the root item The coordinates produced by a mouse down event on the scrollbar of a tree control are translated to the first item in the tree control. Workaround: Use the inBound property to filter these problems out
| |||||
| 121459 Return | 3D Picture controls render non-default font incorrectly in executables Workaround: N/A
| |||||
| 200308 Return | Charts display gaps in waveform data that has a very small dt When data is graphed at high sample rates and the data is added to a chart, LabVIEW incorrectly draws gaps in the chart. These gaps are not present in the data, there is nothing odd with the t0 or dt components of the waveform, and the gaps do not show when the data is returned as an array of DBL values. Workaround: Acquire the data as an array of DBL and timestamp the data manually. Not at all clean.
| |||||
| 176286 Return | Programmatically changing FP.PanelBounds causes part of FP to go Blank Temporarily. Workaround: See KB
| |||||
| 185890 Return | Text on a VI can be mutated to appear as unicode After building a project into an executable, various text for controls and indicators changes languages. It appears that the text was interpreted as unicode. We have not been able to reproduce this in house to find a definite cause. Previously tracked as CAR 179683 Workaround: Contact ni.com/support and have the Applications Engineer search for KB 4Z7BPBUB. This is an internal KB that will give the Engineer instructions on how to fix the issue.
| |||||
| 176848 Return | Picture Control Stops Updating After Setting Properties to Default. Once the picture control's values have reinitialized to default by selecting Data Operations»Reinitialize to Default or programmatically using the method Reinitialize to Default, the mouse position property node stops updating. Workaround: Replace the picture control with a new one from the palette.
| |||||
| 248914 Return | Changing the order of controls or deleting controls in a type def cluster can change references When you create a reference for a control in a type defined cluster LabVIEW uses the cluster order to determine what control the reference is referring to. Say you have a type defined cluster with elements A, B, C and D with cluster order 1,2,3 and 4 respectively. On the block diagram of a VI you have control references to each of the controls. If you open the type def and delete control C the block diagram of the VI will only contain 3 references. Moreover, the reference that used to be for control C will now reference control D. This is because the control is based on cluster order Workaround: N/A
| |||||
| 250588 Return | Warning Generated in a Method or Property of an XControl Appears as an Error in the Top Level VI If you create a method or a property in an Xcontrol in which you have implemented code to generate a warning it is transformed into an error in the calling VI. Workaround: In the VI look for specific error and transform back to a warning
| |||||
| DataSocket | ||||||
| 37020 4A37JOV9 Return | 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.
| |||||
| 46630 2VO0SF00 Return | 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.
| |||||
| Documentation | ||||||
| 141384 Return | Additional Information Needed in the Context Help for "Lock front panel until the event case for this event completes" in the Event Structure Dialog There are currently some resources in the LabVIEW Help that document to Avoid Using an Event Structure Outside a Loop (linked below). However, when creating or modifying the event structure itself there is no information that would indicate that this could cause behavioral issues. Workaround: Text from "Avoid Using an Event Structure Outside a Loop" help document: "Caution: If no Event structure executes to handle an event and front panel locking is enabled, the user interface of the VI becomes unresponsive. If this occurs, click the Abort button to stop the VI. You can disable front panel locking by right-clicking the Event structure and removing the checkmark from the Lock front panel until the event case for this event completes checkbox in the Edit Events dialog box. You cannot turn off front panel locking for filter events."
| |||||
| External Code | ||||||
| 195026 Return | Out of Memory error from Call Library Function Node This error can occur if all of these 3 factors are present. 1) You specify a minimum size to a CLFN input X in terms of another input Y (i.e., not a constant like '4'). 2) The input Y is not a 32-bit parameter (e.g. a U16) 3) Something non-zero occupies the memory directly adjacent to Y, such that when the CLFN interprets the value as a 32-bit value, the resulting value is too large to be allocated. Workaround: Remove one of the three listed conditions
| |||||
| 186228 Return | Call Library Function Node cannot distinguish between case sensitive functions If you have a dll with two functions with the same name but different case, you can only select the first function Workaround: Use Import»Shared Library function
| |||||
| 284901 Return | Call Library Function Node cannot distinguish between case sensitive functions If you have a dll with two functions with the same name but different case, you can only select the first function Workaround: Use Import»Shared Library function
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 153731 Return | Unhandled Exepction can occur if absolute path for system DLL used in CLFN If you use a specific path to a system DLL (C:\windows\system\user32.dll) and build your VI into an application it will create a copy of the DLL inside the application. This can cause an unhandled exception when running Workaround: LabVIEW searches in the system directory when looking for DLLs. If you are using a system DLL simply put the name in the in DLL Path box in the CLFN properties. In the example above you would simply put "user32.dll"
| |||||
| File I/O | ||||||
| 47436 3IKBUP99 Return | 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.
| |||||
| 47819 3N68LE00 Return | 2GB file size limit of datalog files The maximum size of datalog files is 2 GB. Workaround: N/A
| |||||
| 128520 Return | LabVIEW Crashes if TDMS Write is Called with an Invalid File Reference If you call the TDMS Write VI and input an invalid file reference, LabVIEW will crash without reporting an error. This issue may also affect other TDMS VIs as well. This was previously tracked as CAR 128812. Workaround: Check that the file reference is valid before calling TDMS Write.
| |||||
| 124797 Return | Error 8 when using Open/Create/Replace Datalog VI in LabVIEW 8.6 with the write-only option selected If the "write-only" option of the Open/Create/Replace Datalog VIs is selected, then it will result in an Error 8. In LabVIEW 8.5, this would work fine, however, in LabVIEW 8.6, this will result in an error. Workaround: Use "read/write" option rather than the "write-only" with the Open/Create/Replace Datalog VI
| |||||
| 136620 Return | Memory growth with Read TDMS VI for single waveforms A significant memory grwoth occurs when reading a single waveform in a loop from a TDMS file with the Read TDMS VI. This only happens when reading a single waveform, no other type exhibits this behavior (including array of waveforms). The memory gets released when the VI is closed Workaround: Place a build array on the channel name(s) input to create an array with one element. Use an index array on the data output to get the waveform. See attached file.
| |||||
| 160427 Return | Continuously calling XML VIs may increase LabVIEW's memory usage Continuously running VIs which call XML parser VIs mayincrease LabVIEW's memory usage on the first several calls. Workaround: N/A
| |||||
| 99248 Return | Error 1 at Read Datalog with unwired terminal and a cluster containing a path Error 1 occurs at Read Datalog when the record terminal is unwired and the cluster contains an element of the path data type. Workaround: Wire an indicator to the record(s) terminal of the Read Datalog function, or change the path element of the cluster to a string element or simply .
| |||||
| 168144 Return | Scan From File aborts the calling VI if it is pointed to a non-existing file The Scan From File VI throws an error dialog and aborts the VI if it's given a non-existing file instead of returning an error in its output and giving the option to continue. Even if wire error dialog the whole VI still aborts. Workaround: Check for the file existence before calling this VI.
| |||||
| Functions, VIs, and Express VIs | ||||||
| 37575 3PD8N0M8 Return | 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.
| |||||
| 39161 401FEQTL Return | 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.
| |||||
| 39604 49UBP4LE Return | 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. This was previously tracked as CAR 90497 and 3YJ87JCM Workaround: N/A
| |||||
| 41530 4DJFJM00 Return | 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.
| |||||
| 47891 3NRGJTI7 Return | 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
| |||||
| 48016 3P7CBB4Q Return | 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. If you use a negative number for U32 input/output variable, LabVIEW will coerce the value to 0. Workaround: 1. Use the Mathscript node or LabVIEW code for the operation that involves an unsigned, 32-bit integer. 2. Use signed 32-bit integers instead of unsigned 32-bit integers in the formula node.
| |||||
| 50420 44CG88SN Return | 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).
| |||||
| 54942 41CE6I39 Return | 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.
| |||||
| 118373 Return | 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.
| |||||
| 45802 4IDA53I0 Return | Using VI Server Get/Set [Variant] Control Values on Clusters with Fixed Size Arrays creates error 2 The VI Server get/set [variant] control values if used on a cluster with fixed sze arays, results in an error. This is expected as LabVIEW core does not support fixed size arrays. Fixed size arrays are meant to be used only with LabVIEW FPGA. Workaround: Pull the array outside the cluster for running on the development computer.
| |||||
| 118106 Return | 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.
| |||||
| 120864 Return | Append VI List of SubVIs to Report does not include Express VI Configuration Information by default The "include Express VI configuration information (T)" input of Append VI List of SubVIs to Report VI is not True by default, hence it does not include the Express VI configuration information if it's not explicitly mentioned. Workaround: Do not use the default value. Create a control/constant and wire the required value.
| |||||
| 120686 Return | Write to LabVIEW Measurement Files (LVM) using Express VIs takes up a lot of memory The "Write to Measurement File" Express VI consumes a large amount of memory when writing to a Text File (LVM). However, the memory usage is smaller when the same Express VI is used to write a TDM/TDMS File Workaround: Use general LabVIEW VIs (and not Express VIs) to perform an LVM write for large amounts of data. The other option would be to write in smaller chunks.
| |||||
| 122057 Return | Joining Numbers of Different Widths Produce Unexpected Values The Join Number VI produces different results when the inputs are of different widths/sizes. Workaround: Explicitly cast to same size before joining.
| |||||
| 134607 Return | Improper Addition and Subtraction when I32 2D arrays are coerced to work with I64 2D Arrays If a 2D array of I32 is added/subtracted with an I64 2D Array, the output is usually wrong. In the addition case, it generally would be twice the value given in the I32 array. However, this happens only if the I32 array is wired to the Top Terminal (x) of the Function. The addition works fine if the I32 array is wired to the Bottom Terminal (y). The subraction fails more often and does not have a fixed pattern other than it always being zero Workaround: For Addition, Wire I32 to the bottom terminal or explicitly convert it to an I64 before performing the add operation.
| |||||
| 155226 Return | LVM files saved by LabVIEW 8.6 cannot be read by SignalExpress 3.0 The LVM file format in LabVIEW 8.6 was changed to support localization of the decimal separator. This caused a version change to the file format. SignalExpress correctly determines that it cannot read the file, but returns an incorrect error. It should be a version error, not a file type error. Workaround: Open the file in a text editor. If the decimal separator is set to period, change the read and write versions to 1 and it will work. If the decimal separator is set to comma, replace all the commas with periods, replace the decimal separator field itself with a period, and change both versions to 1. SignalExpress will now read the file.
| |||||
| 117448 Return | Polymorphic VIs Incorrectly Identify an I64 Input as I16 Workaround: N/A
| |||||
| 137291 Return | LabVIEW may crash when dropping or performing "Convert to SubVI" on certain express nodes LabVIEW may crash when dropping or performing "Convert to SubVI" on certain express nodes. This problem becomes more likely the longer you have been editing in your current session of LabVIEW. As such, if you hit the crash performing a certain operation, it is likely that if you restart LabVIEW and perform the same action again, LabVIEW will not crash. The likelihood of this crash also increases as the number of targets (Windows, Real-Time, FPGA, etc) or projects currently open in LabVIEW increases. Workaround: If you encounter a crash performing a particular operation, restart LV and try the operation again.
| |||||
| 156518 Return | Sensor Mapping Express VI cannot use model files that are saved in the binary format Workaround: See KB 4VQ9DURQ: Sensor Mapping Express VI does not specify that binary model files are not accepted for more details.
| |||||
| 124783 Return | Sound Input Read VI does not return samples requested If the user inputs a value of "number of samples/ch" into the Sound Input Read VI and the waveform that this returned is only 75% of the samples. Workaround: N/A
| |||||
| 125899 Return | Possible Memory Leak When Reading from Multiple Binary Files A memory leak make occur when reading from multiple binary files. Workaround: N/A
| |||||
| 159232 Return | "Wait on Notification from Multiple" function returns incorrect refnum for named notifiers You can use Obtain Notifier to get multiple refnums to the same notifier. If you pass one of those refnums to the "Wait on Notification From Multiple" function and then use Send Notification on a different one of those refnums, the Wait function will correctly wake up and return data, but the refnum returned by the function will be the one used for the Send Notification instead of the one that the node used when going to sleep. Workaround: You can use Notifier Status function on each of the refnums passed as input to the Wait function in order to get the names of all those notifiers. When the Wait function returns its results, use the Notifier Status function to get the name of the returned notifier, then search the original list for a refnum that has the same name as the one returned. This allows you to identify the original refnum that should have been returned.
| |||||
| 162800 Return | "Wait on Notification from Multiple" returns inconsistent results when multiple refnums refer to same named notifier When using the "Wait On Multiple Notifications" primitive, problems have been observed if two refnums in the input array refer to the same named notifier. These problems apply if the exact same refnum is included multiple times or if different refnums to the same notifier are included. If the Wait node executes and there is already a notification available then the output refnum array will include every refnum that refers to the underlying notifier (including multiple copies of the same refnum) and there will be N copies of the notification in the output notification array, one for each output refnum. If the Wait node does have to go to sleep, when Send Notification executes, the Wait will wake up but will return an array containing only a single refnum and one copy of the notification. Workaround: You can use Notifier Status function on each of the refnums passed as input to the Wait function in order to get the names of all those notifiers. When the Wait function returns its results, use the Notifier Status function to get the name of the returned notifier, then search the original list for all refnums that have the same name as the one returned. This allows you to identify the original refnums that should have been returned.
| |||||
| 113591 Return | Read Palette VI returns blank item path if the item is not installed in the system When reading a palette, it returns empty path in "item path" for all items where the indicated path does not exist on disk. Workaround: Install all the products for the menu.
| |||||
| 177748 Return | MATLAB® Script Node does not allow Parallel Execution Workaround: Call the MATLAB Script Node dynamically using the Call by Reference node to enable parallelism.
| |||||
| 170573 Return | "Delete" method of the Caption class should not be used on instances of strict typedefs This method causes the VI to become corrupt if you call this method on a caption owned by an instance of a strict typedef. Workaround: N/A
| |||||
| 158446 Return | When comparing a sub array created through the Array Subset Function with an identical Array the result is false. Workaround: 1. Place after the "Array Subset" function a "Reshape Array" function. 2. Replace the "Array Subset" function through "Delete from Array" function 3. Turn off auto-preallocate arrays and strings.
| |||||
| 227030 Return | Wait on Notification from Multiple function has unexpected behavior when ignoring previous input. Workaround: See KB
| |||||
| 248421 Return | Bitshift does not work correctly in Expression Nodes and Formula Nodse with a data type smaller than I32 Workaround: N/A
| |||||
| 289842 Return | Get Variant Attribute VI returns wrong value if attribute not found The default value that's returned by the Get Variant Attribute VI is not blank when nothing is wired to the default value terminal. The Get Variant Attribute instead seems to return the last/previous value it returned as the default value. Workaround: Use the Found? output and logic to return a blank variant if neccesary
| |||||
| Import Shared Library Wizard | ||||||
| 36889 4999TKGI Return | 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.
| |||||
| 37271 45I650CI Return | 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.
| |||||
| 37448 44CEN7MQ Return | 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.
| |||||
| 39823 4AIGSL00 Return | 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.
| |||||
| Installation and Activation | ||||||
| 114531 Return | LabVIEW Platform DVD installation fails at LabVIEW DSC installation While installing the LabVIEW DSC module, the installer prompts the user to reboot. After clicking OK to reboot, an error dialog pops up (but soon disappears because it's rebooting). When OS launches after rebooting, the installation does not continue. Workaround: Install MSI 3.1 (WindowsInstaller-KB893803-v2-x86.exe) from the \bin folder of DVD 1 before running the installer
| |||||
| 123135 Return | The Installer Window Appears to Stay Minimized in Windows Vista, and I Cannot Complete My Installation When installing LabVIEW using the Platform DVD, if the main installer screen is minimized, it remains so in the end and can not be maximized through the normal methods. This is a known issue with Windows Vista that affects a few NI installers. Workaround: N/A
| |||||
| 189820 Return | Clicking the ReadMe link from the autorun installation dialog will fail to open the html file in Internet Explorer 8. This issue is present for most National Instruments software released prior to October 2009. Workaround: Open IE8, then click ReadMe while in autorun and the file will open.
| |||||
| LabVIEW Environment | ||||||
| 46449 2JQ91R6I Return | 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: This is already hadled in LV2009; In the right-click "View" menu choose "Always show Labels". Then go ahead and print
| |||||
| 47212 3EIB4MS5 Return | 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
| |||||
| 47791 3MRDJ300 Return | Subpalettes need to be context aware, i.e., need to show/hide when owning library is locked/unlocked LabVIEW does not correctly hide subpalette menus that belong to locked project libraries. Workaround: N/A
| |||||
| 52615 4BMANBJ1 Return | Multi-frame structures do not switch frames on undo If you place a multi-frame structure (Event Structure, Case Structure, etc) on the block diagram, edit a frame in the structure, switch to a different structure and then press ctrl-z to undo the edit, LabVIEW does not switch to the frame that contains the change that you are undoing. Workaround: N/A
| |||||
| 36543 4039KEG8 Return | Edit-time crashes when many modules, drivers, and toolkits are installed Edit-time crashes during various operations (right-click menu selection, VI save, moving a VI from one block diagram to another, building an application [executable], shared library, or source distribution, etc.) can result from LabVIEW's image table overflowing from large amounts of palette icons being loaded in memory due to many installed modules, drivers, and toolkits. In this scenario, may receive LabVIEW error log files reporting "You filled the image table" in image.cpp. Workaround: In Tools->Options->Controls/Functions Palettes, change the Palette Loading from "Load palettes in background" (default behavior) to "Load palettes when needed" and restart LabVIEW. This workaround does not work if you: 1. Perform a palette search. 2. Click "place me on diagram/front panel" from the LabVIEW Help.
| |||||
| 105509 Return | The "do not save automatic changes" setting does not affect libraries The "do not save automatic changes" options setting does not affect any type of library, including classes. Workaround: N/A
| |||||
| 117209 Return | Bundle by Name does not break VI when fields from the input cluster's typedef are deleted Workaround: Change the data type (numeric to string, string to numeric) of the cluster element to be deleted to force breakage at all references to that member. Repair the broken VIs and then remove the cluster element. Or you can delete the cluster element, save (keeping the control open), then mass compile.
| |||||
| 42728 4FEAMCDP Return | Disabling or enabling breakpoints on a single reentrant clone VI is impossible When setting or clearing a breakpoint on a diagram, it is possible to set and clear the breakpoints on an individual reentrant clone without changing the breakpoints on all the other clones of the same VI. However, when you try to disable or enable the breakpoint (a new feature in LabVIEW 8.6), the breakpoint is enabled or disabled on all clones and the original VI. Workaround: N/A
| |||||
| 43671 4GID11F2 Return | Opening VI Properties Window takes a long time When I try to open the VI properites window of a VI it takes a very long time to open. This can occur when you are using a network shared printer (as printer default), and that printer is offline. Workaround: Set default printer to "Microsoft Office Document Image Writer" for example.
| |||||
| 123406 Return | LabVIEW Crashes when Trying to List Errors of a Broken VI If you have a very large VI, it is possible that LabVIEW will crash when you try to List Errors of a broken VI. Workaround: Place a Large Control on your front panel during editing to expand your memory size. A control is attached to the following discussion forum which discusses the issue. Labview 8.6 fatal crash when clicking broken run arrow to list errors.
| |||||
| 134562 Return | LabVIEW may crash when clean up is called on extremely large VIs Workaround: N/A
| |||||
| 148149 Return | Event Structure Cases can Incorrectly Remap to Other Dynamic Events When deleting a user event refnum from a cluster which is input to a Register For Events Function, the associated Event Structure cases can be swapped. Workaround: N/A
| |||||
| 135276 Return | "Show front panel when loaded" option cannot be deselected in certain situations When a new VI is opened in a project, and its Reentrancy is set to Preallocate Clones for Each Instance, the "Show front panel when loaded" option cannot be deselected. Workaround: If you wish to deselect "Show front panel when loaded", do this before Reentrancy is set.
| |||||
| 146503 Return | Under specific conditions, an auto-indexed array of clusters in a For Loop will crash LabVIEW upon saving If a VI has an array of clusters which are auto-indexed in a For Loop, and inside the loop the wire is split into two and sent (1) into a Cluster to Array function and exits auto-indexed and (2) exits directly without auto-indexing, the VI will crash LabVIEW on save. Workaround: N/A
| |||||
| 124752 Return | LabVIEW 8.6 incorrectly displays certain fonts, such as Russian, Hebrew, Arabic, and so on LabVIEW 8.6 incorrectly displays certain fonts, such as Russian, Hebrew, Arabic, and so on. This affects all languages that do not use the Windows 1252 codepage or an IME for input. Text in these languages displays correctly in previous versions of LabVIEW. However, in LabVIEW 8.6, the text either displays incorrectly or with an error about Unicode characters. VIs developed in previous versions of LabVIEW work correctly after you upgrade to LabVIEW 8.6 unless you enter new text. Workaround: The LabVIEW 8.6f1 Patch has been released for this issue.
| |||||
| 163173 Return | Using Ctrl+drag to copy Linked Tunnels Crashes LabVIEW Ctrl-drag to copy linked tunnels causes a crash. This does not happen for non-linked tunnels. Workaround: N/A
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 154260 Return | Context Help does not update for controls or indicators placed in a tab control on front panel Workaround: Right click on the item in the tab control and go to Properties»Documentation and add a custom Description for that item. Doing so will then allow the custom description and the data type to be shown in the context help when mousing over the item.
| |||||
| 95055 Return | Save for previous from LV 8.5 to 8.2 fails if file path is too long Workaround: Save the folder closest to the root directory.
| |||||
| 250119 Return | LabVIEW crashes if you delete a compound arithmetic primitive with a breakpoint Workaround: Remove breakpoint first, then delete.
| |||||
| 150730 Return | Chinese characters give an incorrect behaviour when not locked When typing chinese characters in LabVIEW, if you want to change the tool or the current window, the string will land onto the File menu item of LV. Workaround: To avoid this, the string must be locked by typing the space bar at the end of the string. Still, the string should not move if not locked.
| |||||
| LabVIEW Object Oriented Programming | ||||||
| 48855 3W6K2TMQ Return | Undo on a private data control can leave you in a state where File»Apply Changes is needed but disabled Editing a private data control and then undoing the edits removes the documentation modification on the class. However, while the owning class is broken and expects you to apply the changes you made, the File»Apply Changes menu option is disabled on the private data control. Workaround: Select File»Save or File»Close to save or close the private data control.
| |||||
| 48913 3WGFQJ2K Return | LabVIEW class save prompts sometimes come at incorrect times. If you right-click a control in the Project Explorer window, select Convert Contents of Control to Class from the shortcut menu, and then undo the conversion, LabVIEW might appear as if the class still exists and you might not be able to load a class of the same name as the control. Workaround: Save all files that reference the class you created from the control. This clears the backups of the files and allows the class to leave memory.
| |||||
| 49093 3XHF1O2K Return | Running a dynamic dispatch VI as top-level and another VI that calls the dynamic at the same time can cause unexpected termination of running VIs When you run a VI by pressing its run arrow, that VI is referred to as the "top-level VI". A VI that is running top-level cannot be used as a subVI by another top-level VI. Normally if you run a VI top-level, any callers of that VI are broken until the VI finishes its execution. If you you run a dynamic dispatch VI as the top-level VI, callers of that VI are NOT broken. If you then try to run one of those callers, the dynamic dispatch VI might become idle. Eventually, any VIs using the class that the dynamic dispatch VI belongs to might break, or, in some cases, VIs may be in the strange situation of being editable while running. Workaround: N/A
| |||||
| 50616 45ME5NJ1 Return | Cannot create an override member VI for both a child class and a grandchild class unless you first save the VI that contains the child class You cannot create a VI that overrides the functionality of a child class and then create another VI that overrides the functionality of a grandchild class unless you first save the VIs you want to override. Thus, if you right-click a LabVIEW class in the Project Explorer window and select New»VI for Override from the shortcut menu to create child:A.vi, you cannot select New»VI for Override for the grandchild class to create grandchild:A.vi until you save child:A.vi. This issue occurs because you cannot have two VIs in memory with the same filename that have never been saved. Workaround: Save the VI before you try to override any LabVIEW classes in that VI.
| |||||
| 52027 4A4GRP00 Return | Cannot use the 'New>>VI for Override...' dialog to create override of password-protected VI unless you have the password You use the 'New>>VI for Override...' dialog to override an ancestor VI in a LabVIEW class if the VI you want to override is password-protected. Workaround: Make a public VI which wraps the functionality of the the private VI, and instruct others to override the public VI.
| |||||
| 110527 Return | Create Accessor dialog sometimes creates erroneous accessor VIs The Create Accessor dialog is unable to reliably create an accessor VI for a Class who's private data cluster contains an element with a name which begins or ends with whitespace. The bundle and unbundle nodes on the resulting accessor VI might have an incorrect element of the cluster selected. Workaround: Edit the resulting VI and correct the generated bundle or unbundle nodes.
| |||||
| 52753 4C08OCJ1 Return | Locking all classes in inheritance hierarchy does not hide protected member VIs When you lock a class, all the private member VIs are hidden in the project tree. According to the documentation, if all the classes in a class hierarchy are locked then the protected member VIs should also be hidden. They are not. This is strictly a display issue. Protected VIs are protected and cannot be accessed except within the class and its descendant classes. Workaround: N/A
| |||||
| 110152 Return | Error Creating Override VI for Dynamic Dispatch VI with No Block Diagram If you remove the block diagram from a dynamic dispatch VI then try to use the shortcut option New-> VI for Override, the action will fail with error 1012. Workaround: Create the override VI manually.
| |||||
| 112847 Return | Changing LV class inheritance does not always fix broken wires A child class wire can always connect to a parent class terminal. You may connect a class to another class and get a broken wire, if the wire's class does not inherit from the terminal's class. In the case where the class wire is used but there are no controls/indicators/constants of the class anywhere on the VI, the wire will still be broken. The bug exists if the class is an output wire from one subVI call and an input wire to another subVI call. The inverse problem also exists: Alpha.VI is saved when class A inherits from class B. Now, while Alpha.vi is not in memory, change A to not inherit from B. Load Alpha.vi. It should load broken, but it does not. Forcing a recompile will cause the VI to break. Workaround: Any action that causes LabVIEW to re-evaluate the wire will work to fix this problem. Some options include unloading and reloading the broken VI, deleting the broken wire and rewiring, force recompiling the VI (CTRL+Run Arrow). If you have many broken VIs that need to be fixed simultaneously, hold down Shift+Ctrl when clicking the run arrow to re-evaluate all VIs in memory.
| |||||
| 115897 Return | Cannot fix missing parent class by changing to inherit from LabVIEW Object If a class is missing its parent class, it is broken. The help for this error directs users to change the inheritance and suggests changing to inherit from LabVIEW Object. Changing the inheritance does fix the broken class, but only if you pick any class other than LabVIEW Object. Workaround: You have two possible workarounds: 1) Open the Class Properties dialog for the broken class. Change the broken class to inherit from another class that does exist. Hit "OK" to close the Class Properties dialog. Then change the inheritance again to inherit from LabVIEW Object. 2) You can open the broken class' .lvclass file in a text editor. Find this text: <Property Name="NI.LVClass.ParentClassLinkInfo" Type="Bin"> Delete that tag and everything that follows it until you find the matching </Property> tag. Save the text file. When you next load that class, it will be inheriting from LabVIEW Object. Note that this workaround will not work if the .lvclass file is password protected.
| |||||
| 117709 Return | Unbundling class private data control elements by name follows different rules than unbundling regular cluster elements The Unbundle By Name block diagram object behaves differently for unbundling private data control elements of a LabVIEW class versus unbundling elements of a cluster. If you are unbundling private data control elements by name and a field of the private data control is deleted, LabVIEW may sometimes incorrectly select a new element of the private data control, instead of breaking your VI and requiring you to manually select a new element. Workaround: N/A
| |||||
| 119962 Return | Doing find for "LabVIEW Object" crashes LabVIEW If you attempt to use Edit»Find and Replace... to search for all instances of LabVIEW Object (the ultimate ancestor class of all LabVIEW classes), the development system will crash. Workaround: The only known workaround is a programmatic solution -- writing a VI that opens control references to each control on another VI's front panel and tests if that control is an instance of LabVIEW Object. It can be tricky to write such a VI in versions 8.2 and 8.5. In LV 8.6, there is a VI to help you: [labview]\vi.lib\Utility\LVClass\Is This Control Of LabVIEW Object Class.vi A version of this VI for LV 8.5 may be found by searching the developer forums on ni.com.
| |||||
| 121514 Return | To More Specific node creates undesirable copies of LabVIEW class objects The To More Specific node makes a copy of the class when the operation is successful. This copy is unnecessary and has been identified as a source of performance problems. This bug exists in LV8.2 and later. For further details, please read LabVOOP Performance Issue: To More Specific function. Workaround: 1) Whenever possible, LabVIEW class developers should avoid using the To More Specific node to do type testing -- use dynamic dispatch subVIs instead. That is good programming practice anyway, but this bug makes it even more important. 2) Any LabVIEW class developer who is writing a nested data type -- one where the child class includes an instance of the parent class in its private data control -- needs to be aware of potential performance problems if your data structure gets large, possibly changing to a different implementation of the data structure. These problems will persist until this bug is fixed in a future version of LabVIEW. Some nested data types, such as a simple linked list, may be implementable without using To More Specific by making all operations be dynamic dispatch VIs defined on the parent class, even operations that rightfully should only be called on the child class. The desired functionality is then placed on an override VI in the child class. This lets dynamic dispatching do the work of getting data from a parent class wire onto a child class wire instead of To More Specific.
| |||||
| 124834 Return | Error 1106 using Unflatten from XML on Class with Enum If you place an enum within a class, you will see error 1106 occur at the Unflatten from XML VI under certain conditions. Workaround: N/A
| |||||
| 112627 Return | Creating an accessor VI for strick typedef data creates broken VIs Workaround: Manually fix the created VIs.
| |||||
| 139324 Return | It is possible to receive default outputs values if the dynamic dispatch method has unwired inputs
| |||||
| 147544 Return | Saving .lvclass files for previous version sometimes results in a corrupted file in LV8.6 and 8.5 In LabVIEW 8.6 or 8.5, when you use Save For Previous, there is a potential problem when saving .lvclass files. The newly saved .lvclass file may be corrupted depending upon the types used in the connector panes of member VIs. As a result, the previous version of LabVIEW may crash when you try to load that .lvclass file. The problem arises with certain refnum types, and there is no easy category to describe which refnum types create the problem. Known problem types include all DAQ refnums, storage refnums and I/O refnums. Known safe types include all VI Server refnums, queue refnums and notifier refnums. Workaround: If you use Save For Previous and the resulting .lvclass causes the previous version of LV to crash when you attempt the load, open the .lvclass file in a text editor. The file is structured as XML. In the file, you will find several lines that start with and end with Delete all of these lines. Do not change any other properties! Save the file and then attempt to load again.
| |||||
| 193210 Return | XML parser error when unflattening a LabVIEW class owned by a library Suppose you have a LabVIEW class owned by a library. The Flatten To XML function can successfully flatten objects of that class into XML strings, but the Unflatten From XML function will return an error when trying to recreate the object. The error will claim that the class is not in memory even if it is in memory. Workaround: Move the class out of the library. If this is not an option, you will need to write a custom VI to translate the flattened XML into your class' data.
| |||||
| 103315 Return | Creating a circular link between an Xcontrol and a LVClass can crash LabVIEW. The circular load leads to VIs that are permanently broken and no matter what you do the run arrow will not become fixed. Workaround: Do not create a circular link from your XControl to your class. In other words, write your class completely and then write your XControl using the class. Do not put the XControl or any property/invoke node for the XControl into member VIs of the class.
| |||||
| 194277 Return | Rare instability when dynamic loading classes in combination with static VI references This bug requires four elements to even have a chance of reproducing: 1. TopLevel.vi (or its subVIs) uses Parent.lvclass:Dyn.vi, which is a dynamic dispatch VI. 2. TopLevel.vi (or its subVIs) has a static VI reference to Second.vi. 3. Second.vi (or its subVIs) has any usage of Parent.lvclass, including a constant of the class, a call to a VI in the class, a typedef owned by the class, or any of these for a descendant class. 4. In the course of running TopLevel.vi, a descendant of Parent.lvclass (call it Descendant.lvclass) will be dynamically loaded into memory. If any of these four is not true, the bug does not arise. If these are true, you may see behavior including a dialog claiming that the descendant is not in memory (probable), a LabVIEW crash (common) or the wrong VI executing when the Dyn.vi method is invoked with Descendant.lvclass data (extremely rare). If Second.vi includes dynamic dispatch VI calls, those may have the same problems. This bug exists in LV8.6 and 2009. Workaround: Replace the static VI reference with a call to the Open VI Reference primitive. After making this modification, you will need to restart LabVIEW if you haven't already crashed.
| |||||
| 283943 Return | Many VI Server methods work across contexts and use variants, which can crash LabVIEW when provided with context sensitive data (such as LabVIEW Classes). Writing a VI which passes or returns variants with a VI Server method or property to interact with a VI open in another context can crash LabVIEW when using context sensitive data (such as LabVIEW Classes). Workaround: Make sure that any interaction with context sensitive data is performed by a VI loaded in the same context as the target. If you need to give commands to a target in another context, you may need to load a helper VI in the target's context and use simpler datatypes to instruct the helper VI how to interact with the target.
| |||||
| 284936 Return | Breaking one Override VI in LVOOP shows all siblings as broken but does not explain why When using OOP in LabVIEW, breaking the connector pane of a child class Override VI will make all of its sibling override VI's appear broken even though they are not broken. Hitting run on the broken Run Arrow of any child class Override VI will list all of the child class VIs in the list of "Items with Errors", but none of them will have an error associated with it except for the broken ones. Workaround: Use the red X in the errors window to find the actual broken VI
| |||||
| LabVIEW Project | ||||||
| 48100 3PCAD0J1 Return | Save As»Substitute Copy affects all projects in memory, not just the one that does the Save As operation. If you have Alpha.vi loaded into two separate projects, these are two independent VIs in memory. If you do Save As»Rename then, LabVIEW correctly renames the VI in both projects since the actual source on disk has changed. However, if you do Save As»Substitute Copy, only one project should change. Workaround: Close any projects that you want to contain the original VI before performing the Save As»Substitute Copy operation.
| |||||
| 117582 Return | Private scope has no effect on XControls or StateCharts Marking an XControl or a StateChart as private inside an owning library will not prevent VIs outside the owning library from using that XControl or StateChart. Workaround: No known workaround.
| |||||
| 163371 Return | "Save As:Copy" on a nested library breaks member VIs if use option to add copied library to owner library If you have a nested library, a library that is owned by another library, and you use Save As:Copy, there is an option to add the duplicate library to the original owner library. If you use this option, the member VIs of the duplicate library are all broken because they are not correctly named as members of the owning library. This bug affects all types of libraries, .lvlib, .lvclass, .xctl and .lvsc. Workaround: Option 1: Do not use the "add to owning library" option and instead add the duplicate library to the owner manually after the copy. Option 2: After the copy operation, move the duplicate library out of the owner library and then move it back into the owner library.
| |||||
| MathScript | ||||||
| 112426 Return | In MathScript Node, Import Script does not work for read-only files Import Script through right-clicking a MathScript Node and selecting "Import" does not work for read-only files Workaround: N/A
| |||||
| Menus | ||||||
| 104160 Return | Right Click Wire: Delay in Appearance of ShortCut Menu You may get a noticable delay the first time you right-clicki on a wire if LabVIEW has complex custom probes available. LabVIEW loads all custom probes in /LabVIEW Data/Probes/..., /_probes/..., and /_probes/... the first time it displays the right-click menu for a wire. Depending on the contents of the probe VIs, this delay could potentially grow very large. Workaround: Mass compile the contents of /LabVIEW Data/Probes/..., /_probes/..., and /_probes/... Delete unused probes from the directories listed above.
| |||||
| Miscellaneous | ||||||
| 39908 4AIBSAFF Return | When synchronous display is enabled, disconnecting and reconnecting to a LabVIEW Real-Time target performing image display in a loop causes the Real-Time target to hang If you enable synchronous display on an image display control and then update the control in a loop on a VI running on an Real-Time target, LabVIEW hangs after disconnecting and reconnecting to the target. This issue might occur when you want to run an application that can perform a headless operation, but you still want to perform image display in a loop. Workaround: Right-click the image display control and select Advanced»Synchronous Display from the shortcut menu to disable synchronous display.
| |||||
| 68920 4EE45K1G Return | LabVIEW protects against recursion by removing nodes from block diagram LabVIEW removes VIs from a block diagram of an unedited VI when dropping a VI to another block diagram. Workaround: This is expected behavior since the LabVIEW compiler cannot support native recursion in current versions of LabVIEW. Support for recursion added in LabVIEW 2009.
| |||||
| 117216 Return | Instrument Driver Project Wizard reports a dependency error in report The Instrument Driver Project Wizard incorrectly reports the generated instrument driver has a dependency that is outside of driver and outside of vi.lib. Specifically, the instrument driver report includes the following in the generated report: "The driver is dependent on the following VIs that are not part of the driver or in vi.lib." However, no VI path is noted in the report. Users should ignore this dependency error if no VI path is listed in the report. It is a false error. Workaround: N/A
| |||||
| 116843 Return | Expected End Calculation for Timed Loop Iteration is incorrect when Deadline is used The current calculation for Expected End for the Previous Iteraction is "Actual Start + Deadline" but the correct calculation should be "Actual Start + Deadline - 1". Workaround: Subtract one from the Expected End output before using it.
| |||||
| 117557 Return | Cannot Edit I/O Alias Properties after deleting the bound I/O Variable If the I/O Variable that is bound to the I/O Alias is deleted, then it will not be possible to edit or view the Properties of the I/O Alias. Opening the Properties dialog box of the I/O Alias will result in an error. Workaround: Add the I/O variables back to the project to access the I/O Alias Properties.
| |||||
| 120393 Return | The web server returns a 405 error in response to PUT or DELETE requests routed to web services runtime. The web server returns a 405 error in response to PUT or DELETE requests routed to web services runtime. Workaround: Use HTTP GET or POST methods instead and use application logic in your web method VIs to implement your functionality.
| |||||
| ID | Known Issue | |||||
|---|---|---|---|---|---|---|
| 118215 Return | ActiveX Controls Fail to Load in LabVIEW 8.6 Run-Time I found that ActiveX Controls (WebBrowser and WindowsMediaPlayer etc.) failed to load on a machine with just the LabVIEW 8.6 run-time engine installed. If you install other programs, such as CVI, they start loading and working. Workaround: Reinstall the 8.6 runtime engine and make sure to select the USI component.
| |||||
| 118665 Return | The In-place element structure is always broken if I try to use Variant To / From Element border nodes The in-place element structure is always broken when using Variant To-From Element border nodes, and gives an unwired or bad terminal error even when all the terminals are wired. This worked in 8.5, and code upgraded from 8.5 continues to function unless diagram in structure is modified. Workaround: Create desired structure in 8.5 and upgrade the VI to 8.6. Do no edit the code inside the structure inside 8.5.
| |||||
| 140555 Return | No scrolling limit using a mouse scroll wheel on panes that have a visible vertical scroll bar If a pane has a vertical scroll bar enabled, users can use the mouse's scroll wheel to scroll vertically without limit. Workaround: Use VI server to set your visible coordinates of your pane.
| |||||
| 119144 Return | String caching causes incorrect capitalization of VI filenames when changing their case String caching causes incorrect capitalization of VI filenames when changing their case. Caching is a process by which LabVIEW remembers previously used names, characters, and so on. As a result, if you change the capitalization of the filename of a VI on disk, LabVIEW does not reflect the change when you include the VI in a new project. Workaround: The LabVIEW 8.6f1 Patch has been released for this issue.
| |||||
| 124319 Return | NI TestStand Sequence Editor slows down during certain LabVIEW steps NI TestStand uses a function to get the checksum of the connector pane of a VI without loading the VI to check whether the prototype of the VI has changed. LabVIEW 8.6 calls this function more slowly than LabVIEW 8.5, especially when you wire an I/O control to the connector pane. Workaround: The LabVIEW 8.6f1 Patch has been released for this issue.
| |||||
| Operating System Specific | ||||||
| 91250 453BD7Q6 Return | LabVIEW crashes on Japanese Vista if system locale is set to a Western European codepage If you have a user name that uses Japanese characters and change the system locale to something other than Japanese, LabVIEW crashes. Workaround: Make sure your locale and user name match.
| |||||
| 114264 Return | WebServer does not handle html file whose name contains Japanese characters. If an html file is created from VI which is under a project, "project name»Target Name»VI name.html" will be the default html file name. Most commonly, [Target Name] will be "My computer" in Japanese for any users using Japanese OS. If these characters are included in the html file name, you cannot open the html file through the LabVIEW Web Server. Note: Not all Japanese characters cause problems. Workaround: N/A
| |||||
| 131671 Return | LabVIEW crashes on SuSE 11 Linux LabVIEW crashes on SuSE 11 either when launching or during other loading operations. This can be due to font initialization problems in the OS and can occur when LabVIEW attempts to load a font style that is not available on the system. Workaround: Update the following packages: xorg-x11-fonts xorg-x11-fonts-core Both need to be at least version 7.3-70.2. These can be updated with the "Online Update" tool in SuSE 11, and they are listed under the "recommended" updates with the summary of "x11: Fix for broken font rendering in legacy applications".
| |||||
| 157246 Return | The Property Node "Bring to Front" doesn't work in Windows Vista Workaround: N/A
| |||||
| 166774 Return | Source Distribution containing Report Generation VIs fails on Mac OS and Linux A Source Distribution build containing Report Generation VIs will fail on Mac and Linux. File Not Found: Append Column Headers to Report.vi Workaround: Select the "Remove unused members of project libraries" option.
| |||||
| 242799 Return | Code generation of DAQmx Assistant for Modular Instrument Express VIs fails on second attempt in LabVIEW 64-bit When dropping a DAQmx Assistant or or a Modular Instrument Express VI, everything, including code generation, works the first time, but if another Express VI is dropped, the config page appears, but no code is generated when the user presses [OK]. Workaround: For all versions of LabVIEW 32-bit on the 64-bit machine, disable the VI Server TCP/IP checkbox, exit, and try the code generation again in LabVIEW 64-bit.
| |||||
| Performance | ||||||
| 43026 4FIIUH7N Return | Timed Structures May Leak Memory The Timed Sequence Structure uses a DLL which is loaded when a VI using the timed structure is loaded in memory. Loading and unloading this DLL causes a small memory leak. It is unlikely that your application would be loading and unloading this DLL multiple times. Workaround: In order to work around this problem, you must keep the DLL used by the Timed Structure in memory. To do this, simply have a VI loaded in memory that uses a Timed Sequence Structure. You could do this by having a 'dummy' sub-VI in your top-level VI which just has one instance of a Timed Sequence Structure that does nothing but keep the DLL in memory.
| |||||
| 48663 3ULGC6UX Return | Very Large Constant Arrays May Interfere with Constant Folding When looping through very large constant arrays, LabVIEW may run out of memory. In this case, no constant folding is executed in the code. Workaround: N/A
| |||||
| Remote Panels | ||||||
| 46442 2BCDF100 Return | Remote Panel not correctly displaying hidden/disabled controls when server is a built app. Clients viewing a front panel remotely might see different behavior depending on whether the front panel they are connecting to is from a built application. Specifically, if the front panel is from a built application, any programmatic changes to the front panel made before the client connects to the front panel are not reflected on the client computer. For example, if a Property Node changes a caption on a control before a client connects to that front panel, the client will see the original caption of the control, not the changed caption. Workaround: N/A
| |||||
| 50165 4367OV4I Return | VI in web browser with top-level window or dialog window style does not draw. If you create a VI, select Top-level application window or Dialog options from the Window Appearance page in the VI Properties dialog box, and publish the VI to the web, when you view the VI, it uses the default window style instead of the style you selected. This issue was formerly documented as issue 51263/47MA31QO. Workaround: N/A
| |||||
| 97181 Return | On a Mac, a VI that writes waveform data to a chart on the Web Server crashes the Web browser when accessed from a PC When posting a VI that writes waveform data to a chart inside a loop on the Web Server for remote front panels on a Mac, accessing the remote front panel from a PC may crash the Web browser. Workaround: Use graphs instead of charts. If chart functionality is necessary, you can programmatically create a history of data that gets plotted to the graph on each plot.
| |||||
| 181687 Return | Web publishing tool fails without error The web publishing tool may fail to start the web server if the port is already reserved, yet not return an error. Workaround: Ensure that the port to be used by the web server is not in use.
| |||||
| 136677 Return | Remote panels do not work if Internet Explorer is embedded in an ActiveX or .NET Container If a remote panel is built in LabVIEW 8.6 and embedded in an ActiveX or .NET Container in a LabVIEW 8.6 VI it will not display correctly Workaround: Use a remote subpanel. This is actually the recommended way to accomplish this task
| |||||
| Shared Variables | ||||||
| 48195 3Q9DN1ZU Return | Deployment fails for all Variables in a Library if one Variable has a bad binding LabVIEW fails to deploy all shared variables in a library if one shared variable has an invalid binding. Workaround: To correct this problem, either delete the shared variable that has an invalid binding or unbind the shared variable.
| |||||
| 48349 3R8EFNKY Return | VarClient on cFP reports "variable does not exist" if the variable is published by a host that has two ethernet adapters Network-published shared variables do not function properly if multiple network adapters are enabled on the same computer. Workaround: You can bind variable communication to a specific network adapter. This will allow variable communication to function normally on the bound adapter. It is not currently possible to perform shared variable communication on two network adapters simultaneously. For instructions on binding variable communication to a network adapter see KB 3WK9NH9A: Deploying Shared Variables to a Specific Network Card.
| |||||
| 52799 4C8E5500 Return | Variable Manager May Display the Incorrect Buffer Size When the ServerVariable or ServerVariableInfo class explicitly creates a network variable and configures the server-side buffer for the network variable, the value for the buffer size displayed by Variable Manager is incorrect. Workaround: Use the ServerVariable.GetItemCapacity() method or ServerVariableInfo.ItemCapacity property to retrieve the correct value.
| |||||
| 128059 Return | Shared variable bindings in the same library are not updated properly when copying/renaming the library If you have shared variables in a library which are bound to I/O servers or other variables that are also in the same library, and you rename or save a copy of the library, the bindings still refer to the original library name. Workaround: Manually rebind the variables after copying or renaming the library.
| |||||
| 173080 Return | When a project that contains variables with binding is created in one language and opened in a different language, variables may fail to deploy Workaround: Open the project in the desired language, double-click on the variables with binding, and re-bind the variables.
| |||||
| Source Code Control | ||||||
| 107802 Return | When working with LabVIEW Libraries and their VIs outside of a LabVIEW Project environment, LabVIEW may display incorrect Source Code Control status for files. When working with LabVIEW Libraries and their VIs outside of a LabVIEW Project environment, LabVIEW may display incorrect Source Code Control status for files. For example, files may be checked out but LabVIEW will not reflect this. This problem also applies to LabVIEW XControls, Classes, and Statecharts Workaround: Work with your files inside of a LabVIEW project if you are using Source Code Control.
| |||||
| 123313 Return | Unnecessary IAK file checked into source code control When NI-FieldPoint is installed, and source code control is configured for LabVIEW, when you check in projects to source control the source code provider attempts to check in an IAK file for the project, even if one does not exist. Workaround: If a dialog appears when checking in file, do not check in the iak file if it is not necessary for that project.
| |||||
| 118693 Return | Performance issue when using source control in LabVIEW 8.6 projects. The use of source control increases the access time to project folders compared to LabVIEW 8.5. The slowdown is proportional to the number of files in the project. Workaround: The LabVIEW 8.6f1 Patch has been released for this issue.
| |||||
| 119731 Return | LabVIEW crashes when you perform VI Analyzer tests with source control enabled. The crash occurs if you select a large number of VIs or projects to test and source control is enabled. LabVIEW usually crashes after it analyzes the first few VIs. Workaround: The LabVIEW 8.6f1 Patch has been released for this issue.
| |||||
| 153922 Return | .svn folder causes Mass Compile issues Subversion (SVN) creates .svn folders under each source code controlled folder. The .svn folder stores unchanged versions of the files in the format Name.xyz.svn-base. (Example: Help.vi will be stored as Help.vi.svn-base). Mass compiling a folder under TortoiseSVN source code control results in LabVIEW mass compiling the files present in the hidden .svn folder too. Workaround: In LabVIEW 2009, use the following configuration token in the LabVIEW.ini file - skipSVNFolders=true
| |||||
| Toolkit - Other | ||||||
| 124463 Return | LabVIEW hangs on Launch After VI Analyzer License Expires If you have an evaluation install of the VI Analyzer, and the license expires, then in some cases, LabVIEW will hang on launch. Workaround: Uninstall or activate the VI Analyzer after its license expires.
| |||||
| 135200 Return | LabVIEW 8.6.1 Modules/Toolkits Show Version as 8.6 in MAX LabVIEW 8.6.1 modules store their version strings as 8.6 in the Windows Registry resulting in the module version numbers being shown as 8.6 in MAX when the version is really 8.6.1. This should not affect operation of the module. This is true for 8.6.1 toolkits also. Workaround: To determine whether you have version 8.6.1 or 8.6 of a module or toolkit, check the module or toolkit's installed readme file.
| |||||
| Upgrade - Behavior Change | ||||||
| 51185 47FGSQCS Return | Cannot save VI as the same name as missing library member VI If a library contains a VI and the VI is missing, you should be able to save a VI as the same name as the missing VI in order to rebuild the missing VI. Currently, LabVIEW does not allow this. Workaround: Delete the item from the library, save the new VI as the same name as the missing VI and then move the VI into the library.
| |||||
| 52263 4AJA41TQ Return | 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. If the input waveform to the log function has a time stamp for t0, that value is also lost. Workaround: Extract the Y-array of the waveform and perform the needed operations on Y before re-building the waveform.
| |||||
| 41224 4DA24FXR Return | 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.
| |||||
| 44355 4HGA9JBK Return | Timed-Sequence iteration duration terminal does not work The Iteration Duration output terminal on Timed-Sequence structures no longer functions correctly. Workaround: Use the Global End and Global Start time to calculate the total duration of the structure.
| |||||
| 119444 Return | Multi-column 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
| |||||
| 120556 Return | Constant-folded case structure tunnel coerces to non-folded type in LabVIEW 8.5 but not in previous versions If you have a case structure wired with a constant and including a tunnel, and you have two differing, but coerceable, types wired to the tunnel, the type of the tunnel is now (LabVIEW 8.5 and later) dependent on which case has been folded. In LabVIEW 8.2 and prior, LabVIEW coerces the value based on rules for the type. Among other things, this change means that when you upgrade an application from older versions, it may have broken wires or changes in data types. Workaround: Wire a control to the case structure instead of a constant to prevent the constant folding.
| |||||
| 123728 Return | LabVIEW crashes Passing Decimate Array Output to Feedback Node Initializer LabVIEW crashes if you pass the output of decimate array to the initialization terminal of a feedback node. Workaround: Wire the output of the decimate array to a build array function of one input set to "concatenate inputs". This causes the array to not be marked as a (sub)array in context help and no longer causes crash when wiring to the initializer of the feedback node. [Mike L 8/21/08] Easier workaround: Wire output of decimate array to the Always Copy function.
| |||||
| 128115 Return | Auto-indexing array constants If a constant array is wired into a loop with auto-indexing on, and the indexed value is wired to the case selector of a select structure the compiler may incorrectly interpret the selector as a constant and not generate code for all the cases. Workaround: Instead of an array constant use a hidden control.
| |||||
| 131853 Return | LabVIEW execution hangs or pauses at random times Workaround: N/A
| |||||
| 119204 Return | Plot Legend Does Not Update When Using Property Nodes When the properties of a plot legend are changed by property node or by a reference and a property node, the legend does not redraw. Workaround: A redraw can be forced by changing the property node Plot.Name, changing the property node Legend.Visible, or a mouse movement over the plot legend.
| |||||
| 124113 Return | SubPanel Open Block Diagram option does nothing when VI in SubPanel is running Using the SubPanel container, if you right-click on the container while the main VI is running and select "Open Block Diagram" in LabVIEW 8.6, nothing happens. Workaround: N/A
| |||||
| 125468 Return | Mouse Down Event Callback Caues a Broken Wire on VI Reference VI reference shows a broken wire on a Register Event Callback node when Mouse Down event is selected in LabVIEW 8.6. Workaround: N/A
| |||||
| 125755 Return | HTTP port cannot be set programmatically in LabVIEW Starting with LabVIEW 8.6, the HTTP Port Property node is no longer writeable. If you upgrade code from 8.5 that contains a HTTP Port property that is being written to, it does not generate an error. However, if you run the VI/exe, the port will not be updated with the new value and no error is returned. Workaround: N/A
| |||||
| 188998 Return | Upgrading Tab Controls from LabVIEW 8.2.1 to higher versions results in unexpected behaviors. Upgrading a VI containing a tab control from LabVIEW 8.2.1 to higher versions may result in unexpected changes to the way the tab control looks and works Workaround: Right click->replace the tab control with a new tab control.
| |||||
| 183814 Return | Rare crashing race condition between Release Notifier and Wait For Multiple Notifications in a loop with different refnums each iteration This is a fairly rare race condition introduced in LV 8.6. If the race is lost, LabVIEW crashes. The race is between two Notifier primitives. The first is a Wait For Multiple Notifications primitive. This primitive must be included in a loop. The input array of refnums must be a shift register and the array of refnums must have the ability to be modified on each iteration of the loop -- specifically, occasionally, the loop must empty the array. Further, the modifications to the array must be allowed in parallel to the Wait node, such that the shift register can be updated without waiting for the Wait node to finish. Thus the array of refnums from the left hand shift register is forked, one fork going to the Wait prim and the other fork going to the modification code. The second primitive is the Release Notifier primitive. This primitive will release one of the Notifier refnums that the Wait primitive is waiting on. This must happen in parallel to both the array modifications and the Wait primitive. Under these very rare conditions, LabVIEW may experience an intermitant crash IF you have a fast enough microprocessor. This is not an inplaceness bug or anything that would interfere with the correct functioning of the Notifiers. If you believe you are seeing incorrect Notifier behavior, this bug is not the source. When something goes wrong here, the bug is always a crashing bug, never wrong behavior. This affects both the Wait For Multiple Notifications primitive and the Wait For Multiple Notifications With History primitive. Workaround: Place an "Always Copy" primitive on the array of refnums wire on the fork leading directly to the Wait For Multiple Notifications primitive.
| |||||
| Upgrade - Migration | ||||||
| 116237 Return | The Method Save.Instrument Returns Error 1357 The behavior of the method Save.Instrument has changed when "Save a Copy" is true and the Path to Saved File is the path that the VI reference is loaded from. In LabVIEW 8.5 and previous, you could overwrite the existing VI when Save a Copy was true. In LabVIEW 8.6 this now returns error 1357. Workaround: This behavior was changed to be more correct as you should not be saving a copy of the instrument overwriting the existing VI.
| |||||
| 108672 Return | Replacing outdated Express VI does not give notice If you open the Express VI "Write LabVIEW Measurement File" from previous LabVIEW versions in 8.2 or later, LabVIEW automatically converts it to the newer "Write to Measurement File" Express VI. When this happens, there is no message to the user, so you may not notice that your code has changed. If you click the "Cancel" button in the Express VI Property pages, the previous file path is not preserved. Workaround: N/A
| |||||
| 99651 Return | LabVIEW crash in MemoryManager.cpp line 406 with MixedSignalGraph strict Value property LabVIEW crashes if you create a Value property node from a Mixed Signal Graph reference, unbundle the value, and then change the data in the cluster. Workaround: Create the Value property node from the graph instead of the reference to the graph.
| |||||
| 99825 Return | Table Property Nodes Run Slow After Upgrade from 7.1 Property nodes that are used to update table controls on the front panel (such as Set Cell Value, Active Cell, CellBGcolor, CellFontColor) run about 7 times slower in LabVIEW 8.x versions than in 7.1 and prior. Workaround: Use defer front panel updates to avoid rapid updates of the UI which would probably not be noticed. This design pattern can speed up the program to levels much faster than 7.1 ran before the slowdown.
| |||||
| 45227 4I6EOTBK Return | VI with Several Timed Structures Takes Minutes to Load There is an issue in opening a VI written in a previous version of LabVIEW with many timed structures in LabVIEW 8.5 or later. This only occurs on the first load, once the VI is saved in the current version the load time will return to normal. Workaround: Wrap the Timed-Structures in SubVIs.
| |||||
| 138552 Return | Load VRML File.vi missing "error in" terminal In LabVIEW 8.6, the "error in" terminal was removed from the Load VRML File.vi. LabVIEW 8.2/8.5 has this terminal. Thus, if a VI that has the Load VRML File VI is upgraded to 8.6, the previously working VI will be broken. Workaround: Place a case structure around the Load VRML File VI to handle the error manually.
| |||||
| 142849 Return | Hidden page in a tab causes the VI to crash when upgrading to a newer version of LabVIEW If a VI has a hidden page in it's tab control, then upgrading that VI to a newer version of LabVIEW can result in a LabVIEW crash Workaround: Make the page in the tab visible and then perform the upgrade.
| |||||
| 147187 Return | Crash using Xscale Info or YScale Info graph properties Graph properties Xscale Info and YScale Info available in LabVIEW 6.0 are no longer available. Using these properties will cause your VI to crash when executed. Workaround: Use newer individual properties XScale.Range etc. to adjust your graph properties.
| |||||
| 186404 Return | Default values lost when upgrading from LabVIEW 7.1 to 8.6 or 2009 Workaround: Save in 8.5 before opening in 8.6 or 2009
| |||||
Document last updated on 8/2/2011