You are on page 1of 14

Welcome!

Workshop
2 of 7
Today’s Topics
- Review of:
- LabVIEW Project
- Mechanical Action of Booleans

- Custom Controls and Type Definitions


Review Question 1
True or False?

It is possible to add non-VI files to a LabVIEW


Project.
Review Question 1
True or False?

It is possible to add non-VI files to a LabVIEW


Project.

TRUE
Review Question 2
True or False?

If I am using a virtual folder in the LabVIEW


Project, I must keep all of the related files
together on disk.
Review Question 2
True or False?

If I am using a virtual folder in the LabVIEW


Project, I must keep all of the related files
together on disk.

FALSE
Review Question 3
Which mechanical action causes a Boolean in the False
state to change to True when you click it and stay True
until you release it and LabVIEW has read the value?
a) Switch Until Released
b) Switch When Released
c) Latch Until Released
d) Latch When Released
Review Question 3
Which mechanical action causes a Boolean in the False
state to change to True when you click it and stay True
until you release it and LabVIEW has read the value?
a) Switch Until Released
b) Switch When Released
c) Latch Until Released
d) Latch When Released
Customizing Controls
LabVIEW ships with multiple palettes of controls
available to you. However, you may want to
customize them or create your own

Standard LabVIEW Gauge Customized LabVIEW Gauge


Creating Custom Controls
How to create:
- Right click on the control; select Advanced >> Customize
- The Control Edit window will appear.

Edit Mode

Customize Mode
(low-level changes)
Saving Custom Controls

Three options:
- Custom Control
- Type Definition
- Strict Type Definition

All 3 options create a *.ctl file.

Once you save the custom


control it takes on the name of
the option you chose.
Custom Controls & Type Definitions
Control Type Def Strict Type Def
• No connection • Connection between the• Connection between saved
between the one you saved file and all file and all instances
saved and the instances
instance in the VI
• Forces the data type of • Forces everything about an
• Update the file, but each instance to be instance to be identical to
the instances are not identical (clusters, enum) the strict type definition,
updated except:
• Changes made to file will • label
populate throughout • description
each instance • default value

*.ctl *.ctl *.ctl


Demonstration:
Creating and Saving a Type Definition
Homework
• Create custom controls and type definitions for
the course project.

You might also like