1. Workshop 2 of 7 Welcome!

2. Today’s Topics -Review of: -LabVIEW Project -Mechanical Action of Booleans -Custom Controls and Type Definitions

3. Review Question 1 True or False? It is possible to add non-VI files to a LabVIEW Project.

4. Review Question 1 True or False? It is possible to add non-VI files to a LabVIEW Project. TRUE

5. 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.

6. 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

7. 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 (similar to how a button in Windows operates)? a)Switch Until Released b)Switch When Released c)Latch Until Released d)Latch When Released

8. 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 (similar to how a button in Windows operates)? a)Switch Until Released b)Switch When Released c)Latch Until Released d)Latch When Released

9. Questions?

10. 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

11. 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)

12. 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.

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

14. Demonstration: Creating and Saving a Type Definition

15. Questions?

16. Create custom controls and type definitions for the course project. Homework