CVI™, National Instruments™, NI_DAQ™, NI-VISA™, the National Instruments logo, and The Software is the Instrument™ are trademarks of National
Instruments Corporation. Product and company names are trademarks or trade names of their respective companies.
National Instruments Corporation3LabWindows/CVI Release Notes for Windows
Introduction to LabWindows/CVI
These release notes contain installation instructions, system requirements, new features, and
updated information to help you begin using LabWindows/CVI, version 5.0.
LabWindows/CVI Installation for Windows
Before working o n your data acqui sition and instrumen t control appli cations, you mus t install
LabWindo ws/CVI on your com puter . The LabW indo ws/CVI setup p rogram does this for y ou
in a process that lasts approximately 10 minutes.
Minimum System Requirements for Windows 95/NT
To run LabWindows/CVI for Windows 95/NT, you must have the following:
•Windows 95 or Microsoft Windows NT operating system, version 4.0 or higher
•Personal computer using at least a 33 MHz 486 or higher microprocessor
•VGA resolution (or higher) video adapter
•Minimum of 16 MB of memory
•50 MB free hard disk space
•Microsoft-compatible mouse
Note
The dialog box the Edit Instrument Attributes command displays requires an
800-by-600 video adapter resolution.
Minimum System Requirements for Windows 3.1
To run LabWindows/CVI for Windows 3.1, you must have the following:
•MS-DOS, version 3.1 or higher
•Windows operating system, version 3.1 or higher
•Personal computer using at least a 33 MHz 386 or higher microprocessor
•VGA resolution (or higher) video adapter
•Math coprocessor or one of the following coprocessor emulation programs:
–WEMM387.386 from Watcom
–Q387 from Quickware
•Minimum of 8 MB of memory
•30 MB free hard disk space
•Microsoft-compatible mouse
Note
The dialog box the Edit Instrument Attributes command displays requires an
800-by-600 video adapter resolution.
1.Make sure that your computer and monitor are on and that Windows is installed.
2.If installing fro m disket te, make back-up copi es of your LabWindo ws/CVI di skette s and
store the originals in a safe place.
3.Close all open Windows applications and leave the operating system in Windows.
4.Insert the installation CD into the CD-ROM drive or insert Disk 1 into drive A or drive B
and close the drive door, if necessary.
5.For Windows 95 or Windows NT version 4.0 or higher, choose the Run option from the
desktop taskbar. For Windows 3.1, choose Run from the File menu in the Program
Manager.
6.Type
7.Follow the instructions that appear in the dialog boxes.
x
:setup (where
on OK.
x
is the drive you are using) in the command line box and click
Note
When you install LabWindows/CVI for Windows 95/NT, you must choose your
compatible compiler. If sometime later you want to change your choice, run the
installation progra m again and select the option that allows you to choose a new
compatible compiler. This method is much faster than changing your compiler
choice by reinstalling LabWindows/CVI.
Note
You must choose the Custom Installation option to install the complete
Windows SD K fro m the CD-ROM version of the LabWindows/CVI FDS (Full
Development System). Some Windows SDK header and import library files are
installed with the disk version and the CD-ROM version for the LabWindows/CVI
Base Package. The Windows SDK help file is available only with the CD-ROM
version of the LabWindows/CVI FDS.
National Instruments suggests you install the complete LabWindows/CVI program to take
full advantage of all the LabWindows/CVI capabilities. If you choose to install with options,
select the options you want and follow the directions on the screen. You can run the setup
program again and install additional files, if necessary.
Refer to the
readme.cvi file for installat io n instr uctions , program ming con siderat ions, and
changes that are too recent to be included in the printed LabWindows/CVI documentation.
Installing the Run-Time Engine on a Computer
The Run-time Engine is installed during the LabWindows/CVI installation.
LabWindows/CVI includes a separate Run-time Engine distribution disk, or a directory on
the CD-ROM, that has its own installation program so you can make copies for distribution
as your license agreement permits.
To install the Run-time Engine from the Run-time Engine distribution disk, follow the
directions in the Installing LabWindows/CVI on a Computer section earlier in this document.
Refer to Chapter 7, Creating and Distributing Standalone Executables and DLLs, of the
National Instruments Corporation5LabWindows/CVI Release Notes for Windows
LabWindows/C VI Pro gramme r Refe rence M anual for a descript ion of the LabW indo ws/CVI
Run-time Engine.
NoteThe LabWindows/CVI 5.0 Run-time Engine for Windows 95/NT overwrites
previous versions of the Run-time Engine. Thus, LabWindows/CVI 4.x-generated
executables and DLLs use the new LabWindows/CVI 5.0 Run-time Engine. In
addition, the LabWindows/CVI 4.x Create Distribution Kit feature includes the
LabWindows/CVI 5.0 Run-time Engine instead of the LabWindows/CVI 4.x
Run-time Engine in genera ted distribution kits.
Installing the VISA Library
You need the VISA Library to use the new instrument driver standard the VXIplug&play
Systems Alliance accepts. VISA stands for Virtual Instrument Software Architecture.
NI-VISA is installed as part of the LabWindows/CVI disk and CD-ROM installations for
Windows 95/NT. NI-VISA must be installed separately for LabWindows/CVI for
Windows 3.x.
Installing the IVI Engine
You need the IVI Engine to use IVI (Intelligent Virtual Instruments) drivers on a system. The
IVI Engine is installed as part of LabWindows/CVI for Windows 95/NT and Windows 3.x.
LabWindows/CVI for Windows 95/NT includes a separate set of IVI Engine distribution
disks or a directory on the CD-ROM that has its own installation program so you can make
copies for distrib uti on with you r appl icati o n. On Windows 3.x, the IVI Engine is a static
library that is linked into your application.
What’s New and Different in LabWindows/CVI 5.0
This section includes inf ormatio n about changes an d enhancement s in LabW ind ows/C VI 5.0
that have been made since LabWindows/CVI 4.0.1.
New Features
•IVI (Intelligent Virtual Instruments) driver wizard and support library
•ActiveX Automation Server instrument driver wizard and support library
•DLL debugging in the LabWindows/CVI development environment
•Multithread-safe libraries on Windows 95/NT ; refer to the discussion of each library for
any restrictions
•Direct printing replaces bitmap printing on all Windows platforms
•Ability to scale panels and contents to different screen resolutions and when you resize
the panels
•New Advanced Analysis functions for Vector & Matrix Algebra
National Instruments Corporation7LabWindows/CVI Release Notes for Windows
New Sample Projects
ActiveX Automation of LabWindows/CVI 5.0
to build and run projects
ActiveX Automation of Microsoft Excel 97
Table 2.
New Sample Projects (Continued)
FilenameDescription
hiq\report.prj
hiq\xferdta.prj
ie\iedemo.prj
labview\lvdemo.prj
word\worddemo.prj
samples\analysis\
2dfft.prj
nlinfit.prj
parsevls.prj
polyfit1.prj
transmit.prj
thd.prj
stat.prj
ActiveX Automation of HiQ 3.1/4.0 to generate
a report
ActiveX Automation of HiQ 3.1/4.0 to
transfer data
ActiveX Automation of Microsoft Internet
Explorer 4.0
ActiveX Automation of LabVIEW 5.0
to run VIs
ActiveX Automation of Microsoft Word 97
Demonstrates using FFT to do a 2D FFT
NonLinearFit using the
Levenberg-Marquardt method
Demonstrates Parseval’s theorem
Demonstrates data conditioning for PolyFit
Simulates a transmission and receiver system
Total Harmon ic Distortion
Simple statistics example
stability.prj
samples\custctrl\cviogl
ogldemo.prj
ogldraw.prj
simple.prj
samples\dlldebug
scope.prj and usescope.prj
samples\toolbox
asyncdem.prj
LabWindows/CVI Release Notes for Windows8
Evaluates the stability of the system
3D graph plotting using CVIOGL
instrument driver
Uses CVIOGL instrument driver for OpenGL
rendering
Uses SDK to change Standard Input/Output
window appearance
Creates icon on system taskbar
Queries system for available printers
Demonstrates using OpenGL Glaux library
for 3D rendering
Demonstrates using UIR panels in
multiple threads
Demonstrates using non-UIR threads
Demonstrates UIR panel scaling
Changes to the LabWindows/CVI Development
Environment
This section contains information on several enhancements to the LabWindows/CVI
development environment.
Debugging DLLs in Windows 95/NT
You can now debug DLLs in the LabWindows/CVI development environment. Refer to the
DLL Debugging (Windows 95/NT Only) section in Chapter 3, Project Window, of the
LabWindows/CVI User Manual for more information on different ways to debug DLLs,
location of files required for debugging DLLs, and what restrictions apply.
DLL Debugging Menu Item (Windows 95/NT Only)
This command applies only when you set the Target item in the Build menu to
Dynamic Link Library. If the DLL Debugging command is enabled when you create a
DLL, LabWindows/CVI includes debuggable code in your DLL and generates an extra file
that contains a symbol table and source position information necessary for debugging. The
extra file has the same pathname as the DLL except that its extension is
National Instruments Corporation9LabWindows/CVI Release Notes for Windows
.cdd.
In the LabWind ows/CVI development environment, you can debug only DLLs you create in
LabWindows/CVI with the DLL Debugging command enabled. Other development
environments cannot debug DLLs you create in LabWindows/CVI.
When you debug a DLL in LabWindows/CVI, you can use all the standard debugging
features, but the run-time checking features are not available. Thus, you can use
single-stepping, conditional breakpoints, watch expressions, and the Variables window, but
there is no interactive r epor ting of library errors and no protection ag ainst o v erwriting arrays
or misuse of pointers. When you create a DLL with the DLL Debugging command disabled,
LabWindows/CVI forces the debugging level to None. When you create a DLL with the
DLL Debugging comma nd enabled, LabWindows/CVI forces the debugging level to
No Run-Time checking. You can access the deb ugging level fr om the Run Options command
in the Options menu of the Project window.
Select External Process
This command applies only when you set the Target item in the Run menu to
Dynamic Link Library. The Select External Process command allows you to specify a
standalone executable that uses your DLL. When you execute the command, a dialog box
appears in which you enter the pathname and command line arguments to an external
program. The Run Project item in the Run menu then changes to Run xxx.exe, where
xxx
.exe is the filename of the ex ternal program. When you execute the Run xxx.exe
command, LabWindows/CVI starts the external process and attaches to it for debugging. If
you have s et an y br eakpoi nts in the sour ce f il es for t he DLL, LabWindows/CVI honors th em.
LabWindows/CVI stores external program pathname and command line arguments in
the project.
Automatic Generation of Object Files
The new O icon in the Pro ject windo w applies on ly to source ( .c) files and indicates that you
enabled the Compile into Object option. If this option is enabled when you compile the source
file, LabWindows/CVI creates an object (
non-debuggable code rather than generating debuggable code in memory. Double click on
this icon to toggle the option.
When you open a project, LabWindows/CVI marks each source file with the
compilation only if one of the following conditions applies:
•The object file does not exist on disk.
•The source file or any of the include files on which it depends has a date later than the
date of the object file.
As you work, LabWindows/CVI marks source files for recompilation whenever they or any
of their include files are modified, regardless of the state of the
Build Project or Run Project command, LabWindows/CVI co mpiles all source files marked
for recompilation. For source files with the
corresponding object files.
This feature is useful if you do not want to recompile all your source files each time you load
your project. Debu gging is no t av ailab le for f iles wit h the
when you want to suppress debugging on a source file.
O icon, so this feature also is useful
Create Dynamic Link Library Dialog Box
The ring control Where to Copy DLL allows you to instruct LabWindows/CVI to copy the
DLL to a different directory after you create it. Your choices are the following:
•Do not copy
•Windo ws System directory
•VXIplug&play directory (the
directory)
If you choose to include a type library when yo u create a DLL, LabWindows/CVI now saves
the GUID for the type library in the project. Previous versions of LabWindows/CVI do not
generate a new GUID each time you build the DLL. If you also choose the Include File
Symbols for the exports option, LabWindows/CVI now adds to the type library the integer and
floating-point constants and enums from the header file you specify for the exports.
bin
directory under the VXIplug&play framework
Breakpoints/Tags in Non-Project Files Are Saved in Project
Previous versions of LabWindows/CVI do not sav e breakpoints or tags you set in files that are
not in the project. Also, when you unload the project, b reakpoints and tags in non-project f iles
remain in effect.
T o accomm odate DLL debugg ing, LabWindows/CVI 5.0 now saves all breakpoints and tags
in the project, regardless of whether the f iles to which they apply are in the pr oject. When you
unload the project, LabW in dows/ CVI remov es all br eakpoints and t ags from any non-p roject
files you might hav e open. Ho wev er , LabW indo ws/CVI does n ot sav e breakpoi nts and tags in
the Interactive E x ecu tio n window in the project and does not remove them when yo u unload
a project.
New Control in Watch Expression Dialog Box
Project/DLL is a new control in the Add/Edit Watch Expression dialog box. You use this
control when you debug a DLL but do not have the project for the DLL open. The control
indicates whether the watch expression applies to the current project or to a separate DLL.
The default value for the control is Current Project.
If you want the watch expression to app ly to a DLL that is no t the target of th e current project,
you must supply the name of the DLL. A menu ring to the right of the control contains the
current project value and the names of all currently loaded DLLs.
Activate Panels When Resuming: Clarification
When you enable the Activate Panels When Resuming option in the Run menu of the
Source window, LabWindows/CVI activates your most recently active panel upon resuming
National Instruments Corporation11LabWindows/CVI Release Notes for Windows
execution only if it was the active window at the time execution was suspended. If a
LabWindows/CVI window, such as a Source window, was active at the time execution was
suspended, LabWindows/CVI does not reactivate a window.
For instance, if you suspend execution by selecting the Break Execution option from the
Run menu in a Source window, LabWindows/CVI does not reactivate a window when you
resume execution.
New Print Dialog Box
For more information on printing graphics and text on Windows using the reorganized Print
dialog box, refer to the Revised Pri nt Dialog Boxes on Windowssection in the Chan ges to the
User Interface Library section later in this document.
New Options for Source File Printing
New options fo r printin g source f iles i nclude addi ng the date , time, and f il ename at th e top of
each page, adding page numbering, and choosing various text style options. The text style
options apply to Windows platforms only. The new options on the dialog box correspond to
the new text printing attributes in the User Interface Library. Refer to the Application of
Attributes to Text Printing and New Print Attributes sections in the Changes to the User
Interface Li brary section later in this document.
Edit Menu
The Find and Replace commands of the Edit menu of the Function T ree Editor win dow and
the Function Panel Editor window open dialog boxes similar to the Find and Replace dialog
boxes in the Source window , which allo w you to search and replace text in the entire function
.fp).
panel (
Code Menu
In certain cases, the Select Attribute Constant command in the Code menu replaces the
Select UIR Constant command. This occurs in panels for functions that set or get attribute
values. The User Interface Library, the VISA Library, and IVI dri vers include such functions,
for example,
SetPanelAttribute in the User Interface Library. The panels for these functions each
contain an Attribute ring control and a corresponding Value input control. When you use
either of these two controls, the Select Attribute Constant command appears in the Code
menu. The action of the command differs based on whether you use the Attribute or
Value control.
GetCtrlAttribute, SetCtrlAttribute, GetPanelAttribute, and
New Tools Menu
This section describes the commands in the Tools menu of the Project, Source, Function
Panel, Function Tree Editor, and Fun ction Panel Editor windows.