Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

NIS LabView

2,051 views

Published on

An award winning software for engineers & data acquistition, signal processing ...

Published in: Technology, Business
  • Be the first to comment

NIS LabView

  1. 1. NISARG MARATHA KASHYAP SHAH
  2. 2. LabVIEWPart 1: IntroductionPart 2: The LabVIEW EnvironmentPart 3: Audio-Visual DemoPart 4: Applications, Advantages and Future of LabVIEW
  3. 3. Part 1
  4. 4. PART 1 : IntroductionLabVIEW – Laboratory Virtual Instrument EngineeringWorkbench It is a platform and development environment for a visual programming language from National Instruments. The purpose of such programming is automating the usage of processing and measuring equipment in any laboratory setup. LabVIEW is commonly used for data acquisition, instrument control, and industrial automation on a variety of platforms including Microsoft Windows, various versions of UNIX, Linux, and Mac OS X. The latest version of LabVIEW is version LabVIEW 2011, released in August 2011.
  5. 5. Features of LabVIEW 7.1 Design  Signal and Image Processing  Embedded System Programming  (PC, DSP, FPGA, Microcontroller)  Simulation and Prototyping  And more… Control  Automatic Controls and Dynamic Systems  Mechatronics and Robotics  And more… Measurements  Circuits and Electronics  Measurements and Instrumentation  And more…
  6. 6. What is Data Acquisition and it’s use ? Traditional Experiments – signals from sensors are sent to analog or digital meters, read by the experimenter, and recorded by hand. In automated data acquisition systems the sensors transmit a voltage or current signal directly to a computer via a data acquisition board. Software such as LabVIEW controls the acquisition and processing of such data. The benefits of automated systems are many:  Improved accuracy of recording.  Increased frequency with which measurements can be taken.
  7. 7. Graphical programming language & Data flow LabVIEW relies on graphical symbols rather than textual language to describe programming actions. The principle of dataflow, in which functions execute only after receiving the necessary data, governs execution in a straightforward manner.
  8. 8. How does LabVIEW work?• LabVIEW programs are called: Virtual Instruments (VIs) because their appearence and operation imitate actual instruments.• However, they are analogous to main programs, functions and subroutines from popular language like C, Fortran, Pascal, …
  9. 9. What does a VI look like?
  10. 10.  In LabVIEW you can create or use “virtual instruments” (VI) for data acquisition. A VI allows your computer screen to act as an actual laboratory instrument with characteristics tailored to your particular needs. You can also use built-in examples, or use standard templates for setting up your data acquisition input channels.
  11. 11. Part 2: The LabVIEW EnvironmentA VI has three main parts: • The front panel: an interactive user interface of a VI, so named because it can simulates the front panel of a physical instrument. • The block (or wiring) diagram: • It is the VI’s source code, constructed in LabVIEW’s • graphical programming language, G. It is the actual • executable program. • Subroutine in the block diagram of VI. • Icon/connector
  12. 12. Front PanelEvery user created VI has a front panel that contains the graphicalinterface with which a user interacts. The front panel can house variousgraphical objects ranging from simple buttons to complex graphs. Variousoptions are available for changing the look and feel of the objects on thefront panel to match the needs of any application.Block diagramNearly every VI has a block diagram containing some kind of program logicthat serves to modify data as it flows from sources to sinks. The blockdiagram houses a pipeline structure of sources, sinks, VIs, and structureswired together in order to define this program logic. Most importantly,every data source and sink from the front panel has its analog source andsink on the block diagram. This representation allows the input valuesfrom the user to be accessed from the block diagram. Likewise, newoutput values can be shown on the front panel by code executed in theblock diagram.
  13. 13. Controls• The most common form of a data source in LabVIEW is a control. This element appears as some type of graphical element on the front panel of a VI that can receive input from a user or even another VI. As stated previously, any data source also has an analog symbol that appears on the block diagram so that its value can be read and used in the code pipeline. Controls make no exception to this rule.• Every control has an associated data type that determines what kind of data flows from it on the block diagram.Palettes• Front panel controls and indicators as well as block diagram VIs are available from a palettes visible depending on what window is currently active in the LabVIEW environment. These palettes have their contents separated into sub- categories containing controls, indicators, and VIs.
  14. 14. Figure 4: Typical top-level block diagram and front panel palettes. Typical top-level block diagram and front panel palettes.
  15. 15. Front Panels Simply put, the front panel is the window through which the user interacts with the program. • When you run a VI, you must have the front panel open so that you can input data to the executing program. • The front panel is where you see your program’s output. The front panel is primarily a combination of controls and indicators.
  16. 16. Control? or Indicator?Controls = Inputs from the user = Source Terminals Indicators = Outputs to the user = Destinations
  17. 17. Block Diagrams The block diagram window holds the graphical source code of a LabVIEW VI – it is the actual executable code • You construct the block diagram by wiring together objects that perform specific functions. • The various components of a block diagram are terminals, nodes and wires.
  18. 18. TerminalsWhen you place a control(or indicator) on theFRONT PANEL LabVIEW automatically creates a corresponding control (or indicator) terminal on the BLOCK DIAGRAM
  19. 19. Control or Indicator Terminal? Control terminals have thick borders Indicator terminals have thin borders
  20. 20. Deleting Block Diagram Terminals• By default, you cannot delete a block diagram terminal that belongs to a control (or indicator).• The terminal disappears only when you delete its corresponding control (or indicator) on the FRONT PANEL.
  21. 21. WiresA LabVIEW VI is held together by wires connecting nodesand terminals; they deliver data from one source terminal toone or more destination terminals.
  22. 22. Basic wires used in block diagrams and corresponding typesEach wire has different style or color, depending on the datatype that flows through the wire: Scalar 1D array 2D array Color Floating-point orange number Integer number blue Boolean green String pink
  23. 23. 6hrs
  24. 24. VI Front PanelFront Panel IconToolbarBooleanControl Graph LegendWaveformGraphPlot ScaleLegend Legend
  25. 25. VI Block DiagramBlockDiagramToolbar Divide FunctionSubVI Graph Terminal Wire DataWhile Loop Numeric Timing Boolean ControlStructure Constant Function Terminal
  26. 26. Controls and Functions Palettes Controls Palette (Front Panel Window) Functions Palette (Block Diagram Window)
  27. 27. Tools Palette • Floating Palette • Used to operate and modify front panel and block diagram objects. Automatic Selection ToolOperating Tool Scrolling ToolPositioning/Resizing Tool Breakpoint ToolLabeling Tool Probe ToolWiring Tool Color Copy ToolShortcut Menu Tool Coloring Tool
  28. 28. Status ToolbarRun ButtonContinuous Run Button Additional Buttons on the Diagram ToolbarAbort ExecutionPause/Continue Button Execution Highlighting ButtonText Settings Step Into ButtonAlign Objects Step Over ButtonDistribute Objects Step Out ButtonReorderResize front panelobjects
  29. 29. The Run Button • The Run button, which looks like an arrow, starts VI execution when you click on it • It changes appearance when a VI is actually running. • When a VI won’t compile, the run button is broken
  30. 30. Open and Run a Virtual Instrument Example finder
  31. 31. Creating a VIFront Panel Window Block Diagram Window Control Indicator Terminals Terminals
  32. 32. Help Options Context Help • Online help • Lock help • Simple/Complex Diagram help • Ctrl + H Online reference • All menus online • Pop up on functions in diagram to access online info directly
  33. 33. Debugging Techniques • Finding Errors Click on broken Run button • Execution Highlighting showing error appears Window Click on Execution Highlighting button; data • Probe flow is animated using bubbles. Values are displayed on wires. Right-click on wire to display probe and it shows data as it flows through wire segment You can also select Probe tool from Tools palette and click on wire
  34. 34. Part 3• Shortcuts• Ctrl + T //tile windows• <Ctrl-H> – Activate/Deactivate Context Help Window• <Ctrl-B> – Remove Broken Wires From Block Diagram• <Ctrl-E> – Toggle Between Front Panel and Block Diagram• <Ctrl-Z> – Undo (Also in Edit Menu)•
  35. 35. – Simple program (simple addition, multiplication etc…)– Loops (from video)– Charts graphs (from video)– Case structures (from video)– Tools palette (from video)– Hardware implementation (from video)– Data types, highlight execution, data acquisition, arrays, debugging tools etc…
  36. 36. Hardware implementation
  37. 37. Data Types
  38. 38. arrays
  39. 39. Data acquisition
  40. 40. Part 3 - B
  41. 41. Section II – SubVIs• What is a subVI?• Making an icon and connector for a subVI• Using a VI as a subVI
  42. 42. Block Diagram Nodes Icon Expandable Node Expanded Node• Function Generator VI• Same VI, viewed three different ways• Yellow field designates a standard VI• Blue field designates an Express VI
  43. 43. SubVIs• A SubVI is a VI that can be used within another VI• Similar to a subroutine• Advantages – Modular – Easier to debug – Don’t have to recreate code – Require less memory
  44. 44. Icon and Connector • An icon represents a VI in other Icon block diagrams Terminals • A connector shows available terminals for data transfer Connector
  45. 45. SubVIs Sub VIs
  46. 46. Steps to Create a SubVI• Create the Icon• Create the Connector• Assign Terminals• Save the VI• Insert the VI into a Top Level VI
  47. 47. Create the Icon• Right-click on the icon in the block diagram or front panel
  48. 48. Create the Connector Right click on the icon pane (front panel only)
  49. 49. Assign Terminals
  50. 50. Save The VI• Choose an Easy to Remember Location• Organize by Functionality – Save Similar VIs into one directory (e.g. Math Utilities)• Organize by Application – Save all VIs Used for a Specific Application into one directory or library file (e.g. Lab 1 – Frequency Response) • Library Files (.llbs) combine many VI’s into a single file, ideal for transferring entire applications across computers
  51. 51. Insert the SubVI into a Top Level VIAccessing user-made subVIs Functions >>All Functions >> Select a VIOr Drag icon onto target diagram
  52. 52. Section III – Data Acquisition DAQ Device• Data acquisition (DAQ) basics• Connecting Signals• Simple DAQ application Computer Sensors Cable Terminal Block
  53. 53. Data Acquisition in LabVIEW NI-DAQmxTraditional NI-DAQ Next generation driver:Specific VIs for performing: • VIs for performing a• Analog Input task• Analog Output • One set of VIs for all• Digital I/O measurement types• Counter operations
  54. 54. DAQ – Data AcquisitionTemperature Acquisition using the DAQ Assistant
  55. 55. Data Acquisition Terminology• Resolution - Determines How Many Different Voltage Changes Can Be Measured – Larger Resolution  More Precise Representation of Signal• Range - Minimum and Maximum Voltages – Smaller range  More Precise Representation of Signal• Gain - Amplifies or Attenuates Signal for Best Fit in Range
  56. 56. Hardware Connections SC-2075BNC-2120 NI-ELVIS SCB-68
  57. 57. Section IV – Loops and Charts • For Loop • While Loop • Charts • Multiplots
  58. 58. Loops• While Loops – Have Iteration Terminal – Always Run at least Once – Run According to Conditional Terminal• For Loops – Have Iteration Terminal – Run According to input N of Count Terminal
  59. 59. Loops (cont.) 1. Select the loop 2. Enclose code to be repeated 3. Drop or drag additional nodes and then wire
  60. 60. Charts Waveform chart – special numeric indicator that can display a history of values Controls >> Graph Indicators >> Waveform Chart
  61. 61. Wiring Data into Charts Single Plot Charts Multiplot Charts
  62. 62. Section V – Arrays & File I/O• Build arrays manually• Have LabVIEW build arrays automatically• Write to a spreadsheet file• Read from a spreadsheet file
  63. 63. Adding an Array to the Front PanelFrom the Controls >> All Controls >> Array and Cluster subpalette, select the Array Shell Drop it on the screen.
  64. 64. Adding an Array (cont.)Place data object into shell (i.e. Numeric Control)
  65. 65. Creating an Array with a Loop• Loops accumulate arrays at their boundaries
  66. 66. Creating 2D Arrays
  67. 67. File I/OFile I/O – passing data to and from files- Files can be binary, text, or spreadsheet- Write/Read LabVIEW Measurements file (*.lvm) Writing to LVM file Reading from LVM file
  68. 68. Write LabVIEW Measurement File• Includes the open, write, close and error handling functions• Handles formatting the string with either a tab or comma delimiter• Merge Signals function is used to combine data into the dynamic data type
  69. 69. Section VI – Array Functions & Graphs• Basic Array Functions• Use graphs• Create multiplots with graphs
  70. 70. Array Functions – BasicsFunctions >> All functions>> Array
  71. 71. Array Functions – Build Array
  72. 72. Graphs• Selected from the Graph palette of Controls menuControls>>All Controls>>Graphs Waveform Graph – Plot an array of numbers against their indices Express XY Graph – Plot one array against another Digital Waveform Graph – Plot bits from binary data
  73. 73. Graphs Right-Click on the Graph and choose Properties to Interactively Customize
  74. 74. Section VII – Strings, Clusters, & Error Handling• Strings• Creating Clusters• Cluster Functions• Error I/O
  75. 75. Strings • A string is a sequence of displayable or nondisplayable characters (ASCII) • Many uses – displaying messages, instrument control, file I/O • String control/indicator is in the Controls »Text Control or Text Indicator
  76. 76. Clusters• Data structure that groups data together• Data may be of different types• Analogous to struct in C• Elements must be either all controls or all indicators• Thought of as wires bundled into a cable
  77. 77. Creating a Cluster1. Select a Cluster shell 2. Place objects inside the shellControls >> All Controls >> Array & Cluster
  78. 78. Cluster Functions • In the Cluster subpalette of the Functions>>All functions palette • Can also be accessed by right-clicking on the cluster terminal (Terminal labels reflect data type) Bundle Bundle By Name
  79. 79. Cluster FunctionsUnbundleUnbundle By Name Unbundled cluster in the diagram
  80. 80. Error Clusters• Error cluster contains the following information: – Boolean to report whether error occurred – Integer to report a specific error code – String to give information about the error
  81. 81. Error Handling Techniques• Error information is passed from one subVI to the next• If an error occurs in one subVI, all subsequent subVIs are not executed in the usual manner• Error Clusters contain all error conditions• Automatic Error Handling error clusters
  82. 82. Section VIII - Case & Sequence Structures, FormulaNodes
  83. 83. Case Structures• In the Structures subpalette of Functions palette• Enclose nodes or drag them inside the structure• Stacked like a deck of cards, only one case visibleFunctions >> Execution control
  84. 84. Sequence Structures• In the Execution Control subpalette of Functions palette• Executes diagrams sequentially• Right-click to add new frame
  85. 85. Formula Nodes• In the Structures subpalette• Implement complicated equations• Variables created at border• Variable names are case sensitive• Each statement must terminate with a semicolon (;)• Context Help Window shows available functions Note semicolon
  86. 86. Section IX – Printing & Documentation• Print From File Menu to Printer, HTML, Rich Text File• Programmatically Print Graphs or Front Panel Images• Document VIs in VI Properties » Documentation Dialog• Add Comments Using Free Labels on Front Panel & Block Diagram
  87. 87. Printing• File » Print… Gives Many Printing Options – Choose to Print Icon, Front Panel, Block Diagram, VI Hierarchy, Included SubVIs, VI History• Print Panel.vi (Programmatically Prints a Front Panel) – Functions » All Functions » Application Control• Generate & Print Reports (Functions » Output » Report)
  88. 88. Documenting VIs• VI Properties » Documentation – Provide a Description and Help Information for a VI• VI Properties » Revision History – Track Changes Between Versions of a VI• Individual Controls » Description and Tip… – Right Click to Provide Description and Tip Strip• Use Labeling Tool to Document Front Panels & Block Diagrams
  89. 89. Section X – Basic Programming Architecture• Simple VI Architecture• General VI Architecture• State Machine Architecture
  90. 90. Simple VI Architecture• Functional VI that produces results when run – No “start” or “stop” options – Suitable for lab tests, calculations• Example: Convert C to F.vi
  91. 91. General VI Architecture• Three Main Steps – Startup – Main Application – Shutdown
  92. 92. State Machine Architecture• Advantages – Can go from any state from any other – Easy to modify and debug• Disadvantages – Can lose events if two occur at the same time States: 0: Startup 1: Idle 2: Event 1 3: Event 2 4: Shutdown
  93. 93. Section XI – Remote Front Panels• View & Control LabVIEW Front Panels from a Web Browser• Requires no programming• Remote clients see “live” front panel updates• Multiple clients can view the same panel simultaneously• Only one client can control the front panel at a time
  94. 94. Remote Panel Web Publishing Tool•Tools » Web Publishing Tool…•Click Save to Disk and VI isembedded into an HTML file•After file is saved, it can bereopened and customized inany HTML editor
  95. 95. Remote Front Panels - Resources• NI Developer Zone (zone.ni.com) – Search for Remote Front Panel – Tutorials & Instructions Are Available for Download – Information on Incorporating Web Cameras into Remote Panel Applications
  96. 96. Serial Communication• Popular means of communication between computer and peripheral device• Data sent one bit at a time across the cable• Used for low transfer rates or long distances• Only a cable is needed since most computers have at least one available serial port PC Serial Port RS-232 Cable RS-232 Instrument 110
  97. 97. Serial Hardware Connection• RS-232 – DCE or DTE configurations – 9-pin or 25-pin• RS-422 – DCE or DTE Pin DTE DCE – 8-pin 1 DCD Input Output• RS-485 2 RxD I O – Multidrop 3 TxD O I 4 DTR O I 5 Com - - 6 DSR I O 7 RTS O I 8 CTS I O 9 RI I O 111
  98. 98. Serial CommunicationTerminology• Baud rate – bits per second• Data bits – inverted logic and LSB first• Parity – optional error-checking bit• Stop bits – 1, 1.5, or 2 inverted bits at data end• Flow control – hardware and software handshaking options 112
  99. 99. Using the Instrument I/O Assistant with Serial• Select COMX as the instrument address• Use the I/O Assistant as done with GPIB 113
  100. 100. Summary• LabVIEW can communicate with any instrument that connects to your computer if you know the interface type• Use the Measurement & Automation Explorer (MAX) to detect, configure, and test your GPIB interface and instruments• Use the Instrument I/O Assistant for easy and fast GPIB and serial programming.• An instrument driver eliminates the need for your to have detailed knowledge of the specific strings used by an instrument• Instrument Library – more than 2000 instruments supported• Instrument driver VIs share a common hierarchy and come with an example to help you get started 114
  101. 101. Part 4
  102. 102. ad
  103. 103. disad
  104. 104. app
  105. 105. future
  106. 106. ??
  107. 107. ref
  108. 108. ty

×