LabVIEW Wiki - User contributions [en]

Talk:LVBIT File Extension

2022-07-09T16:50:52Z

Terry stratoudakis: Created page with "I cannot find references to the lvbit file extension. Was this used in older versions of LabVIEW FPGA?"

I cannot find references to the lvbit file extension. Was this used in older versions of LabVIEW FPGA?

LVBITX File Extension

2022-07-09T16:49:58Z

Terry stratoudakis: Created page with "The '''LVBITX File Extension''' (*.lvbitx) is used by the bitfiles of the LabVIEW FPGA module. The bitfile is the result of a successful FPGA compile. This file is based on..."

The '''LVBITX File Extension''' (*.lvbitx) is used by the bitfiles of the LabVIEW FPGA module. The bitfile is the result of a successful FPGA compile. This file is based on the [https://www.ni.com/docs/en-US/bundle/labview-2020-fpga-module/page/lvfpgahelp/compiling_fpga_vis_howto.html bitfile generated] by the AMD/Xilinx FPGA compile tool with some NI specific information added.

LabVIEW

2022-07-09T16:46:50Z

Terry stratoudakis: /* The Future of your LabVIEW Code */

[[Image:LabVIEW_Logo_Vertical_4c.jpg|right|thumb|200px]]
== What is LabVIEW? ==
'''LabVIEW''', short for <u>Lab</u>oratory <u>V</u>irtual <u>I</u>nstrument <u>E</u>ngineering <u>W</u>orkbench, is a fully featured [[Integrated Development Environment (IDE)]] produced by [[National Instruments]]. The programming language is officially named "G" for being graphical even though many refer to the language as LabVIEW. The G language unique in the method by which code is constructed and saved. There is no text based code, but is diagrammatic view of how the data flows through the program. Thus LabVIEW is a much loved tool of the scientist and engineer who can often visualize data flow rather than how a text based conventional programming language must be built to achieve a task.

Originally released for the Apple Macintosh in 1986, LabVIEW is commonly used for data acquisition, instrument control, and industrial automation on a variety of operating systems (OSs), including Microsoft Windows, various versions of Unix, Linux, and macOS. Jeff Kodosky, (a.k.a. the "Father of LabVIEW"), during his keynote address during NIWeek 2017, attempted to create a one line description of LabVIEW, in which he stated:

'''''<div style="text-align:center"><q>LabVIEW is an engineering environment for building test, measurement, and control systems using a virtual-instrument based graphical programming language...</q></div>'''''

After feeling this lacked the emotion users felt while using LabVIEW, he went on to add the line:

'''''<div style="text-align:center"><q>...that inspires users to strive for and achieve more than they expected.</q></div>'''''
<br>
{{TOCnestright}}

==Language Overview==
===Virtual Instruments (VIs)===
LabVIEW programs are called virtual instruments, or VIs, because their appearance and operation imitate physical instruments, such as oscilloscopes and multimeters. LabVIEW contains a comprehensive set of tools for acquiring, analyzing, displaying, and storing data, as well as tools to help you troubleshoot your code.

LabVIEW VIs contain three components:
*the [[Front Panel]]
*the [[Block Diagram]]
*the [[Connector Pane]] (including the VI's Icon):

====[[Front Panel]]====
In LabVIEW, you build a user interface on the '''[[Front Panel]]''' with controls and indicators. Controls are knobs, push buttons, dials, and other input devices. Indicators are graphs, LEDs, and other displays. After you build the user interface, you add code using VIs and structures to control the front panel objects.

====[[Block Diagram]]====
The '''[[Block Diagram]]''' contains this code. In some ways, the [[Block Diagram|block diagram]] resembles a flowchart showing the dataflow from one [[Programming Elements|element]], or "[[node]]", to the next.

In text based code, the code inside of a programming structure is enclosed by brackets making it difficult to differentiate what is in the structure and what is out. In LabVIEW this is not the case. Structures, like: [[While Loop|While Loops]], [[For Loop|For Loops]], and [[Case Structure|Case Structures]] graphically surrounds and encompasses the code that operates within it.

====[[Connector Pane]]====
The '''[[Connector Pane]]''' defines the inputs and outputs of the VI by connecting Controls and Indicators from the [[Front Panel|front panel]] to terminals on the Icon. When the VI is dropped into the [[Block Diagram|block diagram]] of another VI (becoming a SubVI) these terminals are then available to attach wires for inputs and outputs.

===Hardware Connectivity===

You can use LabVIEW to communicate with hardware such as data acquisition, vision, and motion control devices, and GPIB, PXI, VXI, RS-232, and RS-484 devices. LabVIEW also has built-in features for connecting your application to the Web using the LabVIEW Web Server and software standards such as TCP/IP networking and ActiveX.

==Purchasing==
LabVIEW is developed and sold by [[National Instruments]]. This is an American company with distribution via international offices and [[National Instruments]] Alliance members. For more details check out the [[National Instruments]] Web site

== Versions ==
There are many versions of LabVIEW still in use, although the earlier versions are constrained to hard core dedicated enthusiasts. We have heard whispered mention of the use of [[LabVIEW 3.0|Version 3]] and there are many active [[LabVIEW 4.0|Version 4's]] in circulation. More recent additions to the legacy software bin are versions [[LabVIEW 5.0|5.0]], 5.1, [[LabVIEW 6i]] and [[LabVIEW 6i|6.1]], while the current version as of May 2018 is [[LabVIEW 2018]]. In addition there are demo versions available from [[National Instruments]]. Starting in 2017 [[National Instruments]] announced the creation of the next generation of LabVIEW, called LabVIEW NXG. Currently, LabVIEW NXG has had two releases in 2017 and 2018 which comprises [[LabVIEW NXG 1.0]] and [[LabVIEW NXG 2.0|2.0]], respectively.

From version 6.0 onwards NI released the product formerly known as BridgeVIEW as a LabVIEW plugin module called the Data Supervisory and Control module (DSC) and with the advent of [[real time]] boards and the release of the [[Fieldpoint]] real-time network module, there is also a module that allows writing of code for [[Portal:embedded|embedded]] processors referred to as the [[real time|Real Time]] module (RT). Lastly, there are version available for [[PDA]] module (for writing code for PocketPC and PalmOS) and the [[FPGA]] module for writing code for Field Programmable Gate Arrays (LabVIEW on a chip!). These modules now keep track with the current LabVIEW version.

See more on all of the [[LabVIEW Versions]].

== OS Support ==
LabVIEW is supported and G source code development can be accomplished on Windows 9x/2000/NT/XP/Vista/7/8/10, [[Apple|Apple Macintosh]] (including X), PowerMax OS, Solaris, HP-Unix, Sun, [[Linux]], the Pharlap RTOS, and VxWorks RTOS (Real-Time Operating Systems, found on [[National Instruments]] embedded controllers). Executables can be compiled under their respective development systems to run on these platforms. Code developed under one platform can be ported to any of the others, recompiled and run<nowiki>*</nowiki>. [[PDA|LabVIEW PDA]] can run on handheld devices, such as Microsoft Windows Mobile for Pocket PC devices.

<nowiki>*</nowiki>There are of course exceptions to every rule. In this case platform specific sections of the LabVIEW development system will not be transferable. For example, ActiveX or .NET integration which is Windows specific. Furthermore, certain third party device drivers or LabVIEW toolkits installed under one system may not necessarily be available, run, or be recompiled on a different operating system.

==Compiling/Creating Executables==

Since [[LabVIEW 2.0]], G can compiled directly into executables. You can also create stand-alone [[DLL/shared library|shared libraries (DLLs)]], [[Packed Project Library|Packed Project Libraries (PPLs)]], and installers.
LabVIEW has both 32-bit and 64-bit versions with applicable compiler for each. As stated above, except for the listed exceptions, executables can be compiled under their respective development systems to run on the various platforms and "bitnesses".

[[Category:LabVIEW]]

== The Future of your LabVIEW Code ==
LabVIEW is in active development. As of [https://forums.ni.com/t5/LabVIEW/Our-Commitment-to-LabVIEW-as-we-Expand-our-Software-Portfolio/td-p/4101878?profile.language=en November 2020], NI has ceased development of LabVIEW NXG past 2022.

== See Also ==
*[[LabVIEW Bug Reporting]]
*[[LabVIEW tutorial|LabVIEW Tutorial]]
*[https://www.ni.com/en-us/support/downloads/software-products.html Download LabVIEW (NI.com/downloads)]

[[Category:LabVIEW fundamentals]]

LabVIEW

2022-07-09T16:45:51Z

Terry stratoudakis: /* The Future of your LabVIEW Code */

[[Image:LabVIEW_Logo_Vertical_4c.jpg|right|thumb|200px]]
== What is LabVIEW? ==
'''LabVIEW''', short for <u>Lab</u>oratory <u>V</u>irtual <u>I</u>nstrument <u>E</u>ngineering <u>W</u>orkbench, is a fully featured [[Integrated Development Environment (IDE)]] produced by [[National Instruments]]. The programming language is officially named "G" for being graphical even though many refer to the language as LabVIEW. The G language unique in the method by which code is constructed and saved. There is no text based code, but is diagrammatic view of how the data flows through the program. Thus LabVIEW is a much loved tool of the scientist and engineer who can often visualize data flow rather than how a text based conventional programming language must be built to achieve a task.

Originally released for the Apple Macintosh in 1986, LabVIEW is commonly used for data acquisition, instrument control, and industrial automation on a variety of operating systems (OSs), including Microsoft Windows, various versions of Unix, Linux, and macOS. Jeff Kodosky, (a.k.a. the "Father of LabVIEW"), during his keynote address during NIWeek 2017, attempted to create a one line description of LabVIEW, in which he stated:

'''''<div style="text-align:center"><q>LabVIEW is an engineering environment for building test, measurement, and control systems using a virtual-instrument based graphical programming language...</q></div>'''''

After feeling this lacked the emotion users felt while using LabVIEW, he went on to add the line:

'''''<div style="text-align:center"><q>...that inspires users to strive for and achieve more than they expected.</q></div>'''''
<br>
{{TOCnestright}}

==Language Overview==
===Virtual Instruments (VIs)===
LabVIEW programs are called virtual instruments, or VIs, because their appearance and operation imitate physical instruments, such as oscilloscopes and multimeters. LabVIEW contains a comprehensive set of tools for acquiring, analyzing, displaying, and storing data, as well as tools to help you troubleshoot your code.

LabVIEW VIs contain three components:
*the [[Front Panel]]
*the [[Block Diagram]]
*the [[Connector Pane]] (including the VI's Icon):

====[[Front Panel]]====
In LabVIEW, you build a user interface on the '''[[Front Panel]]''' with controls and indicators. Controls are knobs, push buttons, dials, and other input devices. Indicators are graphs, LEDs, and other displays. After you build the user interface, you add code using VIs and structures to control the front panel objects.

====[[Block Diagram]]====
The '''[[Block Diagram]]''' contains this code. In some ways, the [[Block Diagram|block diagram]] resembles a flowchart showing the dataflow from one [[Programming Elements|element]], or "[[node]]", to the next.

In text based code, the code inside of a programming structure is enclosed by brackets making it difficult to differentiate what is in the structure and what is out. In LabVIEW this is not the case. Structures, like: [[While Loop|While Loops]], [[For Loop|For Loops]], and [[Case Structure|Case Structures]] graphically surrounds and encompasses the code that operates within it.

====[[Connector Pane]]====
The '''[[Connector Pane]]''' defines the inputs and outputs of the VI by connecting Controls and Indicators from the [[Front Panel|front panel]] to terminals on the Icon. When the VI is dropped into the [[Block Diagram|block diagram]] of another VI (becoming a SubVI) these terminals are then available to attach wires for inputs and outputs.

===Hardware Connectivity===

You can use LabVIEW to communicate with hardware such as data acquisition, vision, and motion control devices, and GPIB, PXI, VXI, RS-232, and RS-484 devices. LabVIEW also has built-in features for connecting your application to the Web using the LabVIEW Web Server and software standards such as TCP/IP networking and ActiveX.

==Purchasing==
LabVIEW is developed and sold by [[National Instruments]]. This is an American company with distribution via international offices and [[National Instruments]] Alliance members. For more details check out the [[National Instruments]] Web site

== Versions ==
There are many versions of LabVIEW still in use, although the earlier versions are constrained to hard core dedicated enthusiasts. We have heard whispered mention of the use of [[LabVIEW 3.0|Version 3]] and there are many active [[LabVIEW 4.0|Version 4's]] in circulation. More recent additions to the legacy software bin are versions [[LabVIEW 5.0|5.0]], 5.1, [[LabVIEW 6i]] and [[LabVIEW 6i|6.1]], while the current version as of May 2018 is [[LabVIEW 2018]]. In addition there are demo versions available from [[National Instruments]]. Starting in 2017 [[National Instruments]] announced the creation of the next generation of LabVIEW, called LabVIEW NXG. Currently, LabVIEW NXG has had two releases in 2017 and 2018 which comprises [[LabVIEW NXG 1.0]] and [[LabVIEW NXG 2.0|2.0]], respectively.

From version 6.0 onwards NI released the product formerly known as BridgeVIEW as a LabVIEW plugin module called the Data Supervisory and Control module (DSC) and with the advent of [[real time]] boards and the release of the [[Fieldpoint]] real-time network module, there is also a module that allows writing of code for [[Portal:embedded|embedded]] processors referred to as the [[real time|Real Time]] module (RT). Lastly, there are version available for [[PDA]] module (for writing code for PocketPC and PalmOS) and the [[FPGA]] module for writing code for Field Programmable Gate Arrays (LabVIEW on a chip!). These modules now keep track with the current LabVIEW version.

See more on all of the [[LabVIEW Versions]].

== OS Support ==
LabVIEW is supported and G source code development can be accomplished on Windows 9x/2000/NT/XP/Vista/7/8/10, [[Apple|Apple Macintosh]] (including X), PowerMax OS, Solaris, HP-Unix, Sun, [[Linux]], the Pharlap RTOS, and VxWorks RTOS (Real-Time Operating Systems, found on [[National Instruments]] embedded controllers). Executables can be compiled under their respective development systems to run on these platforms. Code developed under one platform can be ported to any of the others, recompiled and run<nowiki>*</nowiki>. [[PDA|LabVIEW PDA]] can run on handheld devices, such as Microsoft Windows Mobile for Pocket PC devices.

<nowiki>*</nowiki>There are of course exceptions to every rule. In this case platform specific sections of the LabVIEW development system will not be transferable. For example, ActiveX or .NET integration which is Windows specific. Furthermore, certain third party device drivers or LabVIEW toolkits installed under one system may not necessarily be available, run, or be recompiled on a different operating system.

==Compiling/Creating Executables==

Since [[LabVIEW 2.0]], G can compiled directly into executables. You can also create stand-alone [[DLL/shared library|shared libraries (DLLs)]], [[Packed Project Library|Packed Project Libraries (PPLs)]], and installers.
LabVIEW has both 32-bit and 64-bit versions with applicable compiler for each. As stated above, except for the listed exceptions, executables can be compiled under their respective development systems to run on the various platforms and "bitnesses".

[[Category:LabVIEW]]

== The Future of your LabVIEW Code ==
LabVIEW is in active development. As of November 2020, NI has ceased development of LabVIEW NXG past 2022.

== See Also ==
*[[LabVIEW Bug Reporting]]
*[[LabVIEW tutorial|LabVIEW Tutorial]]
*[https://www.ni.com/en-us/support/downloads/software-products.html Download LabVIEW (NI.com/downloads)]

[[Category:LabVIEW fundamentals]]

FPGA

2021-08-10T22:05:40Z

Terry stratoudakis:

FPGA is an acronym for Field Programmable Gate Array. An FPGA is an integrated circuit which can be reconfigured using software tools.

FPGAs contain logic blocks, interconnects, and I/O. Older FPGAs had simpler, more homogeneous logic blocks such as look up tables (LUTs). Newer FPGAs have "logic blocks" which are far more complex which can include LUTs, digital signal processing (DSP), and even CPU cores. In this sense, FPGAs are converging into System on Chip (SoC).

AMD (after acquiring Xilinx) and Intel (after acquiring Altera) are the biggest manufacturers of FPGAs.

CPUs and GPUs are not reconfigurable and function based on software.

Historically FPGAs were first configured using schematic capture, then with hardware description languages such as VHDL and Verliog, and now with high level synthesis tools such as LabVIEW FPGA, HDL Coder, Catapult, etc. The next generation of tools may be overlays.

Hardware

2021-05-30T04:30:18Z

Terry stratoudakis: /* Platforms */

{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; font-size:200%; border:none; margin:0; padding:.3em; color:#FFD500; text-align:center;"
| '''The Hardware Portal'''
|-
| The '''Hardware''' Portal covers both communication with Hardware (Protocols) as well as articles pertaining to specific Hardware (Platforms).
|}
__NOTOC__
{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; border:none; color:#FFD500; text-align:center;"
| '''Subcategories'''
| colspan=3 | '''Topics in Hardware'''
|- style="vertical-align:top;"
| style="width:25%; text-align:top; background-color:#EFEFEF;" | <center><small>Select [►] to view subcategories</small></center>
<categorytree mode="Pages" showcount="off" depth="1">Hardware</categorytree>
| style="width:75%;" |

== Protocols ==
* [[Serial]]
* [[Instrument Control|VISA]]
* [[TCP]]
* [[UDP]]

== Platforms ==
*[[Mindstorms]]
*[[Embedded]]
* [[cRIO]]
* [[sbRIO]]
* [[SOM]]
* [[PXI]]
** [[R Series]]
** [[FlexRIO]]
** [[High Speed Serial]]
** [[Vector Signal Transceiver]]
*** [[VST 1st Generation]]
*** [[VST 2nd Generation]]
* [[ATCA]]
* [[Ettus]]
* [[Linx Toolkit Hardware Compatibility List|LINX Toolkit Hardware Compatibility List]]
** [[Arduino]]
** [[Raspberry Pi]]
** [[BeagleBoard]]
|}

[[Category:Portals]]

Hardware

2021-05-30T04:28:30Z

Terry stratoudakis: /* Platforms */

{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; font-size:200%; border:none; margin:0; padding:.3em; color:#FFD500; text-align:center;"
| '''The Hardware Portal'''
|-
| The '''Hardware''' Portal covers both communication with Hardware (Protocols) as well as articles pertaining to specific Hardware (Platforms).
|}
__NOTOC__
{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; border:none; color:#FFD500; text-align:center;"
| '''Subcategories'''
| colspan=3 | '''Topics in Hardware'''
|- style="vertical-align:top;"
| style="width:25%; text-align:top; background-color:#EFEFEF;" | <center><small>Select [►] to view subcategories</small></center>
<categorytree mode="Pages" showcount="off" depth="1">Hardware</categorytree>
| style="width:75%;" |

== Protocols ==
* [[Serial]]
* [[Instrument Control|VISA]]
* [[TCP]]
* [[UDP]]

== Platforms ==
*[[Mindstorms]]
*[[Embedded]]
* [[cRIO]]
* [[PXI]]
** [[FlexRIO]]
** [[High Speed Serial]]
* [[ATCA]]
* [[Ettus]]
* [[Linx Toolkit Hardware Compatibility List|LINX Toolkit Hardware Compatibility List]]
** [[Arduino]]
** [[Raspberry Pi]]
** [[BeagleBoard]]
|}

[[Category:Portals]]

FlexRIO

2021-05-30T04:27:42Z

Terry stratoudakis: Created page with "FlexRIO is an NI FPGA hardware platform in its 2nd generation. The first generation was an outgrowth of the R series FPGA cards. The components common to all cards were grou..."

FlexRIO is an NI FPGA hardware platform in its 2nd generation.

The first generation was an outgrowth of the R series FPGA cards. The components common to all cards were grouped on the part that plugs into the PXI/PXIe chassis. These components include: FPGA, PXI/PXIe interface, and DRAM (optional). I/O was supported by a FlexRIO Adapter Module (FAM). This plugs into the card that plugs into the PXI/PXIe chassis. A module development toolkit (MDK) for making custom FAMs is available for purchase. Not all FAMs work with all FPGA FlexRIO cards.

The models of the FPGA FlexRIO cards are 795x, 796x, 797x. 793x is a standalone device that has its own OS and network connection. 797x has a different interface from the other cards. This could be considered a FlexRIO generation 1.5.

These cards use Virtex-5 and Kintex-7 Xilinx (now AMD) FPGAs with up to 2 GB of onboard DRAM. The cards are PXI and PXIe. PXIe cards support Peer to Peer. None of these cards have multi-gigabit transceiver (MGT) front end interfacing.

The second generation dropped the use of the FAM. NI uses a modular design for the front end (I/O). The user does not have access to change the front end module. These cards use the Xilinx (now AMD) Ultrascale FPGA cards (KU035, KU040, and KU060). These are all PXIe cards with up to 4 GB of onboard DRAM. All have multi-gigabit transceiver (MGT) front end interfacing.

[[Category:FPGA]]

Hardware

2021-05-30T04:10:24Z

Terry stratoudakis: /* Platforms */

{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; font-size:200%; border:none; margin:0; padding:.3em; color:#FFD500; text-align:center;"
| '''The Hardware Portal'''
|-
| The '''Hardware''' Portal covers both communication with Hardware (Protocols) as well as articles pertaining to specific Hardware (Platforms).
|}
__NOTOC__
{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; border:none; color:#FFD500; text-align:center;"
| '''Subcategories'''
| colspan=3 | '''Topics in Hardware'''
|- style="vertical-align:top;"
| style="width:25%; text-align:top; background-color:#EFEFEF;" | <center><small>Select [►] to view subcategories</small></center>
<categorytree mode="Pages" showcount="off" depth="1">Hardware</categorytree>
| style="width:75%;" |

== Protocols ==
* [[Serial]]
* [[Instrument Control|VISA]]
* [[TCP]]
* [[UDP]]

== Platforms ==
*[[Mindstorms]]
*[[Embedded]]
* [[cRIO]]
* [[PXI]]
** [[FlexRIO]]
** [[High Speed Serial]]
* [[Linx Toolkit Hardware Compatibility List|LINX Toolkit Hardware Compatibility List]]
** [[Arduino]]
** [[Raspberry Pi]]
** [[BeagleBoard]]
|}

[[Category:Portals]]

FPGA

2021-05-30T04:08:10Z

Terry stratoudakis:

FPGA is an acronym for Field Programmable Gate Array. An FPGA is an integrated circuit which can be reconfigured using software tools.

FPGAs contain logic blocks, interconnects, and I/O.

AMD (after acquiring Xilinx) and Intel (after acquiring Altera) are the biggest manufacturers of FPGAs.

CPUs and GPUs are not reconfigurable and function based on software.

Historically FPGAs were first configured using schematic capture, then with hardware description languages such as VHDL and Verliog, and now with high level synthesis tools such as LabVIEW FPGA, HDL Coder, Catapult, etc. The next generation of tools may be overlays.

FPGAs have evolved from being having logic blocks which are homogeneous, to having more specialized components such as math focused DSP blocks. Other specialized components include microprocessors and bus interfaces. In this sense, FPGAs are converging into System on Chip (SoC).

FPGA

2020-07-06T20:37:30Z

Terry stratoudakis: Created page with "FPGA is an acronym for Field Programmable Gate Array. An FPGA is an integrated circuit which can be reconfigured using software tools. FPGAs contain logic blocks, interconne..."

FPGA is an acronym for Field Programmable Gate Array. An FPGA is an integrated circuit which can be reconfigured using software tools.

FPGAs contain logic blocks, interconnects, and I/O.

Xilinx and Intel (after acquiring Altera) are the biggest manufacturers of FPGAs.

CPUs and GPUs are not reconfigurable and function based on software.

Historically FPGAs were first configured using schematic capture, then with hardware description languages such as VHDL and Verliog, and now with high level synthesis tools such as LabVIEW FPGA, HDL Coder, Catapult, etc. The next generation of tools may be overlays.

FPGAs have evolved from being having logic blocks which are homogeneous, to having more specialized components such as math focused DSP blocks. Other specialized components include microprocessors and bus interfaces. In this sense, FPGAs are converging into System on Chip (SoC).