Book Image

Data Acquisition using LabVIEW

By : Behzad Ehsani
Book Image

Data Acquisition using LabVIEW

By: Behzad Ehsani

Overview of this book

NI LabVIEW's intuitive graphical interface eliminates the steep learning curve associated with text-based languages such as C or C++. LabVIEW is a proven and powerful integrated development environment to interact with measurement and control hardware, analyze data, publish results, and distribute systems. This hands-on tutorial guide helps you harness the power of LabVIEW for data acquisition. This book begins with a quick introduction to LabVIEW, running through the fundamentals of communication and data collection. Then get to grips with the auto-code generation feature of LabVIEW using its GUI interface. You will learn how to use NI-DAQmax Data acquisition VIs, showing how LabVIEW can be used to appropriate a true physical phenomenon (such as temperature, light, and so on) and convert it to an appropriate data type that can be manipulated and analyzed with a computer. You will also learn how to create Distribution Kit for LabVIEW, acquainting yourself with various debugging techniques offered by LabVIEW to help you in situations where bugs are not letting you run your programs as intended. By the end of the book, you will have a clear idea how to build your own data acquisition system independently and much more.
Table of Contents (18 chapters)
Data Acquisition Using LabVIEW
Credits
About the Author
Acknowledgments
About the Reviewer
www.PacktPub.com
Preface
9
Alternate Software for DAQ

Chapter 6. Real-World DAQ Programming Techniques

We are almost halfway through the book and we have mostly talked about real-world phenomena and how we are able to use a series of VIs to quantify and represent a given real-life phenomenon (such as temperature, voltage/current movement, and so on) and classify and quantify them with numbers or values understandable to a computer. In doing so, we have been concentrated on getting one action done, but have ignored the real thinking processes and methods required just prior to running that certain VI and all work that must be done after running our main VI, when the objective of a program is a complete working system.

In other words, what we have done so far here is prove the concept. While in real-life conditions, a system (consisting of both software and hardware must stand on its own merits and results), and inputs and outputs of it must be repeatable, documentable, and generally understandable by a peer or a colleague. Even what we are working...