Mindanao State University Iligan Institute of Technology

Department of Electrical, Electronics, and Computer

Engineering
A. Bonifacio Avenue, Tibanga, 9200 Iligan City, Philippines
www.msuiit.edu.ph +63.63.221.4056

Laboratory No.1

NAVIGATING LABVIEW
IN PARTIAL FULFILLMENT
OF THE COURSE REQUIREMENTS IN
EE 179.1

Submmitted by:
Mohammadnur P. Madayan

Submitted to:
Prof. Marven E. Jabian
I. INTRODUCTION

LabVIEW is a graphical programming environment you can use to quickly and efficiently create
applications with professional user interfaces. Millions of engineers and scientists use LabVIEW to
develop sophisticated measurement, test, and control system applications using intuitive icons and wires.
In addition, the LabVIEW platform is scalable across different targets and OSs. In fact, LabVIEW offers
unrivaled integration with thousands of hardware devices and provides hundreds of built-in libraries for
advanced analysis and data visualization for you to create virtual instruments you can customize to your
needs.

Because LabVIEW programs imitate the appearance and operation of physical instruments, such
as oscilloscopes and multimeters, LabVIEW programs are called virtual instruments or,more commonly,
VIs. VIs have front panels and block diagrams. The front panel is the user interface. The block diagram is
the programming behind the user interface. After you build the front panel, you add code using graphical
representations of functions to control the front panel objects. The code on the block diagram is graphical
code, also known as G code or block diagram code.

In contrast to text-based programming languages, like C++ and Visual Basic, LabVIEW uses
icons instead of lines of text to create applications. In text-based programming, instructions determine the
order of program execution. LabVIEW uses graphical dataflow programming. In graphical dataflow
programming, the flow of data through the nodes on the block diagram determines the execution order.
Graphical programming and dataflow execution are the two major ways LabVIEW is different from most
other general-purpose programming languages.

II. EQUIPMENTS

1. Personal Computer

2. LabView Software
III. EXERCISE 1-1 Concept: Exploring a VI

A. GOAL
1. To identify the parts of an existing VI.
B. OBSERVATION/DISCUSSION/RESULT

LabVIEW has two important user windows namely the front panel window (fig 1.1) and the
block diagram window (fig 1.2).

Figure 1.1

Based on figure 1.1 above, there are 5 indicators, 1 control, 1 run button, 1 connector pane, 1 icon
pane, and 1 free label in the front panel window.

Figure 1.2

Based on figure 1.2 above, there is 1 control, 5 indicators, 5 constants, and 2 freelabels.

In navigating an existing VI, a user can also use the context help to learn more about the items on
the block diagram window. I have also verified that in the testing of seconds breakdown VI, the
simulation works properly.
 C. CONCLUSION

After doing this exercise, I have learned some important parts/items of an existing VI and I have
learned also that Labview has two important user windows the front panel window and the block
diagram window.

IV. EXERCISE 1-2 Concept: Locating Controls, Functions, and Vis

A. GOAL
1. To learn to use the palettes and search for controls, functions, and VIs.
B. OBSERVATION/DISCUSSION/RESULT

In this exercise, it is good for me to discover that palettes of Labview are customizable I can
view it in the way I want. In this exercise, I discovered that I can just use palettes to locate easily the
functions and controls I need in my front panel window. I can also just use palettes to locate easily the
functions and controls I need in my block diagram window. Besides palletes, there are another features of
Labview that a user can use to make his/her work easily and those are the quick and drop feature and the
global search feature.

C. CONCLUSION

After doing this exercise, I have fulfilled my objective which is to learn to use the palettes and
search for controls, functions, and VIs. In addition to that, I have also discovered that there are amazing
features of Labview that I can use to make my work easily and customized.

V. EXERCISE 1-3 Concept: Using Tool Selection

A. GOAL

1. To become familiar with automatic tool selection and the Tools palette in LabVIEW.

B. OBSERVATION/DISCUSSION/RESULT

By using tools from the tool palette of Labview, the user still will have an access to modification
actions he/she can do like modifying the size of the waveform chart, renaming the numeric control,
changing the value of the numeric control and others. These modification actions are possible through
using the tools features of LabVIEW. A modification of these kinds is shown in the fig 1.3 below.
 Figure 1.3

C.CONCLUSION

After doing this exercise, I have become familiar with the automatic tool selection and the Tools
palette in LabVIEW. And more importantly, I have learned that through using these features of LabVIEW,
I can do stuffs like changing the size of a table or chart; renaming a table or chart, repositioning items in
the front panel and block diagram window; changing the color of certain items; and the likes.

VI. EXERCISE 1-4 Concept: Dataflow

A. GOAL
1. To understand how dataflow determines the execution order in a VI.
B. OBSERVATION/DISCUSSION/RESULT

Fig 1.4

By using fig 1.4 and answering the following questions below, the user will be able to find out
how data flow determines execution order.

1. Which node executes first? Is there any dependency between the File Dialog function and the
Simulate Signal Express VI?
The node that will execute first will be the file dialog box or the simulate signal express. From the
figure 1.4, it can be find out that there is no dependency between these nodes.
2. Which node executes last?
The last node to execute is the Simple Error Handler VI
 3. Because a green wire connects the File Dialog function to the TDMS File Viewer VI, can the
TDMS File Viewer VI execute before the TDMS Close function?

No. The TDMS File Viewer VI cannot execute before the TDMS Close function because the
yellow error wire connecting the TDMS Close function and the
TDMS File Viewer VI forces data dependency. Remember, the data to all inputs of a node must
be available before a node can execute. Therefore, the TDMS File Viewer VI must receive data
from both the green Boolean wire and the yellow error wire before the VI can execute

4. How many nodes must execute before the TDMS Write function can execute?

Three nodes must execute before the TDMS Write function can execute: File Dialog, TDMS
Open, and Simulate Signal.

5. Should a well-designed block diagram flow in a particular direction?

Yes. A well-designed block diagram typically flows from left to right.

Figure 1.5

6. By using figure 1.5, which express VI executes last ?

Either the Statistics Express VI or the Write to Measurement File Express VI executes last or they
execute in parallel.
 Figure 1.6

7. Using figure 1.6, which express VI executes last ?

The Write to Measurement File Express VI executes last.

Figure 1.7

8. In figure 1.7, which Tone Measurements Express VI executes last?

Either one of the Tone Measurement Express VIs can execute last.

C. CONCLUSION

After doing this exercise, I have learned how dataflow determines the execution order in a VI. A
block diagram node executes when it receives all required inputs. In a node execution, an output data is
produced and that data is passed to the next node in the data flow path. The movement of data through the
nodes determines the execution order of the VIs and functions on the block diagram.
VII. EXERCISE 1-5 Simple AAP VI

A. GOAL
1. To create a simple VI that acquires, analyzes, and presents data.
B. OBSERVATION/DISCUSSION/RESULT

The input for the VI that we will design in this exercise is an analog channel of sine wave data.
The outputs include a graph of the sine data, a file that logs the data, and an indicator that displays the
average data value. In this exercise, it is a plus to note and remember the following reminders for the
program architecture of the VI that we will design.

Use the DAQ Assistant to acquire the sine wave from the data acquisition device.
Use the Statistics Express VI to determine the average value of the sine wave. Because this
signal is cyclical, you could also use the Cycle Average option in the Amplitude and Level
Measurements Express VI to determine the average value of the sine wave.
Use the Write to Measurement File Express VI to log the data and use the Waveform Graph
to display the data on the front panel window.

Figure 1.8. Data flow of the VI that we will design

 Figure 1.9. Expected front panel as described in steps 5-6 of exercise 1-5.

Figure 1.10. Expected block diagram as described in steps 7-14 of exercise 1-5.

Figure 1.11

As we can see in figure 1.11, the expected result that is described in the testing step of exercise 1-
5 is satisfied.
 C. CONCLUSION

After doing this exercise, I have learned how to design and create a simple VI that is capable of
acquiring, analyzing, and displaying/presenting data.

VIII. REFERENCES

1. LabVIEWTM Core 1 Course Manual, 2012 Edition, National Instruments, 2012.

2. LabVIEWTM Core 1 Exercises Manual, 2012 Edition, National Instruments, 2012.