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

Error conditions


The most common and most obvious error condition is when an attempt is made to wire (connect) two incompatible objects (different types) or functions together. In this condition a broken wire appears. A VI with even one broken wire will not run. Most functions have an error input and output that are very helpful. Error wires are a cluster and carry more than one form of information. Note the expanded Front Panel window showing the three components (Status, Code, and Source) that are encompassed in an error cluster notice. In the following figure (left) a hypothetical VI that does nothing; therefore, there is no error, so the status is a green checkmark (this is a Boolean value) and can be used as such.

A useful and common use for this Boolean value is to use the false state (where there is no error) to continue running with the rest of the program where you suspect the possibility of a frequent error condition that may exist. In our example, note that we start by opening...