OnlineCore2 2012 Day1Exercises

on
TM
rib
uti
LabVIEW Core 2
Exercises
ist
Course Software Version 2012

August 2012 Edition
Part Number 325293D-01
LabVIEW Core 2 Exercises
Copyright
rD
19932012 National Instruments. All rights reserved.

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.
End-User License Agreements and Third-Party Legal Notices
t fo
You can find end-user license agreements (EULAs) and third-party legal notices in the following locations:
Notices are located in the <National Instruments>\_Legal Information and <National Instruments> directories.
EULAs are located in the <National Instruments>\Shared\MDF\Legal\license directory.
Review <National Instruments>\_Legal Information.txt for more information on including legal information in installers built with NI products.
Trademarks
No
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.
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: HelpPatents in your software, the patents.txt file on your media, or the National Instruments
Patent Notice at ni.com/patents.
on
uti
rib
ist
rD
t fo
ni.com
Worldwide Offices
No
Worldwide Technical Support and Product Information
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
To comment on National Instruments documentation, refer to the National Instruments Web site at ni.com/info and enter the Info Code feedback.
on
Contents
Student Guide
uti
NI Certification........................................................................................................................................................................................v
Course Description ..................................................................................................................................................................................vi
What You Need to Get Started ................................................................................................................................................................vi
Installing the Course Software ................................................................................................................................................................vii
Course Goals ...........................................................................................................................................................................................vii
Course Conventions.................................................................................................................................................................................viii
rib
A.
B.
C.
D.
E.
F.
Lesson 1
Moving Beyond Dataflow
Concept: Comparing Queues With Local Variables..................................................................................................1-3

Concept: Comparing Event Structure Design with Polling Design...........................................................................1-11
ist
Exercise 1-1
Exercise 1-2
Lesson 2
Implementing Design Patterns
rD
Simple State Machine Template ................................................................................................................................2-3

Concept: Producer/ConsumerEvents .....................................................................................................................2-17
Concept: Producer/Consumer Error Handling...........................................................................................................2-21
Histogram...................................................................................................................................................................2-27
User Access Level .....................................................................................................................................................2-39
Lesson 3
Controlling the User Interface
Display Temperature and Limits ...............................................................................................................................3-3

Customizing the VI Window .....................................................................................................................................3-9
Using SubVIs .............................................................................................................................................................3-15
No
Exercise 3-1
Exercise 3-2
Exercise 3-3
t fo
Exercise 2-1
Exercise 2-2
Exercise 2-3
Exercise 2-4
Exercise 2-5
National Instruments
iii
Contents
ni.com
Create Folder and File................................................................................................................................................4-3

Write Multiple Channels with Simple Header...........................................................................................................4-7
Read TDMS Files ......................................................................................................................................................4-13
uti
Exercise 4-1
Exercise 4-2
Exercise 4-3
on
Lesson 4
File I/O Techniques
Lesson 5
Improving an Existing VI
Concept: Refactoring Inherited Code ........................................................................................................................5-1
rib
Exercise 5-1
Lesson 6
Creating and Distributing Applications
No
t fo
Appendix A
Setting Up Your Hardware
ist
Preparing Files for Distribution .................................................................................................................................6-3

Creating and Debugging a Stand-Alone Application ................................................................................................6-7
Building an Installer and Debugging on a Remote Machine.....................................................................................6-11
rD
Exercise 6-1A
Exercise 6-1B
Exercise 6-1C
iv
on
Student Guide
uti
Thank you for purchasing the LabVIEW Core 2 course kit. You can begin developing an application soon after you complete this course. This exercise manual and
the accompanying software are used in the two-day, hands-on LabVIEW Core 2 course.
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. Visit ni.com/
training for online course schedules, syllabi, training centers, and class registration.
rib
A. NI Certification
Experienced User
Advanced User
ist
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 courses that are part of the LabVIEW training series. Refer to ni.com/training for more
information about NI Certification.
LabVIEW Core 3*
Managing Software
Engineering in LabVIEW
LabVIEW Connectivity
Advanced Architectures
in LabVIEW
New User
Courses
LabVIEW Core 1*
rD
LabVIEW Core 2*
Object-Oriented Design
and Programming
in LabVIEW
Certifications
LabVIEW Performance
Certified LabVIEW
Developer Exam
Certified LabVIEW
Architect Exam
LabVIEW Instrument Control
LabVIEW Real-Time 1
LabVIEW Real-Time 2
LabVIEW FPGA
LabVIEW DAQ and Signal Conditioning
Modular Instruments Series
t fo
Certified LabVIEW
Associate Developer Exam
No
Other Courses
*Core courses are strongly recommended to realize maximum productivity gains when using LabVIEW.
| v
Student Guide
ni.com
vi
on
B. Course Description
In the course manual, each lesson consists of the following:
uti
The LabVIEW Core 2 course teaches you programming concepts, techniques, features, VIs, and functions you can use to create test 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 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
course and exercise manuals are divided into lessons, described as follows.
An introduction that describes the purpose of the lesson and what you will learn
A description of the topics in the lesson
A summary or quiz that tests and reinforces important concepts and skills taught in the lesson
rib
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 a set of additional exercises to complete if time permits
For course and exercise manual updates and corrections, refer to ni.com/info and enter the Info Code core2.
rD
Note
ist
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.
t fo
If you do not have this hardware, you still can complete the exercises. Alternate instructions are provided for completing the exercises without hardware. You also
can substitute other hardware for those previously mentioned. For example, you can use another National Instruments DAQ device connected to a signal source, such
as a function generator.
C. What You Need to Get Started
Before you use this course manual, make sure you have all of the following items:
No
Computer running Windows 7/Vista/XP
Multifunction DAQ device configured as Dev1 using Measurement & Automation Explorer (MAX)
DAQ Signal Accessory or BNC-2120, wires, and cable
on
LabVIEW Professional Development System 2012 or later

DAQmx 9.5.5 or later
uti
LabVIEW Core 2 course CD, from which you install the following folders:
Directory
Description
Contains VIs used in the course
Solutions
Contains completed course exercises
rib
Exercises
D. Installing the Course Software

Complete the following steps to install the course software.
ist
1. Insert the course CD in your computer. The LabVIEW Core 2 Course Setup dialog box appears.
2. Click Install the course materials.
3. Follow the onscreen instructions to complete installation and setup.
Note
rD
Exercise files are located in the <Exercises>\LabVIEW Core 2\ folder.
Folder names in angle brackets, such as <Exercises>, refer to folders on the root directory of your computer.
E. Course Goals
t fo
This course prepares you to do the following:
Apply common design patterns that use queues and events
Use event programming effectively
Programmatically control user interface objects
Evaluate file I/O formats and use them in applications
Modify existing code for improved usability
No
| vii
Student Guide
viii
Prepare, build, debug, and deploy stand-alone applications
on
ni.com
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 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 HelpFind Examples, for example VIs
you can use and incorporate into VIs you create
uti
rib
F. Course Conventions
The following conventions appear in this course manual:
The symbol leads you through nested menu items and dialog box options to a final action. The sequence ToolsInstrumentation
Find Instrument Drivers directs you to drop down the Tools menu, select the Instrumentation item, and finally select the Find
Instrument Drivers option.
ist
This icon denotes a tip, which alerts you to advisory information.
rD
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.
This icon indicates that an exercise requires a plug-in DAQ device.
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 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, variables, filenames, and extensions.
No
monospace bold
t fo
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 that are different from the other examples.
on
Exercises
uti
Concept: Comparing Queues With Local Variables
Exercise 1-2
Concept: Comparing Event Structure Design with Polling Design
No
t fo
rD
ist
rib
Exercise 1-1
| 1-1
No
t fo
on
uti
rib
ist
rD
Concept: Comparing Queues With Local Variables
on
Exercise 1-1
Goal
uti
In this exercise, you run and examine a prebuilt producer/consumer design pattern VI that transfers data that a producer loop generates to consumer loops using local
variables and queues.
Description
Queues data that the producer loop generates.
Dequeues data in the consumer loop.
Waits for the queue to empty before exiting the VI.
Uses local variables to read and display data from the producer loop.
No
t fo
rD
ist
rib
The following sections describe how the Queues vs Local Variables VI does the following.
Creates a queue.
1-3
Lesson 1
ni.com
1-4
on
1. Open Queues vs Local Variables.lvproj in the <Exercises>\LabVIEW Core 2\Queues versus Local Variables directory.
2. Double-click Queues vs Local Variables.vi in the Project Explorer window to open the VI. The front panel of this VI is shown in Figure 1-1.
t fo
rD
ist
rib
uti
Figure 1-1. Front Panel of the Queues vs Local Variables VI
4. Stop the VI.
No
3. Run the VI. The Producer Loop generates data and transfers it to each consumer loop using a local variable and a queue. Observe the behavior of the VI when
the consumer loops are set to the same speed as the producer loop.
on
5. Display and examine the block diagram for this VI. The following sections describe parts of this block diagram in more detail.
No
t fo
rD
ist
rib
uti
Figure 1-2. Block Diagram of the Queues vs Local Variables VI
1-5
Lesson 1
ni.com
1-6
on
Creating a Queue
You create the queue with code shown in Figure 1-3. This code is located to the left of the producer loop.
uti
Figure 1-3. Creating the Queue
1
2
rib
Max queue sizeSets the maximum number of elements that the queue can hold.
Data Type numeric constantWired to the element data type input of the Obtain Queue function, specifies the type of data that you want the queue to contain.
Obtain QueueCreates the queue and defines the data type.
ist
Queuing Data Generated by the Producer Loop
Enqueue ElementAdds each data element the Generate Sine VI generates in the Producer Loop to the back of the queue.
No
t fo
rD
Figure 1-4. Queuing Data the Producer Loop Generates
on
Dequeuing Data from the Producer Loop inside the Queue Consumer Loop
uti
Figure 1-5. Dequeuing Data inside the Consumer Loop
rib
Dequeue ElementRemoves an element from the front of the queue and sends the data element to the Queue Consumer Loop waveform chart.
Get Queue StatusIndicates how many elements remain in the queue. In order to process these data elements, you must execute the Queue Consumer Loop
faster than the Producer Loop, or continue to process after the Producer Loop stops.
No
t fo
rD
ist
1-7
Lesson 1
ni.com
on
Waiting for the Queue to Empty
uti
Figure 1-6. Waiting for the Queue to Empty
rib
rD
ist
While LoopWaits for the queue to empty before stopping the VI. Refer to this While Loop as the Queue Wait Loop.
Get Queue StatusReturns information about the current state of the queue, such as the number of data elements currently in the queue.
Equal To 0?Wired to the stop condition of the Queue Wait Loop checks if the queue is empty.
Release QueueReleases and clears references to the queue.
Simple Error HandlerReports any error at the end of execution.
No
t fo
1-8
on
Local Variable Consumer Loop

The Producer Loop also writes the generated sine wave data to a local variable while the Local Variable Consumer Loop periodically reads out the sine wave data
from the same local variable.
ist
rib
uti
Figure 1-7. Local Variable Consumer Loop
Update CountersUpdates the counters for missed or duplicated samples.
Test
rD
2. Run the VI.
t fo
Local Variable Consumer Loop

1. Switch to the front panel of the Queues vs Local Variables VI.
3. Select different speeds for the Local Variable Consumer Loop and observe the Local Variable Consumer Loop chart and the results generated on the Missing
Samples indicator or Duplicated Samples indicator.
Ensure that the Loop Speed selected is Same as Producer Loop and observe the Producer Loop chart and the Local Variable Consumer Loop chart. A race
No
condition may occur resulting in missed points or duplicated data.
Select 2x from the pull-down menu of the Loop Speed control and observe the Local Variable Consumer Loop chart. A race condition occurs because data
is consumed faster than it is produced, allowing the local variable to read the same value multiple times.
1-9
Lesson 1
ni.com
1-10
Select 1/2 as Producer from the pull-down menu of the Loop Speed control and observe the Local Variable Consumer Loop chart. A race condition occurs
on
because data is produced faster than it is consumed. The data changes before the local variable has a chance to read it.
Select the remaining options available from the pull-down menu of the Loop Speed control and observe the data retrieval.
uti
4. Stop the VI.
Data transfer between two non-synchronized parallel loops using local variables causes a race condition. This occurs when the Producer Loop is writing a value
to a local variable while the Local Variable Consumer Loop is periodically reading out the value from the same local variable. Because the parallel loops are not
synchronized, the value can be written before it has actually been read or vice versa resulting in data starvation or data overflow.
rib
Queue Consumer Loop

1. Run the VI.
2. Select the loop time speed of the Queue Consumer Loop and observe the Queue Consumer Loop waveform chart and the results generated on the Samples in
Queue indicator.
ist
Ensure that the Loop Speed selected is Same as Producer and observe the value of the Samples in Queue indicator. The value should remain zero. Hence
with queues, you will not lose data when the producer and consumer loops are executing at the same rate.
Select 2x from the pull-down menu of the Loop Speed control and observe the value of the Samples in Queue indicator. The value should remain zero.
rD
Hence with queues, you will not lose data if the consumer loop is executing much faster than the producer loop.
Select 1/2 as Producer from the pull-down menu of the Loop Speed control and observe the value of the Samples in Queue indicator. The data points
accumulate in the queue. You need to process the accumulated elements in the queue before reaching the maximum size of the queue to avoid data loss.
Select the remaining options available from the pull-down menu of the Loop Speed control and observe the synchronization of data transfer between the
3. Stop the VI.
t fo
producer loop and the consumer loop using queues.
When the Producer Loop and Queue Consumer Loop run at the same speed, the number of elements in the queue remains unchanged. When the Queue Consumer
Loop runs slower, the queue quickly backs up and the Producer Loop must wait for the Queue Consumer Loop to remove the elements. When the Queue
Consumer Loop runs faster, the queue quickly empties and the consumer loop must wait for the Producer loop to insert elements. Hence queues synchronize the
data transfer between the two independent parallel loops and thus avoid loss or duplication of data.
End of Exercise 1-1
No
4. Close the VI. Do not save changes.
Concept: Comparing Event Structure Design with Polling Design
on
Exercise 1-2
Goal
To convert a polling-based application to an event-based application
uti
Description
First you observe the behavior of a polling VI.
Next, you modify the polling VI to create a more efficient, event-driven VI and observe the changes in behavior.
rib
Finally, you add different types of events to the VI.
Table 1-1 lists the events you will implement in the UI Event Handler VI you create.
Table 1-1. User Interface Events
ist
Event
Event Description
Stops the While Loop.
Time Check: Value Change
Displays a time stamp when you click the Time Check button.
Pane: Mouse Down
Displays the coordinates of the front panel point you click.
Panel Close?
Handles the event in which the user tries to close the running VI by clicking the window close button.
Produces a beep when the mouse cursor moves over the Stop button.
Observing the Polling VI Behavior
t fo
Stop: Mouse Enter
1. Open and run Polling.vi.
rD
Stop: Value Change
Open the Events.lvproj file in the <Exercises>\LabVIEW Core 2\Events directory and open the Polling VI from the project.
No
2. Examine the performance of a polling VI using the Windows Task Manager.
Press the <Ctrl-Alt-Delete> keys and select Start Task Manager from the menu.
Click the Performance tab in the Windows Task Manager window.
1-11
Lesson 1
ni.com
on
Run the VI.

Notice how high the CPU usage is.
3. Open the block diagram, turn on execution highlighting, and run the VI again.
uti
Stop the VI and notice how the CPU usage drops.
4. Notice how often the Time Check terminal sends data to the Case structure and how often the While Loop iterates.
Modifying the Polling VI to Use Events Instead of Polling

1. Save the VI as UI Event Handler.vi so you can modify it.
2. Close Polling.vi.
ist
Select Open additional copy and add the copy to the project.
rib
5. Stop the VI and turn off execution highlighting.
3. Open the block diagram of Events.vi and move the Stop terminal and the Time Check terminal outside the While Loop. You move these terminals into the
appropriate event cases later in this exercise.
rD
4. Delete the Case structure and clean up any broken wires.
5. Place an Event structure inside the While Loop between the iteration terminal and the conditional terminal.
No
t fo
6. Right-click the Event structure and select Edit Events Handled by This Case from the shortcut menu.
1-12
on
7. Configure the event as shown in Figure 1-8.
t fo
rD
ist
rib
uti
Figure 1-8. Configuring the "Stop": Value Change Event
Click Stop in the Event Sources panel.
Click Value Change in the Events panel.
No
8. Click OK to close the dialog box.
1-13
Lesson 1
ni.com
1-14
on
9. Place a True constant inside the new "Stop": Value Change event and wire it to the conditional terminal of the While Loop as shown in Figure 1-9.
rib
uti
Figure 1-9. Event Structure with "Stop": Value Change Event
ist
NewVal event dataResize the event data items list so that only one item displays. Click the item and select NewVal.
rD
Observing the Behavior of the Event-Driven VI

1. Run the VI.
2. Notice that the Iteration indicator does not increment.
3. Switch to the block diagram and enable execution highlighting.
t fo
4. Notice that the While Loop is executing the first iteration. The Event structure is waiting for an event.
5. Disable execution highlighting and switch back to the front panel.
6. Click the Stop button to stop the VI.
No
7. Notice that the VI stops running even though the Stop button is disconnected.
8. Notice that the Stop button stays depressed even though the mechanical action is set to Latch When Released. The reason the button stays depressed is because
the VI stopped running after you clicked the button.
on
9. Reset the Stop button by clicking it again.

10. Drag the terminal of the Stop button into the "Stop": Value Change event as shown in Figure 1-10.
ist
rib
uti
Figure 1-10. "Stop": Value Change Event with Stop Button Terminal
No
t fo
12. Notice this time the VI stops and the button resets.
rD
11. Run the VI and click the Stop button again.
1-15
Lesson 1
ni.com
on
Programming the "Time Check": Value Change Event

1. Add a new event case and create a Time Check: Value Change event as shown in Figure 1-11.
Right-click the event structure and select Add Event Case.
uti
Figure 1-11. Event Structure with "Time Check": Value Change Event
ist
rib
In the Edit Events window, select Time Check in the Event Sources panel and Value Change in the Events panel.
Move the Time Check terminal from outside the While Loop into the "Time Check": Value Change event case.
Get Date/Time In SecondsCreates a time stamp in memory.
IndicatorDisplays the current time output of the Get Date/Time In Seconds function.
t fo
2. Run the VI.
rD
3. Click the Time Check button to see the current time display in the current time indicator.
5. Stop the VI.
No
4. Display the Task Manager window and notice that CPU usage has decreased when you use events instead of polling.
1-16
on
Adding More Notifier Events to the VI

1. Add a new event case and create a Mouse Down event as shown in Figure 1-12.
uti
Figure 1-12. Event Structure with "Pane": Mouse Down Event
ist
rib
In the Edit Events window, select PanesPane in the Event Sources panel and MouseMouse Down in the Events panel.
Coords event dataClick the event data node and select CoordsAll Elements.
Coords indicatorRight-click the output of the Coords event data item and select CreateIndicator from the shortcut menu.
2. Run the VI.

3. Click on different parts of the front panel.
rD
Notice that the Coords indicator displays the coordinates for each point you click.
No
4. Stop the VI.
t fo
Notice that the other events continue to behave as before.
1-17
Lesson 1
ni.com
on
Adding Filter Events to the VI

1. Add a new event case and create a Panel Close? event as shown in Figure 1-13.
uti
Figure 1-13. Event Structure with Panel Close? Event
rib
3
2
ist
After you add the event, in the Edit Events window, select <This VI> in the Event Sources panel and Panel Close? in the Events panel.
Event data nodeClick the Event Data Node and select Source from the menu.
Two Button Dialog function and Not functionWire the T button? output to the Not function and wire the Not function to the Discard? event filter node.
String constantWire Are you sure you want to close the window? to the message input.
Yes and No string constantsWire Yes to the T button name ("OK") input and wire No to the F button name ("Cancel") input.
rD
t fo
2. Save and run the VI.
3. Click the X at the top-right of the window of the front panel.
4. Notice that clicking the No button cancels the event and returns to the VI.
6. Stop the VI if necessary.
No
5. Clicking the Yes button stops and closes the VI.
1-18
on
Challenge
1. If you have a sound card, add an event that produces a sound when the cursor is over the Stop button.
Tip
Use Quick Drop to find the Beep.vi.
No
t fo
rD
ist
rib
uti
End of Exercise 1-2
1-19
No
t fo
on
uti
rib
ist
rD
on
uti
Exercises
Simple State Machine Template
Exercise 2-2
Concept: Producer/ConsumerEvents
Exercise 2-3
Concept: Producer/Consumer Error Handling
Exercise 2-4
Histogram
Exercise 2-5
User Access Level
No
t fo
rD
ist
rib
Exercise 2-1
| 2-1
No
t fo
on
uti
rib
ist
rD
Simple State Machine Template
on
Exercise 2-1
Goal
Use the Simple State Machine template in LabVIEW to create an application in which users control the acquisition and saving of waveform data.
uti
Scenario
You want to use an event-based state machine design to build a robust application that acquires and saves waveform data. You begin with the Simple State Machine
template, which provides a LabVIEW project file and all the supporting VIs and type definition controls you need to create an event-based state machine application.
Design
No
t fo
rD
ist
rib
The Simple State Machine project template provides documentation on how to modify the code to build a customized state machine application. Once you create a
project using the template, you customize the code for different events so that they generate, acquire, and save waveform data. You use the Generate Data VI, available
in the Shared folder, to generate sine waves for this application. Finally, you update the custom controls provided by the default template so that the controls handle
the data you generate.
2-3
Lesson 2
ni.com
on
Implementation
1. Click the Create Project button on the Getting Started window.
2. Select the Simple State Machine Template as shown in Figure 2-1.
No
t fo
rD
ist
rib
uti
Figure 2-1. Create Project Using Simple State Machine Template
2-4
on
3. Complete the configuration of the project as shown in Figure 2-2.
uti
Figure 2-2. Project Configuration in the Create Project Dialog Box
rib
ist
t fo
rD
Project NameEnter Acquire and Save as the name of your new project.
Project RootYou can use the default location on disk.
File Name PrefixThis prefix becomes part of the name of project library files and VIs this template creates. LabVIEW also updates icon banners with this prefix.
Edit OverlayClick this button to customize the icon further.
No
2-5
Lesson 2
ni.com
2-6
on
4. Click the Finish button to create and open the Acquire and Save project.
5. In the Project Explorer window, notice that the project contains documentation, type definitions, and a main VI called WMFMain.vi.
6. Add the Shared folder to the Acquire and Save project as shown in Figure 2-3.
uti
Figure 2-3. Adding the Shared Folder to the Project
rib
ist
Right-click My Computer and select AddFolder (Snapshot) from the shortcut menu.
Navigate to <Exercises>\LabVIEW Core 2\Shared and click the Current Folder button to add it to the project. Be sure the Shared folder is open when
you click the Current Folder button.
No
t fo
rD
7. Double-click WFMMain.vi in the Project Explorer window and review the template comments on the front panel.
on
8. Open the block diagram and notice the While Loop and Case structure typical of a state machine design pattern as shown Figure 2-4.
rib
uti
Figure 2-4. While Loop and Case Structure Typical of State Machine Design
ist
t fo
rD
Case structureContains a case for each state defined in the Initial State type definition.
Shift registersMaintain state information, error information, and data from one iteration of the While Loop to the next. These registers ensure that information
is accessible in each event and case.
Block diagram commentHelps guide you in updating the template.
No
2-7
Lesson 2
ni.com
2-8
on
9. Update the front panel as shown in Figure 2-5.

Figure 2-5. Updating the Front Panel
uti
rD
ist
rib
LabelsUpdate the button labels to Acquire Waveform and Log to File. The labels correspond to the terminals on the block diagram and are displayed there,
as well.
Boolean TextChange the Boolean text displayed on the buttons to Acquire and Save. The Boolean text is the text displayed on the button.
Waveform graphDelete comments before adding the Waveform Graph.
t fo
10. Open the block diagram and move the Waveform Graph terminal outside the While Loop. You will move it again later.
Double-click the Waveform Graph on the front panel to find the Waveform Graph terminal on the block diagram.
No
Tip
on
11. Edit the Initial State type definition, shown in Figure 2-6.
uti
Figure 2-6. Initial State Type Definition
Initial State type definitionRight-click the Initial State type definition and select Open Type Def.
States enumRight-click the States enum and select Edit Items.
No
t fo
rD
ist
rib
2-9
Lesson 2
ni.com
on
12. Edit the enum states as shown in Figure 2-7.
Click OK to close the dialog box.

Select FileApply Changes.
t fo
rD
ist
rib
uti
Figure 2-7. States Enum Properties Dialog Box
No
Save the WfmState.ctl file and close the control editor window.
2-10
on
13. Edit the Data type definition so that you can use it with the waveform data in the application.
a. Open and edit the Data type definition, as shown in Figure 2-8.
ist
rib
uti
Figure 2-8. Editing the Data Type Definition
Data type definitionRight-click the Data type definition and select Open Type Def.
Default template componentsThe template includes three data components by default: a Boolean, a string, and a numeric. Delete the default data components
from the cluster in the type definition.
Open the Generate Data VI, located in the Shared folder in the Project Explorer window, and copy the Y control.
Paste the Y control inside the Data type definition and rename the Y control to Array.
rD
Select FileApply changes to apply the updated type definition to the open VI.
No
Close the Generate Data VI.
t fo
Save and close the control editor window.
2-11
Lesson 2
ni.com
on
14. Complete the Acquire Waveform case as shown in Figure 2-9.
Delete the Bundle by Name function and the One Button Dialog function in this case before completing the block diagram shown in Figure 2-9.
rib
uti
Figure 2-9. Updating the Acquire Waveform Case
ist
t fo
rD
Bundle By NameWire the Data typedef to the input cluster of a Bundle By Name function.
Waveform graph terminalDrag the terminal from outside the While Loop into the Acquire Waveform case.
Generate Data VIOpen the Shared folder in the Project Explorer window and drag the Generate Data VI to the block diagram. Wire the Y output to the
Waveform Graph terminal.
Create constants for the signal and noise input terminals of the Generate Data VI.
Wire the Y output of the Generate Data VI to the Array input of the Bundle By Name function.
No
2-12
on
15. Complete the Log to File case as shown in Figure 2-10.
rib
uti
Figure 2-10. Updating the Log to File Case
1
3
rD
ist
Convert to Dynamic DataConfigure with the following options:
t fo
Input Data Type1D array of scalarssingle channel

Scalar Data TypeFloating point numbers (double)
Start TimeZero
Write to Measurement File Express VIConfigure with the following options:
No
ActionAsk user to choose file

ActionAsk each iteration
If a file already existsOverwrite file
After you configure the Write To Measurement File Express VI, right-click the Express VI and select View As Icon.
3
Wire the Convert to Dynamic Data function to the Signals input of the Write To Measurement File Express VI.
2-13
Lesson 2
ni.com
2-14
on
16. Open the Stop case as shown in Figure 2-11.
t fo
rD
ist
rib
uti
Figure 2-11. Updating the Stop Case
(Value Not Used) enumYou may want to update the label for readability. However, the application does not use the enum value because the Stop button stops
the loop before the next state executes.
18. Save the VI.
No
17. Click the broken Run button to find errors and clean up the code. Because you replaced the data elements in the Data type definition, the Boolean that the Bundle
By Name function uses in some cases is no longer valid. Delete these Bundle By Name functions and rewire the data to the shift register.
on
Test
1. Run the VI.
2. Click the Acquire button multiple times. The Waveform Graph updates with new data from each time.
uti
3. Click the Save button.

4. When you finish acquiring and saving data, click the Stop button.
5. Save and close the VI.
No
t fo
rD
ist
rib
End of Exercise 2-1
2-15
No
t fo
on
uti
rib
ist
rD
Concept: Producer/ConsumerEvents
Goal
As a group, explore the Producer Consumer template.
uti
Scenario
on
Exercise 2-2
You have a VI that uses the Producer/Consumer design pattern to process messages. The consumer rate is slower than the producer and therefore, a backlog is created.
The VI clears messages from the backlog in the order the messages are received, until a high priority message is introduced. High priority messages are processed as
soon as they are received and then the VI resumes processing normal priority messages.
rib
Implementation
1. Open the Producer Consumer project located in the <Exercises>\LabVIEW Core 2\Producer Consumer - Event directory, and then open the
Main.vi, shown in Figure 2-12 from the project.
2. Run the VI.
No
3. Click the Normal Priority button.
t fo
rD
ist
Figure 2-12. Producer Consumer - Events Main VI Front Panel
Notice the State to Execute indicator says Normal Priority.
2-17
Lesson 2
ni.com
2-18
on
Notice that Processed Value increased by 1.

Notice the High Priority? Boolean indicator is off.
4. Click the Normal Priority button several times.
uti
Notice that the Backlog indicator increases.

Notice that the Backlog decreases by 1 every second.
rib
5. Click the High Priority button.
Notice that State to Execute says High Priority and the Processed Value indicator says 1000.
Notice the High Priority? Boolean indicator is on.
ist
6. Watch the flow of data on the block diagram.
Select WindowTile Left and Right.
Click the Highlight Execution button on the block diagram and then run the VI and watch what happens when you click the Normal Priority button.
rD
Click the High Priority button.
Notice that the Wait (ms) in the Default state of the Consumer loop is set to 1000. This is what causes the processing of one message per second.
7. Disable Highlight Execution.
t fo
8. Click the Normal Priority button several times to create a backlog.

9. While the backlog is present click the Stop button.
Notice that the VI stops even though the backlog has not been processed.
No
The Enqueue Element at Opposite End function caused this to occur. If the Stop should occur after all messages in the backlog are processed, then this
function would be replaced with a regular Enqueue Element function.
Delete the error cluster wire running through the Default state of the Consumer loop.
Right-click the error output tunnel of the Case Structure and select CreateConstant.
uti
Run the VI again and click Normal Priority.
on
10. Inject an error and see what happens:
Notice that the VI does not behave properly anymore. This is because an error in the Consumer loop has caused the Consumer loop to shutdown. Because
the Consumer loop was doing the bulk of the work, the VI does not behave correctly. The Producer loop is still running.
rib
11. Close the VI and the project. Do not save your changes.
This VI does not include any error handling. You modify a version of this VI in Exercise 2-3 to enable error handling so the VI shuts down if an error occurs.
No
t fo
rD
ist
End of Exercise 2-2
2-19
No
t fo
on
uti
rib
ist
rD
Concept: Producer/Consumer Error Handling
Goal
Scenario
uti
Use buttons to inject errors into the Producer/Consumer template to test the error handling code.
on
Exercise 2-3
You need to test the error handling in the Producer/Consumer design pattern VI, so you will inject simulated errors as the VI runs.
Design
rib
Add buttons to inject simulated errors in the producer loop and the consumer loop.
Implementation
1. Open the Producer Consumer project located in the <Exercises>\LabVIEW Core 2\Producer Consumer - Error directory, and then open the
Main.vi from the project.
ist
This VI is similar to the one you used in Exercise 2-2. The Producer Error and Consumer Error buttons are provided on the front panel, as shown in Figure 2-13.
You modify the block diagram to enable the buttons and test error handling in this VI.
No
t fo
rD
Figure 2-13. Producer Consumer Main VI Front Panel with Error Buttons
2-21
Lesson 2
ni.com
on
2. Create a new event to inject an error into the Producer Loop as shown in Figure 2-14.
uti
Figure 2-14. Producer Consumer Producer Error: Value Change Event
rib
ist
Producer Error: Value Change EventRight-click the Event Structure and select Add Event Case.
Producer ErrorDrag the terminal into the new Event Case.
Error Ring ConstantWhen an error occurs, the VI stops running and the error message you select here is displayed in a dialog box.
rD
No
t fo
Refer to Figure 2-15 to configure the Error Ring Constant.
2-22
uti
Figure 2-15. Select Error
on
3. Click the Error Ring constant and configure it to display the message 15: LabVIEW: Resource not found as shown in Figure 2-15.
rib
t fo
rD
ist
Error Code RangeSelect LabVIEW from the drop-down list.
Error CodeSelect any error in the list and type 15 to find this error quickly.
No
2-23
Lesson 2
ni.com
on
4. Create the code for the Consumer Error button in the Consumer Loop as shown in Figure 2-16.
rib
uti
Figure 2-16. Producer Consumer Consumer Error Code
rD
ist
Custom Error CodeRefer to Figure 2-17 to create a custom error message.
Consumer ErrorDrag the terminal into the Default case of the Case Structure in the Consumer Loop.
No
t fo
2-24
on
5. Click the Error Ring constant and configure it to display a Custom Error Code as shown in Figure 2-17.
No
t fo
6. Save the VI.
rD
ist
rib
uti
Figure 2-17. Custom Error Code
2-25
Lesson 2
ni.com
on
Test
1. Run Main.vi.
2. Send several normal and high priority messages to create a backlog.
uti
3. Click the Producer Error button.

4. Run the VI again and send multiple messages.
5. Click the Consumer Error button.
No
t fo
rD
ist
rib
End of Exercise 2-3
2-26
Histogram
on
Exercise 2-4
Goal
Scenario
You want to create an application which does the following:

Simulates acquisition of a waveform.
Simulates processing of the waveform which includes generating a histogram.
Saves a snapshot of a histogram.
rib
uti
Modify the producer/consumer template to create a histogram from acquired data.
You can modify the producer/consumer template to handle those three tasks as well as errors and UI events from the producer/consumer template itself.
ist
Design
No
t fo
rD
After copying the template, you update the producer loop to generate waveform data and you update the consumer loop to display a histogram and take a snapshot
of the histogram when the user specifies.
2-27
Lesson 2
ni.com
on
Implementation
1. Move and rename the Producer Consumer project and files.
Open the Producer Consumer.lvproj located in the <Exercises>\LabVIEW Core 2\Producer Consumer - Template directory.
uti
Select FileSave As and set the save as options as shown in Figure 2-18, and then click the Continue button.
t fo
rD
ist
rib
Figure 2-18. Save As Options
Enter Histogram as the name of the project, and save the project to the <Exercises>\LabVIEW Core 2\Histogram directory.
2. Close the Producer Consumer - Template Project Explorer window.
No
3. Open Histogram.lvproj and rename the project VIs in LabVIEW so that LabVIEW can update all links and instances of the VIs.
Right-click Main.vi in the Project Explorer window and select Rename.

Rename the VI as Histogram Main.vi and click OK.
2-28
on
4. Add the Shared folder to the project as an auto-populating folder. The Shared folder contains the Generate Data VI and the Running Histogram VI that you use
later.
5. Open the block diagram of the Histogram Main VI.
uti
6. Update the Consumer Message type definition, shown in Figure 2-19 to handle waveform data.
Figure 2-19. Consumer Message Type Definition
Consumer Message type definitionRight-click the Consumer Message type definition located to the left of the producer loop on the Histogram Main VI block
diagram and select Open Type Def.
No
t fo
rD
ist
rib
2-29
Lesson 2
ni.com
2-30
on
Modify the Consumer Message type definition as shown in Figure 2-20.
uti
Figure 2-20. Consumer Message Type Definition
ist
rib
t fo
rD
ArrayAdd an array to the type definition so it can handle waveform data. Rename the Array Signal.
Numeric IndicatorAdd a numeric indicator to the array.
Right-click the cluster border and select Reorder Controls In Cluster and arrange them so that the Signal control is directly below the Numeric Data control.
No
7. Display the type definition as an icon on the block diagram as shown in Figure 2-21.
on
Apply changes, save, and close the type definition.
uti
Figure 2-21. Viewing a Type Definition as an Icon
ist
rib
Right-click the Consumer Message type definition and select AutoSizingArrange Vertically from the shortcut menu.
Right-click the Consumer Message type definition and select View Cluster as Icon to save space on the block diagram.
No
t fo
rD
2-31
Lesson 2
ni.com
2-32
on
8. Send signal data through the Consumer Message type definition. Complete the Timeout event in the producer loop as shown in Figure 2-22.
Figure 2-22. Updating the Producer Loop Timeout Event
uti
rib
3
5
rD
ist
Consumer Message type definitionCopy the Consumer Message type definition and paste it inside the Timeout event case.
Bundle By Name functionWire the Consumer Message typedef to the input cluster input.
t fo
Expand the node to display two elements.

Select Consumer State and Signal.
Generate Data VIDrag the Generate Data VI from the Shared folder in the Project Explorer window into the Timeout event case.
Wire the Y output of the Generate Data VI to the Signal input of the Bundle By Name function.
Create a control for the signal input of the Generate Data VI.
Create a constant for the Consumer State input.
Enqueue ElementRight-click the queue wire and select InsertQueue Operations PaletteEnqueue Element.
No
Wire the error wire through the Enqueue Element function to the Get Queue Status function. It will appear wired, but when you insert the node, the error wire
is behind the Enqueue Element function.
on
9. Create the Display case in the consumer loop as shown in Figure 2-23.
Figure 2-23. Updating the Consumer Loop Display Case
8
rD
ist
rib
uti
10
Open to the Default case of the Case structure and rename the case to Display, Default.
Unbundle By Name functionChange the Numeric Data element to Signal and remove the Boolean Data wire and element.
Running Histogram VIDrag the Running Histogram VI from the Shared folder in the Project Explorer window.
Numeric controlCreate a control for the bins input and label the control Bins.
XY Graph (Silver)On the front panel, place an XY Graph (Silver) and rename it Histogram.
Bundle functionWire the histogram and x axis outputs from the Running Histogram VI to the Bundle function.
Replace the right Histogram tunnel with a shift register and complete the shift register.
Wire the left shift register to the Case structure.
Right-click the Histogram output tunnel and select Linked Input tunnelCreate & Wire Unwired Cases and then click the Histogram input tunnel on the left.
No
t fo
10 Right-click the left shift register and create a constant.
2-33
Lesson 2
ni.com
2-34
on
10. Create a Snapshot event in the producer loop by changing the High Priority Message: Value Change event, as shown in Figure 2-24.
Figure 2-24. Updating the Producer Loop Snapshot: Value Change Event
1
rD
ist
rib
uti
Change the event nameChange the label of the High Priority button to Snapshot. Changing the name of the button changes the event name.
Bundle By Name functionDelete the values wired to the Boolean Data and Numeric Data inputs of the Bundle By Name function and hide the terminals.
Change the value of the Consumer State string constant to Snapshot.
Double-click the Snapshot control to locate the button on the front panel. Change the Boolean text displayed on the button to Snapshot.
No
t fo
on
11. Add the Snapshot case to the consumer loop as shown in Figure 2-25.
Figure 2-25. Updating the Consumer Loop Snapshot Event
4
rib
uti
rD
ist
Duplicate the Initialize caseRight-click the case structure and select Duplicate Case. Rename the duplicate case Snapshot.
Unbundle functionAfter you wire the input, the Unbundle function contains two 1D arrays.
Build Array functionWire both 1D Array outputs to the Build Array function.
Write to Spreadsheet File VIWire the appended array output of the Build Array function to the 2D data input.
t fo
No
12. Delete the Normal Priority Message event from the Event structure in the Producer Loop. LabVIEW deletes the corresponding button from the front panel.
2-35
Lesson 2
ni.com
2-36
on
13. Cleanup the front panel of the VI as shown in Figure 2-26.
Test
1. Run the VI.
rD
ist
rib
uti
Figure 2-26. Cleaning Up the Front Panel of the Histogram Main VI
t fo
2. To create the look of a histogram in the chart, click the plot legend and select a horizontal bar plot type from the bottom row. You may also want to remove the
line interpolation by clicking the plot legend and selecting Interpolation from the shortcut menu.
3. Notice how changing the Signal and Bins values changes the look of the histogram.
4. Click the Snapshot button. A file dialog box displays so you can save the histogram file.
No
Choose a name for the new file, including .txt.
While the dialog box is open, the Backlog indicator rises.
The Backlog indicator should quickly decrease.

5. Click the Stop button to stop the VI.
uti
6. Open the saved text file and review the contents to see the bins and values of the histogram.
on
Click the Save button to save the file.
7. Save and close the Histogram project.
No
t fo
rD
ist
rib
End of Exercise 2-4
2-37
No
t fo
on
uti
rib
ist
rD
User Access Level
on
Exercise 2-5
Goal
To create a gating application, using a functional global variables design pattern, which restricts user access to certain features based on different user access levels.
uti
Scenario
You need to create an application in which some features are not available to all users. You create a finite number of user access levels and assign an appropriate user
level to various users. You use a functional global variable design pattern to check for different access levels.
Design
rib
The following table describes the different actions you need to handle so you can implement user access control. In this exercise, you create a custom control to handle
these items.
Action
Description
Reads information about authorized users and their access levels from a specified file and stores this access information in
memory.
Set Current Access Level
Sets the access level of the current user in application memory.
Get Current Access Level
Retrieves the access level from memory so that the application can determine if a user has access to a certain feature.
No
t fo
rD
ist
Read User Access Level File
2-39
Lesson 2
ni.com
2-40
on
Implementation
1. Open the User Level FGV.lvproj project from <Exercises>\LabVIEW Core 2\FGVs.
uti
2. Open the User Level FGV folder in the Project Explorer window and then open User Access Level FGV.vi. The User Access Level FGV VI already contains
several items on the front panel, an icon, and connector pane.
3. Create a type-defined enum control and modify the front panel as shown in Figure 2-27.
t fo
Enum (Silver)Right-click the enum control and select Make Type Def, and then right-click and select Open Type Def.
No
rD
ist
rib
Figure 2-27. User Access Level FGV Front Panel
on
4. Add the three actions listed in the Design section of this exercise to the User Level Cmd type definition as shown in Figure 2-28.
rib
uti
Figure 2-28. Editing the User Access Level Cmd Enum
EnumRight-click and select Edit Items.
rD
ist
5. Save the enum as User Level Cmd.ctl in <Exercises>\LabVIEW Core 2\FGVs\User Level FGV and close the custom control editor window.
t fo
6. From the User Access Level FGV VI front panel, assign a terminal from the top-level of the User Access Level FGV VI connector pane to the User Level Cmd
control as shown in Figure 2-29.
Figure 2-29. Assign the User Level Cmd Control to a Connector Pane Terminal
No
Connector pane terminalClick this terminal, then click the User Level Cmd control to assign the control to the connector pane terminal.
Right-click the connector pane terminal and select This Connection IsRequired. By making this terminal required, an application must provide a value to
the User Level Cmd input when you use the User Access Level VI in another VI.
2-41
Lesson 2
ni.com
2-42
on
7. Create the framework for the functional global variable design by completing the block diagram as shown in Figure 2-30.
Figure 2-30. Creating the Functional Global Variable Design Framework
uti
rib
rD
ist
Case selectorWire the Error In cluster to the case selector of the outer case structure to set the error and no error cases.
Case selectorWire User Level Cmd to the case selector.
Case structureRight-click the Case structure and select Add Case for Every Value from the shortcut menu and then select Read User Access Level File,
Default.
Error In/Error OutWire Error In to Error Out through the default case.
Wire Error In/Error Out through all casesRight-click the output tunnel and select Linked Input TunnelCreate & Wire Unwired Cases. When the cursor
changes to a wiring tool, click on the left-side input tunnel. Small white triangles inside the input and output tunnels indicate the link.
t fo
No
Tip Use the Add Case for Every Value option when you know that each case diagram is significantly different. If cases contain similar subdiagrams, use
the Duplicate Case option instead. After you duplicate a case, you can modify and rename it.
on
8. Complete the Read User Access Level File case as shown in Figure 2-31.
Figure 2-31. Configuring the Read User Access Level File Case
4
rib
uti
ist
The path to User Access Levels.txt is relative to where you save the User Access Level FGV VI. In this case, the text file is in a parallel directory.
Read From Spreadsheet File VIClick the polymorphic selector and select String.
rD
Wire the all rows output through a tunnel on the Case Structure to the While Loop.
Shift registerRight-click the tunnel and select Replace with Shift Register. Click the left side of the While Loop to complete the shift register.
LabelRight-click the wire and select Visible ItemsLabel to show the label, then type the name User Names & Levels.
Link the output tunnel to the corresponding input tunnel and create and wire unwired cases of the tunnel.
No
t fo
2-43
Lesson 2
ni.com
on
9. Complete the Set Current Access Level case as shown in Figure 2-32.
Figure 2-32. Configuring the Set Current Access Level Case
rib
uti
ist
Index Array functionWire the User Names & Levels wire to an Index Array function.
User Levels Column and Names Column constantsCreate constants for the index (col) input of the Index Array function.
Shift registerChange the tunnel to shift register.
Right-click the output tunnel and select Link Input TunnelCreate & Wire All Unwired Cases.
No
t fo
rD
2-44
on
10. Leave the Get Current Access Level case as shown in Figure 2-33.
ist
rib
uti
Figure 2-33. Get Current Access Level Case
11. Wire the Error Case as shown in Figure 2-34.
No
t fo
rD
Figure 2-34. No Error Case
2-45
Lesson 2
ni.com
2-46
on
Test
uti
1. From the project, open User Access Levels.txt and review the contents of the file. This file contains the names of authorized users and their access levels.
You can add additional user names and levels if you want.
2. Double-click User Access Level FGV Unit Test.vi in the Project Explorer window to open the VI. This VI takes a user name you input, sets the permissions
of the VI to the user's access level, and tests whether the proper access level is set.
3. Complete the Set User Access Level: Value Change event as shown in Figure 2-35.
rib
Figure 2-35. Completing the Set User Access Level: Value Change Event
2
t fo
rD
ist
User Access Level FGV VIThis is the VI you modified in this exercise. It has already been placed on the block diagram.
User Level Cmd ConstantsRight-click the User Level Cmd input and select CreateConstant.
No
on
4. Complete the Access Secure Area: Value Change event case as shown in Figure 2-36.
rD
ist
rib
uti
Figure 2-36. Completing the Access Secure Area: Value Change Event
5. Run the VI with the following user names and verify the user level is correct by clicking the Test Access Level button.
Paul
George
Ringo
6. Save and close the project.
End of Exercise 2-5

User Level
Operator
Admin
Admin
Operator
No
John
t fo
User Name
2-47
No
t fo
on
uti
rib
ist
rD
on
uti
Exercise 3-2
Customizing the VI Window
Exercise 3-3
Using SubVIs
No
t fo
rD
ist
Display Temperature and Limits
rib
Exercises
Exercise 3-1
| 3-1
No
t fo
on
uti
rib
ist
rD
Display Temperature and Limits
on
Exercise 3-1
Goal
Use Property Nodes to change the properties of front panel objects programmatically.
uti
Scenario
Disable and enable the controls at the start and completion of execution.
Set the x value of the chart to the user-defined value.
Clear the waveform chart so it initially contains no data.
Challenge: Change the color of a plot if the data exceeds a certain value.
ist
Design
You build this VI in four stages, including a challenge.
Part 3Clear Chart
No
t fo
Part 4Challenge: Change the Plot Color
rD
Part 1Disable Controls

Part 2Enable Controls
rib
Complete a VI that records temperature to a waveform chart. During execution, the VI performs the following tasks:
3-3
Lesson 3
ni.com
on
Implementation
uti
Part 1Disable Controls

1. Open Temperature Limit.vi from the Temperature Limit project located in the <Exercises>\LabVIEW Core 2\Temp Limit - Ctl Props
directory.
rD
ist
rib
Figure 3-1. Temperature Limit Front Panel
2. Run the VI and then click the Start Acquisition button.
No
Click the Stop button.
t fo
Notice that while the VI runs, the controls are still enabled.You can change the values on the controls while the VI runs.
3-4
on
3. Modify the block diagram as shown in Figure 3-2 to disable the controls when the VI is running.
Figure 3-2. Temperature LimitDisable Controls Block Diagram
uti
rib
ist
rD
Delta t (ms) Property NodeRight-click the Delta t (ms) control and select CreateProperty NodeDisabled. Right click the property node and select
Change All to Write.
High Limit Property NodeIn the Timeout Event Case, right-click the High Limit control and select CreateProperty NodeDisabled.
t fo
Place the Property Node outside the While Loop, so you can move it into the Start: Value Change event case.
Right-click the property node and select Change All to Write.
Temperature Property NodeIn the Timeout Event Case, right-click the Temperature indicator and select CreateProperty NodeX Scale
Offset and MultiplierMultiplier.
No
Place the Property Node outside the While Loop, so you can move it into the Start: Value Change event case.
Right-click the property node and select Change All to Write.
Move the High Limit property node into the Start: Value Change event case.
4
To Double Precision FloatConverts the I32 input from the Delta t (ms) control to a double precision number.
Right-click the Delta t (ms) property node and select CreateConstant and set it to Disabled and Grayed Out.
3-5
Lesson 3
ni.com
on
Test
1. Run the VI and click the Start Acquisition button. The Delta t (ms) and High Limit controls are disabled and grayed out.
2. Stop the VI.
No
t fo
rD
ist
rib
uti
3. Run the VI a second time, click the Start Acquisition button and notice that the controls are still disabled.
3-6
on
Part 2Enable Controls

You want to disable the controls while the VI is running, however, you want to enable them again the next time you run the VI.
1. Modify the block diagram as shown in Figure 3-3 to enable the controls each time you run the VI.
uti
Figure 3-3. Temperature LimitEnable Controls Block Diagram
rib
rD
ist
Create copies of the Delta t (ms) and High Limit property nodes and drag them to the left of the While Loop.
Create a constant to enable the controls.
t fo
Test
1. Run the VI and notice that the controls are enabled again before you click the Start Acquisition button.
No
2. Set different values for the controls and click the Start Acquisition button. Notice that the data displayed on the chart starts from where it stopped the last time
you ran the VI.
3-7
Lesson 3
ni.com
3-8
on
Part 3Clear Chart

You want to clear the chart each time you run the VI.
1. Modify the block diagram as shown in Figure 3-4 to clear old data from the chart each time you run the VI.
ist
rib
uti
Figure 3-4. Temperature LimitClear Chart Block Diagram
rD
Temperature Property NodeCreate a copy of the Temperature Property node and drag it to the left of the While Loop.
Click the new property node and select History Data.
Right-click the History input and select CreateConstant. This creates a cluster with values of 0 to initialize the temperature chart to 0 when the VI starts running.
t fo
Test
1. Run the VI, click the Start Acquisition button and let the VI run for a few seconds, then click the Stop button.
2. Run the VI a second time. Notice that the chart clears before you click the Start Acquisition button and new data is written to it.
End of Exercise 3-1
No
Part 4Challenge: Change the Plot Color

Modify the VI so that the Data plot changes color when it exceeds the high limit.
Customizing the VI Window
on
Exercise 3-2
Goal
Affect the attributes of a VI by using Property Nodes and Invoke Nodes.
uti
Scenario
You can set the appearance properties of a VI statically by using the VI properties page. However, robust user interfaces often must modify the appearance of a front
panel while the program runs.
Hide the tool bar
Hide the menu bar
Hide the scroll bars
Move to the center of the screen
Write data to an Excel file
Design
rD
ist
rib
Modify the Temperature Limit VI to have the following appearance and behaviors when the VI is running:
Properties
Use the following properties and methods on the VI class:
ShowMenuBarWhen this property is false, the menu bar of the VI is not displayed.
t fo
Figure 3-5. VI Menu Bar
Tool Bar VisibleWhen this property is false, the tool bar of the VI is not displayed.
No
Figure 3-6. VI Tool Bar
3-9
Lesson 3
ni.com
3-10
CenterEach time this method is called, the VI moves to the center of the screen.
Tip
uti
on
Methods
Unlike properties, a method has an effect every time you call it. Therefore, you should call methods only when you want to perform an action. For example, if you
call the Fp.Center method during each iteration of a loop, the VI is continually centered, thereby preventing the user from moving it. You can use a Case structure to
control calling the method in a given iteration of a loop. Use the following method on the VI class:
Use the Context Help window to view descriptions of each property and method.
rib
After you implement the changes to the VI, when you run the Temperature Limit VI it should move to the center of the screen and look similar to Figure 3-7.
No
t fo
rD
ist
Figure 3-7. Temperature Limit VI Front Panel with Customized Appearance
on
Implementation
Part 1Set Appearance Properties
1. Open the Temperature Limit VI from the Temperature Limit project located in the <Exercises>\LabVIEW Core 2\Temp Limit - Methods directory.
No
t fo
rD
ist
rib
uti
2. Modify the block diagram as shown in Figure 3-8 to hide the scrollbars, menu bar, and tool bar, and center the front panel on the screen while the VI is running.
3-11
Lesson 3
ni.com
ist
rib
uti
on
Figure 3-8. Temperature Limit VIMethods Block Diagram
Property NodeRight-click the property node and select Link toPanePane.
Right-click and select Change All to Write.

Expand the node to display two properties and set them to Horizontal Scroll Bar Visibility and Vertical Scrollbar Visibility.
Off While Running constantRight-click one of the inputs to the Pane property node and select CreateConstant.
Property NodeRight-click the property node and choose Select ClassVI ServerVIVI.
Right-click and select Change All to Write.

Expand the node to display two properties.
Click the top property and select Front Panel WindowShow Menu Bar.
t fo
rD
Click the lower property and select Tool BarVisible.
When you wire a False constant to each of the properties, the menu bar and tool bar will be hidden when the VI runs.
Invoke NodeClick Method and select Front PanelCenter. You must wire the reference from the VI property node before setting this method.
3. Save the VI.
No
Note Notice that the scrollbar visibility properties apply to the Pane class, not the VI class. The front panel can be split into multiple panes using the
horizontal splitter bar or vertical splitter bar. Each pane can have its own scrollbars.
3-12
on
Test
1. Run the VI.
2. Verify that the scroll bars, tool bar, and menu bar are not displayed, and that the front panel window is centered on the screen while the VI runs.
No
t fo
rD
ist
rib
uti
3. Stop the VI.
3-13
Lesson 3
ni.com
on
Part 2Export Data

Add a method to export Temperature chart data to Excel.
1. Modify the block diagram as shown in Figure 3-9 to export the data displayed on the Temperature chart to Excel.
2. Save the VI.

Test
1. Run the VI.
rD
Temperature Invoke NodeRight-click the Temperature indicator and select CreateInvoke NodeExport Data to Excel.
t fo
ist
rib
uti
Figure 3-9. Temperature Limit VIExport to Excel Block Diagram
End of Exercise 3-2
No
2. Click Stop. The Export Data to Excel method creates a temporary Excel file with the data from the Waveform chart. View the data in the Excel file.
3-14
Using SubVIs
on
Exercise 3-3
Goal
Use control references to create subVIs that modify VI, graph, or chart properties.
uti
Scenario
Create subVIs for the Temperature Limit VI that allow you to handle some of the functionality that you enabled in Exercise 3-1 and Exercise 3-2.
Implementation
rib
1. Open the Temperature Limit VI from the Temperature Limit Project located in the <Exercises>\LabVIEW Core 2\Temp Limit - SubVIs directory.
hide scroll bars while running
set dialog properties
reenable the controls when you stop the VI
ist
2. The block diagram, as shown in Figure 3-10 includes code to:
No
t fo
rD
Figure 3-10. Temperature LimitSubVIs Start
3-15
Lesson 3
ni.com
3-16
on
In this exercise, you modify the block diagram to use subVIs and use control references. Figure 3-11 describes the subVIs you create and use to make the Temperature
Limit VI more modular and scalable.
Figure 3-11. Temperature Limit VIComplete Block Diagram
ist
rib
uti
Set Scroll Bar State SubVIHides the scroll bars when the VI runs.
Set Dialog Properties SubVIHides the tool bar and menu bar when the VI runs.
Set Enable State on Multiple Controls VISets all the controls in the input array to the Enable state value.
3. Create the Set Scroll Bar State subVI.
rD
t fo
On the Temperature Limit block diagram, highlight the code shown in Figure 3-12 and select EditCreate SubVI.
No
Figure 3-12. Set Scroll Bar State Code to Highlight
on
4. Open the subVI.
Double-click the subVI icon on the block diagram to open and modify the front panel of the subVI you just created as shown in Figure 3-13.
Figure 3-13. Set Scroll Bar State SubVI Front Panel
t fo
rD
ist
rib
uti
Pane Ref Out IndicatorCreate a copy of the Pane Ref In control. Right-click the copy and select Change to Indicator and change the label.
Assign the Pane Ref Out indicator to the top right terminal of the connector pane. Connections for the other controls and indicators should already be created.
No
3-17
Lesson 3
ni.com
3-18
on
5. Modify the block diagram of the Set Scroll Bar State subVI as shown in Figure 3-14.
rib
uti
Figure 3-14. Set Scroll Bar State SubVI Block Diagram
ist
6. Wire the reference and error wires through the Error case.
7. Create a meaningful icon for the subVI and save it as Set Scroll Bar State.vi in the <Exercises>\LabVIEW Core 2\Temp Limit - SubVI
directory.
rD
8. Create the Set Dialog Properties subVI.
9. On the Temperature Limit VI, highlight the code shown in Figure 3-15 and select EditCreate SubVI.
No
t fo
Figure 3-15. Set Dialog Properties Code to Highlight
on
10. Open the subVI you just created and modify the front panel as shown in Figure 3-16.
Figure 3-16. Set Dialog Properties SubVI Front Panel
t fo
rD
ist
rib
uti
VI Ref Out IndicatorCreate a copy of the VI Ref Control. Right-click the copy and select Change to Indicator and change the label.
Assign the VI Ref Out indicator to the top right terminal of the connector pane. Connections for the other controls and indicators should already be created.
No
3-19
Lesson 3
ni.com
3-20
rib
uti
on
Figure 3-17. Set Dialog Properties SubVI Block Diagram
Not functionInvert the logic for the Enable Dialog Properties button when wired to the property node to show the menu bar and tool bar
ist
11. Wire the reference and error wires through the Error case.
12. Create a meaningful icon for the subVI and save it as Set Dialog Properties.vi in the <Exercises>\LabVIEW Core 2\Temp Limit - SubVI
directory.
rD
13. Add the Set Enable State on Multiple Controls VI to the block diagram of the Temperature Limit VI.
The Set Enable State on Multiple Controls VI is provided for you in the Temperature Limit project.
No
Figure 3-18.
t fo
Drag two copies of the VI from the Project Explorer Window onto the Temperature Limit block diagram and complete the block diagram as shown in
rib
uti
on
Figure 3-18. Temperature Limit Block Diagram Complete
ist
VI Server ReferencesCreate references for the Delta t (ms) control, the High Limit control, and the Start button control.
Right-click each of the controls and select CreateReference.

The High Limit control is in the Timeout event case.
Build ArrayExpand the node to accept three inputs.
Set Enable State on Multiple Controls subVICreate a copy of the subVI and the Disabled State constant and place them in the Start: Value Change event
case.
Test
rD
t fo
1. Run the Temperature Limit VI and verify that it behaves as expected.

2. Save and close all open VIs and the Temperature Limit project.
No
End of Exercise 3-3
3-21
No
t fo
on
uti
rib
ist
rD

OnlineCore2 2012 Day1Exercises

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

OnlineCore2 2012 Day1Exercises

Uploaded by

Copyright:

Available Formats

on

Course Software Version 2012

19932012 National Instruments. All rights reserved.

End-User License Agreements and Third-Party Legal Notices

Worldwide Technical Support and Product Information

National Instruments Corporate Headquarters

Concept: Comparing Queues With Local Variables..................................................................................................1-3

Simple State Machine Template ................................................................................................................................2-3

Display Temperature and Limits ...............................................................................................................................3-3

LabVIEW Core 2 Exercises

Create Folder and File................................................................................................................................................4-3

Concept: Refactoring Inherited Code ........................................................................................................................5-1

Preparing Files for Distribution .................................................................................................................................6-3

LabVIEW Instrument Control

LabVIEW DAQ and Signal Conditioning

Modular Instruments Series

LabVIEW Core 2 Exercises

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

A description of the topics in the lesson

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

C. What You Need to Get Started

Computer running Windows 7/Vista/XP

LabVIEW Professional Development System 2012 or later

Contains VIs used in the course

Contains completed course exercises

D. Installing the Course Software

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

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

This course prepares you to do the following:

Apply common design patterns that use queues and events

Use event programming effectively

Programmatically control user interface objects

Evaluate file I/O formats and use them in applications

Modify existing code for improved usability

LabVIEW Core 2 Exercises

Prepare, build, debug, and deploy stand-alone applications

This course does not describe any of the following:

This icon denotes a tip, which alerts you to advisory information.

This icon denotes a note, which alerts you to important information.

Moving Beyond Dataflow

Concept: Comparing Queues With Local Variables

Concept: Comparing Event Structure Design with Polling Design

LabVIEW Core 2 Exercises

Concept: Comparing Queues With Local Variables

Queues data that the producer loop generates.

Dequeues data in the consumer loop.

Waits for the queue to empty before exiting the VI.

LabVIEW Core 2 Exercises

Moving Beyond Dataflow

Figure 1-1. Front Panel of the Queues vs Local Variables VI

4. Stop the VI.

Figure 1-2. Block Diagram of the Queues vs Local Variables VI

LabVIEW Core 2 Exercises

Moving Beyond Dataflow

Figure 1-3. Creating the Queue

Obtain QueueCreates the queue and defines the data type.

Queuing Data Generated by the Producer Loop

Figure 1-4. Queuing Data the Producer Loop Generates

Figure 1-5. Dequeuing Data inside the Consumer Loop

LabVIEW Core 2 Exercises

Moving Beyond Dataflow

Waiting for the Queue to Empty

Figure 1-6. Waiting for the Queue to Empty