LabVIEW 2010 Service Pack 1 Readme for Windows
Version 10.0.1
December 2010
This file contains important last-minute information about LabVIEW 2010 Service Pack 1 (SP1) for Windows, including installation and upgrade issues, compatibility issues, a partial list of bugs fixed for LabVIEW 2010 SP1, changes from LabVIEW 2010, and a link to the Web page that contains known issues for LabVIEW.
Refer to the LabVIEW Upgrade Notes for more information about upgrade and compatibility issues and a complete list of new features in LabVIEW 2010 and related service packs. Refer to the LabVIEW Release Notes for installation instructions and a complete list of system requirements. After you install LabVIEW, refer to the labviewmanuals directory to access these documents. You also can access the LabVIEW Release Notes and LabVIEW Upgrade Notes at ni.com.
Refer to the National Instruments Web site for the latest information about LabVIEW 2010 SP1.
Refer to the labview
eadme directory for readme files about LabVIEW add-ons, such as modules and toolkits.
Installing LabVIEW 2010 SP1
Installing Another Language Version
Licensing
Known Issues
LabVIEW 2010 SP1 (64-bit)
Additions to the LabVIEW Help
Bug Fixes
Installing LabVIEW 2010 SP1
If you have LabVIEW 2010 installed, you can install LabVIEW 2010 SP1 without uninstalling LabVIEW 2010.
Note: You cannot have both LabVIEW 2010 and LabVIEW 2010 SP1 installed simultaneously because LabVIEW 2010 SP1 installs over LabVIEW 2010.
If you do not have LabVIEW 2010 installed, you can install LabVIEW 2010 SP1 without first installing LabVIEW 2010.
Refer to the LabVIEW Release Notes for more information about installing LabVIEW on Windows.
Installing Another Language Version
If you have LabVIEW 2010 SP1 installed in another language, uninstall that version before you install the new language version.
Licensing
LabVIEW relies on licensing activation. You must activate a valid LabVIEW license before you can run LabVIEW. To activate the license, use the serial number you received as part of your installation package. If you upgrade to LabVIEW 2010 SP1 from LabVIEW 2010, use your existing LabVIEW 2010 serial number during installation.
Refer to the LabVIEW Release Notes for more information about licensing in LabVIEW.
Known Issues
You can access the software and documentation known issues list online. Refer to the National Instruments Web site for an up-to-date list of known issues in LabVIEW 2010 and related service packs.
LabVIEW 2010 SP1 (64-bit)
When run on Windows (64-bit), LabVIEW 2010 SP1 (64-bit) provides access to more memory than a 32-bit operating system or a 32-bit application can provide. LabVIEW 2010 SP1 (64-bit) includes nearly all of the development environment features of LabVIEW 2010 SP1 (32-bit), including the LabVIEW Application Builder.
Refer to the National Instruments Web site for information about obtaining a copy of LabVIEW 2010 SP1 (64-bit).
Supported Hardware
LabVIEW 2010 SP1 (64-bit) supports many hardware devices. Drivers are available for DAQ devices, VISA devices, GPIB devices, and image acquisition devices. For GPIB devices, you must use at least NI-488.2 2.6 for Windows. Refer to the specific hardware documentation for more information about compatibility with LabVIEW 2010 SP1 (64-bit).
Supported Modules
LabVIEW 2010 SP1 (64-bit) supports only the NI Vision Development Module. Refer to the Vision Development Module documentation for more information. LabVIEW 2010 SP1 (64-bit) does not support any additional modules.
Additions to the LabVIEW Help
The following list contains additional changes to LabVIEW that are not included in the LabVIEW Help, the LabVIEW Upgrade Notes, or both:
The Mass Compile dialog box includes the Include warnings for read-only VIs checkbox, which determines whether the mass compile results include warnings next to the read-only VIs.
The Advanced TDMS palette includes the TDMS Generate Random Data VI, which generates random data that you can use to test the performance of the Advanced TDMS VIs and functions.
The TDMS Configure Asynchronous Writes function does not include the data mode input.
On the Web Server page of the Options dialog box, the Configure Web Application Server button launches NI Web-based Monitoring and Configuration on the local system.
On the Web Server page of the Options dialog box, the Enable Web Server checkbox is renamed Enable Remote Panel Server.
In the Icon Editor dialog box, select Edit»Import Icon from Owning Library to import the icon of the owning project library. LabVIEW creates a user layer with the name NI_Library and with the icon of the owning library as the glyph. If a user layer with that name already exists, the new user layer overwrites the existing user layer.
The VISA Find Resource function returns error code -1073807343 if the system locates no devices.
LabVIEW 2010 and related service packs do not support the Disconnect Polys And Typedefs method.
If you wire a combination of signed and unsigned integers to the upper limit, x, and lower limit inputs of the In Range and Coerce function, the data type of the coerced(x) output must be large enough to represent the full range of possible input values. If the coerced(x) output is an unsigned integer, the signed input values must be positive because an unsigned integer cannot represent a negative number.
When a change to a VI in a packed project library impacts the inplaceness of the connector pane, by default the caller VI adapts to inplaceness changes. As a result, you do not need to recompile the VI that calls the packed library. If you want the caller VI to recompile when the inplaceness changes, remove the checkmark from the Callers adapt at run time to Exported VI connector pane state checkbox on the Connector Pane State page of the Packed Library Properties dialog box. If you make a non-inplaceness change to a VI in a packed library, the VI must recompile.
Some National Instruments components require Microsoft Silverlight 4.0. If you use a component that requires Silverlight, a dialog box prompts you to install Silverlight from the Internet. Microsoft Silverlight 4.0 is available from the Microsoft Web site at microsoft.com/silverlight.
Due to compiler optimizations in LabVIEW 2010 and related service packs, VIs can execute faster but might take up to five times longer to compile. You might not notice these changes unless you load a large VI. Refer to the National Instruments Web site for more information about compiler optimizations.
Bug Fixes
The following table contains the IDs and titles of a subset of issues fixed in LabVIEW 2010 SP1. If you have a CAR ID, you can search this list to validate the issue has been fixed.
240720—Array subset doesn't get copied at inplace node boundary
246966—Write to Text File output changed from LabVIEW 2009 to 2010 if the user selects cancel in the file dialog
255982—Child Class Property Node does not output until deleting and rewiring any part of the VI
256324—Indicator in LabVIEW 2010 subVI does not update from local variable
276831—Output of zero generated from the multiply node with certain DAQmx properties and VIs when using highlight execution
To force a recompile of a VI without recompiling its subVIs, press the <Ctrl> key while you click the Run button. To force a recompile of all VIs in memory, press the <Ctrl-Shift> keys while you click the Run button. To force a recompile of the entire current VI hierarchy, close all VIs currently opened, open the top-level VI, and press the <Ctrl-Shift> keys while you click the Run button. This method does not recompile any of the VIs called dynamically in the hierarchy.
You also can force a recompile of all VIs in a specified directory using the following steps.
Open LabVIEW.
Select Tools»Advanced»Mass Compile to display the Mass Compile dialog box.
Navigate to the desired directory and click the Current Folder button.
Click the Mass Compile button to force a recompile of all VIs in that directory.
Click the Done button to return to LabVIEW.
Copyright
© 2010 National Instruments Corporation. All rights reserved.
For copyright notices, conditions, and disclaimers, including information regarding certain third-party components used in LabVIEW, refer to the Copyright topic of the LabVIEW Help.
Trademarks
LabVIEW, National Instruments, NI, ni.com, LabVIEW, the National Instruments corporate logo, and the Eagle logo are trademarks of National Instruments Corporation. Refer to the Trademark Information at ni.com/trademarks for other National Instruments trademarks.
Patents
For patents covering the National Instruments products/technology, refer to the appropriate location: Help» Patents in your software, the patents.txt file on your media, or the National Instruments Patent Notice at ni.com/patents.