Labview Core 2 Course Manual: Instruments Not For Distribution

uti ts
LabVIEW Core 2 TM
rib en
Course Manual
on
ist um
Course Software Version 2011
August 2011 Edition
r D str
Part Number 325292C-01
LabVIEW Core 2 Course Manual
Copyright
© 1993–2011 National Instruments Corporation. All rights reserved.
t fo l In
Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including
photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent
of National Instruments Corporation.
National Instruments respects the intellectual property of others, and we ask our users to do the same. NI software is protected by
copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to
others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable
license or other legal restriction.
No na
For components used in USI (Xerces C++, ICU, HDF5, b64, Stingray, and STLport), the following copyright stipulations apply. For a
listing of the conditions and disclaimers, refer to either the USICopyrights.chm or the Copyrights topic in your software.
Xerces C++. This product includes software that was developed by the Apache Software Foundation (http://www.apache.org/).
Copyright 1999 The Apache Software Foundation. All rights reserved.
ICU. Copyright 1995–2009 International Business Machines Corporation and others. All rights reserved.
tio
HDF5. NCSA HDF5 (Hierarchical Data Format 5) Software Library and Utilities
Copyright 1998, 1999, 2000, 2001, 2003 by the Board of Trustees of the University of Illinois. All rights reserved.
b64. Copyright © 2004–2006, Matthew Wilson and Synesis Software. All Rights Reserved.
Stingray. This software includes Stingray software developed by the Rogue Wave Software division of Quovadx, Inc.
Copyright 1995–2006, Quovadx, Inc. All Rights Reserved.
Na
STLport. Copyright 1999–2003 Boris Fomitchev

Trademarks
CVI, LabVIEW, National Instruments, NI, ni.com, 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.
The mark LabWindows is used under a license from Microsoft Corporation. Windows is a registered trademark of Microsoft
Corporation in the United States and other countries. Other product and company names mentioned herein are trademarks or trade
names of their respective companies.
Members of the National Instruments Alliance Partner Program are business entities independent from National Instruments and have
no agency, partnership, or joint-venture relationship with National Instruments.
Patents
For patents covering 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.
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na
Worldwide Technical Support and Product Information

ni.com
Worldwide Offices
Visit ni.com/niglobal to access the branch office Web sites, which provide up-to-date contact information, support phone
numbers, email addresses, and current events.
National Instruments Corporate Headquarters
11500 North Mopac Expressway Austin, Texas 78759-3504 USA Tel: 512 683 0100
For further support information, refer to the Additional Information and Resources appendix. To comment on National Instruments
documentation, refer to the National Instruments Web site at ni.com/info and enter the Info Code feedback.
Contents
Student Guide
uti ts
A. NI Certification .....................................................................................................v
B. Course Description ...............................................................................................vi
C. What You Need to Get Started .............................................................................vii
D. Installing the Course Software..............................................................................vii
rib en
E. Course Goals.........................................................................................................viii
F. Course Conventions ..............................................................................................ix
on
Lesson 1
ist um
Common Design Techniques
A. Design Patterns .....................................................................................................1-2
B. Single Loop Design Patterns.................................................................................1-3
C. Multiple Loop Design Patterns .............................................................................1-7
D.
r D str Timing a Design Pattern .......................................................................................1-11
Lesson 2
Synchronization Techniques
A. Notifiers ................................................................................................................2-2
B. Queues ..................................................................................................................2-3
t fo l In
Lesson 3
Event Programming
A. Events....................................................................................................................3-2
B. Event-Driven Programming..................................................................................3-3
No na
C. Caveats and Recommendations ............................................................................3-11

D. Event-Based Design Patterns................................................................................3-11
Lesson 4
tio
Error Handling
A. Importance of Error Handling...............................................................................4-2
B. Detect and Report Errors ......................................................................................4-2
C. Errors and Warnings .............................................................................................4-3
D. Ranges of Error Codes ..........................................................................................4-4
Na
E. Error Handlers.......................................................................................................4-5
Lesson 5
Controlling the User Interface
A. Property Nodes .....................................................................................................5-2
B. Invoke Nodes ........................................................................................................5-4
C. VI Server Architecture..........................................................................................5-5
D. Control References ...............................................................................................5-6
© National Instruments Corporation iii LabVIEW Core 2 Course Manual

Contents
Lesson 6
File I/O Techniques
A. File Formats ..........................................................................................................6-2
B. Binary Files...........................................................................................................6-4
uti ts
C. TDMS Files...........................................................................................................6-12
Lesson 7
rib en
Improving an Existing VI
A. Refactoring Inherited Code...................................................................................7-2
on
B. Typical Refactoring Issues....................................................................................7-4
C. Comparing VIs......................................................................................................7-7
ist um
Lesson 8
Creating and Distributing Applications
A. Preparing the Files ................................................................................................8-2
B. Build Specifications ..............................................................................................8-3
r D str
C. Building the Application and Installer..................................................................8-5
Appendix A
Additional Information and Resources
t fo l In
Glossary
No na
tio
Na
LabVIEW Core 2 Course Manual iv ni.com

Student Guide
Thank you for purchasing the LabVIEW Core 2 course kit. You can begin
developing an application soon after you complete this course. This course
uti ts
manual and the accompanying software are used in the two-day, hands-on
LabVIEW Core 2 course.
rib en
You can apply the full purchase of this course kit toward the corresponding
course registration fee if you register within 90 days of purchasing the kit.
on
Visit ni.com/training for online course schedules, syllabi, training
centers, and class registration.
ist um
A. NI Certification
The LabVIEW Core 2 course is part of a series of courses designed to build
your proficiency with LabVIEW and help you prepare for the NI Certified
LabVIEW Associate Developer exam. The following illustration shows the
r D str courses that are part of the LabVIEW training series. Refer to ni.com/
training for more information about NI Certification.
t fo l In
New User Experienced User Advanced User

Courses
LabVIEW Core 1* LabVIEW Core 3* Managing Software

Engineering in LabVIEW
LabVIEW Core 2*
LabVIEW Connectivity Advanced Architectures
No na
in LabVIEW
Object-Oriented Design
and Programming
in LabVIEW
LabVIEW Performance
Certifications
tio
Certified LabVIEW Certified LabVIEW Certified LabVIEW

Associate Developer Exam Developer Exam Architect Exam
Other Courses
LabVIEW Instrument Control

Na
LabVIEW Real-Time 1 LabVIEW Real-Time 2

LabVIEW FPGA LabVIEW DAQ and Signal Conditioning Modular Instruments Series
*Core courses are strongly recommended to realize maximum productivity gains when using LabVIEW.
© National Instruments Corporation v LabVIEW Core 2 Course Manual

Student Guide
B. Course Description
The LabVIEW Core 2 course teaches you programming concepts,
techniques, features, VIs, and functions you can use to create test
uti ts
and measurement, data acquisition, instrument control, datalogging,
measurement analysis, and report generation applications. This course
assumes that you are familiar with Windows, that you have experience
rib en
writing algorithms in the form of flowcharts or block diagrams, and that you
have taken the LabVIEW Core 1 course or have equivalent experience. The
on
course and exercise manuals are divided into lessons, described as follows.
In the course manual, each lesson consists of the following:
ist um
• An introduction that describes the purpose of the lesson and what
you will learn
• A description of the topics in the lesson
r D str • A summary quiz that tests and reinforces important concepts and
skills taught in the lesson
In the exercise manual, each lesson consists of the following:

• A set of exercises to reinforce those topics
• Some lessons include optional and challenge exercise sections or
t fo l In
a set of additional exercises to complete if time permits
Note For course and exercise manual updates and corrections, refer to ni.com/info
and enter the Info Code core2.
No na
Several exercises use a plug-in multifunction data acquisition (DAQ) device

connected to a DAQ Signal Accessory or BNC-2120 containing a
temperature sensor, function generator, and LEDs.
If you do not have this hardware, you still can complete the exercises.
tio
Alternate instructions are provided for completing the exercises without

hardware. Exercises that explicitly require hardware are indicated with
an icon, shown at left. You also can substitute other hardware for those
previously mentioned. For example, you can use another National
Na
Instruments DAQ device connected to a signal source, such as a function

generator.
LabVIEW Core 2 Course Manual vi ni.com

Student Guide
C. What You Need to Get Started

Before you use this course manual, make sure you have all of the following
items:
uti ts
❑ Windows XP or later installed on your computer; this course is
optimized for Windows XP
rib en
❑ Multifunction DAQ device configured as Dev1 using Measurement &
Automation Explorer (MAX)
on
❑ DAQ Signal Accessory or BNC-2120, wires, and cable
ist um
❑ LabVIEW Professional Development System 2011 or later
❑ DAQmx 9.3.5 or later

r D str ❑ LabVIEW Core 2 course CD, from which you install the following
folders:
Directory Description
Exercises Contains VIs used in the course
t fo l In
Solutions Contains completed course exercises
D. Installing the Course Software

Complete the following steps to install the course software.
No na
1. Insert the course CD in your computer. The LabVIEW Core 2 Course

Setup dialog box appears.
2. Click Install the course materials.
tio
3. Follow the onscreen instructions to complete installation and setup.
Exercise files are located in the <Exercises>\LabVIEW Core 2\ folder.
Note Folder names in angle brackets, such as <Exercises>, refer to folders on the root
Na
directory of your computer.
© National Instruments Corporation vii LabVIEW Core 2 Course Manual

Student Guide
E. Course Goals
This course prepares you to do the following:
• Apply common design patterns that use notifiers, queues, and events
uti ts
• Use event programming effectively
• Programmatically control user interface objects
rib en
• Evaluate binary file I/O formats and use them in applications
• Modify existing code for improved usability
on
• Prepare, build, and deploy stand-alone applications
ist um
You will apply these concepts as you build a project that uses VIs you create
throughout the course. While these VIs individually illustrate specific
concepts and features in LabVIEW, they constitute part of a larger project
built throughout the course.
r D str This course does not describe any of the following:
• LabVIEW programming methods covered in the LabVIEW Core 1
course
• Every built-in VI, function, or object; refer to the LabVIEW Help for
t fo l In
more information about LabVIEW features not described in this course
• Developing a complete application for any student in the class; refer to
the NI Example Finder, available by selecting Help»Find Examples,
for example VIs you can use and incorporate into VIs you create
No na
tio
Na
LabVIEW Core 2 Course Manual viii ni.com

Student Guide
F. Course Conventions
The following conventions appear in this course manual:
uti ts
» The » symbol leads you through nested menu items and dialog box options
to a final action. The sequence Tools»Instrumentation»Find Instrument
Drivers directs you to drop down the Tools menu, select the
rib en
Instrumentation item, and finally select the Find Instrument Drivers
option.
on
This icon denotes a tip, which alerts you to advisory information.
ist um
This icon denotes a note, which alerts you to important information.
This icon denotes a caution, which advises you of precautions to take to

avoid injury, data loss, or a system crash.
bold r D str Bold text denotes items that you must select or click in the software, such as
menu items and dialog box options. Bold text also denotes sections of dialog
boxes and hardware labels.
italic Italic text denotes variables, emphasis, a cross-reference, or an introduction

to a key concept. Italic text also denotes text that is a placeholder for a word
t fo l In
or value that you must supply.
monospace Text in this font denotes text or characters that you should enter from the
keyboard, sections of code, programming examples, and syntax examples.
This font is also used for the proper names of disk drives, paths, directories,
programs, subprograms, subroutines, device names, functions, operations,
No na
variables, filenames, and extensions.
monospace bold Bold text in this font denotes the messages and responses that the computer
automatically prints to the screen. This font also emphasizes lines of code
tio
that are different from the other examples.
Platform Text in this font denotes a specific platform and indicates that the text
following it applies only to that platform.
Na
© National Instruments Corporation ix LabVIEW Core 2 Course Manual

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on
Common Design Techniques
1
uti ts
You can develop better programs in LabVIEW and in other programming
rib en
languages if you follow consistent programming techniques. Design
patterns represent techniques that have proved themselves useful time and
on
time again. To facilitate development, LabVIEW provides templates for
several common design patterns. This lesson discusses two different
categories of programming design patterns—single loop and multiple loops.
ist um
Single loop design patterns include the simple VI, the general VI, and the
state machine.
Multiple loop design patterns include the parallel loop VI, the master/slave,
and the producer/consumer.
r D str Understanding the appropriate use of each design pattern helps you create
more efficient LabVIEW VIs.
Topics
t fo l In
A. Design Patterns
B. Single Loop Design Patterns
C. Multiple Loop Design Patterns
No na
D. Timing a Design Pattern

tio
Na
© National Instruments Corporation 1-1 LabVIEW Core 2 Course Manual

Lesson 1 Common Design Techniques
A. Design Patterns
Application design patterns represent LabVIEW code implementations and
techniques that are solutions to specific problems in software design. Design
uti ts
patterns typically evolve through the efforts of many developers and are
fine-tuned for simplicity, maintainability, and readability. Design patterns
represent the techniques that have proved themselves useful over time.
rib en
Furthermore, as a pattern gains acceptance, it becomes easier to
recognize—this recognition alone helps you to read and make changes
on
to your code.
LabVIEW includes several built-in VI templates for several standard design
ist um
patterns that you will learn about in later lessons. To access the design
patterns, select File»New to display the New dialog box. The design
patterns are available in the VI»From Template»Frameworks»Design
Patterns folder. Listed below are the different kinds of design patterns.
r D str • Master/Slave Design Pattern—Use this template to build a master/slave
design pattern. The master loop always executes. It notifies one or more
slave loops to execute their code. The slave loop or loops continue
executing until they complete, then wait for another notification.
Contrast this with the producer/consumer pattern in which the consumer
loops execute only when they have data in their queue.
t fo l In
• Producer/Consumer Design Pattern (Data)—Use this template to build
a producer/consumer design pattern. Use this template when you need
to execute a process, such as data analysis, when a data source, such as
a triggered acquisition, produces data at an uneven rate and you need to
execute the process when the data becomes available.
No na
• Producer/Consumer Design Pattern (Events)—Use this template to

build a producer/consumer design pattern with events to produce queue
items. Use this design pattern instead of the user interface event handler
pattern for user interfaces when you want to execute code
tio
asynchronously in response to an event without slowing the user

interface responsiveness.
• Queued Message Handler—Use this template to build a queued message
handler design pattern, in which each message handling code can queue
any number of new messages.
Na
LabVIEW Core 2 Course Manual 1-2 ni.com

• Standard State Machine—Use this template to build a standard state

machine design pattern. Each state executes code and determines which
state to transition to. Contrast this design pattern with the user interface
event handler pattern, in which code executes in response to user
uti ts
actions. Contrast this design pattern also with the queued message
handler pattern, in which each message handling code can queue any
number of messages.
rib en
• User Interface Event Handler—Use this template to build a user
interface event handler design pattern. Use this pattern for dialog boxes
on
and other user interfaces in which code executes in response to user
actions. You also can create and execute user-defined events that the VI
ist um
can handle the same way as user interface events.
B. Single Loop Design Patterns

You learned to design three different types of design patterns in the
LabVIEW Core 1 course—the simple architecture, the general architecture,
r D str and the state machine.
Simple VI Design Patterns

When performing calculations or making quick lab measurements, you do
t fo l In
not need a complicated architecture. Your program might consist of a single
VI that takes a measurement, performs calculations, and either displays the
results or records them to disk. The simple VI design pattern usually does
not require a specific start or stop action from the user. The user just clicks
the Run button. Use this architecture for simple applications or for
functional components within larger applications. You can convert these
No na
simple VIs into subVIs that you use as building blocks for larger
applications.
Figure 1-1 displays the block diagram of the Determine Warnings VI that
was the course project in the LabVIEW Core 1 course. This VI performs a
tio
single task—it determines what warning to output dependent on a set of

inputs. You can use this VI as a subVI whenever you must determine the
warning level.
Na
Notice that the VI in Figure 1-1 contains no start or stop actions from the
user. In this VI all block diagram objects are connected through data flow.
You can determine the overall order of operations by following the flow of
data. For example, the Not Equal function cannot execute until the Greater
Than or Equal function, the Less Than or Equal function, and both Select
functions have executed.

uti ts
rib en
on
ist um
Figure 1-1. Simple VI Architecture
General VI Design Patterns

r D str A general VI design pattern has three main phases—startup, main
application, and shutdown. Each of the following phases may contain code
that uses another type of design pattern.
• Startup—Initializes hardware, reads configuration information from
files, or prompts the user for data file locations.
t fo l In
• Main Application—Consists of at least one loop that repeats until the
user decides to exit the program or the program terminates for other
reasons such as I/O completion.
• Shutdown—Closes files, writes configuration information to disk, or
resets I/O to the default state.
No na
Figure 1-2 shows the general VI design pattern.

tio
Na
Figure 1-2. General VI Design Pattern

In Figure 1-2, the error cluster wires control the execution order of the three
sections. The While Loop does not execute until the Start Up VI finishes
running and returns the error cluster data. Consequently, the Shut Down VI
cannot run until the main application in the While Loop finishes and the
uti ts
error cluster data leaves the loop.
Tip Most loops require a Wait function, especially if that loop monitors user input
rib en
on the front panel. Without the Wait function, the loop might run continuously and
use all of the computer system resources. The Wait function forces the loop to run
on
asynchronously even if you specify 0 milliseconds as the wait period. If the operations
inside the main loop react to user inputs, you can increase the wait period to a level
acceptable for reaction times. A wait of 100 to 200 ms is usually good because most users
ist um
cannot detect that amount of delay between clicking a button on the front panel and the
subsequent event execution.
For simple applications, the main application loop is obvious and contains
r D str code that uses the simple VI design pattern. When the application incudes
complicated user interfaces or multiple tasks such as user actions, I/O
triggers, and so on, the main application phase gets more complicated.
State Machine Design Pattern

The state machine design pattern is a modification of the general design
t fo l In
pattern. It usually has a start up and shut down phase. However, the main
application phase consists of a Case structure embedded in the loop. This
architecture allows you to run different code each time the loop executes,
depending upon some condition. Each case defines a state of the machine,
hence the name, state machine. Use this design pattern for VIs that are easily
No na
divided into several simpler tasks, such as VIs that act as a user interface.
A state machine in LabVIEW consists of a While Loop, a Case structure,

and a shift register. Each state of the state machine is a separate case in
the Case structure. You place VIs and other code that the state should
tio
execute within the appropriate case. A shift register stores the state that
should execute upon the next iteration of the loop. The block diagram of a
state machine VI with five states appears in Figure 1-3. Figure 1-4 shows the
other cases, or states, of the state machine.
Na

uti ts
rib en
on
ist um
Figure 1-3. State Machine with Startup State
r D str
t fo l In
No na
tio
Na
Figure 1-4. Idle (Default), Event 1, and Event 2 States
In the state machine design pattern, you design the list of possible tasks, or
states, and then map them to each case. For the VI in the previous example,
the possible states are Startup, Idle, Event 1, and Event 2. An enumerated

constant stores the states. Each state has its own case in the Case structure.
The outcome of one case determines which case to execute next. The shift
register stores the value that determines which case to execute next.
uti ts
The state machine design pattern can make the block diagram much smaller,
and therefore, easier to read and debug. Another advantage of the state
machine architecture is that each case determines the next state, unlike
Sequence structures that must execute every frame in sequence.
rib en
A disadvantage of the state machine design pattern is that with the approach
on
in the previous example, it is possible to skip states. If two states in the
structure are called at the same time, this model handles only one state, and
ist um
the other state does not execute. Skipping states can lead to errors that are
difficult to debug because they are difficult to reproduce. More complex
versions of the state machine design pattern contain extra code that creates
a queue of events, or states, so that you do not miss a state. Refer to
Lesson 2, Synchronization Techniques, for more information about
queue-based state machines.
r D str
C. Multiple Loop Design Patterns
This section describes the following multiple loop design patterns—parallel
t fo l In
loop, master/slave, and producer/consumer data.
Parallel Loop Design Pattern

Some applications must respond to and run several tasks concurrently.
One way to improve parallelism is to assign a different loop to each task.
For example, you might have a different loop for each button on the front
No na
panel and for every other kind of task, such as a menu selection, I/O trigger,
and so on. Figure 1-5 shows this parallel loop design pattern.
tio
Na
Figure 1-5. Parallel Loop Design Pattern

This structure is straightforward and appropriate for some simple menu VIs,
where you expect a user to select from one of several buttons that perform
different actions. The parallel loop design pattern lets you handle multiple,
simultaneous, independent tasks. In this design pattern, responding to
uti ts
one action does not prevent the VI from responding to another action. For
example, if a user clicks a button that displays a dialog box, parallel loops
can continue to respond to I/O tasks.
rib en
However, the parallel loop design pattern requires you to coordinate and
communicate between different loops. You cannot use wires to pass data
on
between loops because doing so prevents the loops from running in parallel.
Instead, you must use a messaging technique for passing information among
ist um
processes. Refer to Lesson 2, Synchronization Techniques, for messaging
techniques using notifiers and queues.
Master/Slave Design Pattern

r D str The master/slave design pattern consists of multiple parallel loops. Each of
the loops may execute tasks at different rates. One loop acts as the master,
and the other loops act as slaves. The master loop controls all the slave loops
and communicates with them using messaging techniques, as shown in
Figure 1-6.
t fo l In
No na
tio
Figure 1-6. Master/Slave Design Pattern
Use the master/slave design pattern when you need a VI to respond to user
interface controls while simultaneously collecting data. For example, you
Na
want to create a VI that measures and logs a slowly changing voltage once
every five seconds. The VI acquires a waveform from a transmission line
and displays it on a graph every 100 ms. The VI also provides a user
interface that allows the user to change parameters for each acquisition. The
master/slave design pattern is well suited for this acquisition application.
For this application, the master loop contains the user interface. The voltage
acquisition occurs in one slave loop, while the graphing occurs in another
slave loop.

Using the standard master/slave design pattern approach to this VI, you
would put the acquisition processes in two separate While Loops, both of
them driven by a master loop that receives inputs from the user interface
controls. This ensures that the separate acquisition processes do not affect
uti ts
each other, and that any delays caused by the user interface, such as
displaying a dialog box, do not delay any iterations of the acquisition
processes.
rib en
VIs that involve control also benefit from the use of master/slave design
patterns. Consider a VI where a user controls a free-motion robotic arm
on
using buttons on a front panel. This type of VI requires efficient, accurate,
and responsive control because of the physical damage to the arm or
ist um
surroundings that might occur if control is mishandled. For example, if the
user instructs the arm to stop its downward motion, but the program is
occupied with the arm swivel control, the robotic arm might collide with the
support platform. Apply the master/slave design pattern to the application to
avoid these problems. In this case, the master loop handles the user
interface, and each controllable section of the robotic arm has its own slave
r D str loop. Because each controllable section of the arm has its own loop and its
own piece of processing time, the user interface has more responsive control
of the robotic arm.
t fo l In
With a master/slave design pattern, it is important that no two While Loops
write to the same shared data. Ensure that no more than one While Loop
may write to any given piece of shared data. Refer to Lesson 2,
Synchronization Techniques, for more information about implementing an
application based on the master/slave design pattern.
No na
The slave must not take too long to respond to the master. If the slave is
processing a signal from the master and the master sends more than
one message to the slave, the slave receives only the latest message. This
use of the master/slave architecture could cause a loss of data. Use a
master/slave architecture only if you are certain that each slave task takes
tio
less time to execute than the master loop.
Producer/Consumer Design Pattern

The producer/consumer design pattern is based on the master/slave design
Na
pattern and improves data sharing among multiple loops running at different
rates. Similar to the master/slave design pattern, the producer/consumer
design pattern separates tasks that produce and consume data at different
rates. The parallel loops in the producer/consumer design pattern are
separated into two categories—those that produce data and those that
consume the data produced. Data queues communicate data among the
loops. The data queues also buffer data among the producer and consumer
loops.

Tip A buffer is a memory device that stores temporary data among two devices, or in
this case, multiple loops.
Use the producer/consumer design pattern when you must acquire multiple
uti ts
sets of data that must be processed in order. Suppose you want to create a VI
that accepts data while processing the data sets in the order they were
received. The producer/consumer pattern is ideal for this type of VI because
rib en
queuing (producing) the data occurs much faster than the data can be
processed (consumed). You could put the producer and consumer in the
on
same loop for this application, but the processing queue could not receive
additional data until the first piece of data was completely processed. The
producer/consumer approach to this VI queues the data in the producer loop
ist um
and processes the data in the consumer loop, as shown in Figure 1-7.
Tip Queue functions allow you to store a set of data that can be passed among multiple
loops running simultaneously or among VIs. Refer to Lesson 2, Synchronization
r D strTechniques, for more information about queues and implementing applications using the
producer/consumer design pattern.
t fo l In
No na
tio
Na
Figure 1-7. Producer/Consumer Design Pattern
This design pattern allows the consumer loop to process the data at its own
pace, while the producer loop continues to queue additional data.

You also can use the producer/consumer design pattern to create a VI that
analyzes network communication. This type of VI requires two processes to
operate at the same time and at different speeds. The first process constantly
polls the network line and retrieves packets. The second process analyzes
uti ts
the packets retrieved by the first process.
In this example, the first process acts as the producer because it supplies data
to the second process, which acts as the consumer. The producer/consumer
rib en
design pattern is an effective architecture for this VI. The parallel producer
and consumer loops handle the retrieval and analysis of data off the network,
on
and the queued communication between the two loops allows buffering of
the network packets retrieved. Buffering can become important when
ist um
network communication is busy. With buffering, packets can be retrieved
and communicated faster than they can be analyzed.
D. Timing a Design Pattern

r D str This section discusses two forms of timing—execution timing and software
control timing. Execution timing uses timing functions to give the processor
time to complete other tasks. Software control timing involves timing a
real-world operation to perform within a set time period.
t fo l In
Execution Timing
Execution timing involves timing a design pattern explicitly or based on
events that occur within the VI. Explicit timing uses a function that
specifically allows the processor time to complete other tasks, such as the
Wait Until Next ms Multiple function. When timing is based on events, the
design pattern waits for some action to occur before continuing and allows
No na
the processor to complete other tasks while it waits.
Use explicit timing for design patterns such as the master/slave,

producer/consumer, and state machine. These design patterns perform some
tio
type of polling while they execute.
Tip Polling is the process of making continuous requests for data from another device.
In LabVIEW, this generally means that the block diagram continuously asks if there is
data available, usually from the user interface.
Na
For example, the master/slave design pattern shown in Figure 1-8 uses a
While Loop and a Case structure to implement the master loop. The master
executes continuously and polls for an event of some type, such as the user
clicking a button. When the event occurs, the master sends a message to the
slave. You need to time the master so it does not take over the execution of
the processor. In this case, you typically use the Wait (ms) function to
regulate how frequently the master polls.

Tip Always use a timing function such as the Wait (ms) function or the Wait Until Next
ms Multiple function in any design pattern that continually executes and needs to be
regulated. If you do not use a timing function in a continuously executing structure,
LabVIEW uses all the processor time, and background processes may not run.
uti ts
rib en
on
ist um
r D str
t fo l In
No na
Figure 1-8. Master/Slave Design Pattern
Notice that the slave loop does not contain any form of timing. The use of
Synchronization functions, such as queues and notifiers, to pass messages
provides an inherent form of timing in the slave loop because the slave loop
tio
waits for the Notifier function to receive a message. After the Notifier
function receives a message, the slave executes on the message. This creates
an efficient block diagram that does not waste processor cycles by polling
for messages. This is an example of execution timing by waiting for an
event.
Na
When you implement design patterns where the timing is based on the
occurrence of events, you do not have to determine the correct timing
frequency because the execution of the design pattern occurs only when an
event occurs. In other words, the design pattern executes only when it
receives an event.

Software Control Timing

Many applications that you create must execute an operation for a specified
amount of time. Consider implementing a state machine design pattern for
a temperature data acquisition system. If the specifications require that the
uti ts
system acquire temperature data for 5 minutes, you could remain in the
acquisition state for 5 minutes. However, during that time you cannot
process any user interface actions such as stopping the VI. To process user
rib en
interface actions, you must implement timing so that the VI continually
executes for specified time. Implementing this type of timing involves
on
keeping the application executing while monitoring a real-time clock.
In the LabVIEW Core 1 course, you implemented software control timing to
ist um
monitor the time until the VI should acquire the next piece of data, as shown
in Figure 1-9. Notice the use of the Elapsed Time Express VI to keep track
of a clock.
r D str
t fo l In
No na
Figure 1-9. Use of the Elapsed Time Express VI

tio
If you use the Wait (ms) function or the Wait Until Next ms Multiple
function to perform software timing, the execution of the function you are
timing does not occur until the wait function finishes. These timing
functions are not the preferred method for performing software control
Na
timing, especially for VIs where the system must continually execute. A
better method for software control timing utilizes the Get Date/Time In
Seconds function to get the current time and track it using shift registers.

uti ts
rib en
on
ist um
r D str Figure 1-10. Software Timing Using the Get Date/Time In Seconds Function
The Get Date/Time In Seconds function, connected to the left terminal of the
shift register, initializes the shift register with the current system time. Each
state uses another Get Date/Time In Seconds function and compares the
current time to the start time. If the difference in these two times is greater
t fo l In
or equal to the wait time, the state finishes executing and the rest of the
application executes.
Tip Always use the Get Date/Time In Seconds function instead of the Tick Count (ms)
function for this type of comparison because the value of the Tick Count (ms) function
can rollover to 0 during execution.
No na
tio
Na

Self-Review: Quiz
1. The state machine is an example of a design pattern.
uti ts
a. True
b. False
rib en
2. Which of the following are reasons for using a multiple loop design
on
pattern?
ist um
a. Execute multiple tasks concurrently
b. Execute different states in a state machine
c. Execute tasks at different rates
d. Execute start up code, main loop, and shutdown code
r D str
3. Software control timing allows the processor time to complete other
tasks.
t fo l In
a. True
b. False
No na
tio
Na

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on
Self-Review: Quiz Answers

1. The state machine is an example of a design pattern.
uti ts
a. True
b. False
rib en
2. Which of the following are reasons for using a multiple loop design
on
pattern?
ist um
a. Execute multiple tasks concurrently
b. Execute different states in a state machine
c. Execute tasks at different rates
d. Execute start up code, main loop, and shutdown code
r D str
3. Software control timing allows the processor time to complete other
tasks.
t fo l In
a. True
b. False
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Synchronization Techniques
2
uti ts
Variables are useful in LabVIEW for passing data between parallel
rib en
processes. However, when using variables it is often difficult to synchronize
data transfers and you must take care to avoid race conditions. This lesson
on
introduces notifiers and queues as alternative methods for passing data
between parallel processes. Notifiers and queues have advantages over
using variables because of the ability to synchronize the transfer of data.
ist um
Topics
A. Notifiers
B. Queues
r D str
t fo l In
No na
tio
Na

Lesson 2 Synchronization Techniques
A. Notifiers
A more effective implementation of the master/slave design pattern uses
notifiers to synchronize data transfer. A notifier sends data along with a
uti ts
notification that the data is available. Using a notifier to pass data from the
master to the slave removes any issues with race conditions. Using notifiers
also provides a synchronization advantage because the master and slave are
rib en
timed when data is available, providing for an elegant implementation of the
master/slave design pattern. Figure 2-1 shows the master/slave design
on
pattern using notifiers.
ist um
r D str
t fo l In
No na
tio
Figure 2-1. Master/Slave Design Pattern Using Notifiers
The notifier is created before the loops begin using the Obtain Notifier
function. The master loop uses the Send Notification function to notify the
Na
slave loop through the Wait on Notification function. After the VI has
finished using the notifiers, the Release Notifier function releases the
notifiers.
The following benefits result from using notifiers in the master/slave design
pattern:
• Both loops are synchronized to the master loop. The slave loop only
executes when the master loop sends a notification.

• You can use notifiers to create globally available data. Thus, you can
send data with a notification. For example, in Figure 2-1, the Send
Notification function sends the string instruction.
• Using notifiers creates efficient code. You need not use polling to
uti ts
determine when data is available from the master loop.
However, using notifiers can have drawbacks. A notifier does not buffer the
rib en
data. If the master loop sends another piece of data before the slave loop(s)
reads the first piece of data, that data is overwritten and lost.
on
B. Queues
ist um
Queues are similar to notifiers, except that a queue can store multiple pieces
of data. By default, queues work in a first in, first out (FIFO) manner.
Therefore, the first piece of data inserted into the queue is the first piece of
data that is removed from the queue. Use a queue when you want to process
r D str all data placed in the queue. Use a notifier if you want to process only the
current data.
When used, the producer/consumer design pattern, queues pass data and
synchronize the loops.
t fo l In
No na
tio
Na
Figure 2-2. Producer/Consumer Design Pattern Using Queues

The queue is created before the loops begin using the Obtain Queue
function. The producer loop uses the Enqueue Element function to add data
to the queue. The consumer loop removes data from the queue using the
Dequeue Element function. The consumer loop does not execute until data
uti ts
is available in the queue. After the VI has finished using the queues, the
Release Queue function releases the queues. When the queue releases, the
Dequeue Element function generates an error, effectively stopping the
rib en
consumer loop. This eliminates the need to use a variable to stop the loops.
The following benefits result from using queues in the producer/consumer
on
design pattern:
• Both loops are synchronized to the producer loop. The consumer loop
ist um
only executes when data is available in the queue.
• You can use queues to create globally available data that is queued,
removing the possibility of losing the data in the queue when new data
is added to the queue.
• Using queues creates efficient code. You need not use polling to
r D str determine when data is available from the producer loop.
Queues are also useful for holding state requests in a state machine. In the
implementation of a state machine that you have learned, if two states are
t fo l In
requested simultaneously, you might lose one of the state requests. A queue
stores the second state request and executes it when the first has finished.
To practice the concepts in this section, complete Exercise 2-1.

No na
Case Study: Weather Station Project

The weather station project acquires temperature and wind speed data,
and analyzes it to determine if the situation requires a warning. If the
temperature is too high or too low, it alerts the user to a danger of heatstroke
tio
or freezing. It also monitors the wind speed to generate a high wind warning
when appropriate.
The block diagram consists of two parallel loops, which are synchronized
using queues. One loop acquires data for temperature and wind speed and
Na
the other loop analyzes the data. The loops in the block diagram use the
producer/consumer design pattern and pass the data through the queue.
Queues help process every reading acquired from the DAQ Assistant.
Code for acquiring temperature and wind speed is placed in the producer
loop. Code containing the state machine for analysis of temperature-weather
conditions is within the no error case of the consumer loop. The code using
a queue is more readable and efficient than the code using only state
machine architecture. The Obtain Queue function creates the queue

reference. The producer loop uses the Enqueue Element function to add data
obtained from the DAQ Assistant to the queue. The consumer loop uses the
Dequeue Element function to get the data from the queue and provide it to
the state machine for analysis. The Release Queue function marks the end
uti ts
of queue by destroying it. The use of queues also eliminates the need for a
shared variable to stop the loops because the Dequeue Element function
stops the consumer loop when the queue is released.
rib en
Figure 2-3 shows the block diagram consisting of a producer and a
consumer loop. Data transfer and synchronization between the loops is
on
achieved by the queue functions.
ist um
r D str
t fo l In
No na
Figure 2-3. Data Transfer and Synchronization of Parallel Loops Using Queues
tio
Na

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on
Self-Review: Quiz
1. Which of the following buffer data?
uti ts
a. Notifiers
b. Queues
c. Global Variables
rib en
d. Local Variables
on
ist um
2. Match the following:
Obtain Queue Destroys the queue reference
r D str Get Queue Status Assigns the data type of the queue
Release Queue Adds an element to the back of the queue

t fo l In
Enqueue Element Determines the number of elements currently

in the queue
No na
3. Which of the following are valid data types for Queues and Notifiers?
a. String
tio
b. Numeric
c. Enum
d. Array of Booleans
Na
e. Cluster of a String and a Numeric

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on

1. Which of the following buffer data?
uti ts
a. Notifiers
b. Queues
c. Global Variables
rib en
d. Local Variables
on
ist um
2. Match the following:
Obtain Queue Assigns the data type of the queue
r D str Get Queue Status Determines the number of elements

currently in the queue
Release Queue Destroys the queue reference

t fo l In
Enqueue Element Adds an element to the back of the queue

No na
3. Which of the following are valid data types for Queues and Notifiers?
a. String
tio
b. Numeric
c. Enum
d. Array of Booleans
Na
e. Cluster of a String and a Numeric

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Event Programming
3
uti ts
Event-based design patterns allow you to create more efficient and flexible
rib en
applications. Event-based design patterns use the Event structure to respond
directly to the user or other events. This lesson describes event-driven
on
programming using the Event structure and design patterns that use the
Event structure.
ist um
Topics
A. Events
B. Event-Driven Programming
C. Caveats and Recommendations
r D str D. Event-Based Design Patterns
t fo l In
No na
tio
Na

Lesson 3 Event Programming
A. Events
LabVIEW is a dataflow programming environment where the flow of data
determines the execution order of block diagram elements. Event-driven
uti ts
programming features extend the LabVIEW dataflow environment to allow
the user’s direct interaction with the front panel and other asynchronous
activity to further influence block diagram execution.
rib en
Note Event-driven programming features are available only in the LabVIEW Full and
on
Professional Development Systems. You can run a VI built with these features in the
LabVIEW Base Package, but you cannot reconfigure the event-handling components.
ist um
What Are Events?
An event is an asynchronous notification that something has occurred.
Events can originate from the user interface, external I/O, or other parts of
the program. User interface events include mouse clicks, key presses, and so
on. External I/O events include hardware timers or triggers that signal when
r D str data acquisition completes or when an error condition occurs. Other types
of events can be generated programmatically and used to communicate with
different parts of the program. LabVIEW supports user interface and
programmatically generated events. LabVIEW also supports ActiveX and
t fo l In
.NET generated events, which are external I/O events.
In an event-driven program, events that occur in the system directly

influence the execution flow. In contrast, a procedural program executes in
a pre-determined, sequential order. Event-driven programs usually include
a loop that waits for an event to occur, executes code to respond to the event,
No na
and reiterates to wait for the next event. How the program responds to each
event depends on the code written for that specific event. The order in which
an event-driven program executes depends on which events occur and on the
order in which they occur. Some sections of the program might execute
frequently because the events they handle occur frequently, and other
tio
sections of the program might not execute at all because the events never
occur.
Why Use Events?

Na
Use user interface events in LabVIEW to synchronize user actions on the

front panel with block diagram execution. Events allow you to execute a
specific event-handling case each time a user performs a specific action.
Without events, the block diagram must poll the state of front panel objects
in a loop, checking to see if any change has occurred. Polling the front panel
requires a significant amount of CPU time and can fail to detect changes if
they occur too quickly. By using events to respond to specific user actions,
you eliminate the need to poll the front panel to determine which actions the
user performed. Instead, LabVIEW actively notifies the block diagram each

time an interaction you specified occurs. Using events reduces the CPU
requirements of the program, simplifies the block diagram code, and
guarantees that the block diagram can respond to all interactions the user
makes.
uti ts
Use programmatically generated events to communicate among different
parts of the program that have no dataflow dependency. Programmatically
generated events have many of the same advantages as user interface events
rib en
and can share the same event-handling code, making it easy to implement
advanced architectures, such as queued state machines using events.
on
B. Event-Driven Programming
ist um
In Lesson 1, Common Design Techniques, you learned how event-driven
programming extends the LabVIEW dataflow environment to allow
user interaction with the front panel. You also learned about
r D str programmatically-generated events allow for easy implementation of
advanced architectures, such as queued state machines.
Event Structure Components

Use the Event structure, shown as follows, to handle events in a VI.
t fo l In
The Event structure works like a Case structure with a built-in Wait on
No na
Notification function. The Event structure can have multiple cases, each of
which is a separate event-handling routine. You can configure each case to
handle one or more events, but only one of these events can occur at a time.
When the Event structure executes, it waits until one of the configured
tio
events occur, then executes the corresponding case for that event. The Event
structure completes execution after handling exactly one event. It does not
implicitly loop to handle multiple events. Like a Wait on Notification
function, the Event structure can time out while waiting for notification of
an event. When this occurs, a specific Timeout case executes.
Na
The event selector label at the top of the Event structure indicates which
events cause the currently displayed case to execute.
View other event cases by clicking the down arrow next to the case name and
selecting another case from the shortcut menu.
The Timeout terminal at the top left corner of the Event structure specifies
the number of milliseconds to wait for an event before timing out.

The default is –1, which specifies to wait indefinitely for an event to occur.
If you wire a value to the Timeout terminal, you must provide a Timeout
case.
uti ts
The Event Data Node behaves similarly to the Unbundle By Name function.
This node is attached to the inside left border of each event case. The node
identifies the data LabVIEW provides when an event occurs. You can resize
rib en
this node vertically to add more data items, and you can set each data item
in the node to access any event data element. The node provides different
on
data elements in each case of the Event structure depending on which
event(s) you configure that case to handle. If you configure a single case to
ist um
handle multiple events, the Event Data Node provides only the event data
elements that are common to all the events configured for that case.
The Event Filter Node is similar to the Event Data Node.

r D str This node is attached to the inside right border of filter event cases. The node
identifies the subset of data available in the Event Data Node that the event
case can modify. The node displays different data depending on which
event(s) you configure that case to handle. By default, these items are
inplace to the corresponding data items in the Event Data Node. If you do
not wire a value to a data item of an Event Filter Node, that data item
t fo l In
remains unchanged.
Refer to the Notify and Filter Events section of this lesson for more
information about filter events.
The dynamic event terminals are available by right-clicking the Event

No na
structure and selecting Show Dynamic Event Terminals from the shortcut
menu.
These terminals are used only for dynamic event registration.

tio
Refer to the Dynamic Event Registration topic and the Modifying

Registration Dynamically topic of the LabVIEW Help for more information
about using these terminals.
Na
Note Like a Case structure, the Event structure supports tunnels. However, by default
you do not have to wire Event structure output tunnels in every case. All unwired tunnels
use the default value for the tunnel data type. Right-click a tunnel and deselect Use
Default If Unwired from the shortcut menu to revert to the default Case structure
behavior where tunnels must be wired in all cases. You also can configure the tunnels to
wire the input and output tunnels automatically in unwired cases.
Refer to the LabVIEW Help for information about the default values for data
types.

Notify and Filter Events

Notify events are an indication that a user action has already occurred, such
as when the user has changed the value of a control. Use notify events to
respond to an event after it has occurred and LabVIEW has processed it. You
uti ts
can configure any number of Event structures to respond to the same notify
event on a specific object. When the event occurs, LabVIEW sends a copy
of the event to each Event structure configured to handle the event in
rib en
parallel.
on
Filter events inform you that the user has performed an action before
LabVIEW processes it, which allows you to customize how the program
responds to interactions with the user interface. Use filter events to
ist um
participate in the handling of the event, possibly overriding the default
behavior for the event. In an Event structure case for a filter event, you can
validate or change the event data before LabVIEW finishes processing it, or
you can discard the event entirely to prevent the change from affecting the
r D str VI. For example, you can configure an Event structure to discard the Panel
Close? event, which prevents the user from interactively closing the front
panel of the VI.
Filter events have names that end with a question mark, such as Panel
Close?, to help you distinguish them from notify events. Most filter events
t fo l In
have an associated notify event of the same name, but without the question
mark, which LabVIEW generates after the filter event if no event case
discarded the event.
For example, you can use the Mouse Down? and Shortcut Menu Activation?
filter events to display a context menu when you left-click a control. To
No na
perform this action, modify the data returned by the Button event data field
of the Mouse Down? filter event. The value of the left mouse button is 1, and
the value of the right mouse button is 2. In order to display the context menu
when you left-click a control, change the Button event data field to 2 so that
tio
LabVIEW treats a left-click like a right-click. Refer to the Left-click

Shortcut Menu VI in the labview\examples\general directory for an
example of using filter events.
As with notify events, you can configure any number of Event structures to
Na
respond to the same filter event on a specific object. However, LabVIEW

sends filter events sequentially to each Event structure configured for the
event. The order in which LabVIEW sends the event to each Event structure
depends on the order in which the events were registered. Each Event
structure must complete its event case for the event before LabVIEW can
notify the next Event structure. If an Event structure case changes any of the
event data, LabVIEW passes the changed data to subsequent Event
structures in the chain. If an Event structure in the chain discards the event,
LabVIEW does not pass the event to any Event structures remaining in the

chain. LabVIEW completes processing the user action which triggered the
event only after all configured Event structures handle the event without
discarding it.
uti ts
Note National Instruments recommends you use filter events only when you want to
take part in the handling of the user action, either by discarding the event or by modifying
the event data. If you only want to know that the user performed a particular action, use
rib en
notify events.
on
Event structure cases that handle filter events have an Event Filter Node.
You can change the event data by wiring new values to these terminals. If
you do not wire a value to the data item of the Event Filter Node, the default
ist um
value equals the value that the corresponding item in the Event Data Node
returns. You can completely discard an event by wiring a TRUE value to the
Discard? terminal.
r D strNote A single case in the Event structure cannot handle both notify and filter events.
A case can handle multiple notify events but can handle multiple filter events only if the
event data items are identical for all events.
Refer to the Using Events in LabVIEW section of this lesson for more
information about event registration.
t fo l In
Tip In the Edit Events dialog box, notify events are signified by a green arrow, and filter
events are signified by a red arrow.
Using Events in LabVIEW

No na
LabVIEW can generate many different events. To avoid generating

unwanted events, use event registration to specify which events you want
LabVIEW to notify you about. LabVIEW supports two models for event
registration—static and dynamic.
tio
Static registration allows you to specify which events on the front panel of
a VI you want to handle in each Event structure case on the block diagram
of that VI. LabVIEW registers these events automatically when the VI runs,
so the Event structure begins waiting for events as soon as the VI begins
Na
running. Each event is associated with a control on the front panel of the VI,
the front panel window of the VI as a whole, or the LabVIEW application.
You cannot statically configure an Event structure to handle events for the
front panel of a different VI. Configuration is static because you cannot
change at run time which events the Event structure handles.
Dynamic event registration avoids the limitations of static registration by

integrating event registration with the VI Server, which allows you to use
Application, VI, and control references to specify at run time the objects for

which you want to generate events. Dynamic registration provides more

flexibility in controlling what events LabVIEW generates and when it
generates them. However, dynamic registration is more complex than static
registration because it requires using VI Server references with block
uti ts
diagram functions to explicitly register and unregister for events rather than
handling registration automatically using the information you configured in
the Event structure.
rib en
Note In general, LabVIEW generates user interface events only as a result of direct user
interaction with the active front panel. LabVIEW does not generate events, such as Value
on
Change, when you use shared variables, global variables, local variables, DataSocket,
and so on. However, you can use the Value (Signaling) property to generate a Value
ist um
Change event programmatically. In many cases, you can use programmatically generated
events instead of queues and notifiers.
The event data provided by a LabVIEW event always include a time stamp,
r D str an enumeration that indicates which event occurred, and a VI Server
reference to the object that triggered the event. The time stamp is a
millisecond counter you can use to compute the time elapsed between
two events or to determine the order of occurrence. The reference to the
object that generated the event is strictly typed to the VI Server class of that
object. Events are grouped into classes according to what type of object
t fo l In
generates the event, such as Application, VI, or Control. If a single case
handles multiple events for objects of different VI Server classes, the
reference type is the common parent class of all objects. For example, if you
configure a single case in the Event structure to handle events for a numeric
control and a color ramp control, the type of the control reference of the
event source is Numeric because the numeric and color ramp controls are in
No na
the Numeric class. If you register for the same event on both the VI and
Control class, LabVIEW generates the VI event first.
Note Clusters are the only container objects for which you can generate events.
tio
LabVIEW generates Control events for clusters, before it generates events for the objects
they contain, except in the case of the Value Change event. The Value Change event
generates the event on an element in the cluster, then on the cluster itself. If the Event
structure case for a VI event or for a Control event on a container object discards the
event, LabVIEW does not generate further events.
Na
Each Event structure and Register For Events function on the block diagram
owns a queue that LabVIEW uses to store events. When an event occurs,
LabVIEW places a copy of the event into each queue registered for that
event. An Event structure handles all events in its queue and the events in
the queues of any Register For Events functions that you wired to the
dynamic event terminals of the Event structure. LabVIEW uses these queues
to ensure that events are reliably delivered to each registered Event structure
in the order the events occur.

By default, when an event enters a queue, LabVIEW locks the front panel
that contains the object that generated that event. LabVIEW keeps the front
panel locked until all Event structures finish handling the event. While the
front panel is locked, LabVIEW does not process front panel activity but
uti ts
places those interactions in a buffer and handles them when the front panel
is unlocked.
For example, a user might anticipate that an event case launches an
rib en
application that requires text entry. Since the user already knows text entry
is needed, he might begin typing before the application appears on the front
on
panel. If the Lock front panel (defer processing of user action) until this
event case completes option is enabled, once the application launches and
ist um
appears on the front panel, it processes the key presses in the order in which
they occurred. If the Lock front panel (defer processing of user action)
until this event case completes option is disabled, the key presses might be
processed elsewhere on the front panel, since LabVIEW does not queue
r D str their execution to depend on the completion of the event case.
Front panel locking does not affect certain actions, such as moving the
window, interacting with the scroll bars, and clicking the Abort button.
LabVIEW can generate events even when no Event structure is waiting to

handle them. Because the Event structure handles only one event each time
t fo l In
it executes, place the Event structure in a While Loop to ensure that an Event
structure can handle all events that occur.
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
No na
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 (defer
processing of user action) until this event case completes checkbox in the Edit Events
dialog box. You cannot turn off front panel locking for filter events.
tio
Static Event Registration

Static event registration is available only for user interface events. Use the
Edit Events dialog box to configure an Event structure to handle a statically
registered event. Select the event source, which can be the application, the
Na
VI, or an individual control. Select a specific event the event source can
generate, such as Panel Resize, Value Change, and so on. Edit the case to
handle the event data according to the application requirements.
LabVIEW statically registers events automatically and transparently when

you run a VI that contains an Event structure. LabVIEW generates events
for a VI only while that VI is running or when another running VI calls the
VI as a subVI.

When you run a VI, LabVIEW sets that top-level VI and the hierarchy of
subVIs the VI calls on its block diagram to an execution state called
reserved. You cannot edit a VI or click the Run button while the VI is in the
reserved state because the VI can be called as a subVI at any time while its
uti ts
parent VI runs. When LabVIEW sets a VI to the reserved state, it
automatically registers the events you statically configured in all Event
structures on the block diagram of that VI. When the top-level VI finishes
rib en
running, LabVIEW sets it and its subVI hierarchy to the idle execution state
and automatically unregisters the events.
on
Refer to the labview\examples\general\uievents.llb for
examples of using static event registration.
ist um
Configuring Events
Before you configure events for the Event structure to handle, refer to the
Caveats and Recommendations when Using Events in LabVIEW topic of the
r D str LabVIEW Help.
Complete the following steps to configure an Event structure case to handle

an event.
1. (Optional) If you want to configure the Event structure to handle a user
event, a Boolean control within a radio buttons control, or a user
t fo l In
interface event that is generated based on a reference to an application,
VI, or control, you first must dynamically register that event. Refer to
the Dynamically Registering Events topic of the LabVIEW Help for
more information about using dynamic events.
2. Right-click the border of the Event structure and select Edit Events
No na
Handled by This Case from the shortcut menu to display the Edit
Events dialog box to edit the current case. You also can select Add
Event Case from the shortcut menu to create a new case.
3. Specify an event source in the Event Sources pane.
tio
4. Select the event you want to configure for the event source, such as Key
Down, Timeout, or Value Change from the Events list. When you
select a dynamic event source from the Event Sources list, the Events
list displays that event. This is the same event you selected when you
registered the event. If you have registered for events dynamically and
Na
wired event reg refnum out to the dynamic event terminal, the sources
appear in the Dynamic section.
5. If you want to add additional events for the current case to handle, click
the + button and repeat steps 3 and 4 to specify each additional event.
The Event Specifiers section at the top of the dialog box lists all the
events for the case to handle. When you click an item in this list, the
Event Sources section updates to highlight the event source you

selected. You can repeat steps 3 and 4 to redefine each event or click the
X button to remove the selected event.
6. Click the OK button to save the configuration and close the dialog box.
The event cases you configured appear as selection options in the event
uti ts
selector label at the top of the Event structure and the Event Data node
displays the data common to all events handled in that case.
7. (Optional) You can use a Timeout event to configure an Event structure
rib en
to wait a specified amount of time for an event to occur. Wire a value to
the Timeout terminal at the top left of the Event structure to specify the
on
number of milliseconds the Event structure should wait for an event to
occur before generating a Timeout event. The default value for the
ist um
Timeout terminal is –1, which specifies to wait indefinitely for an event
to occur.
8. Repeat steps 1 through 6 for each event case you want to configure.
r D str Refer to the following VIs for examples of using events:

labview\examples\general\dynamicevents.llb
labview\examples\general\uievents.llb
Event Example
t fo l In
Figure 3-1 shows an Event structure configured with the Menu Selection
(User) event. This VI uses the Event structure to capture menu selections
made using the user-defined menu named sample.rtm. The ItemTag
returns the menu item that was selected and the MenuRef returns the refnum
to the menubar. This information is passed to the Get Menu Item Info
function. Refer to examples\general\uievents.llb for more
No na
examples of using events.

tio
Na
Figure 3-1. Menu Selection (User) Event
Note If you use the Get Menu Selection function with an Event structure configured to
handle the same menu item, the Event structure takes precedence, and LabVIEW ignores
the Get Menu Selection function. In any given VI, use the Event structure or the Get
Menu Selection function to handle menu events, not both.

C. Caveats and Recommendations

The following list describes some of the caveats and recommendations to
consider when incorporating events into LabVIEW applications.
uti ts
• Avoid using an Event structure outside a loop.
LabVIEW can generate events even when no Event structure is waiting
to handle them. Because the Event structure handles only one event each
rib en
time it executes, place the Event structure in a While Loop that
terminates when the VI is no longer interested in events to ensure that an
on
Event structure handles all events that occur.
• Remember to read the terminal of a latched Boolean control in its Value
ist um
Change event case.
When you trigger an event on a Boolean control configured with a
latching mechanical action, the Boolean control does not reset to its
default value until the block diagram reads the terminal on the Boolean
control. You must read the terminal inside the event case for the
r D str mechanical action to work correctly.
• Avoid placing two Event structures in one loop.
National Instruments recommends that you place only one Event
structure in a loop. When an event occurs in this configuration, the Event
t fo l In
structure handles the event, the loop iterates, and the Event structure
waits for the next event to occur. If you place two Event structures in a
single loop, the loop cannot iterate until both Event structures handle an
event. If you have enabled front panel locking for the Event structures,
the user interface of the VI can become unresponsive depending on how
the user interacts with the front panel.
No na
Refer to the Caveats and Recommendations when Using Events in

LabVIEW topic of the LabVIEW Help for more caveats and
recommendations when you use events in LabVIEW.
tio
D. Event-Based Design Patterns

Event-based design patterns provide efficiency gains because they only
respond when an event occurs. When LabVIEW executes the Event
Na
structure, the VI that contains the Event structure sleeps until a registered
events occurs, or generates. When a registered event generates, the Event
structure automatically wakes up and executes the appropriate subdiagram
to handle the event.

User Interface Event Handler Design Pattern

The user interface event handler design pattern provides a powerful and
efficient architecture for handling user interaction with LabVIEW. Use the
user interface event handler for detecting when a user changes the value of
uti ts
a control, moves or clicks the mouse, or presses a key.
The standard user interface event handler template consists of an Event
rib en
structure contained in a While Loop, as shown in Figure 3-2. Configure the
Event structure to have one case for each category of event you want to
on
detect. Each event case contains the handling code that executes
immediately after an event occurs.
ist um
Because the event handler loop wakes up precisely when an event occurs
and sleeps in between events, you do not have to poll or read control values
repeatedly in order to detect when a user clicks a button. The user interface
event handler allows you to minimize processor use without sacrificing
r D str interactivity.
3
t fo l In
2
4
No na
tio
1 Event Structure 3 Timeout Terminal

2 While Loop 4 Event Data Node
Figure 3-2. User Interface Event Handler Design Pattern
A common problem when using the user interface event handler is that it
Na
computes the While Loop termination before the Event structure executes.
This can cause the While Loop to iterate one more time than you expected.
To avoid this situation, compute the While Loop termination within all your
event handling code.
The event handler code must execute quickly, generally within 200 ms.
Anything slower can make it feel as if the user interface is locked up. Also,
if the event handler code takes a long time to execute, the Event structure
might lock. By default, the front panel locks while an event is handled. You

can disable front panel locking for each event case to make the user interface
more responsive. However, any new events that are generated while an event
is being handled will not be handled immediately. So, the user interface will
still seem unresponsive.
uti ts
Any code that is in an event case cannot be shared with another Event
structure. You must use good code design when using the Event structure.
Modularize code that will be shared between multiple Event structure cases.
rib en
The Event structure includes a Timeout event, which allows you to control
on
when the Timeout event executes. For example, if you set a Timeout of
200 ms, the Timeout event case executes every 200 ms in the absence of
ist um
other events. You can use the Timeout event to perform critical timing in
your code.
Producer/Consumer (Events) Design Pattern

r D str One of the most versatile and flexible design patterns combines the
producer/consumer and user interface event handler design patterns.
A VI built using the producer/consumer (events) pattern responds to the
user interface asynchronously, allowing the user interface to continuously
respond to the user. The consumer loop of this pattern responds as events
occur, similar to the consumer loop of the producer/consumer (data) design
t fo l In
pattern.
The producer/consumer (events) design pattern uses the same

implementation as the producer/consumer (data) design pattern except the
producer loop uses an Event structure to respond to user interface events, as
shown in Figure 3-3. The Event structure enables continuous response to
No na
user interaction.
tio
Na

uti ts
rib en
on
ist um
r D str
t fo l In
Figure 3-3. Producer/Consumer (Events) Design Pattern
Figure 3-3 shows how the Producer/Consumer (Events) template uses

synchronization functions to expand the functionality of the design pattern.
No na
Queues have the ability to transfer any data type. The data type transferred
in Figure 3-3 is a string. A string is not the most efficient data type for
passing data in design patterns. A more efficient data type for passing data
in design patterns is a cluster consisting of an enumerated type control and
tio
a variant.

Na

Self-Review: Quiz
1. Using user interface events allows you to synchronize user actions on
the front panel with block diagram execution.
uti ts
a. True
b. False
rib en
on
2. The Event structure handles only one event each time it executes.
ist um
a. True
b. False
3. Which of the following are examples of user interface events?

r D str a. Mouse click
b. Keystroke
c. Event Filter Node
t fo l In
d. Value change of a control
4. Which of the following operations will generate a Value Change event

for a numeric control?
No na
a. Click inside the digital display window and enter a number from the
keyboard
b. Click the increment or decrement arrow buttons
tio
c. Place the cursor to the right of the digit you want to change and press
the up or down arrow keys
d. Update the numeric control using a local variable
Na

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on

1. Using user interface events allows you to synchronize user actions on
the front panel with block diagram execution.
uti ts
a. True
b. False
rib en
on
2. The Event structure handles only one event each time it executes.
ist um
a. True
b. False
3. Which of the following are examples of user interface events?

r D str a. Mouse click
b. Keystroke
c. Event Filter Node
t fo l In
d. Value change of a control
4. Which of the following operations will generate a Value Change event

for a numeric control?
No na
a. Click inside the digital display window and enter a number from
the keyboard
b. Click the increment or decrement arrow buttons
tio
c. Place the cursor to the right of the digit you want to change and
press the up or down arrow keys
d. Update the numeric control using a local variable
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Error Handling
4
uti ts
By default, LabVIEW automatically handles any error when a VI runs by
rib en
suspending execution, highlighting the subVI or function where the error
occurred, and displaying an error dialog box. Automatic error handling is
on
convenient for quick prototypes and proof-of-concept development, but not
recommended for professional application development. If you rely on
automatic error handling your application might stop in a critical section of
ist um
your code because of an error dialog box. The user might be unable to
continue running the application or fix the problem.
By manually implementing error handling, you control when popup dialogs

occur. If you plan to create a stand-alone application, you must incorporate
manual error handling because LabVIEW does not display automatic error
r D str handling dialog boxes in the LabVIEW Run-Time Engine.
Topics
t fo l In
A. Importance of Error Handling
B. Detect and Report Errors
C. Errors and Warnings
D. Ranges of Error Codes
No na
E. Error Handlers
tio
Na

Lesson 4 Error Handling
A. Importance of Error Handling

Error handling is the mechanism for anticipation, detection, and resolution
of warnings and errors. Error handling is an essential component in your
uti ts
LabVIEW application development. With error handling you quickly
pinpoint the source of programming errors. Without it, you might observe
unexpected behavior but struggle to find the source of the problem.
rib en
Error handling is also extremely valuable when you test your application to
ensure that your error reporting is meaningful and that the error handling
on
code safely stops your application when an error occurs. For example,
during stress testing you are setting values or conditions that are beyond the
ist um
normal operational capacity of your application which often result in errors.
When such errors occur, you want to ensure proper shutdown of your
application.
Error handling continues to be important after an application is deployed.

Error handling can help detect system and environment differences—such
r D str as differences in file systems, memory, and disk resources.
B. Detect and Report Errors

t fo l In
To implement good error handling, you must determine the actions to take
when an error occurs at every point in your application. To begin with, you
must utilize the error terminals on functions and VIs. Since the error cluster
is implemented as a flow-through parameter, you should propagate errors by
wiring the error out cluster of the first node you want to execute to the error
in cluster of the next node you want to execute. You must continue to do this
No na
for sequences of nodes.
As the VI runs, LabVIEW tests for errors at each node. If LabVIEW does
not find any errors, the node executes normally. If LabVIEW detects an
tio
error, the node passes the error to the next node without executing that part
of the code. Any subVIs that you create should also implement this
flow-through behavior.
Use the Merge Error function to merge the error out cluster values from
Na
parallel sequences. Refer to Figure 4-1 for an example of merging error

information from parallel node sequences.

uti ts
rib en
on
Figure 4-1. Merge Errors From Multiple Sources
ist um
At the end of your application after all error sources are merged into
one error cluster, you must report errors to the user using the Simple Error
Handler VI or another error reporting mechanism.
C. Errors and Warnings

r D str Recall that the error in and error out clusters include the following
components of information:
• status is a Boolean value that reports TRUE if an error occurred.
• code is a 32-bit signed integer that identifies the error numerically. A
t fo l In
nonzero error code coupled with a status of FALSE signals a warning
rather than a error.
• source is a string that identifies where the error occurred.
Notice that an error is defined as status value of TRUE, regardless of the

No na
code value. A nonzero code with a status of FALSE is considered a warning.

Although most errors have negative code values and warnings have positive
code values, this is not universally true. Therefore you should rely on the
status value and the code value to detect errors and warnings.
tio
Warnings are typically considered less severe than errors. Some APIs and
functions, such as the Match Regular Expression function, only report
errors. However, other APIs such as the VISA API for controlling
stand-alone instruments often reports warnings. A common VISA warning
occurs when calling the VISA Read function and specifying the number of
Na
bytes to read. In this case, VISA returns a warning with the following
description: The number of bytes transferred is equal to the
requested input count. More data might be available.
Unlike when an error occurs, nodes execute normally even when LabVIEW
detects a warning. Even though code executes normally, it is important that
during development you monitor warnings to ensure proper behavior of
your application. To ensure that warning information is propagated
correctly, it is important to use shift-registers for error cluster wires in loops

so that the warning information is propagated through all iterations. Refer

to Figure 4-2 for proper use of the shift-register to propagate errors and
warnings to successive loop iterations.
uti ts
rib en
on
Figure 4-2. Use Shift Registers to Propagate Errors and Warnings
ist um
By default, the Simple Error Handler VI displays a dialog with a description
of any errors that occurred and does not report warnings. However, the
Simple Error Handler VI can be configured for other error handling
r D str behavior. You can select the type of dialog from the following options:
• No dialog—Displays no dialog box. This is useful if you want to have
programmatic control over handling errors.
• OK message (default)—Displays a dialog box with a single OK button.
After the user acknowledges the dialog box, the VI returns control to the
main VI.
t fo l In
• Continue or stop message—Displays a dialog box with buttons, which

the user can use to either continue or stop. If the user selects Stop, the
VI calls the Stop function to halt execution.
• OK message with warnings—Displays a dialog box with any warnings
and a single OK button. After the user acknowledges the dialog box, the
No na
VI returns control to the main VI.

• Continue/Stop + Warnings—Displays a dialog box with any warnings
and buttons, which the user can use to either continue or stop. If the user
selects Stop, the VI calls the Stop function to halt execution.
tio
D. Ranges of Error Codes

VIs and functions in LabVIEW can return numeric error codes. Each
Na
product or group of VIs defines a range of error codes. Refer to the Ranges
of LabVIEW Error Codes topic of the LabVIEW Help for error code tables
listing the numeric error codes and descriptions for each product and VI
grouping.
In addition to defining error code ranges, LabVIEW reserves some error

code ranges for you to use in your application. You can define custom error
codes in the range of –8999 through –8000, 5000 through 9999, or 500,000
through 599,999.

Some numeric error codes are used by more than one group of VIs and
functions. For example, error 65 is both a serial error code, indicating a
serial port timeout, and a networking error code, indicating that a network
connection is already established.
uti ts
E. Error Handlers
rib en
An error handler is a VI or code that changes the normal flow of the program
when an error occurs. The Simple Error Handler VI is an example of a
on
built-in error handler that is used in LabVIEW. You can implement other
error handlers that are customized for your application. For example, you
might choose to log error information to a file. Another common error
ist um
handler is a VI that redirects code to a cleanup or shutdown routine when an
error occurs so that your application exits gracefully. Figure 4-3 shows a
state machine error handler that sets the next state to be the Shutdown state
when an error in status is TRUE.
r D str
t fo l In
Figure 4-3. State Machine Error Handler

No na
tio
Na

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on
Self-Review: Quiz
1. Merge Errors function concatenates error information from multiple
sources.
uti ts
a. True
b. False
rib en
on
2. All errors have negative error codes and all warnings have positive error
codes.
ist um
a. True
b. False
r D str
t fo l In
No na
tio
Na

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on

1. Merge Errors function concatenates error information from multiple
sources.
uti ts
a. True
b. False
rib en
on
2. All errors have negative error codes and all warnings have positive error
codes.
ist um
a. True
b. False
r D str
t fo l In
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Controlling the User Interface
5
uti ts
When writing programs, often you must change the attributes of front panel
rib en
objects programmatically. For example, you may want to make an object
invisible until a certain point in the execution of the program. In LabVIEW,
on
you can use VI Server to access the properties and methods of front panel
objects. This lesson explains the Property Nodes, Invoke Nodes, VI Server,
and control references.
ist um
Topics
A. Property Nodes
B. Invoke Nodes
r D str C. VI Server Architecture
D. Control References
t fo l In
No na
tio
Na

Lesson 5 Controlling the User Interface
A. Property Nodes
Property Nodes access the properties of an object. In some applications, you
might want to programmatically modify the appearance of front panel
uti ts
objects in response to certain inputs. For example, if a user enters an invalid
password, you might want a red LED to start blinking. Another example is
changing the color of a trace on a chart. When data points are above a certain
rib en
value, you might want to show a red trace instead of a green one. Property
Nodes allow you to make these modifications programmatically. You also
on
can use Property Nodes to resize front panel objects, hide parts of the front
panel, add cursors to graphs, and so on.
ist um
Property Nodes in LabVIEW are very powerful and have many uses. Refer
to the LabVIEW Help for more information about Property Nodes.
Creating Property Nodes

r D str When you create a property from a front panel object by right-clicking the
object, selecting Create»Property Node, and selecting a property from the
shortcut menu, LabVIEW creates a Property Node on the block diagram that
is implicitly linked to the front panel object. If the object has a label, the
Property Node has the same label. You can change the label after you create
the node. You can create multiple Property Nodes for the same front panel
t fo l In
object.
Using Property Nodes

When you create a Property Node, it initially has one terminal representing
a property you can modify for the corresponding front panel object. Using
No na
this terminal on the Property Node, you can either set (write) the property
or get (read) the current state of that property.
For example, if you create a Property Node for a digital numeric control
using the Visible property, a small arrow appears on the right side of the
tio
Property Node terminal, indicating that you are reading that property value.
You can change the action to write by right-clicking the terminal and
selecting Change To Write from the shortcut menu. Wiring a False
Boolean value to the Visible property terminal causes the numeric control
Na
to vanish from the front panel when the Property Node receives the data.
Wiring a True Boolean value causes the control to reappear.
Figure 5-1. Using Property Nodes

To get property information, right-click the node and select Change All to
Read from the shortcut menu. To set property information, right-click the
node and select Change All to Write from the shortcut menu. If a property
is read only, Change to Write is dimmed in the shortcut menu. If the small
uti ts
direction arrow on the Property Node is on the right, you are getting the
property value. If the small direction arrow on a Property Node is on the left,
you are setting the property value. If the Property Node in Figure 5-1 is set
rib en
to Read, when it executes it outputs a True value if the control is visible or
a False value if it is invisible.
on
Tip Some properties are read-only, such as the Label property, or write only, such as the
Value (Signaling) property.
ist um
To add terminals to the node, right-click the white area of the node and select
Add Element from the shortcut menu or use the Positioning tool to resize
the node. Then, you can associate each Property Node terminal with a
r D str different property from its shortcut menu.
Tip Property Nodes execute each terminal in order from top to bottom.
Some properties use clusters. These clusters contain several properties

that you can access using the cluster functions. Writing to these properties
t fo l In
as a group requires the Bundle function and reading from these properties
requires the Unbundle function. To access bundled properties, select All
Elements from the shortcut menu. For example, you can access all the
elements in the Position property by selecting Properties»Position»
All Elements from the shortcut menu.
No na
However, you also can access the elements of the cluster as individual
properties, as shown in Figure 5-2.
tio
Na
Figure 5-2. Properties Using Clusters

B. Invoke Nodes
Invoke Nodes access the methods of an object.
uti ts
Use the Invoke Node to perform actions, or methods, on an application or
VI. Unlike the Property Node, a single Invoke Node executes only a single
method on an application or VI. Select a method by using the Operating tool
rib en
to click the method terminal or by right-clicking the white area of the node
and selecting Methods from the shortcut menu. You also can create an
implicitly linked Invoke Node by right-clicking a front panel object,
on
selecting Create»Invoke Node, and selecting a method from the shortcut
menu.
ist um
The name of the method is always the first terminal in the list of parameters
in the Invoke Node. If the method returns a value, the method terminal
displays the return value. Otherwise, the method terminal has no value.
The Invoke Node lists the parameters from top to bottom with the name of
r D str the method at the top and the optional parameters, which are dimmed, at the
bottom.
Example Methods
t fo l In
An example of a method common to all controls is the Reinitialize to
Default method. Use this method to reinitialize a control to its default value
at some point in your VI. The VI class has a similar method called
Reinitialize All to Default.
Figure 5-3 is an example of a method associated with the Waveform Graph

No na
class. This method exports the waveform graph image to the clipboard or to
a file.
tio
Na
Figure 5-3. Invoke Node for the Export Image Method

C. VI Server Architecture
The VI Server is an object-oriented, platform-independent technology that
provides programmatic access to LabVIEW and LabVIEW applications.
uti ts
VI Server performs many functions; however, this lesson concentrates on
using the VI Server to control front panel objects and edit the properties of
a VI and LabVIEW. To understand how to use VI Server, it is useful to
rib en
understand the terminology associated with it.
Object-Oriented Terminology
on
Object-oriented programming is based on objects. An object is a member of
ist um
a class. A class defines what an object is able to do, what operations it can
perform (methods), and what properties it has, such as color, size, and so on.
Objects can have methods and properties. Methods perform an operation,

such as reinitializing the object to its default value. Properties are the
r D str attributes of an object. The properties of an object could be its size, color,
visibility, and so on.
Control Classes
LabVIEW front panel objects inherit properties and methods from a class.
When you create a Stop control, it is an object of the Boolean class and has
t fo l In
properties and methods associated with that class, as shown in Figure 5-4.
Control Class
Control
Example Property: Visible
Example Method: Reinitialize to Default
No na
Boolean Sub-Class Array Sub-Class

Boolean Array
Example Property: Boolean Text Example Property: Number of Rows
tio
Stop Object
Stop
Visible: Yes
Reinitialize to Default: No
Boolean Text: Stop
Figure 5-4. Boolean Class Example

Na
VI Class
Controls are not the only objects in LabVIEW to belong to a class. A VI
belongs to the VI Class and has its own properties and methods associated
with it. For instance, you can use VI class methods to abort a VI, to adjust
the position of the front panel window, and to get an image of the block
diagram. You can use VI class properties to change the title of a front panel
window, to retrieve the size of the block diagram, and to hide the Abort
button.

D. Control References
A Property Node created from the front panel object or block diagram
terminal is an implicitly linked Property Node. This means that the Property
uti ts
Node is linked to the front panel object. What if you must place your
Property Nodes in a subVI? Then the objects are no longer located on the
front panel of the VI that contains the Property Nodes. In this case, you need
rib en
an explicitly linked Property Node. You create an explicitly linked Property
Node by wiring a reference to a generic Property Node.
on
If you are building a VI that contains several Property Nodes or if you are
accessing the same property for several different controls and indicators,
ist um
you can place the Property Node in a subVI and use control references to
access that node. A control reference is a reference to a specific front panel
object.
This section shows one way to use control references. Refer to the
Controlling Front Panel Objects topic of the LabVIEW Help for more
r D str information about control references.
Creating a SubVI with Property Nodes

As shown in Figure 5-5, the simplest way to create explicitly linked
t fo l In
Property Nodes is to complete the following steps:
1. Create your VI.
2. Select the portion of the block diagram that is in the subVI, as shown in
the first part of Figure 5-5.
3. Select Edit»Create SubVI. LabVIEW automatically creates the control
No na
references needed for the subVI.

4. Customize and save the subVI. As you can see in the second part of
Figure 5-5, the subVI uses the default icon.
tio
Na
Objects Selected to Create SubVI Edit»Create SubVI used

Figure 5-5. Using Edit»Create SubVI to Create Control References

Figure 5-6 shows the subVI created. Notice that the front panel Control
Refnum controls have been created and connected to a Property Node on the
block diagram.
uti ts
rib en
on
ist um
Created SubVI Front Panel Created SubVI Block Diagram
Figure 5-6. Sub VI Created Using Edit»Create SubVI
r D str Note A red star on the Control Reference control indicates that the refnum is strictly
typed. Refer to the Strictly Typed and Weakly Typed Control Refnums section of the
Controlling Front Panel Objects topic of the LabVIEW Help for more information about
weakly and strictly typed control references.
t fo l In
Creating Control References
To create a control reference for a front panel object, right-click the object
or its block diagram terminal and select Create»Reference from the
shortcut menu.
No na
You can wire this control reference to a generic Property Node. You can pass
the control reference to a subVI using a control refnum terminal.
Using Control References

tio
Setting properties with a control reference is useful for setting the same
property for multiple controls. Some properties apply to all classes of
controls, such as the Disabled property. Some properties are only applicable
to certain control classes, such as the Lock Boolean Text in Center property.
Na
The following example shows how to construct a VI that uses a control

reference on the subVI to set the Enable/Disable state of a control on the
main VI front panel.

uti ts
rib en
on
ist um
1 2
r D str 1 Main VI 2 SubVI

Figure 5-7. Control References
The main VI sends a reference for the digital numeric control to the subVI
along with a value of zero, one, or two from the enumerated control. The
subVI receives the reference by means of the Ctl Refnum on its front panel
t fo l In
window. Then, the reference is passed to the Property Node. Because the
Property Node now links to the numeric control in the main VI, the Property
Node can change the properties of that control. In this case, the Property
Node manipulates the enabled/disabled state.
Notice the appearance of the Property Node in the block diagram. You
No na
cannot select a property in a generic Property Node until the class is chosen.
The class is chosen by wiring a reference to the Property Node. This is an
example of an explicitly linked Property Node. It is not linked to a control
until the VI is running and a reference is passed to the Property Node. The
tio
advantage of this type of Property Node is its generic nature. Because it has
no explicit link to any one control, it may be reused for many different
controls. This generic Property Node is available on the Functions palette.
Selecting the Control Type

Na
When you add a Control Refnum to the front panel of a subVI, you next
need to specify the VI Server Class of the control. This specifies the type of
control references that the subVI will accept. In the previous example,
Control was selected as the VI Server Class type, as shown in Figure 5-7.
This allows the VI to accept a reference to any type of front panel control.
However, you can specify a more specific class for the refnum to make the
subVI more restrictive. For example, you can select Digital as the class, and
the subVI only can accept references to numeric controls of the class

Digital. Selecting a more generic class for a control refnum allows it to

accept a wider range of objects, but limits the available properties to those
that apply to all objects which the Property Node can accept.
uti ts
To select a specific control class, right-click the control and select Select VI
Server Class»Generic»GObject»Control from the shortcut menu. Then,
select the specific control class.
rib en
Creating Properties and Methods with the Class Browser Window
on
You can use the Class Browser window to select an object library and create
a new property or method.
ist um
Complete the following steps to create a new property or method using the
Class Browser window.
1. Select View»Class Browser to display the Class Browser window.
r D str
t fo l In
No na
tio
2. From the Object library pull-down menu, select a library.

Na
3. Select a class from the Class pull-down menu. Use the following buttons
to navigate the classes.
• Click the Select View button to toggle between an alphabetical view
and a hierarchical view of the items in the Class pull-down menu and
the Properties and Methods list.
• Click the Search button to launch the Class Browser Search dialog
box.

4. From the Properties and Methods list in the Class Browser window,
select a property or method. The property or method you select appears
in the Selected property or method box.
5. Click the Create button or the Create Write button to attach a node
uti ts
with the selected property or method to your mouse cursor and add the
node to the block diagram. The Create button creates a property for
reading or a method. This button dims when you select a write-only
rib en
property. To create a property for writing, click the Create Write
button. The Create Write button dims when you select a method or
on
read-only property. You also can drag a property or method from the
Properties and Methods list directly to the block diagram.
ist um
6. Repeat steps 2 through 5 for any other properties and methods you want
to create and add to the block diagram.

r D str
t fo l In
No na
tio
Na

Self-Review: Quiz
1. For each of the following items, determine whether they operate on a VI
class or a Control class.
uti ts
• Format and Precision
• Blinking
rib en
• Reinitialize to Default Value
• Show Tool Bar
on
ist um
2. You have a ChartGraph control refnum, shown at left, in a subVI. Which
of the following control references could you wire to the control refnum
terminal of the subVI? (multiple answers)
r D str a. Control reference of an XY graph
b. Control reference of a numeric array
c. Control reference of a waveform chart
d. Control reference of a Boolean control
t fo l In
No na
tio
Na

Na
tio
No na
t fo l In
r D str
ist um
rib en
uti ts
on

1. For each of the following items, determine whether they operate on a VI
class or a Control class.
uti ts
• Format and Precision: Control
• Blinking: Control
rib en
• Reinitialize to Default Value: Control
• Show Tool Bar: VI
on
ist um
2. You have a GraphChart control refnum, shown at left, in a subVI. Which
control references could you wire to the control refnum terminal of the
subVI?
r D str a. Control reference of an XY graph
b. Control reference of a numeric array
c. Control reference of a waveform chart
d. Control reference of a Boolean control
t fo l In
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

File I/O Techniques
6
uti ts
Frequently, the decision to separate the production of data and the
rib en
consumption of data into separate processes occurs because you must write
the data to a file as it is acquired. In such cases, you must choose a file
on
format. This lesson explains ASCII, Binary, and Technical Data
Management Streaming (TDMS) file formats and when each is a good
choice for your application.
ist um
Topics
A. File Formats
B. Binary Files
r D str C. TDMS Files
t fo l In
No na
tio
Na

Lesson 6 File I/O Techniques
A. File Formats
At their lowest level, all files written to your computer’s hard drive
are a series of binary bits. However, many formats for organizing and
uti ts
representing data in a file are available. In LabVIEW, three of the most
common techniques for storing data are the ASCII file format, direct binary
storage, and the TDMS file format. Each of these formats has advantages
rib en
and some formats work better for storing certain data types than others.
on
When to Use Text (ASCII) Files
Use text format files for your data to make it available to other users or
ist um
applications if disk space and file I/O speed are not crucial, if you do not
need to perform random access reads or writes, and if numeric precision is
not important.
Text files are the easiest format to use and to share. Almost any computer
r D str can read from or write to a text file. A variety of text-based programs can
read text-based files.
Store data in text files when you want to access it from another application,
such as a word processing or spreadsheet application. To store data in text
format, use the String functions to convert all data to text strings. Text files
t fo l In
can contain information of different data types.
Text files typically take up more memory than binary and datalog files if
the data is not originally in text form, such as graph or chart data, because
the ASCII representation of data usually is larger than the data itself.
For example, you can store the number –123.4567 in 4 bytes as a
No na
single-precision, floating-point number. However, its ASCII representation

takes 9 bytes, one for each character.
In addition, it is difficult to randomly access numeric data in text files.

tio
Although each character in a string takes up exactly 1 byte of space, the

space required to express a number as text typically is not fixed. To find the
ninth number in a text file, LabVIEW must first read and convert the
preceding eight numbers.
Na
You might lose precision if you store numeric data in text files. Computers
store numeric data as binary data, and typically you write numeric data to a
text file in decimal notation. Loss of precision is not an issue with binary
files.
When to Use Binary Files

Storing binary data, such as an integer, uses a fixed number of bytes on disk.
For example, storing any number from 0 to 4 billion in binary format, such
as 1, 1,000, or 1,000,000, takes up 4 bytes for each number.

Use binary files to save numeric data and to access specific numbers from a
file or randomly access numbers from a file. Binary files are machine
readable only, unlike text files, which are human readable. Binary files are
the most compact and fastest format for storing data. You can use multiple
uti ts
data types in binary files, but it is uncommon.
Binary files are more efficient because they use less disk space and because
you do not need to convert data to and from a text representation when you
rib en
store and retrieve data. A binary file can represent 256 values in 1 byte of
disk space. Often, binary files contain a byte-for-byte image of the data as it
on
was stored in memory, except for cases like extended and complex numeric
values. When the file contains a byte-for-byte image of the data as it was
ist um
stored in memory, reading the file is faster because conversion is not
necessary.
Datalog Files
r D str A specific type of binary file, known as a datalog file, is the easiest method
for logging cluster data to file. Datalog files store arrays of clusters in a
binary representation. Datalog files provide efficient storage and random
access, however, the storage format for datalog files is complex, and
therefore they are difficult to access in any environment except LabVIEW.
Furthermore, in order to access the contents of a datalog file, you must know
t fo l In
the contents of the cluster type stored in the file. If you lose the definition of
the cluster, the file becomes very difficult to decode. For this reason, datalog
files are not recommended for sharing data with others or for storing data in
large organizations where you could lose or misplace the cluster definition.
When to Use TDMS Files

No na
To reduce the need to design and maintain your own data file format,
National Instruments has created a flexible data model called Technical
Data Management Streaming, which is natively accessible through
LabVIEW, LabWindows™/CVI™, and DIAdem, and is portable to other
tio
applications such as Microsoft Excel. The TDMS data model offers several
unique benefits such as the ability to scale your project requirements and
easily attach descriptive information to your measurements while streaming
your data to disk.
Na
The TDMS file format consists of two files—a .tdms file and a
.tdms_index file. The .tdms file is a binary file that contains data and
stores properties about that data. The .tdms_index file is a binary index
file that speeds up access while reading and provides consolidated
information on all the attributes and pointers in the TDMS file. All the
information in the .tdms_index file is also contained in the .tdms file.
For this reason, the .tdms_index file can be automatically regenerated
from the .tdms file. Therefore, when you distribute TDMS files, you only
need to distribute the .tdms file. The internal structure of the TDMS file

format is publicly documented, so it is possible to create third-party

programs to write and read TDMS files. In addition, there is a TDM Excel
Add-in Tool available on ni.com that you can install to load .tdms files
into Microsoft Excel.
uti ts
Use TDMS files to store test or measurement data, especially when the data
consists of one or more arrays. TDMS files are most useful when storing
arrays of simple data types such as numbers, strings, or Boolean data.
rib en
TDMS files cannot store arrays of clusters directly. If your data is stored in
arrays of clusters, use another file format, such as binary, or break the cluster
on
up into channels and use the structure of the TDMS file to organize them
logically.
ist um
Use TDMS files to create a structure for your data. Data within a file is
organized into channels. You can also organize channels into channel
groups. A file can contain multiple channel groups. Well-grouped data
simplifies viewing and analysis and can reduce the time required to search
for a particular piece of data.
r D str Use TDMS files when you want to store additional information about your
data. For example, you might want to record the following information:
• Type of tests or measurements
t fo l In
• Operator or tester name
• Serial numbers
• Unit Under Test (UUT) numbers for the device tested
• Time of the test
No na
• Conditions under which the test or measurement was conducted
B. Binary Files
tio
Although all file I/O methods eventually create binary files, you can directly
interact with a binary file by using the Binary File functions. The following
list describes the common functions that interact with binary files.
Open/Create/Replace File—Opens a reference to a new or existing file for

Na
binary files as it does for ASCII Files.
Write to Binary File—Writes binary data to a file. The function works

much like the Write to Text File function, but can accept most data types.
Read from Binary File—Reads binary data starting at its current file
position. You must specify to the function the data type to read. Use this
function to access a single data element or wire a value to the count input.
This causes the function to return an array of the specified data type.

Get File Size—Returns the size of the file in bytes. Use this function in
combination with the Read from Binary File function when you want to read
all of a binary file. Remember that if you are reading data elements that are
larger than a byte you must adjust the count to read.
uti ts
Get/Set File Position—These functions get and set the location in the file
where reads and writes occur. Use these functions for random file access.
rib en
Close File—Closes an open reference to a file.
on
Figure 6-1 shows an example that writes an array of doubles to a binary file.
Refer to the Arrays section of this lesson for more information about the
ist um
Prepend array or string size? option.
r D str
t fo l In
Figure 6-1. Writing a Binary File
Binary Representation
Each LabVIEW data type is represented in a specified way when written to
a binary file. This section discusses the representation of each type and
No na
important issues when dealing with the binary representation of each type.
Tip A bit is a single binary value. Represented by a 1 or a 0, each bit is either on or off.
A byte is a series of 8 bits.
tio
Boolean Values
LabVIEW represents Boolean values as 8-bit values in a binary file. A value
of all zeroes represents False. Any other value represents True. This divides
Na
files into byte-sized chunks and simplifies reading and processing files. To
efficiently store Boolean values, convert a series of Boolean values into an
integer using the Boolean Array To Number function. Figure 6-2 shows
two methods for writing six Boolean values to a binary file.

uti ts
rib en
on
ist um
r D str
Figure 6-2. Writing Boolean Values to a Binary File
t fo l In
Table 6-1 displays a binary representation of the file contents resulting from
running the programs in Figure 6-2. Notice that Method B is a more efficient
storage method.
Table 6-1. Results of Figure 6-2

No na
Method A 00000001 00000001 00000000 00000001

00000000 00000001
Method B 00101011
tio
8-bit Integers
Unsigned 8-bit integers (U8) directly correspond to bytes written to the file.
When you must write values of various types to a binary file, convert each
type into an array of U8s using the Boolean Array To Number, String to
Na
Byte Array, Split Number, and Type Cast functions. Then, you can
concatenate the various arrays of U8s and write the resulting array to a file.
This process is unnecessary when you write a binary file that contains only
one type of data.

Table 6-2. U8 Representation
Binary Value U8 Value

00000000 0
uti ts
00000001 1
00000010 2
rib en
11111111 255
on
Other Integers
ist um
Multi-byte integers are broken into separate bytes and are stored in files in
either little-endian or big-endian byte order. Using the Write to Binary File
function, you can choose whether you store your data in little-endian or
big-endian format.
Little-endian byte order stores the least significant byte first, and the most
r D str significant byte last. Big-endian order stores the most significant byte first,
and the least significant byte last.
From a hardware point of view, Intel x86 processors use the little-endian
byte order while Motorola, PowerPC and most RISC processors use the
t fo l In
big-endian byte order. From a software point of view, LabVIEW uses the
big-Endian byte order when handling and storing data to disk, regardless of
the platform. However, the operating system usually reflects the byte order
format of the platform it’s running on. For example, Windows running on an
Intel platform usually stores data to file using the little-endian byte order. Be
No na
aware of this when storing binary data to disk. The binary file functions of
LabVIEW have a byte order input that sets the endian form of the data.
Table 6-3. Integer Representations

tio
Little-endian Big-endian
U32 Value Value Value
0 00000000 00000000 00000000 00000000
00000000 00000000 00000000 00000000
Na
1 00000001 00000000 00000000 00000000

00000000 00000000 00000000 00000001
255 11111111 00000000 00000000 00000000
00000000 00000000 00000000 11111111

Table 6-3. Integer Representations (Continued)
Little-endian Big-endian
U32 Value Value Value
uti ts
65535 11111111 11111111 00000000 00000000
00000000 00000000 11111111 11111111
rib en
4,294,967,295 11111111 11111111 11111111 11111111
11111111 11111111 11111111 11111111
on
Floating-Point Numbers
ist um
Floating point numbers are stored as described by the IEEE 754 Standard
for Binary Floating-Point Arithmetic. Single-precision numerics use 32-bits
each and double-precision numerics use 64-bits each. The length of
extended-precision numerics depends on the operating system.
r D str Strings
Strings are stored as a series of unsigned 8-bit integers, each of which is a
value in the ASCII Character Code Equivalents Table. This means that there
is no difference between writing strings with the Binary File functions and
writing them with the Text File functions.
t fo l In
Arrays
Arrays are represented as a sequential list of each of their elements. The
actual representation of each element depends on the element type. When
you store an array to a file you have the option of preceding the array with
a header. A header contains a 4-byte integer representing the size of each
No na
dimension. Therefore, a 2D array with a header contains two integers,

followed by the data for the array. Figure 6-3 shows an example of writing
a 2D array of 8-bit integers to a file with a header. The prepend array or
string size? input of the Write to Binary File function enables the header.
tio
Notice that the default value of this terminal is True. Therefore, headers are
added to all binary files by default.
Na

uti ts
rib en
on
ist um
Figure 6-3. Writing a 2D Array of Unsigned Integers to a File with a Header
Table 6-4 shows the layout of the file that the code in Figure 6-3 generates.
Notice that the headers are represented as 32-bit integers even though the
data is 8-bit integers.
r D str Table 6-4. Example Array Representation In Binary File
4 3 1 2 3 4 5 6 7 8 9 10 11 12
Clusters
t fo l In
Datalog files best represent clusters in binary files. Refer to the Datalog
Files section for more information.
Sequential vs. Random Access

When reading a binary file, there are two methods of accessing data. The
No na
first is to read each item in order, starting at the beginning of a file. This is
called sequential access and works similar to reading an ASCII file. The
second is to access data at an arbitrary point within the file for random
access. For example, if you know that a binary file contains a 1D array of
32-bit integers that was written with a header and you want to access the
tio
tenth item in the array, you could calculate the offset in bytes of that element
in the file and then read only that element. In this example, the element has
an offset of 4 (the header) + 10 (the array index) × 4 (the number of bytes in
an I32) = 44.
Na
Sequential Access
To sequentially access all the data in a file, you can call the Get File Size
function and use the result to calculate the number of items in the file, based
on the size of each item and the layout of the file. You can then wire the
number of items to the count terminal of the Read Binary function.

Figure 6-4 shows an example of this method.
uti ts
rib en
Figure 6-4. Sequentially Reading an Entire File
on
Alternately, you can sequentially access the file one item at a time by
ist um
repeatedly calling the Read Binary function with the default count of 1.
Each read operation updates the position within the file so that you read a
new item each time read is called. When using this technique to access data
you can check for the End of File error after calling the Read Binary
function or calculate the number of reads necessary to reach the end of the
file by using the Get File Size function.
r D str
Random Access
To randomly access a binary file, use the Set File Position function to set the
read offset to the point in the file you want to begin reading. Notice that
t fo l In
the offset is in bytes. Therefore, you must calculate the offset based on the
layout of the file. In Figure 6-5, the VI returns the array item with the
index specified, assuming that the file was written as a binary array of
double-precision numerics with no header, like the one written by the
example in Figure 6-1.
No na
tio
Figure 6-5. Randomly Accessing a Binary File

Na
Datalog Files
Datalog files are designed for storing a list of records to a file. Each record
is represented by a cluster, and can contain multiple pieces of data with any
data type. Datalog files are binary files, however, they use a different API
than other binary files. The Datalog functions allow you to read and write
arrays of clusters to and from datalog files.

When you open a datalog file for either reading or writing, you must specify
the record type used by the file. To do this, wire a cluster of the appropriate
type to the Open/Create/Replace Datalog function. After the file is open,
you program datalog files like any other binary file. Random access is
uti ts
available, although offsets are specified in records instead of bytes.
Figure 6-6 shows an example of writing a datalog file. Notice that the cluster
bundles the data and opens the datalog file.
rib en
on
ist um
r D str
Figure 6-6. Writing a Datalog File
t fo l In
Figure 6-7 shows an example of randomly accessing a datalog file. Notice

that the Record Definition cluster matches the cluster used to write the file.
If the record type wired to the Open/Create/Replace Datalog function does
not match the records in the file being opened, an error occurs.
No na
tio
Na
Figure 6-7. Reading a Datalog File
Instead of using random access, you can read an entire datalog file by wiring
the output of the Get Number of Records function to the count input of the
Read Datalog function.

C. TDMS Files
Creating TDMS Files
uti ts
In LabVIEW, you can create TDMS Files in two ways. Use the Write to
Measurement File Express VI and Read from Measurement File Express VI
or the TDM Streaming API.
rib en
With the Express VIs you can quickly save and retrieve data from the TDMS
format. Figure 6-8 shows the configuration dialog box for the Write to
on
Measurement File Express VI. Notice that you can choose to create a
LabVIEW measurement data file (LVM) or TDMS file type. However, these
ist um
Express VIs give you little control over your data grouping and properties
and do not allow you to use some of the features that make TDMS files
useful, such as defining channel names and channel group names.
r D str
t fo l In
No na
tio
Na
Figure 6-8. Creating a TDMS with Write to Measurement File Express VI

To gain access to the full capabilities of TDMS files, use the TDM
Streaming functions. Use the TDM Streaming functions to attach
descriptive information to your data and quickly save and retrieve data.
Some of the commonly used TDM Streaming functions are described in the
uti ts
TDMS API section of this lesson.
Data Hierarchy
rib en
Use TDMS files to organize your data in channels and in channel groups.
on
A channel stores measurement signals or raw data in a TDMS file. The
signal is an array of measurement data. Each channel also can have
properties that describe the data. The data stored in the signal is stored as
ist um
binary data on disk to conserve disk space and efficiency.
A channel group is a segment of a TDMS file that contains properties to

store information as well as one or more channels. You can use channel
r D str groups to organize your data and to store information that applies to multiple
channels.
TDMS files each contain as many channel group and channel objects as you
want. Each of the objects in a file has properties associated with it, which
creates three levels of properties you can use to store data. For example, test
t fo l In
conditions are stored at the file level. UUT information is stored at the
channel or channel group level. Storing plenty of information about your
tests or measurements can make analysis easier.
TDMS API
The following describes some of the most commonly used TDM Streaming
No na
VIs and functions.

• TDMS Open—Opens a reference to a TDMS file for reading or writing.
tio
• TDMS Write—Streams data to the specified TDMS file. It also allows

you to create channels and channel groups within your file.
• TDMS Read—Reads the specified TDMS file and returns data from the
specified channel and/or channel group.
Na
• TDMS Set Properties—Sets the properties of the specified TDMS file,

channel group, or channel.
• TDMS Get Properties—Returns the properties of the specified TDMS
file, channel group, or channel.
• TDMS Close—Closes a reference to a TDMS File. Notice that you only
must close the file reference, any references that you acquire to channels
and channel groups close automatically when you close the file
reference.

• TDMS File Viewer—Opens the specified TDMS file and presents the
file data in the TDMS File Viewer dialog box.
• TDMS List Contents—Provides a list of group and channel names
contained within the specified TDMS file.
uti ts
• TDMS Defragment—Defragments the file data in the specified TDMS
data. Use this function to clean up your TDMS data when it becomes
cluttered and to increase performance.
rib en
• TDMS Flush—Flushes the system memory of all TDMS data to
maintain data security.
on
TDMS Programming
ist um
Writing a TDMS File
Figure 6-9 shows the simplest form of writing measurement data with the
TDMS API. This example writes data to the channel Main Channel in the
r D str channel group Main Group.
t fo l In
No na
Figure 6-9. Write Data to a TDMS File at the Channel Level

tio
Na

Reading a TDMS File

Figure 6-10 shows the simplest form of reading data using the TDMS API.
This example reads all the data in the channel Main Channel from channel
group Main Group and displays it in the Channel Data waveform graph.
uti ts
Next, the example reads data from all the channels in the channel group
Main Group and displays it in the Group Data waveform graph.
rib en
on
ist um
r D str
Figure 6-10. Read Data Back from the TDMS File
Writing TDMS Custom Properties

t fo l In
The TDMS data model automatically creates certain properties when some
data types are written. However, in many cases you may want to create a
property specific to your particular needs, such as UUT, serial number, and
test temperature. This task can be accomplished using the TDMS Set
Properties function with which you can write properties at the file, group, or
No na
channel level.
tio
Na

The file level of a property determines which input terminals need to be

wired. For example, to write a group property, only the group name input
must be wired. To write a channel property, both the group name and
channel name inputs must be wired. But, to write a file property, the group
uti ts
name and channel names inputs should be left unwired. Figure 6-11
illustrates these examples.
rib en
on
ist um
r D str
t fo l In
Figure 6-11. Write Custom Properties at Three Different Levels
before Writing Data to the File
With the TDMS Set Properties function, you can specify an individual
property by itself or specify many properties by using arrays. Figure 6-11
shows two properties specified at the file level (TestID and Plant). You could
No na
expand this to specify many more properties by increasing the size of the
array. Arrays are not necessary if only a single property, such as a serial
number, is written.
Property values can also be different data types. In Figure 6-11, string
tio
properties are written at the file and group level. But at the channel level,
two numeric properties are written to specify the minimum and maximum
temperature.
Na

Reading TDMS Custom Properties

When a TDMS file has been written, the properties can be read back into
LabVIEW using TDMS Get Properties function. Properties are returned
only for the level specified by the wiring of the group name and channel
uti ts
name inputs. This process is similar to writing the properties, as it is shown
in Figure 6-12.
rib en
on
ist um
r D str
Figure 6-12. Read TDMS Properties from Three Different Levels
t fo l In
In this configuration, the property values are returned as an array of Variant
data because the data could be a string, double, Boolean, or another data
type. The data can be displayed on the front panel as a Variant or it can be
converted in LabVIEW to the appropriate data type. If a property name and
its data type are known, they can be wired as inputs to TDMS Get Properties
function and read directly with the correct data type.
No na
tio
Na

TDMS File Viewer

Use the TDMS File Viewer VI when developing a TDMS application to
automatically see everything that has been written to a TDMS file by
making a single VI call. The TDMS File Viewer VI is flexible and can read
uti ts
complex TDMS files. The TDMS File Viewer VI is included with the
TDMS API, so it can be easily placed in a program. Place the TDMS File
Viewer VI after the file is closed to use it. The TDMS File Viewer launches
rib en
another window in which you can view the data and properties inside the
TDMS file.
on
ist um
r D str
t fo l In
No na
Figure 6-13. TDMS File Viewer
Grouping TDMS Data

tio
Carefully consider the best way to group your data because the data
grouping can have a significant impact on the execution speed and
implementation complexity of writes and reads. Consider the original
format of your data and how you want to process or view the data when
Na
choosing a grouping scheme.
One technique is to group data by the type of data. For example, you might
put numeric data in one channel group and string data in another, or you
might put time domain data in one group and frequency domain data in
another. This makes it easy to compare the channels in a group, but can
make it difficult to find two channels that are related to each other.
Figure 6-14 shows an example of grouping by the type of data. In this
example, the temperature data is placed in one group and the wind data is

placed in another. Each group contains multiple channels of data. Notice

that when grouping by data type you typically have a fixed number of
groups, two in this case, and a dynamically determined number of channels.
uti ts
rib en
on
ist um
r D str
t fo l In
Figure 6-14. Grouping Data by Type
Another technique is to group related data. For example, you might put all
No na
the data that applies to a single UUT in one group. Grouping related data
allows you to easily locate all the related data about a particular subject, but
makes it harder to compare individual pieces of data among subjects.
Relational grouping helps convert cluster-based storage to a TDMS format.
tio
You can store all the information from a given cluster in a channel group,
with arrays in the cluster representing channels within the group, and scalar
items in the cluster representing properties of the channel group.
Figure 6-15 shows an example of relational grouping.
Na

uti ts
rib en
on
ist um
r D str Figure 6-15. Grouping Related Data
Notice that the input data is an array of clusters, each of which contains
multiple pieces of information about a test. Each test is stored as a separate
t fo l In
channel group. Information that applies to the entire test, such as Test Status,
is stored as properties of the channel group. Arrays of data, such as the time
data and power spectrum, are stored in channels, and information which
relates to the arrays of data, such as the RMS Value and Fundamental
Frequency, are stored as properties of the channels. Relational data typically
uses a fixed number of channels in a group, but the number of groups is
No na
dynamic.

tio
Na

Self-Review: Quiz
1. You need to store test results and organize the data into descriptive
groups. In the future, you need to efficiently view the test results by
uti ts
group. Which file storage format should you use?
a. Tab-delimited ASCII
rib en
b. Custom binary format
c. TDMS
on
d. Datalog
ist um
2. You must write a program which saves Portable Network Graphics
(PNG) image files. Which file storage method should you use?
r D str a. Storage file VIs
b. Binary file functions
c. ASCII file VIs
d. Datalog file VIs
t fo l In
3. You must store data that other engineers will later analyze with
Microsoft Excel. Which file storage format should you use?
No na

c. TDMS
d. Datalog
tio
4. Which of the following is a little-endian representation of an unsigned

32-bit integer (U32) with a value of 10?
Na
a. 00001010 00000000 00000000 00000000

b. 00000000 00000000 00000000 00001010
c. 00001010
d. 01010000 00000000 00000000 00000000

5. You can use the Binary File functions to read ASCII files.
a. True
b. False
uti ts
6. TDMS files store properties only at the channel or channel group level.
rib en
a. True
on
b. False
ist um
r D str
t fo l In
No na
tio
Na


1. You need to store test results and organize the data into descriptive
groups. In the future, you need to efficiently view the test results by
uti ts
group. Which file storage format should you use?
rib en
c. TDMS
on
d. Datalog
ist um
2. You must write a program which saves Portable Network Graphics
(PNG) image files. Which file storage method should you use?
r D str a. Storage file VIs
b. Binary file functions
c. ASCII file VIs
d. Datalog file VIs
t fo l In
3. You need to store data which other engineers will later analyze with
Microsoft Excel. Which file storage format should you use?
No na

c. TDMS
d. Datalog
tio
4. Which of the following is a little endian representation of an unsigned

32-bit integer (U32) with a value of 10?
Na
a. 00001010 00000000 00000000 00000000

b. 00000000 00000000 00000000 00001010
c. 00001010
d. 01010000 00000000 00000000 00000000

5. You can use the Binary File functions to read ASCII files.
a. True
b. False
uti ts
6. TDMS files store properties only at the channel or channel group level.
rib en
a. True
on
b. False
ist um
r D str
t fo l In
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Improving an Existing VI
7
uti ts
A common problem when you inherit VIs from other developers is that
rib en
features may have been added without attention to design, thus making it
progressively more difficult to add features later in the life of the VI. This is
on
known as software decay. One solution to software decay is to refactor the
software. Refactoring is the process of redesigning software to make it more
readable and maintainable so that the cost of change does not increase over
ist um
time. Refactoring changes the internal structure of a VI to make it more
readable and maintainable, without changing its observable behavior.
In this lesson, you will learn methods to refactor inherited code and
r D str experiment with typical issues that appear in inherited code.
Topics
A. Refactoring Inherited Code
B. Typical Refactoring Issues
t fo l In
C. Comparing VIs
No na
tio
Na

Lesson 7 Improving an Existing VI
A. Refactoring Inherited Code

Write large and/or long-term software applications with readability in mind
because the cost of reading and modifying the software is likely to outweigh
uti ts
the cost of executing the software. It costs more for a developer to read and
understand poorly designed code than it does to read code that was created
to be readable. In general, more resources are allocated to reading and
rib en
modifying software than to the initial implementation. Therefore VIs that
are easy to read and modify are more valuable than those that are not.
on
Creating well-designed software facilitates rapid development and
decreases possible decay. If a system starts to decay, you can spend large
ist um
amounts of time tracking down regression failures, which is not productive.
Changes also can take longer to implement because it is harder to
understand the system if it is poorly designed.
r D str Consider the inherited VI shown in Figure 7-1.

t fo l In
No na
tio
Na
Figure 7-1. Inherited VI

You can refactor the code as shown in Figure 7-2.
uti ts
rib en
on
ist um
Figure 7-2. Refactored Inherited Code
The refactored code performs the same function as the inherited code, but
the refactored code is more readable. The inherited code violates many of
r D str the block diagram guidelines you have learned.
When you make a VI easier to understand and maintain, you make it more
valuable because it is easier to add features to or debug the VI. The
refactoring process does not change observable behavior. Changing the way
t fo l In
a VI interacts with clients (users or other VIs) introduces risks that are not
present when you limit changes to those visible only to developers. The
benefit of keeping the two kinds of changes separate is that you can better
manage risks.
No na
Refactoring versus Performance Optimization

Although you can make changes that optimize the performance of a VI, this
is not the same as refactoring. Refactoring specifically changes the internal
structure of a VI to make it easier to read, understand, and maintain.
tio
A performance optimization is not refactoring because the goal of

optimization is not to make the VI easier to understand and modify. In fact,
performance optimization can make VIs more difficult to read and
understand, which might be an acceptable trade-off. Sometimes you must
sacrifice readability for improved performance, however, readability usually
Na
takes priority over speed of performance.
When to Refactor
The right time to refactor is when you are adding a feature to a VI or
debugging it. Although you might be tempted to rewrite the VI from scratch,
there is value in a VI that works, even if the block diagram is not readable.
Good candidates for complete rewrites are VIs that do not work or VIs that

satisfy only a small portion of your needs. You also can rewrite simple VIs
that you understand well. Consider what works well in an existing VI before
you decide to refactor.
uti ts
B. Typical Refactoring Issues
When you refactor a VI, manage the risk of introducing bugs by making
rib en
small, incremental changes to the VI and testing the VI after each
change. The flowchart shown in Figure 7-3 indicates the process for
on
refactoring a VI.
ist um
Improve Block Diagram
Test VI
r D str Is VI Acceptable?
No
Yes
t fo l In
Add Features or Use VI
Figure 7-3. Refactoring Flowchart
When you refactor to improve the block diagram, make small cosmetic
No na
changes before tackling larger issues. For example, it is easier to find

duplicated code if the block diagram is well organized and the terminals are
well labeled.
There are several issues that can complicate working with an inherited VI.
tio
The following sections describe typical problems and the refactoring

solutions you can use to make inherited VIs more readable.
Disorganized or Poorly Designed Block Diagram

Na
Improve the readability of a disorganized VI by relocating objects within the

block diagram. You also can create subVIs for sections of the VI that are
disorganized. Place comments on areas of a VI that are disorganized to
improve the readability of the VI.
Overly Large Block Diagram

A VI that has a block diagram that is larger than the screen size is difficult
to read. You should refactor the VI to make it smaller. The act of scrolling
complicates reading a block diagram and understanding the code. Improve

a large block diagram by moving objects around. Another technique to

reduce the screen space a block diagram occupies is to create subVIs for
sections of code within the block diagram. If you cannot reduce the block
diagram to fit on the screen, limit the scrolling to one direction.
uti ts
Poorly Named Objects and Poorly Designed Icons
Inherited VIs often contain controls and indicators that do not have
rib en
meaningful names. For example, the name of Control 1, shown in
Figure 7-4, does not indicate its purpose. Control 2 is the same control,
on
renamed to make the block diagram more readable and understandable.
ist um
1 2
1 Poorly Named Control 2 Meaningfully Named Control

r D str Figure 7-4. Naming Controls
VI names and icons also are important for improving the readability of a VI.
For example, the name My Acq.vi, shown on the left in Figure 7-5, does
t fo l In
not provide any information about the purpose of the VI. You can give the
VI a more meaningful name by saving a copy of the VI with a new name and
replacing all instances of the VI with the renamed VI. A simpler method is
to open all callers of the VI you want to rename, then save the VI with a new
name. When you use this method, LabVIEW automatically relinks all open
callers of the VI to the new name. Acq Window Temperature.vi reflects
No na
a more meaningful name for the VI.

tio
1 2 3
1 Poorly Named VI 3 Meaningful VI Name and VI Icon

2 Meaningfully Named VI
Na
Figure 7-5. Poorly Named SubVI
The VI icon also should clarify the purpose of the VI. The default icons used
for VI 1 and VI 2 in Figure 7-5 do not represent the purpose of the VI. You
can improve the readability of the VI by providing a meaningful icon, as
shown for VI 3.
By renaming controls and VIs and creating meaningful VI icons, you can
improve the readability of an inherited VI.

Unnecessary Logic
When you read the block diagram in Figure 7-6, notice that it contains
unnecessary logic. If a portion of the block diagram does not execute, delete
it. Understanding code that executes is difficult, but trying to understand
uti ts
code that never executes is inefficient and complicates the block diagram.
rib en
on
ist um
Figure 7-6. Unnecessary Logic
Duplicated Logic
r D str If a VI contains duplicated logic, you always should refactor the VI by
creating a subVI for the duplicated logic. This can improve the readability
and testability of the VI.
t fo l In
Lack of Dataflow Programming
If there are Sequence structures and local variables on the block diagram,
the VI probably does not use data flow to determine the programming flow.
You should replace most Sequence structures with the state machine design
pattern. Delete local variables and wire the controls and indicators directly.
No na
Complicated Algorithms
Complicated algorithms can make a VI difficult to read. Complicated
algorithms can be more difficult to refactor because there is a higher
tio
probability that the changes introduce errors. When you refactor a

complicated algorithm, make minor changes and test the code frequently.
In some cases you can refactor a complicated algorithm by using built-in
LabVIEW functions. For example, the VI in Figure 7-7 checks a user name
and password against a database.
Na

uti ts
rib en
on
ist um
Figure 7-7. Complicated Algorithm VI
You could refactor this VI using the built-in functions for searching strings,
as shown in Figure 7-8.
r D str
t fo l In
No na
Figure 7-8. Refactored VI

tio
C. Comparing VIs
The LabVIEW Professional Development System includes a utility to
determine the differences between two VIs loaded into the memory. Select
Na
Tools»Compare»Compare VIs to display the Compare VIs dialog box.
From this dialog box, you can select the VIs you want to compare, as well
as the characteristics of the VIs to check. When you compare the VIs, both
VIs display a Differences window that lists all differences between the
two VIs. In this window, you can select various differences and details that
you can circle for clarity.

Refactoring Checklist
Use the following refactoring checklist to help determine if you should
refactor a VI. If you answer yes to any of the items in the checklist, refer to
uti ts
the guidelines in the When to Refactor section of this lesson to refactor
the VI.
❑ Disorganized block diagram
rib en
❑ Overly large block diagram
on
❑ Poorly named objects and poorly designed icons
ist um
❑ Unnecessary logic
❑ Duplicated logic
r D str ❑ Lack of dataflow programming
❑ Complicated algorithms
t fo l In
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Creating and Distributing Applications
8
uti ts
This lesson describes the process of creating a stand-alone application and
rib en
installer for your LabVIEW projects.
Topics
on
A. Preparing the Files
ist um
B. Build Specifications
C. Building the Application and Installer
r D str
t fo l In
No na
tio
Na

Lesson 8 Creating and Distributing Applications
A. Preparing the Files

A stand-alone application allows the user to run your VIs without installing
the LabVIEW development system. Installers distribute the stand-alone
uti ts
application. Installers can include the LabVIEW Run-Time Engine, which
is necessary for running stand-alone applications. However, you can also
download the LabVIEW Run-Time Engine at ni.com/downloads.
rib en
Before you can create a stand-alone application with your VIs, you must
first prepare your files for distribution. The following topics describe a few
on
of the issues you need to consider as part of your preparation. Refer to the
Preparing Files section of the Building Applications Checklist topic in the
ist um
LabVIEW Help for more information.
VI Properties
Use the VI Properties dialog box to customize the window appearance and
r D str size. You might want to configure a VI to hide scroll bars, or you might want
to hide the buttons on the toolbar.
Path Names
Consider the path names you use in the VI. Assume you read data from a
t fo l In
file during the application, and the path to the file is hard-coded on the block
diagram. Once an application is built, the file is embedded in the executable,
changing the path of the file. Being aware of these issues will help you to
build more robust applications in the future.
Quit LabVIEW
No na
In a stand-alone application, the top-level VI must quit LabVIEW or close

the front panel when it is finished executing. To completely quit and close
the top-level VI, you must call the Quit LabVIEW function on the block
diagram of the top-level VI.
tio
External Code
Know what external code your application uses. For example, do you call
any system or custom DLLs or shared libraries? Are you going to process
command line arguments? These are advanced examples that are beyond the
Na
scope of this course, but you must consider them for the application. Refer
to the Using External Code in LabVIEW topic in the LabVIEW Help.

VI Server Properties and Methods

Not all VI Server properties and methods are supported in the LabVIEW
Run-Time Engine. Unsupported VI server properties and methods return
errors when called from the Run-Time Engine. Use proper error handling to
uti ts
detect any of these unsupported properties and methods. You can also
review the VI Server Properties and Methods Not Supported in the
LabVIEW Run-Time Engine topic in the LabVIEW Help.
rib en
Providing Online Help in Your LabVIEW Applications
on
As you put the finishing touches on your application, you should provide
online help to the user. To create effective documentation for VIs, create VI
ist um
and object descriptions that describe the purpose of the VI or object and give
users instructions for using the VI or object.
Use the following functions, located on the Help palette, to

programmatically show or hide the Context Help window and link from
VIs to HTML files or compiled help files:
r D str • Use the Get Help Window Status function to return the status and
position of the Context Help window.
• Use the Control Help Window function to show, hide, or reposition
the Context Help window.
t fo l In
• Use the Control Online Help function to display the table of contents,
jump to a specific topic in the file, or close the online help.
• Use the Open URL in Default Browser VI to display a URL or HTML
file in the default Web browser.
No na
B. Build Specifications
tio
After you have prepared your files for distribution, you need to create a build
specification for your application. The Build Specifications node in the
Project Explorer window allows you to create and configure build
specifications for LabVIEW builds. A build specification contains all the
Na
settings for the build, such as files to include, directories to create, and
settings for VIs.
Note If you previously hid Build Specifications in the Project Explorer window, you
must display the item again to access it in the Project Explorer window.

You can create and configure the following types of build specifications:
• Stand-alone applications—Use stand-alone applications to provide
other users with executable versions of VIs. Applications are useful
when you want users to run VIs without installing the LabVIEW
uti ts
development system. Stand-alone applications require the LabVIEW
Run-Time Engine. (Windows) Applications have a .exe extension.
(Mac OS) Applications have a .app extension.
rib en
• Installers—(Windows) Use installers to distribute stand-alone
applications, shared libraries, and source distributions that you create
on
with the Application Builder. Installers that include the LabVIEW
Run-Time Engine are useful if you want users to be able to run
ist um
applications or use shared libraries without installing LabVIEW.
• .NET Interop Assemblies—(Windows) Use .NET interop assemblies to
package VIs for the Microsoft .NET Framework. You must install the
Microsoft .NET Framework 2.0 or higher to build a .NET interop
r D str assembly using the Application Builder.
• Packed project libraries—Use packed project libraries to package
multiple LabVIEW files into a single file. When you deploy VIs in a
packed library, fewer files deploy because the packed library is a single
file. The top-level file of a packed library is a project library. Packed
libraries contain one or more VI hierarchies that compile for a specific
t fo l In
operating system. Packed libraries have a .lvlibp extension.
• Shared libraries—Use shared libraries if you want to call VIs using
text-based programming languages, such as LabWindows/CVI,
Microsoft Visual C++, and Microsoft Visual Basic. Using shared
libraries provides a way for programming languages other than
No na
LabVIEW to access code developed with LabVIEW. Shared libraries

are useful when you want to share the functionality of the VIs you build
with other developers. Other developers can use the shared libraries but
cannot edit or view the block diagrams unless you enable debugging.
(Windows) Shared libraries have a .dll extension. (Mac OS) Shared
tio
libraries have a .framework extension. (Linux) Shared libraries have a

.so extension. You can use .so or you can begin with lib and end with
.so, optionally followed by the version number. This allows other
applications to use the library.
Na
• Source distributions—Use source distributions to package a collection

of source files. Source distributions are useful if you want to send code
to other developers to use in LabVIEW. You can configure settings for
specified VIs to add passwords, remove block diagrams, or apply other
settings. You also can select different destination directories for VIs in a
source distribution without breaking the links between VIs and subVIs.

• Web services (RESTful)—(Windows) Publish VIs within LabVIEW

Web services to provide a standardized method for the LabVIEW Web
Server to deploy applications that any HTTP client can access. Web
services support clients across most major platforms and programming
uti ts
languages and allow you to easily implement and deploy Web
applications over a network using LabVIEW.
• Zip files—Use zip files when you want to distribute files or an entire
rib en
LabVIEW project as a single, portable file. A zip file contains
compressed files, which you can send to users. Zip files are useful if you
on
want to distribute selected source files to other LabVIEW users. You
also can use the Zip VIs to create zip files programmatically.
ist um
Refer to the Configuring Build Specifications section of the Building
Applications Checklist topic in the LabVIEW Help for more information.
C. Building the Application and Installer

r D str
System Requirements
Applications that you create with Build Specifications generally have the
same system requirements as the LabVIEW development system. Memory
requirements vary depending on the size of the application created.
t fo l In
You can distribute these files without the LabVIEW development system;
however, to run stand-alone applications and shared libraries, users must
have the LabVIEW Run-Time Engine installed.
Configuring Build Specifications

No na
You must create build specifications in the Project Explorer window.

Expand My Computer, right-click Build Specifications, select New and
the type of build you want to configure from the shortcut menu. Use the
pages in the Source Distribution Properties, Application Properties,
tio
Shared Library Properties, Installer Properties, .NET Interop

Assembly Properties, Web Service (RESTful) Properties, Packed
Library Properties, or Zip File Properties dialog boxes to configure
settings for the build specification. After you define these settings, click the
OK button to close the dialog box and update the build specification in the
Na
project. The build specification appears under Build Specifications.

Right-click a specification and select Build from the shortcut menu to
complete the build. You also can select Build All from the shortcut menu to
build all specifications under Build Specifications. If you rebuild a given
specification, LabVIEW overwrites the existing files from the previous
build that are part of the current build.

Refer to the Caveats and Recommendations for Building Installers topic in

the LabVIEW Help for more information.
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Summary
• LabVIEW features the Application Builder, which enables you to create
stand-alone executables and installers. The Application Builder is
uti ts
available in the Professional Development Systems or as an add-on
package.
• Creating a professional, stand-alone application with your VIs involves
rib en
understanding the following:
on
– The architecture of your VI
– The programming issues particular to the VI
ist um
– The application building process
– The installer building process
r D str
t fo l In
No na
tio
Na

Notes
uti ts
rib en
on
ist um
r D str
t fo l In
No na
tio
Na

Additional Information and Resources
A
uti ts
This appendix contains additional information about National Instruments
rib en
technical support options and LabVIEW resources.
National Instruments Technical Support Options
on
Visit the following sections of the award-winning National Instruments
ist um
Web site at ni.com for technical support and professional services:
• Support—Technical support at ni.com/support includes the
following resources:
– Self-Help Technical Resources—For answers and solutions,
visit ni.com/support for software drivers and updates,
r D str a searchable KnowledgeBase, product manuals, step-by-step
troubleshooting wizards, thousands of example programs, tutorials,
application notes, instrument drivers, and so on. Registered
users also receive access to the NI Discussion Forums at
t fo l In
ni.com/forums. NI Applications Engineers make sure every
question submitted online receives an answer.
– Standard Service Program Membership—This program entitles
members to direct access to NI Applications Engineers via phone
and email for one-to-one technical support, as well as exclusive
access to eLearning training modules at ni.com/eLearning.
No na
NI offers complementary membership for a full year after purchase,

after which you may renew to continue your benefits.
For information about other technical support options in your
area, visit ni.com/services or contact your local office at
tio
ni.com/contact.
• System Integration—If you have time constraints, limited in-house
technical resources, or other project challenges, National Instruments
Alliance Partner members can help. The NI Alliance Partners joins
Na
system integrators, consultants, and hardware vendors to provide

comprehensive service and expertise to customers. The program ensures
qualified, specialized assistance for application and system
development. To learn more, call your local NI office or visit
ni.com/alliance.
You also can visit the Worldwide Offices section of ni.com/niglobal

to access the branch office Web sites, which provide up-to-date contact
information, support phone numbers, email addresses, and current events.
© National Instruments Corporation A-1 LabVIEW Core 2 Course Manual

Appendix A Additional Information and Resources
Other National Instruments Training Courses

National Instruments offers several training courses for LabVIEW users.
These courses continue the training you received here and expand it to other
uti ts
areas. Visit ni.com/training to purchase course materials or sign up for
instructor-led, hands-on courses at locations around the world.
rib en
National Instruments Certification
on
Earning an NI certification acknowledges your expertise in working with
NI products and technologies. The measurement and automation industry,
your employer, clients, and peers recognize your NI certification credential
ist um
as a symbol of the skills and knowledge you have gained through
experience. Visit ni.com/training for more information about the
NI certification program.
LabVIEW Resources
r D str This section describes how you can receive more information regarding
LabVIEW.
LabVIEW Publications
t fo l In
LabVIEW Books
Many books have been written about LabVIEW programming and
applications. The National Instruments Web site contains a list of all
the LabVIEW books and links to places to purchase these books.
Visit http://zone.ni.com/devzone/cda/tut/p/id/5389 for more
No na
information.
tio
Na
LabVIEW Core 2 Course Manual A-2 ni.com

Glossary
uti ts
automatic scaling Ability of scales to adjust to the range of plotted values. On graph
scales, autoscaling determines maximum and minimum scale values.
rib en
B
on
block diagram Pictorial description or representation of a program or algorithm. The
block diagram consists of executable icons called nodes and wires that
ist um
carry data between the nodes. The block diagram is the source code for
the VI. The block diagram resides in the block diagram window of
the VI.
Boolean controls and Front panel objects to manipulate and display Boolean (TRUE or
indicators FALSE) data.
r D str
broken Run button Button that replaces the Run button when a VI cannot run because of
errors.
broken VI VI that cannot run because of errors; signified by a broken arrow in the
t fo l In
broken Run button.
No na
tio
Na
© National Instruments Corporation G-1 LabVIEW Core 2 Course Manual

Glossary
C
channel 1. Physical—A terminal or pin at which you can measure or generate
an analog or digital signal. A single physical channel can include more
uti ts
than one terminal, as in the case of a differential analog input channel
or a digital port of eight lines. A counter also can be a physical channel,
although the counter name is not the name of the terminal where the
rib en
counter measures or generates the digital signal.
2. Virtual—A collection of property settings that can include a name,
on
a physical channel, input terminal connections, the type of
measurement or generation, and scaling information. You can define
ist um
NI-DAQmx virtual channels outside a task (global) or inside a task
(local). Configuring virtual channels is optional in Traditional
NI-DAQ (Legacy) and earlier versions, but is integral to every
measurement you take in NI-DAQmx. In Traditional NI-DAQ
(Legacy), you configure virtual channels in MAX. In NI-DAQmx, you
can configure virtual channels either in MAX or in your program, and
r D str you can configure channels as part of a task or separately.
3. Switch—A switch channel represents any connection point on a
switch. It can be made up of one or more signal wires (commonly one,
two, or four), depending on the switch topology. A virtual channel
t fo l In
cannot be created with a switch channel. Switch channels may be used
only in the NI-DAQmx Switch functions and VIs.
checkbox Small square box in a dialog box which you can select or clear.
Checkboxes generally are associated with multiple options that you
can set. You can select more than one checkbox.
No na
conditional terminal Terminal of a While Loop that contains a Boolean value that
determines if the VI performs another iteration.
Context Help window Window that displays basic information about LabVIEW objects when
tio
you move the cursor over each object. Objects with context help
information include VIs, functions, constants, structures, palettes,
properties, methods, events, and dialog box components.
control Front panel object for entering data to a VI interactively or to a subVI

Na
programmatically, such as a knob, push button, or dial.
Controls palette Palette that contains front panel controls, indicators, and decorative
objects.
current VI VI whose front panel, block diagram, or Icon Editor is the active
window.
LabVIEW Core 2 Course Manual G-2 ni.com

Glossary
D
DAQ See data acquisition (DAQ).
uti ts
DAQ Assistant A graphical interface for configuring measurement tasks, channels,
and scales.
DAQ device A device that acquires or generates data and can contain multiple
rib en
channels and conversion devices. DAQ devices include plug-in
devices, PCMCIA cards, and DAQPad devices, which connect to a
on
computer USB or IEEE 1394 port. SCXI modules are considered DAQ
devices.
ist um
data acquisition 1. Acquiring and measuring analog or digital electrical signals from
(DAQ) sensors, acquisition transducers, and test probes or fixtures.
2. Generating analog or digital electrical signals.
data flow
r D str Programming system that consists of executable nodes that execute
only when they receive all required input data. The nodes produce
output data automatically when they execute. LabVIEW is a dataflow
system. The movement of data through the nodes determines the
execution order of the VIs and functions on the block diagram.
t fo l In
data type Format for information. In LabVIEW, acceptable data types for most
VIs and functions are numeric, array, string, Boolean, path, refnum,
enumeration, waveform, and cluster.
default Preset value. Many VI inputs use a default value if you do not specify
a value.
No na
device An instrument or controller you can access as a single entity that

controls or monitors real-world I/O points. A device often is connected
to a host computer through some type of communication network.
See also DAQ device and measurement device.
tio
drag To use the cursor on the screen to select, move, copy, or delete objects.
driver Software that controls a specific hardware device, such as a DAQ

device.
Na
dynamic data type Data type used by Express VIs that includes the data associated with a
signal and attributes that provide information about the signal, such as
the name of the signal or the date and time LabVIEW acquired the
data. Attributes specify how the signal appears on a graph or chart.

Glossary
E
Error list window Window that displays errors and warnings occurring in a VI and in
some cases recommends how to correct the errors.
uti ts
error message Indication of a software or hardware malfunction or of an unacceptable
data entry attempt.
rib en
Express VI A subVI designed to aid in common measurement tasks. You configure
an Express VI using a configuration dialog box.
on
F
ist um
For Loop Iterative loop structure that executes its subdiagram a set number of
times. Equivalent to text-based code: For i = 0 to n – 1, do....
front panel Interactive user interface of a VI. Front panel appearance imitates
physical instruments, such as oscilloscopes and multimeters.
r D str
function Built-in execution element, comparable to an operator, function, or
statement in a text-based programming language.
Functions palette Palette that contains VIs, functions, block diagram structures, and
t fo l In
constants.
G
General Purpose GPIB. Synonymous with HP-IB. The standard bus used for controlling
Interface Bus electronic instruments with a computer. Also called IEEE 488 bus
No na
because it is defined by ANSI/IEEE Standards 488-1978, 488.1-1987,

and 488.2-1992.
graph 2D display of one or more plots. A graph receives and plots data as a
tio
block.
I
I/O Input/Output. The transfer of data to or from a computer system
Na
involving communications channels, operator input devices, and/or

data acquisition and control interfaces.
icon Graphical representation of a node on a block diagram.
indicator Front panel object that displays output, such as a graph or LED.
instrument driver A set of high-level functions that control and communicate with
instrument hardware in a system.

Glossary
Instrument I/O Add-on launched from the Instrument I/O Assistant Express VI that
Assistant communicates with message-based instruments and graphically parses
the response.
uti ts
L
label Text object used to name or describe objects or regions on the front
rib en
panel or block diagram.
on
LabVIEW Laboratory Virtual Instrument Engineering Workbench. LabVIEW is
a graphical programming language that uses icons instead of lines of
text to create programs.
ist um
LED Light-emitting diode.
legend Object a graph or chart owns to display the names and plot styles of
r D str plots on that graph or chart.
M
MAX See Measurement & Automation Explorer.
Measurement & The standard National Instruments hardware configuration and

t fo l In
Automation Explorer diagnostic environment for Windows.
measurement device DAQ devices such as the E Series multifunction I/O (MIO) devices,
SCXI signal conditioning modules, and switch modules.
menu bar Horizontal bar that lists the names of the main menus of an application.
No na
The menu bar appears below the title bar of a window. Each
application has a menu bar that is distinct for that application, although
some menus and commands are common to many applications.
tio
N
NI-DAQ Driver software included with all NI DAQ devices and signal
conditioning components. NI-DAQ is an extensive library of VIs and
ANSI C functions you can call from an application development
Na
environment (ADE), such as LabVIEW, to program an NI

measurement device, such as the M Series multifunction I/O (MIO)
DAQ devices, signal conditioning modules, and switch modules.

Glossary
NI-DAQmx The latest NI-DAQ driver with new VIs, functions, and development
tools for controlling measurement devices. The advantages of
NI-DAQmx over earlier versions of NI-DAQ include the DAQ
Assistant for configuring channels and measurement tasks for your
uti ts
device for use in LabVIEW, LabWindows/CVI, and Measurement
Studio; NI-DAQmx simulation for most supported devices for testing
and modifying applications without plugging in hardware; and a
rib en
simpler, more intuitive API for creating DAQ applications using fewer
functions and VIs than earlier versions of NI-DAQ.
on
node Program execution element. Nodes are analogous to statements,
operators, functions, and subroutines in text-based programming
ist um
languages. On a block diagram, nodes include functions, structures,
and subVIs.
numeric controls and Front panel objects to manipulate and display numeric data.
indicators
r D str
O
object Generic term for any item on the front panel or block diagram,
including controls, indicators, structures, nodes, wires, and imported
t fo l In
pictures.
Operating tool Tool to enter data into controls or to operate them.
P
No na
palette Displays objects or tools you can use to build the front panel or block
diagram.
plot Graphical representation of an array of data shown either on a graph or

a chart.
tio
Positioning tool Tool to move and resize objects.
project A collection of LabVIEW files and files not specific to LabVIEW that
you can use to create build specifications and deploy or download files
Na
to targets.
Project Explorer Window in which you can create and edit LabVIEW projects.
window
Properties dialog Dialog boxes accessed from the shortcut menu of a control or indicator
boxes that you can use to configure how the control or indicator appears in
the front panel window.

Glossary
pull-down menus Menus accessed from a menu bar. Pull-down menu items are usually
general in nature.
PXI PCI eXtensions for Instrumentation. A modular, computer-based
uti ts
instrumentation platform.
rib en
sample Single analog or digital input or output data point.
on
scale Part of graph, chart, and some numeric controls and indicators that
contains a series of marks or points at known intervals to denote units
ist um
of measure.
shortcut menu Menu accessed by right-clicking an object. Menu items pertain to that
object specifically.
stringr D str Representation of a value as text.
structure Program control element, such as a Flat Sequence structure, Stacked

Sequence structure, Case structure, For Loop, While Loop, or Timed
Loop.
t fo l In
subpalette Palette that you access from another palette that is above the subpalette
in hierarchy.
subVI VI used on the block diagram of another VI. Comparable to a

subroutine.
No na
T
task A collection of one or more channels, timing, triggering, and other
properties in NI-DAQmx. A task represents a measurement or
generation you want to perform.
tio
template VI VI that contains common controls and indicators from which you can
build multiple VIs that perform similar functions. Access template VIs
from the New dialog box.
Na
terminal Object or region on a node through which data pass.
tip strip Small yellow text banners that identify the terminal name and make it
easier to identify terminals for wiring.
tool Special cursor to perform specific operations.
toolbar Bar that contains command buttons to run and debug VIs.

Glossary
Traditional NI-DAQ An older driver with outdated APIs for developing data acquisition,
(Legacy) instrumentation, and control applications for older National
Instruments DAQ devices. You should use Traditional NI-DAQ
(Legacy) only in certain circumstances. Refer to the NI-DAQ Readme
uti ts
for more information about when to use Traditional NI-DAQ (Legacy),
including a complete list of supported devices, operating systems, and
application software and language versions.
rib en
V
on
VI See virtual instrument (VI).
ist um
virtual instrument Program in LabVIEW that models the appearance and function of a
(VI) physical instrument.
W r D str
waveform Multiple voltage readings taken at a specific sampling rate.
waveform chart Indicator that plots data points at a certain rate.
While Loop Loop structure that repeats a section of code until a condition occurs.
t fo l In
wire Data path between nodes.
Wiring tool Tool to define data paths between terminals.

No na
tio
Na

Labview Core 2 Course Manual: Instruments Not For Distribution

Uploaded by

Copyright:

Available Formats

Labview Core 2 Course Manual: Instruments Not For Distribution

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Labview Core 2 Course Manual: Instruments Not For Distribution

Uploaded by

Copyright:

Available Formats

uti ts

STLport. Copyright 1999–2003 Boris Fomitchev

Worldwide Technical Support and Product Information

C. Caveats and Recommendations ............................................................................3-11

© National Instruments Corporation iii LabVIEW Core 2 Course Manual

LabVIEW Core 2 Course Manual iv ni.com

New User Experienced User Advanced User

LabVIEW Core 1* LabVIEW Core 3* Managing Software

Certified LabVIEW Certified LabVIEW Certified LabVIEW

LabVIEW Instrument Control

LabVIEW Real-Time 1 LabVIEW Real-Time 2

© National Instruments Corporation v LabVIEW Core 2 Course Manual

In the course manual, each lesson consists of the following:

In the exercise manual, each lesson consists of the following:

Several exercises use a plug-in multifunction data acquisition (DAQ) device

Alternate instructions are provided for completing the exercises without

Instruments DAQ device connected to a signal source, such as a function

LabVIEW Core 2 Course Manual vi ni.com

C. What You Need to Get Started

❑ DAQmx 9.3.5 or later

Solutions Contains completed course exercises

D. Installing the Course Software

1. Insert the course CD in your computer. The LabVIEW Core 2 Course

3. Follow the onscreen instructions to complete installation and setup.

Exercise files are located in the <Exercises>\LabVIEW Core 2\ folder.

directory of your computer.

© National Instruments Corporation vii LabVIEW Core 2 Course Manual

LabVIEW Core 2 Course Manual viii ni.com

This icon denotes a caution, which advises you of precautions to take to

italic Italic text denotes variables, emphasis, a cross-reference, or an introduction

variables, filenames, and extensions.

that are different from the other examples.

© National Instruments Corporation ix LabVIEW Core 2 Course Manual

D. Timing a Design Pattern

© National Instruments Corporation 1-1 LabVIEW Core 2 Course Manual

LabVIEW includes several built-in VI templates for several standard design

• Producer/Consumer Design Pattern (Events)—Use this template to

asynchronously in response to an event without slowing the user

LabVIEW Core 2 Course Manual 1-2 ni.com

• Standard State Machine—Use this template to build a standard state

B. Single Loop Design Patterns

Simple VI Design Patterns

single task—it determines what warning to output dependent on a set of

© National Instruments Corporation 1-3 LabVIEW Core 2 Course Manual

General VI Design Patterns

Figure 1-2 shows the general VI design pattern.

Figure 1-2. General VI Design Pattern

LabVIEW Core 2 Course Manual 1-4 ni.com

State Machine Design Pattern

A state machine in LabVIEW consists of a While Loop, a Case structure,

© National Instruments Corporation 1-5 LabVIEW Core 2 Course Manual

Figure 1-4. Idle (Default), Event 1, and Event 2 States

LabVIEW Core 2 Course Manual 1-6 ni.com

Parallel Loop Design Pattern

Figure 1-5. Parallel Loop Design Pattern

© National Instruments Corporation 1-7 LabVIEW Core 2 Course Manual

Master/Slave Design Pattern

Figure 1-6. Master/Slave Design Pattern

LabVIEW Core 2 Course Manual 1-8 ni.com