LabVIEW Basics II

1. LabVIEW Basics II

2. LabVIEW Basics II Course Manual What You Need To Get Started LabVIEW Basics II CD • Data acquisition board and cable • DAQ Signal Accessory Computer running LabVIEW 8 and Windows 2000/XP

3. File Locations Root Directory Exercises <or> Solutions LabVIEW Basics II

4. Instructional Methods • Lecture gives a foundation in the topic • Instructor reinforces foundation through demonstrations and quizzes

5. Instructional Methods • Concept exercises allow you to further explore a topic • Examples: • Watch a simulation • Experiment with example VIs • Search the documentation

6. Instructional Methods • Development exercises give you hands-on experience in a topic • Demonstration of a finished development exercise further reinforces the learning process

7. Getting The Most Out Of This Course • Experiment with hands-on exercises to understand the methods used • Implementations given are only one possible solution—you may find a better one • Do not come to class prepared to develop an outside application; concentrate on the exercises given to build a good foundation

8. Courses New User LabVIEW Basics I LabVIEW Basics II Experienced User LabVIEW Intermediate I LabVIEW Intermediate II Advanced User LabVIEW Advanced I • Skills learned: • LabVIEW environment navigation • Basics application creation using LabVIEW • Basics of data acquisition and instrument control • Skills learned: • Modular application development • Structured design and development practices • Inter-application communication and connectivity techniques • Skills learned: • Large application design • Advanced development techniques • Implementing multideveloper projects • Certifications • Certified LV Associate Developer Exam • Skills tested: • LabVIEW environment knowledge • Certified LabVIEW Developer Exam • Skills tested: • LabVIEW application development expertise • Certified LabVIEW Architect Exam • Skills tested: • LabVIEW application development mastery

9. Course Learning Map LabVIEW Basics II Common Design Techniques Controlling the User Interface Communicating Among Multiple Loops Advanced File I/O Improving an Existing VI Creating and Distributing an Executable

10. Lesson 1Common Design Techniques • Single Loop Architectures • Parallelism • Multiple Loop Architectures • Timing a Design Pattern

11. A. Single Loop Architectures • Simple • Single VI that takes a measurement, performs calculations, and either displays the results or records them to disk • Usually does not require a specific start or stop action from the user

12. A. Single Loop Architectures • General VI • Three phases: Start-up, Main Application, and Shut-down

13. A. Single Loop Architectures • General VI

14. A. Single Loop Architectures • State Machine • Usually has a start-up and shut-down state, but also contains other states

15. A. Single Loop Architectures • State Machine

16. B. Parallelism • Execute multiple tasks at the same time

17. B. Parallelism • Passing data among parallel loops is a challenge • How do the loops stop in this example?

18. B. Parallelism • How do the loops stop in this example?

19. B. Parallelism • Read the Stop button from a file • Each loop independently accesses the file • However, reading and writing to files can consume much processor time

20. C. Multiple Loop Architectures • Parallel Loop

21. C. Multiple Loop Architectures • Producer/Consumer

22. D. Timing a Design Pattern - Execution Execution Timing • Provides the design pattern with a function that specifically allows the processor time to complete other tasks • In some cases, a function is not necessary

23. D. Timing a Design Pattern – Execution

24. D. Timing a Design Pattern – Software Control Software Control Timing • Consider implementing a state machine design pattern for a data acquisition system • If you must acquire data for 5 minutes, you could remain in the acquisition state until the 5 minutes elapses • However, during that time you cannot process any user interface actions such as stopping the VI • To process user interface actions, you must implement timing so that the VI continually executes for the specified time

25. D. Timing a Design Pattern Execution Timing Software Control Timing

26. Summary—Quiz Are the following statements True or False? • Software control timing allows the processor time to complete other tasks. • Execution timing allows the processor time to complete other tasks. • You can use a wire to pass data among parallel loops.