UNIT V ADVANCED LabVIEW AND APPLICATIONS Important two marks 1. What is the main objective of LabVIEW connectivity?

? The LbVIEW connectivity provides information on using Origin as an Automation Server from LabVIEW client. Origin supports communication with LabVIEW versions 5.0, 6.1, and 7.0. There are two aspects to the LabVIEW connectivity in Origin: 1. Building-block VIs 2. LabVIEW VI Browser Tool 2. Explain about Building-block VIs These building-block VIs are contained in the file Origin Automation Server.llb. When Origin is installed on a system in which LabVIEW was already installed, this file is placed under the \user.lib subfolder of the the LabVIEW installation folder. These VIs will then be visible from the Functions->User Libraries palette in LabVIEW. If Origin is installed before LabVIEW, this file should be copied from the \Samples\Automation Server\LabVIEW subfolder of the Origin installation to the \user.lib subfolder of the LabVIEW installation, in order for them to be accessible from the LabVIEW Functions palette. Note that there are three LabVIEW subfolders under the Origin Samples area, specific to LabVIEW versions 5.0, 6.1, and 7.0 3. Explain about LabVIEW VI Broswer Tool In addition to the collection of building-block VIs shipped with Origin, a LabVIEW VI Browser tool is also provided. This tool, which can be launched from the Tools menu, provides a way for the Origin user to browse their LabVIEW VIs, select a particular VI, and then run the VI from within the Origin environment. For instance, if you create a particularly LabVIEW VI that collects data and then sends the data to an Origin worksheet or matrix, you can browse to that VI and run the VI to place the data in Origin, and then perform further graphing and analysis on the data with Origin. This tool also allows you to transfer data contained in a VI to an Origin worksheet or matrix. 4. How to choose OAOpenCommunication.vi Right click inside the window, and from the Functions palette, choose User Libraries, and then paletteMenu. Then choose OAOpenCommunication.vi and place it in the window. The icon for this VI is

5. How to add the OAExecute VI Right-click again and add the OAExecute VI from the same palette, and place it next to the OAOpenCommunication VI. The OAExecute VI looks like:

6. Explain the origin of Building-block VIs Building-block VIs The Origin product is shipped with a collection of building-block VIs that can be included in your custom VIs to easily communicate with Origin. These building-block VIs all have names that start with OA, such as: OAOpenCommunication.VI open communication with Origin OACloseCommuniation.VI close communication OAExecute.VI send a LabTalk script command to Origin 7. What is OAOpenCommunication.vi Call to Automation Open LabVIEW function to open communication with Origin.ApplicationSI if no error on input. This SubVI (or its functionality) must be present in any project using the rest of the samples.

8. Draw the front panel for OAOpenCommunication.vi

9. Draw the block diagram for OAOpenCommunication.vi

10. Explain about OACloseCommunication.vi Call to Automation Close LabVIEW function if no error on input. Uses Origin.ApplicationSI.

11. Draw the front panel for OACloseCommunication.vi

12. Draw the block diagram for OACloseCommunication.vi

13. Define OABeginSession.vi Call to Origin Automation Server method BeginSession if no error on input. Uses Origin.ApplicationSI

14. Draw the front panel for OABeginSession.vi

15. Draw the Block diagram for OABeginSession.vi

16. Define Labwindows/CVI. LabWindows/CVI extends the functionality of LabVIEW Real-Time by allowing you to use ANSI C code on LabVIEW Real-Time (RT) targets. This document discusses the details and benefits of using LabWindows/CVI to incorporate ANSI C code in LabVIEW Real-Time applications. 17. What are the Benefits of Using LabWindows/CVI DLLs in LabVIEW Real-Time? LabWindows/CVI can compile code into a LabVIEW Real-Time-compatible DLL that the LabVIEW Real-Time environment can call and execute. This feature reduces development time for real-time applications in the following ways: You can reuse large amounts of existing ANSI C code, which greatly reduces development time for LabVIEW Real-Time applications. You can develop portions of your LabVIEW Real-Time applications in ANSI C. You can take advantage of the LabWindows/CVI development environment to create LabVIEW Real-Time VISA drivers for non-NI PXI/CompactPCI hardware. Therefore, you can incorporate third-party hardware into LabVIEW Real-Time applications. 18. Explain the Architecture of LabWindows/CVI DLLs Running on LabVIEW Real-Time. When you deploy LabWindows/CVI DLLs to LabVIEW Real-Time, you must carefully design the LabWindows/CVI DLL architecture to ensure determinism and reliability. You must avoid creating full-scale programs in LabWindows/CVI and then simply porting the entire application to LabVIEW Real-Time by way of a DLL. Instead, you should deploy DLLs that are modular stand-alone tasks to LabVIEW Real-Time. Deploying a C-based analysis library to LabVIEW Real-Time is an example of such a task. Implementations of instrument and thirdparty hardware drivers are also modular components that promote determinism and reliability on LabVIEW Real-Time. 19. Explain the LabWindows/CVI Functions Compatible with LabVIEW Real-Time. LabVIEW Real-Time hardware devices include an embedded real-time OS. As discussed in the Overview of LabVIEW Real-Time section above, the real-time OS is different from traditional OSs, such as Windows, and offers a slightly different set of functions. When you create a DLL in LabWindows/CVI, you can specify to include LabVIEW Real-Time compatibility. When you do so, LabWindows/CVI includes only the built-in LabWindows/CVI library functions that are compatible with the real-time OS.

20. What are the functions available in LabWindows/CVI libraries? Functions from the following native LabWindows/CVI libraries are compatible with the LabVIEW Real-Time Support Engine. Analysis or Advanced Analysis Library ANSI C Formatting and I/O TCP Support Library Utility Library 21. Explain Debugging LabWindows/CVI DLLs on LabVIEW Real-Time Targets. LabWindows/CVI 7.1 introduced remote debugging, which allows you to debug DLLs while they are running on real-time targets. The debugger, which is on the local computer, and the debuggee, which is on the target computer, communicate over a TCP/IP connection. Without this technology, DLLs specified for use on LabVIEW Real-Time targets would have to be debugged on the host machine. While you can detect and fix many errors using this method, there is no way to guarantee that the DLL would work when ported over to real-time targets because of the inherent differences between the Windows and real-time OSs. With remote debugging, you can use all of the debugging tools available on the host machine, such as the ability to set regular and conditional breakpoints, set the next statement, and view and change the value of variables, to ensure the DLL functions properly on LabVIEW Real-Time targets. 22. Explain about LabWindows/CVI Program Development. LabWindows/CVI is a software development environment for C programmers. LabWindows/CVI provides powerful function libraries and a comprehensive set of software tools for data acquisition, analysis, and presentation that you can use to interactively develop data acquisition and instrument control applications. You can edit, compile, link, and debug ANSI C programs in the LabWindows/CVI development environment. Additionally, you can use compiled C object modules, dynamic link libraries (DLLs), C libraries, and instrument drivers in conjunction with ANSI C source files when you develop programs. 23. What are the elements of LabWindows/CVI? Typical LabWindows/CVI applications include the following elements: User interface Data acquisition Data analysis Program control

24. Draw the block diagram of LabWindows/CVI

25. Why Use an Instrument Driver? To understand the benefits of IVI drivers, we need to start by defining instrument drivers in general and describing why they are useful. An instrument driver is a set of software routines that controls a programmable instrument. Each routine corresponds to a programmatic operation, such as configuring, writing to, reading from, and triggering the instrument. Instrument drivers simplify instrument control and reduce test program development time by eliminating the need to learn the programming protocol for each instrument. 26. List out the IVI class specifications. Class Digital multimeter (DMM) Oscilloscope Arbitrary waveform/function generator DC power supply Switch Power meter Spectrum analyzer RF signal generator IVI Driver IviDmm IviScope IviFgen IviDCPwr IviSwtch IviPwrMeter IviSpecAn IviRFSigGen

27. Explain state caching. IVI drivers keep track of an instruments status so that I/O is only performed when necessary, preventing redundant configuration commands from being sent. This can significantly improve test system performance. 28. Define Interchangeability. IVI drivers enable exchange of instruments with minimal code changes, reducing the time and effort needed to integrate measurement devices into new or existing systems. The IVI class specifications provide syntactic interchangeability but may not provide behavioral interchangeability. In other words, the program may run on two different instruments but the results may not be the same due to differences in the way the instrument itself functions. 29. How to Create a VI and Access the Driver Launch LabVIEW. From the File menu, select New VI. The Front Panel and Block Diagram appear. Right-click in the Block Diagram. The Functions palette appears. Select the Instrument I/O subpalette and then the Instrument Drivers subpallete. You can access all instrument driver VIs from this palette. Click Instrument Drivers. Select hp34401a from the palette. Select the hp34401a IVI driver from the palette. 30. What are the Biomedical applications in LabVIEW? Analog ECG Signal Generator NIBP Analyzer Measuring Blood Pressure File Format Converter Biosignal Logger HRV Analyzer ECG Feature Extractor

31. Draw the block diagram for LabVIEW application in process control

IMPORTANT UNIVERSITY QUESTIONS: 1. Explain about LabVIEW connectivity. 2. What are the Origins building-block VIs and explain it briefly? 3. Create a LabVIEW Real-Time DLLs in LabWindows/CVI. 4. Creating a Debuggable LabVIEW Real-Time DLL in LabWindows/CVI 5. How to Setting a Property in an IVI-C Driver? 6. Explain the various elements in LabWindows/CVI and draw the block diagram. 7. Explain the Editing and Debugging tools briefly. 8. Explain the application of LabVIEW in digital image processing. 9. Explain the application of LabVIEW in biomedical field. 10. Explain the application of LabVIEW in process control. 11. Explain the application of LabVIEW in physical process.

Reference Books
R1 VIRTUAL INSTRUMENTATION USING LabVIEW R2 P.C BASED INSTRUMENTATION - MATHIVANAN R3 DATA COMMUNICATIONS FOR INSTRUMENTATION AND CONTROL R4 DATA COMMUNICATIONS AND NETWORKING-A.FOROUZAN