Academic Company Events NI Developer Zone Support Solutions Products & Services Contact NI MyNI
4 ratings:
 3.5 out of 5     Rate this Document

LabVIEW 8.2 Readme Files

Primary Software: LabVIEW Development Systems>>LabVIEW Base Package
Primary Software Version: 8.2
Primary Software Fixed Version: N/A
Secondary Software: LabVIEW Development Systems>>LabVIEW Full Development System, LabVIEW Development Systems>>LabVIEW Professional Development System

Problem: I have not installed LabVIEW 8.2. Can I still access the readme files?

Solution: The Windows, Mac OS, and Linux readme files are attached below. This document also lists the known issues from each readme. The readme files also are located on the LabVIEW 8.2 CD and installed in the labview\readme directory on Windows or the labview directory on Mac OS and Linux.

Each readme file contains important last-minute information about LabVIEW 8.2, including installation and upgrade issues, compatibility issues, and changes from LabVIEW 8.0. Refer to the LabVIEW Upgrade Notes (linked below) for more information about upgrade and compatibility issues and for a complete list of new features in LabVIEW 8.2. Refer to the LabVIEW Release Notes (linked below) for installation instructions. You can access both of these documents by selecting Help»Search the LabVIEW Help in LabVIEW and navigating to the LabVIEW Documentation Resources book.

LabVIEW 8.2 Known Issues for WINDOWS Operating System

Installation
  • If you uninstall LabVIEW 8.2 and a previous version of LabVIEW remains on the system, the previous version of LabVIEW might try to repair itself the next time you open it. The repair process might remove any patches you installed for that version of LabVIEW. Make sure to reinstall any patches you have on the system after the repair finishes. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • If you install LabVIEW 8.2 and then install a previous version of LabVIEW on the same computer, Windows Explorer crashes if you use Windows Explorer to perform an operation on an LLB. As a workaround, select Tools»Options, select Environment from the Category list, remove the checkmark from the Enable Windows Explorer for LLB files checkbox, and click the OK button. Display the same Environment Options page again, place a checkmark in the Enable Windows Explorer for LLB files checkbox, click the OK button, and restart the computer.
Compatibility
  • LabVIEW 8.2 is not compatible with NI TestStand 3.1 and earlier. Refer to the National Instruments Web site at ni.com to access the Upgrade Advisor and purchase NI TestStand 3.5 or later.
  • The NI Publish-Subscribe Protocol (NI-PSP) networking technology is incompatible with the Windows XP Service Pack 2 firewall. You must disable this firewall for networking to function correctly. Refer to the KnowledgeBase at ni.com for more information about the firewall.
  • If you have Windows XP Service Pack 2 installed, a Security Alert dialog box appears when you launch LabVIEW or the NI Example Finder for the first time. If you select the Keep blocking this program option, the LabVIEW VI Server, LabVIEW Web Server, and any server written in LabVIEW cannot accept incoming connections from a remote computer. Select the Unblock this program, despite the security risk option to configure your computer to launch LabVIEW without any changes in functionality. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
VIs, Express VIs, and Functions
  • The links to subVIs from the labview\vi.lib directory might break when you use File»Save for Previous Version to save application VIs for a previous version of LabVIEW. Right-click the subVIs and select Relink To SubVI from the shortcut menu to relink the subVIs.
  • With automatic saving for recovery, LabVIEW does not save backups of a VI file in an LLB if the name of the VI contains characters such as ? or / that the operating system does not allow. If automatic saving for recovery is enabled, LabVIEW notifies you the first time the VI you are modifying cannot be saved.
  • 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. To correct this problem, use the internal, language-independent object types and property names. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • If you create a new, untitled VI while using the Storage VIs, the numbering of the untitled VI might be inconsistent.
  • The Storage VIs do not support the extended-precision, floating-point data type. If you wire this data type to a Storage VI, LabVIEW returns a compiler error when you run the VI.
  • The Delete Data VI does not work with .tdm files. If you use this VI with a .tdm file, the size of the file does not change, but you cannot access the data you try to delete.
  • The Sound File Read VI uses large amounts of memory to read an entire .wav file. Read the data from the .wav file piece by piece rather than in one large file.
  • 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.
  • The Read From Measurement File Express VI returns an error if you call it on the same file multiple times, which makes using this Express VI in a subVI problematic.
  • If the Database Connectivity Toolkit is installed, you cannot place the Database Variant To Data function on the block diagram. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • If an example VI from LabVIEW 7.x or earlier opens another VI by specifying the example VI name as a path in the Open VI Reference function, you receive an error when you run that example in LabVIEW 8.x. Remove the String To Path function wired to the vi path input of the Open VI Reference function to correct the error.
  • If you configure a Call Library Function Node to call a LabVIEW DLL, LabVIEW hangs if you place a checkmark in the Specify path on diagram checkbox on the Function page of the Call Library Function dialog box and you select Run in UI thread in the Thread control. If you configure the Call Library Function Node to call a DLL written in C with these same settings, LabVIEW works correctly.
Block Diagram Objects
  • 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 register an ActiveX event, you must unregister the event explicitly. Otherwise, memory leaks might occur because the ActiveX control does not know that the client has disconnected.
  • When you select Tools»Compare»Compare VIs and use the Compare VIs dialog box, LabVIEW does not display differences between values of cluster constants.
Environment
  • A blue field does not surround the palette icons for Express VIs from LabVIEW 7.x and earlier that you open in LabVIEW 8.2. For example, if you use a LabVIEW 7.1 toolkit in LabVIEW 8.2, a blue field does not surround the icons for Express VIs on the toolkit palette. You must mass compile the Express VIs to display the blue field around the icons.
  • If you define a custom run-time menu for a control and you save that run-time menu with the control, you cannot localize the run-time menu. As a workaround, you can save the custom run-time menu to an external file and point the control to that file, or you can build the run-time menu dynamically with localized strings.
  • LabVIEW does not correctly hide subpalette menus that belong to locked project libraries.
  • When you print the VI Hierarchy window, LabVIEW does not print the VI labels.
LabVIEW MathScript
  • If you select File»Save for Previous Version and save a VI that contains a MathScript Node for LabVIEW 8.0, the VI is broken when you load it in LabVIEW 8.0. To correct this problem, load the VI in LabVIEW 8.0 and then modify the script in the MathScript Node. For example, add and remove a space. Then click the block diagram outside of the MathScript Node. When you click the Run button, the VI runs correctly.
  • MathScript does not support string inputs that use LaTeX syntax.
  • If you mass compile VIs last saved in a previous version of LabVIEW and the VIs contain MathScript Nodes, LabVIEW might return error messages, but LabVIEW compiles and saves the VIs correctly.
  • If a LabVIEW MathScript contains a findobj, gca, gco, get, or set function, LabVIEW ignores the function and executes the remainder of the script as normal. LabVIEW does not return errors or warnings for these functions in a script.
LabVIEW Object-Oriented Programming
  • If you delete a control, indicator, or constant of a LabVIEW class, the backup object keeps the LabVIEW class loaded in that application instance. This backup object can cause a problem if the LabVIEW class is loaded in more than one application instance. To edit the LabVIEW class, make sure the class is loaded in only one application instance. The backup object might be the only reason the LabVIEW class stays in memory in an application instance. To remove the backup object for the LabVIEW class, save or close the VI(s). Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • If you rename a parent class while any child classes are in memory, LabVIEW does not record the mutation history of the class correctly. LabVIEW resets any flattened data or non-default data in memory to the default value. To avoid losing data, rename a class only when it is not in memory. Refer to the KnowledgeBase at ni.com for more information about renaming LabVIEW classes.
  • If a LabVIEW class is broken because a member VI is missing from the LabVIEW class, you cannot fix the class by deleting the missing member VI from the Project tree.
DataSocket
  • If you call the DataSocket Open, DataSocket Write, and DataSocket Close functions in succession repeatedly, LabVIEW leaks memory. 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.
  • If a dialog box is already open, you cannot use the DataSocket Open function.
  • You cannot use the http protocol with the DataSocket VI and functions in LabVIEW-built shared libraries.
  • You cannot use front panel DataSocket data binding with fixed-sized arrays.
  • If you use the DataSocket Server Manager to create a Boolean object, the DataSocket Server Manager converts the Boolean object to numeric data in the configuration file.
Shared Variables
  • You can read from and write to private single-process shared variables.
  • If you open a VI that contains a shared variable from a zip file, LabVIEW displays a file dialog box indicating that it cannot find the file for the global VI associated with the shared variable. Click the Cancel button to recreate the global VI.
  • LabVIEW fails to deploy all shared variables in a library if one shared variable has an invalid binding. To correct this problem, either delete the shared variable that has an invalid binding or unbind the shared variable.
  • If you select File»Save for Previous Version and save a VI that contains a Shared Variable node for LabVIEW 8.0, the VI might not return correct results. If you save the VI for LabVIEW 8.0.1, the VI returns correct results. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • Network-published shared variables do not function properly if multiple network adapters are enabled on the same computer.
Miscellaneous
  • LabVIEW returns out of memory errors when a VI built in one version of LabVIEW calls a DLL that in turn calls another DLL built in a different version of LabVIEW.
  • If the server on which the Xmath license is installed is offline, LabVIEW hangs when you open a VI that contains an Xmath Script node.
  • If a remote panel server is a LabVIEW development system, when a client requests a VI, LabVIEW saves an in-memory image of the VI and sends an up-to-date VI image to the client. Therefore, the remote front panel and the local VI front panel look the same. However, if a built application is a remote panel server, LabVIEW acquires the VI image from disk and sends it to the client. In this case, the VI image that the client receives might be out of sync with the in-memory image of the VI on the server computer if the client connects to a VI that has already been running. The remote front panel might not show an updated version of the VI front panel on the server computer. Refer to the KnowledgeBase at ni.com for more information about using remote panel servers with built applications.
  • If you have more than one Ethernet card, Logos is automatically assigned to the primary Ethernet card. To assign Logos to a different Ethernet card, switch the Ethernet cards.
  • The maximum size of datalog files is 2 GB.
  • .NET type definitions do not correctly update when you change the related assembly.
  • If you use the Edit Items page of the Enum Properties dialog box to edit an enumerated type control that contains a large amount of items, LabVIEW 8.2 might perform slower than LabVIEW 8.0. To avoid this problem, use the Labeling tool to add or edit items directly from the front panel. Refer to the Adding Items to Enumerated Type Controls topic in the LabVIEW Help for more information about adding items to enumerated type controls.


LabVIEW 8.2 Known Issues for MAC Operating System

VIs, Express VIs, and Functions
  • The links to subVIs from the labview\vi.lib directory might break when you use File»Save for Previous Version to save application VIs for a previous version of LabVIEW. <Control>-click the subVIs and select Relink To SubVI from the shortcut menu to relink the subVIs.
  • With automatic saving for recovery, LabVIEW does not save backups of a VI file in an LLB if the name of the VI contains characters such as ? or / that the operating system does not allow. If automatic saving for recovery is enabled, LabVIEW notifies you the first time the VI you are modifying cannot be saved.
  • You cannot use the http protocol with the DataSocket VI and functions in LabVIEW-built shared libraries.
  • You cannot use the DataSocket Write function to write to a text file. To correct this problem, use the File I/O VIs to write to text files.
  • The Read From Measurement File Express VI returns an error if you call it on the same file multiple times, which makes using this Express VI in a subVI problematic.
  • If an example VI from LabVIEW 7.x or earlier opens another VI by specifying the example VI name as a path in the Open VI Reference function, you receive an error when you run that example in LabVIEW 8.x. Remove the String To Path function wired to the vi path input of the Open VI Reference function to correct the error.
  • If you configure a Call Library Function Node to call a LabVIEW DLL, LabVIEW hangs if you place a checkmark in the Specify path on diagram checkbox on the Function page of the Call Library Function dialog box and you select Run in UI thread in the Thread control. If you configure the Call Library Function Node to call a DLL written in C with these same settings, LabVIEW works correctly.
Block Diagram Objects
  • 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.
  • When you select Tools»Compare»Compare VIs and use the Compare VIs dialog box, LabVIEW does not display differences between values of cluster constants.
Environment
  • A blue field does not surround the palette icons for Express VIs from LabVIEW 7.x and earlier that you open in LabVIEW 8.2. For example, if you use a LabVIEW 7.1 toolkit in LabVIEW 8.2, a blue field does not surround the icons for Express VIs on the toolkit palette. You must mass compile the Express VIs to display the blue field around the icons.
  • If you define a custom run-time menu for a control and you save that run-time menu with the control, you cannot localize the run-time menu. As a workaround, you can save the custom run-time menu to an external file and point the control to that file, or you can build the run-time menu dynamically with localized strings.
  • LabVIEW does not correctly hide subpalette menus that belong to locked project libraries.
  • When you print the VI Hierarchy window, LabVIEW does not print the VI labels.
  • Custom run-time menus do not display shortcut key assignments.
LabVIEW Object-Oriented Programming
  • If you delete a control, indicator, or constant of a LabVIEW class, the backup object keeps the LabVIEW class loaded in that application instance. This backup object can cause a problem if the LabVIEW class is loaded in more than one application instance. To edit the LabVIEW class, make sure the class is loaded in only one application instance. The backup object might be the only reason the LabVIEW class stays in memory in an application instance. To remove the backup object for the LabVIEW class, save or close the VI(s). Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • If you rename a parent class while any child classes are in memory, LabVIEW does not record the mutation history of the class correctly. LabVIEW resets any flattened data or non-default data in memory to the default value. To avoid losing data, rename a class only when it is not in memory. Refer to the KnowledgeBase at ni.com for more information about renaming LabVIEW classes.
  • If a LabVIEW class is broken because a member VI is missing from the LabVIEW class, you cannot fix the class by deleting the missing member VI from the Project tree.
Shared Variables
  • You can read from and write to private single-process shared variables.
  • If you open a VI that contains a shared variable from a zip file, LabVIEW displays a file dialog box indicating that it cannot find the file for the global VI associated with the shared variable. Click the Cancel button to recreate the global VI.
  • LabVIEW fails to deploy all shared variables in a library if one shared variable has an invalid binding. To correct this problem, either delete the shared variable that has an invalid binding or unbind the shared variable.
  • If you select File»Save for Previous Version and save a VI that contains a Shared Variable node for LabVIEW 8.0, the VI might not return correct results. If you save the VI for LabVIEW 8.0.1, the VI returns correct results. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • Network-published shared variables do not function properly if multiple network adapters are enabled on the same computer.
Miscellaneous
  • If a remote panel server is a LabVIEW development system, when a client requests a VI, LabVIEW saves an in-memory image of the VI and sends an up-to-date VI image to the client. Therefore, the remote front panel and the local VI front panel look the same. However, if a built application is a remote panel server, LabVIEW acquires the VI image from disk and sends it to the client. In this case, the VI image that the client receives might be out of sync with the in-memory image of the VI on the server computer if the client connects to a VI that has already been running. The remote front panel might not show an updated version of the VI front panel on the server computer. Refer to the KnowledgeBase at ni.com for more information about using remote panel servers with built applications.
  • The maximum size of datalog files is 2 GB.
  • If you use the Edit Items page of the Enum Properties dialog box to edit an enumerated type control that contains a large amount of items, LabVIEW 8.2 might perform slower than LabVIEW 8.0. To avoid this problem, use the Labeling tool to add or edit items directly from the front panel. Refer to the Adding Items to Enumerated Type Controls topic in the LabVIEW Help for more information about adding items to enumerated type controls.
LabVIEW 8.2 Known Issues for LINUX Operating System

VIs, Express VIs, and Functions
  • The links to subVIs from the labview\vi.lib directory might break when you use File»Save for Previous Version to save application VIs for a previous version of LabVIEW. Right-click the subVIs and select Relink To SubVI from the shortcut menu to relink the subVIs.
  • With automatic saving for recovery, LabVIEW does not save backups of a VI file in an LLB if the name of the VI contains characters such as ? or / that the operating system does not allow. If automatic saving for recovery is enabled, LabVIEW notifies you the first time the VI you are modifying cannot be saved.
  • If you run a VI that includes 3D Picture Control VIs more than once, LabVIEW crashes. To correct this problem, either update the DRI drivers for your X server or set the environment variable LIBGL_ALWAYS_INDIRECT to anything.
  • You cannot use the http protocol with the DataSocket VI and functions in LabVIEW-built shared libraries.
  • The Sound File Read VI uses large amounts of memory to read an entire .wav file. Read the data from the .wav file piece by piece rather than in one large file.
  • The Sound Output Set Volume VI returns a warning and fails to set the output volume if the operating system uses a version of the Open Sound System (OSS) driver that does not allow you to set the volume level through the dsp device file.
  • 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.
  • The Read From Measurement File Express VI returns an error if you call it on the same file multiple times, which makes using this Express VI in a subVI problematic.
  • If an example VI from LabVIEW 7.x or earlier opens another VI by specifying the example VI name as a path in the Open VI Reference function, you receive an error when you run that example in LabVIEW 8.x. Remove the String To Path function wired to the vi path input of the Open VI Reference function to correct the error.
  • If you configure a Call Library Function Node to call a LabVIEW DLL, LabVIEW hangs if you place a checkmark in the Specify path on diagram checkbox on the Function page of the Call Library Function dialog box and you select Run in UI thread in the Thread control. If you configure the Call Library Function Node to call a DLL written in C with these same settings, LabVIEW works correctly.
Block Diagram Objects
  • 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.
  • When you select Tools»Compare»Compare VIs and use the Compare VIs dialog box, LabVIEW does not display differences between values of cluster constants.
Environment
  • A blue field does not surround the palette icons for Express VIs from LabVIEW 7.x and earlier that you open in LabVIEW 8.2. For example, if you use a LabVIEW 7.1 toolkit in LabVIEW 8.2, a blue field does not surround the icons for Express VIs on the toolkit palette. You must mass compile the Express VIs to display the blue field around the icons.
  • If you define a custom run-time menu for a control and you save that run-time menu with the control, you cannot localize the run-time menu. As a workaround, you can save the custom run-time menu to an external file and point the control to that file, or you can build the run-time menu dynamically with localized strings.
  • LabVIEW does not correctly hide subpalette menus that belong to locked project libraries.
  • When you print the VI Hierarchy window, LabVIEW does not print the VI labels.
LabVIEW Object-Oriented Programming
  • If you delete a control, indicator, or constant of a LabVIEW class, the backup object keeps the LabVIEW class loaded in that application instance. This backup object can cause a problem if the LabVIEW class is loaded in more than one application instance. To edit the LabVIEW class, make sure the class is loaded in only one application instance. The backup object might be the only reason the LabVIEW class stays in memory in an application instance. To remove the backup object for the LabVIEW class, save or close the VI(s). Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • If you rename a parent class while any child classes are in memory, LabVIEW does not record the mutation history of the class correctly. LabVIEW resets any flattened data or non-default data in memory to the default value. To avoid losing data, rename a class only when it is not in memory. Refer to the KnowledgeBase at ni.com for more information about renaming LabVIEW classes.
  • If a LabVIEW class is broken because a member VI is missing from the LabVIEW class, you cannot fix the class by deleting the missing member VI from the Project tree.
Shared Variables
  • You can read from and write to private single-process shared variables.
  • If you open a VI that contains a shared variable from a zip file, LabVIEW displays a file dialog box indicating that it cannot find the file for the global VI associated with the shared variable. Click the Cancel button to recreate the global VI.
  • LabVIEW fails to deploy all shared variables in a library if one shared variable has an invalid binding. To correct this problem, either delete the shared variable that has an invalid binding or unbind the shared variable.
  • If you select File»Save for Previous Version and save a VI that contains a Shared Variable node for LabVIEW 8.0, the VI might not return correct results. If you save the VI for LabVIEW 8.0.1, the VI returns correct results. Refer to the KnowledgeBase at ni.com for more information about correcting this problem.
  • Network-published shared variables do not function properly if multiple network adapters are enabled on the same computer.
Miscellaneous
  • If you run a VI that calls version 8.0 or 8.0.1 of the LabVIEW Run-Time Engine, LabVIEW crashes.
  • If a remote panel server is a LabVIEW development system, when a client requests a VI, LabVIEW saves an in-memory image of the VI and sends an up-to-date VI image to the client. Therefore, the remote front panel and the local VI front panel look the same. However, if a built application is a remote panel server, LabVIEW acquires the VI image from disk and sends it to the client. In this case, the VI image that the client receives might be out of sync with the in-memory image of the VI on the server computer if the client connects to a VI that has already been running. The remote front panel might not show an updated version of the VI front panel on the server computer. Refer to the KnowledgeBase at ni.com for more information about using remote panel servers with built applications.
  • The maximum size of datalog files is 2 GB.
  • Creating a new project might generate an error if you use Fedora Core 3 or Fedora Core 4 with SELinux. Use the Update Agent to install the latest selinux-policy-targeted package to correct this error.
  • If you use the Edit Items page of the Enum Properties dialog box to edit an enumerated type control that contains a large amount of items, LabVIEW 8.2 might perform slower than LabVIEW 8.0. To avoid this problem, use the Labeling tool to add or edit items directly from the front panel. Refer to the Adding Items to Enumerated Type Controls topic in the LabVIEW Help for more information about adding items to enumerated type controls.


Related Links:
LabVIEW 8.2 Upgrade Notes
LabVIEW 8.2 Release Notes

Attachments:


readmeWindows.htmlreadmeMacOS.htmlreadmeLinux.html

Report Date: 08/04/2006
Last Updated: 12/18/2006
Document ID: 403D2UKP

Your Feedback! poor Poor  |  Excellent excellent   Yes No
 Document Quality? 
 Answered Your Question? 
  1 2 3 4 5
Please Contact NI for all product and support inquiries.submit