Product and company names listed are trademarks or trade names of their respective companies.
This file contains installation and programming considerations and changes that are too recent to be included in the LabWindows/CVI Help. The LabWindows/CVI Release Notes contain important information about changes and enhancements made in LabWindows/CVI 8.0.
Minimum System Requirements
To run LabWindows/CVI 8.0, you must have the following items:
Personal computer using a Pentium 600 or higher microprocessor
Windows 2000/XP
800 × 600 resolution (or higher) video adapter
Minimum of 128 MB of RAM, 256 MB recommended
150 MB free hard disk space
Microsoft-compatible mouse
Installing LabWindows/CVI
National Instruments recommends that you install the complete LabWindows/CVI 8.0 program to take full advantage of all LabWindows/CVI 8.0 functionality. If you choose to install with options, select the options you want and follow the on-screen directions. If necessary, you can run the setup program again to install or remove additional files.
Before Installation
When you install or activate LabWindows/CVI 8.0, your user account must have administrator privileges. When you run LabWindows/CVI for the first time after installation, your user account must have administrator privileges.
You must explicitly check the Win32 SDK feature of the LabWindows/CVI installer to install the complete Windows SDK from the LabWindows/CVI Full Development System (FDS). Some Windows SDK header and import library files are included when you install the LabWindows/CVI Base Package. The Windows SDK help file is available only with the LabWindows/CVI FDS.
The LabWindows/CVI installation includes the LabWindows/CVI 8.0 Run-Time Engine. This version overwrites previous versions of the run-time engine. After you install LabWindows/CVI 8.0, executables and DLLs created with previous versions of LabWindows/CVI automatically use the new LabWindows/CVI 8.0 Run-Time Engine.
If you install LabWindows/CVI onto a network drive, you might encounter an error during installation that prevents files that the IVI Instrument Driver Wizard requires from being installed. This issue does not affect other functionality in LabWindows/CVI.
If you have installed Microsoft Security Update 896358, you might not be able to view topics within the LabWindows/CVI Help if the file is on a network drive. To solve this issue, copy the .chm files that LabWindows/CVI installs to your local hard drive and launch them as normal.
If you uncheck the top-level LabWindows/CVI feature in the installer feature tree, the installer installs some components that you cannot then uninstall. Therefore, National Instruments recommends that you leave the top-level LabWindows/CVI feature checked.
The IVI Installer Creator and IVI Specific Driver Test Suite items are selected by default in the installer feature tree only if the IVI Compliance Package is installed. If the IVI Compliance Package is not installed, you can select these items, but you must then install the IVI Compliance Package from the NI Device Drivers CD to use these features.
Running the Installation
If you have a previous version of LabWindows/CVI installed on your machine, be sure to install version 8.0 in a different directory or uninstall the previous version before installing version 8.0.
Complete the following steps to install LabWindows/CVI:
Run setup.exe from the distribution media where the installation files are located.
On installation startup, the National Instruments LabWindows/CVI 8.0 screen appears. Select Install LabWindows/CVI.
Continue to follow the instructions on the screen.
Activating LabWindows/CVI
Complete the following steps to activate LabWindows/CVI 8.0.
When you launch LabWindows/CVI for the first time after installation, LabWindows/CVI displays the Evaluation License dialog box. Click Activate to launch the NI Activation Wizard.
In the NI Activation Wizard, select one of the following methods to acquire the activation code and click Next.
Automatically activate through a secure Internet connection—Automatically receive an activation code.
Use a Web browser, email client, telephone, or fax machine to acquire an activation code—Contact National Instruments to obtain an activation code. You will then enter the code in the NI Activation Wizard to activate LabWindows/CVI.
Apply a 20-character activation code previously acquired for this computer—Enter a code you have obtained to activate LabWindows/CVI.
The remaining instructions assume you select the Automatically activate through a secure Internet connection option. If you select an alternate option, follow the instructions on the screen to complete product activation.
Enter or verify your serial number. Click Next.
Continue to follow the instructions on the screen.
When you successfully activate LabWindows/CVI, click Finish.
After Installation
Installing LabWindows/CVI in a New Directory—If you installed driver or toolkit software for a previous version of LabWindows/CVI and you install LabWindows/CVI 8.0 in a new directory, you must reinstall the LabWindows/CVI portion of the driver or toolkit software into the new LabWindows/CVI directory.
Known Issues
Updating an Existing Distribution—The LabWindows/CVI distribution creation feature no longer provides the option to include .obj files for both compatible compilers. If you convert an existing distribution that has this option enabled, LabWindows/CVI includes the .obj files only for the current compatible compiler in the updated distribution.
Using the NI Instrument I/O Assistant—The Instrument I/O Assistant 2.0, which is included in the NI Device Drivers CD packaged with LabWindows/CVI, generates LabWindows/CVI code that is not backward compatible with code that previous versions of the Instrument I/O Assistant generate. If you run code generated with the Instrument I/O Assistant 2.0 with an existing application, the code in that application might not compile.
Uninstalling LabWindows/CVI—If you have multiple versions of LabWindows/CVI installed and you uninstall one of the versions, the remaining installation will be missing its file associations, and its automation capabilities will not function properly. To fix this problem, perform a repair installation of the remaining LabWindows/CVI version.
Making Backup .uir Files—If you have been using LabWindows/CVI 7.1 or earlier, make backup copies of your .uir files. Once you save .uir files in LabWindows/CVI 8.0, the .uir files are no longer compatible with versions 7.1 or earlier. You cannot load .uir files that you have saved in LabWindows/CVI 8.0 in LabWindows/CVI 7.1 or earlier.
You can save .uir files you create or load in LabWindows/CVI 8.0 in LabWindows/CVI 7.1 format. Select File»Save .uir As and specify LabWindows/CVI 7.1 User Interface (*.uir) for the Save as type option. If you save a user interface with features that were added in LabWindows/CVI 8.0, those features are removed when you save the file in 7.1 format.
Using Microsoft Excel as an ActiveX Control—If you develop an application that uses Excel as an ActiveX control on a LabWindows/CVI user interface panel, make sure that a separate instance of Excel is not running simultaneously. Otherwise, programmatic calls to the Excel control might not work as expected after the separate Excel application terminates.
Navigating the Tools Library Topics in the LabWindows/CVI Help—If you click a link from a topic in the Tools Library section of the LabWindows/CVI Help or from the toolslib function panel help, you cannot use the Back button in the help viewer toolbar to return to the original topic.
Analysis Function Behavior Changes—The updated Advanced Analysis Library functions are backward compatible with the previous versions. However, the following function behavior has changed with LabWindows/CVI 8.0:
SVD and CxSVD—The following formula defines the SVD factorization of an n-by-m matrix A: A = USVT.
Prior to LabWindows/CVI 8.0, U is an orthogonal matrix of dimensions n-by-m. In LabWindows/CVI 8.0, U is an orthogonal matrix of dimensions n-by-min(n, m).
Prior to LabWindows/CVI 8.0, V is an orthogonal matrix of dimensions m-by-m. In LabWindows/CVI 8.0, V is an orthogonal matrix of dimensions m-by-min(n, m).
Prior to LabWindows/CVI 8.0, S is a diagonal matrix of dimensions m-by-m. In LabWindows/CVI 8.0, S is a diagonal matrix of dimensions min(n, m)-by-min(n, m).
Prior to LabWindows/CVI 8.0, CxSVD has the following requirement: If numberOfRows (n) < numberOfColumns (m), you must allocate m*m*sizeof(ComplexNum) bytes of memory to the input matrix and the U orthogonal matrix. LabWindows/CVI 8.0 no longer has this requirement.
Lu and CxLU—Prior to LabWindows/CVI 8.0, if the input matrix is singular, the functions stop the decomposition and return SingularMatrixErr. In LabWindows/CVI 8.0, if the input matrix is singular, the functions complete the decomposition and return SingularMatrixWarn. In this case, there are one or more zero elements along the diagonal of U.
CxTrace—CxTrace accepts only a square matrix. Prior to LabWindows/CVI 8.0, the function requires both the number of rows and the number of columns as input parameters. In LabWindows/CVI 8.0, matrixSize specifies both the number of rows and the number of columns. The numberOfColumns parameter prior to LabWindows/CVI 8.0 is a reserved parameter in LabWindows/CVI 8.0. This parameter is not referenced in the function.
ConditionNumber and CxConditionNumber—Prior to LabWindows/CVI 8.0, these functions return NaN for singular input matrices. In LabWindows/CVI 8.0, these functions return Inf for singular input matrices.
GenLSFit—In LabWindows/CVI 8.0, GenLSFit calculates the mean squared error as the weighted mean square error, which differs from the prior implementation of the function.
发表于 2022-5-18 15:28:15
