LabVIEW Software is a system-design platform and development environment for a visual programming language from National Instruments. LabVIEW Software can be explained Laboratory Virtual Instrument Engineering Workbench
The programming paradigm used in LabVIEW software, sometimes called G, is based on data availability. If there is enough data available to a subVI or function that subVI or function will directing. Execution flow is determined by the structure of a graphical block diagram (the LabVIEW-source code) on which the programmer links different function-nodes by drawing wires.
These wires propagate variables and any node can execute as soon as all its input data become available. Since this might be the case for multiple nodes simultaneously, LabVIEW software can execute inherently in parallel. Multi-processing and multi-threading hardware is exploited automatically by the built-in scheduler, which multiplexes multiple OS threads over the nodes ready for execution.
LabVIEW Software Features
- It contains New chapter on MathScript
- New building block that spans the entire book, building on each chapter topics
- Major upgrade to worked examples and additional homework problems
- New features can be covered including MathScript, Matrix data type, Advanced Analysis Library, Simulated Data Acquisition, and much more
LabVIEW software integrates the creation of user interfaces (termed front panels) into the development cycle. LabVIEW software programs-subroutines are termed virtual instruments. Each VI has three components:
- Block diagram
- Front panel
- Connector panel.
The connector panel is used to represent the VI in the block diagrams of other, calling VIs. The front panel is built using controls and indicators. Here most of the controls are inputs: they allow a user to supply information to the VI. And the Indicators are outputs: they indicate, or display, the results based on the inputs given to the VI. The back panel, which is a block diagram, includes the graphical source code. All of the objects placed on the front panel will appear on the back panel as terminals. The back panel also contains structures and functions which perform operations on controls and supply data to indicators.
The structures and programs are found on the Functions palette and can be placed on the back panel. Collectively controls, indicators, structures, and functions will be referred to as nodes. Nodes are connected to one another using wires, e.g., two controls and an indicator can be wired to the addition function so that the indicator shows the sum of the two controls. Thus a virtual instrument can be run as either a program, with the front panel serving as a user interface, or when dropped as a node onto the block diagram, the front panel defines the inputs and outputs for the node through the connector panel. This implies each VI can be easily tested before being embedded as a subroutine into a larger program.
The graphical approach also allows non programmers to build programs by dragging and dropping virtual representations of lab equipment with which they are already familiar. The LabVIEW software programming environment, with the included examples and documentation, makes it simple to create small app’s. This is a benefit on one side, but there is also a certain danger of underestimating the expertise needed for high-quality G programming.
For complex algorithms or large-scale code is important that a programmer possess an extensive knowledge of the special LabVIEW software and the topology of its memory management. The most advanced LabVIEW software development systems offer the ability to build self-operated applications. More, it is possible to make distributed applications, which communicate by a client–server model, and are thus easier to implement due to the naturally parallel nature of G.
Functional Global Variable – Exchange information without using global variables. It can be used to Exchange information with less wiring and the limitation is all owning VIs are kept in memory.
State machine – Controlled execution that depends on past events. User interfaces, Complex logic, Communication protocols and the dis advantage is All possible states must be known in advance
Event-driven user interface – Lossless processing of user actions. The purpose of Graphical user interface. And it had only one event structure in a loop so it was a main limitation of this contents.
Master-slave – Run independent processes simultaneously. Simple GUI for data acquisition and visualization process. It can be requires prevention of race conditions.
Producer-buyer – Asynchronous of multithreaded execution of loops. It can be the process of Data sampling and visualization. It can’t be control order of execution, it was a demerits of this process
Interfacing to devices
LabVIEW software includes extensive support for interfacing to devices, instruments, camera, and other devices. Users interface to hardware by either writing direct bus commands (USB, GPIB, Serial) or using high-level, device-specific, drivers that provide native LabVIEW software function nodes for controlling the device.
LabVIEW Apk includes built-in support for National Instruments hardware platforms such as CompactDAQ and CompactRIO, with large number of device-specific blocks for such a hardware, the Measurement and Automation explorer and Virtual Instrument Software Architecture toolsets. National Instruments makes thousands of device drivers available for download on the National Instruments Driver Network.
Compiling of code
LabVIEW software contains a compiler that produces native code for the CPU platform. This aids performance. The graphical code is translated into operating machine code by interpreting the syntax and by compiling. The LabVIEW software is strictly enforced during the editing process and compiled into the executable machine code when requested to run or upon saving. In the latter case, the source code and executable are converted into a single file. The Labview run-time engine helps to executable while running this process, which contains some precompiled code to perform common tasks that are defined by the G language.
The run-time engine decreases compiling time and provides a consistent interface to various operating systems, graphic systems, hardware components, etc. The run-time environment creates the code portable across platforms. Generally, LabVIEW software code can be slower than equivalent compiled C code, although the differences often lie over with program optimization than inherent execution rpm.
Thanks for visiting Filmiwoods.com.