Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Data Acquisition Using LabVIEW

You're reading from   Data Acquisition Using LabVIEW Transform physical phenomena into computer-acceptable data using a truly object-oriented language

Arrow left icon
Product type Paperback
Published in Dec 2016
Publisher Packt
ISBN-13 9781782172161
Length 150 pages
Edition 1st Edition
Arrow right icon
Authors (2):
Arrow left icon
Behzad Ehsani Behzad Ehsani
Author Profile Icon Behzad Ehsani
Behzad Ehsani
Yik Yang Yik Yang
Author Profile Icon Yik Yang
Yik Yang
Arrow right icon
View More author details
Toc

Table of Contents (12) Chapters Close

Preface 1. LabVIEW Basics FREE CHAPTER 2. Most Common Communication Buses 3. Using the DAQ Assistant to Automatically Generate LabVIEW Code 4. DAQ Programming Using LabVIEW 5. Debugging Techniques 6. Real-World DAQ Programming Techniques 7. Real-Time Issues 8. DAQ at a Distance - Network and Distributed Systems 9. Alternate Software for DAQ 10. Non-National Instrument Devices DAQ 11. LabVIEW and Simple Microcontrollers

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

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image