LabVIEW Wiki - User contributions [en]

TortoiseSVN client to Subversion

2025-04-23T15:03:12Z

Bryan: Updated link to JKI Toolkit and added link Viewpoint Systems' toolkit.

TortoiseSVN is a free Subversion client integrated as a Windows shell extension. [http://tortoisesvn.net/]

After downloading and installing TortoiseSVN, one can: [[Point to an existing repository]] [[Add a directory to the repository]] [[Configure TortoiseSVN to work with LabVIEW]]

Below are links to some available TortoiseSVN Toolkits. Visit provider's pages for additional information:

- [https://www.vipm.io/package/jki_tool_tortoisesvn/ JKI TortoiseSVN Toolkit]
 
- [https://www.viewpointusa.com/product/ni-labview-toolkits/tsvn-toolkit/ Viewpoint Systems TSVN Toolkit]

[[Category:SCC]]
[[Category:SVN]]

Set up differencing capabilities

2023-09-19T13:35:18Z

Bryan: /* Using LVCompare.exe and TortoiseSVN */

== Easy Setup For Git ==
The easiest way to setup LVCompare and LVMerge for use with Git is to copy/paste the following into Git Bash

<nowiki>cd && git clone https://gitlab.com/sas-blog/LVCompare-Merge-Setup.git && cd LVCompare-Merge-Setup && ./setupLVTools.sh</nowiki>

This will clone a repo and run a shell script to set everything up. You can read more about it here:
https://blog.sasworkshops.com/the-easiest-way-to-setup-lvcompare-and-lvmerge/

After that, you can use the difftool command in Git Bash to view diffs or use your favorite Git GUI.

There are several methods setting up differencing LabVIEW VIs with subversion. A new feature in LabVIEW 2009 in the program LVCompare.exe which allows graphical differencing from the command line. In older versions, TortoiseSVN can be coupled with the open source LVDiff to achieve the same goal.

== LVCompare.exe National Instruments Documentation ==
This documentation describes the options you can pass to LVCompare.exe. For example, you can instruct LVCompare.exe to ignore changes in the position of front panel objects by pass in "-nofppos". For the full set of documentation please refer to the link below:
[http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/configlvcomp_thirdparty/ LVCompare.exe from National Instruments]

== Using LVCompare.exe and svn CLI ==
From the command line, subversion cannot normally compare binary files such as vis. The svn diff command has a switch --diff-cmd to allow an external differencing engine to be used. This will be leveraged to used LVComare to operate on vis.

To use LVCompare.exe with subversion in the command line, first add "C:\Program Files\National Instruments\Shared\LabVIEW Compare" to your system PATH variable (this allows the command prompt to find LVcompare.exe).

The output of the diff command is quite complicated (from [http://subversion.tigris.org/faq.html#diff-cmd] subversion FAQ):
<blockquote>When using an external diff command, Subversion builds a fairly complicated command line. First is the specified --diff-cmd. Next comes the specified --extensions (although empty --extensions are ignored), or '-u' if --extensions is unspecified (or specified as ''). Third and fourth, Subversion passes a '-L' and the first file's label (e.g. "project_issues.html (revision 11209)"). Fifth and sixth are another '-L' and the second label. Seventh and eighth are the first and second file names (e.g. ".svn/text-base/project_issues.html.svn-base" and ".svn/tmp/project_issues.html.tmp").
 
If your preferred diff command does not support these arguments, you may need to create a small wrapper script to discard arguments and just use the last couple file paths.
 
Warning: Beware that Subversion does not expect the external diff program to change the files it receives, and doing so may scramble the working copy.
</blockquote>
On windows, this wrapper is easy to create. Save the following file as LVdiff.bat in the same directory as LVCompare.exe. This formulates the LVCompare command correctly.
<blockquote>
@ECHO OFF 
lvcompare "%cd%\%~7" "%cd%\%~6"
</blockquote>
Then, to execute the diff, use the following command:
<blockquote>
svn diff --diff-cmd LVdiff.bat --force CHANGED.vi
</blockquote>
where CHANGED.vi is the one you want to diff.

IMPORTANT: As stated in the FAQ, subversion does not expect diff to make any changes, so make sure not to save the text-base vi.

== Using LVCompare.exe and TortoiseSVN ==
For users of the TortoiseSVN client and LabVIEW 2009, it is also possible extend TortoiseSVN's built-in differencing functionality to allow VIs to be compared from a simple Windows Explorer right-click menu using LVCompare.exe. This can be achieved by adding an entry for .VI files to the "Advanced" list of TortoiseSVN's Diff settings with the following syntax<ref>http://zone.ni.com/devzone/cda/tut/p/id/9407</ref>:
<blockquote>
"C:\Program Files\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" %base %mine
</blockquote>
''Note:'' If you're using 32-bit LabVIEW on a 64-bit Windows OS, the path would be:
<blockquote>
"C:\'''Program Files (x86)'''\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" %base %mine
</blockquote>
(from [http://zone.ni.com/devzone/cda/tut/p/id/9407] Command-Line Graphical Differencing of VIs)

== Using TortoiseSVN and LVDiff for VIs ==
TortoiseSVN has its own program (TortoiseMerge) to show the differences between two different versions of a file. This works well with text files but since LabVIEW VIs are binary files it is advantageous to use LabVIEW's graphical differencing capabilities.

The professional version of LabVIEW has a "CMP Compare two VIs.vi" in the ...\LabVIEW x.x\project\procmphier.llb library.

The open-source "LVDiff" tool (see [http://meta-diff.sourceforge.net/] for the main download but download the updated "lvdiff.vi" from the link here [http://forums.ni.com/ni/board/message?board.id=170&message.id=354286&requireLogin=False] since the version currently in the .zip file does not work with VIs in libraries) provides a wrapper to call this VI.

Be sure to update the paths in the .lvdiff file.

Open Windows Explorer. 
Right-click on a directory and select "TortoiseSVN...Settings" from the pop-up menu. 
Under "External Programs" select "Diff Viewer". 
[[Image:DiffViewerPageNew2.png]]
 
Click on the "Advanced..." button and add a ".vi" extension with the "External Program" pointing to "lvdiff.exe". 
[[Image:SettingUpLVDiff.png]]
 

To compare a file with the previous version in the repository right-click on the file in Windows explorer and select "TortoiseSVN...Diff with previous version".

== Using SourceTree and LVDiff for VIs ==
You can invoke LVCompare.exe from Atlassian SourceTree by using the application found here: [https://github.com/smithed/vicompare VI Compare].
Set up SourceTree using the steps below.
{| class="wikitable"
|-
| Go To Tools>>Options ||
[[File:Tools,options.png]]
|-
| Select "Diff". Then Select "Custom" for External Diff Tool and Merge tool ||
[[File:2019-07-29 11h45 51.png]]
|-
| Navigate to the installed executables. Specify <"$LOCAL" "$REMOTE"> for Diff Command Arguments and <"$BASE" "$REMOTE" "$LOCAL" "$MERGED"> for Merge Command Arguments ||
[[File:2019-07-29 11h46 08.png]]
|}

[[Category:SCC]]
[[Category:SVN]]

Set up differencing capabilities

2023-09-19T13:34:33Z

Bryan: /* Using LVCompare.exe and TortoiseSVN */

== Easy Setup For Git ==
The easiest way to setup LVCompare and LVMerge for use with Git is to copy/paste the following into Git Bash

<nowiki>cd && git clone https://gitlab.com/sas-blog/LVCompare-Merge-Setup.git && cd LVCompare-Merge-Setup && ./setupLVTools.sh</nowiki>

This will clone a repo and run a shell script to set everything up. You can read more about it here:
https://blog.sasworkshops.com/the-easiest-way-to-setup-lvcompare-and-lvmerge/

After that, you can use the difftool command in Git Bash to view diffs or use your favorite Git GUI.

There are several methods setting up differencing LabVIEW VIs with subversion. A new feature in LabVIEW 2009 in the program LVCompare.exe which allows graphical differencing from the command line. In older versions, TortoiseSVN can be coupled with the open source LVDiff to achieve the same goal.

== LVCompare.exe National Instruments Documentation ==
This documentation describes the options you can pass to LVCompare.exe. For example, you can instruct LVCompare.exe to ignore changes in the position of front panel objects by pass in "-nofppos". For the full set of documentation please refer to the link below:
[http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/configlvcomp_thirdparty/ LVCompare.exe from National Instruments]

== Using LVCompare.exe and svn CLI ==
From the command line, subversion cannot normally compare binary files such as vis. The svn diff command has a switch --diff-cmd to allow an external differencing engine to be used. This will be leveraged to used LVComare to operate on vis.

To use LVCompare.exe with subversion in the command line, first add "C:\Program Files\National Instruments\Shared\LabVIEW Compare" to your system PATH variable (this allows the command prompt to find LVcompare.exe).

The output of the diff command is quite complicated (from [http://subversion.tigris.org/faq.html#diff-cmd] subversion FAQ):
<blockquote>When using an external diff command, Subversion builds a fairly complicated command line. First is the specified --diff-cmd. Next comes the specified --extensions (although empty --extensions are ignored), or '-u' if --extensions is unspecified (or specified as ''). Third and fourth, Subversion passes a '-L' and the first file's label (e.g. "project_issues.html (revision 11209)"). Fifth and sixth are another '-L' and the second label. Seventh and eighth are the first and second file names (e.g. ".svn/text-base/project_issues.html.svn-base" and ".svn/tmp/project_issues.html.tmp").
 
If your preferred diff command does not support these arguments, you may need to create a small wrapper script to discard arguments and just use the last couple file paths.
 
Warning: Beware that Subversion does not expect the external diff program to change the files it receives, and doing so may scramble the working copy.
</blockquote>
On windows, this wrapper is easy to create. Save the following file as LVdiff.bat in the same directory as LVCompare.exe. This formulates the LVCompare command correctly.
<blockquote>
@ECHO OFF 
lvcompare "%cd%\%~7" "%cd%\%~6"
</blockquote>
Then, to execute the diff, use the following command:
<blockquote>
svn diff --diff-cmd LVdiff.bat --force CHANGED.vi
</blockquote>
where CHANGED.vi is the one you want to diff.

IMPORTANT: As stated in the FAQ, subversion does not expect diff to make any changes, so make sure not to save the text-base vi.

== Using LVCompare.exe and TortoiseSVN ==
For users of the TortoiseSVN client and LabVIEW 2009, it is also possible extend TortoiseSVN's built-in differencing functionality to allow VIs to be compared from a simple Windows Explorer right-click menu using LVCompare.exe. This can be achieved by adding an entry for .VI files to the "Advanced" list of TortoiseSVN's Diff settings with the following syntax<ref>http://zone.ni.com/devzone/cda/tut/p/id/9407</ref>:
<blockquote>
"C:\Program Files\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" %base %mine
</blockquote>
''Note:'' If you're using 32-bit LabVIEW on a 64-bit Windows OS, the path would be:
<blockquote>
"C:\'''Program Files (x86)'''\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" %base %mine
</blockquote
(from [http://zone.ni.com/devzone/cda/tut/p/id/9407] Command-Line Graphical Differencing of VIs)

== Using TortoiseSVN and LVDiff for VIs ==
TortoiseSVN has its own program (TortoiseMerge) to show the differences between two different versions of a file. This works well with text files but since LabVIEW VIs are binary files it is advantageous to use LabVIEW's graphical differencing capabilities.

The professional version of LabVIEW has a "CMP Compare two VIs.vi" in the ...\LabVIEW x.x\project\procmphier.llb library.

The open-source "LVDiff" tool (see [http://meta-diff.sourceforge.net/] for the main download but download the updated "lvdiff.vi" from the link here [http://forums.ni.com/ni/board/message?board.id=170&message.id=354286&requireLogin=False] since the version currently in the .zip file does not work with VIs in libraries) provides a wrapper to call this VI.

Be sure to update the paths in the .lvdiff file.

Open Windows Explorer. 
Right-click on a directory and select "TortoiseSVN...Settings" from the pop-up menu. 
Under "External Programs" select "Diff Viewer". 
[[Image:DiffViewerPageNew2.png]]
 
Click on the "Advanced..." button and add a ".vi" extension with the "External Program" pointing to "lvdiff.exe". 
[[Image:SettingUpLVDiff.png]]
 

To compare a file with the previous version in the repository right-click on the file in Windows explorer and select "TortoiseSVN...Diff with previous version".

== Using SourceTree and LVDiff for VIs ==
You can invoke LVCompare.exe from Atlassian SourceTree by using the application found here: [https://github.com/smithed/vicompare VI Compare].
Set up SourceTree using the steps below.
{| class="wikitable"
|-
| Go To Tools>>Options ||
[[File:Tools,options.png]]
|-
| Select "Diff". Then Select "Custom" for External Diff Tool and Merge tool ||
[[File:2019-07-29 11h45 51.png]]
|-
| Navigate to the installed executables. Specify <"$LOCAL" "$REMOTE"> for Diff Command Arguments and <"$BASE" "$REMOTE" "$LOCAL" "$MERGED"> for Merge Command Arguments ||
[[File:2019-07-29 11h46 08.png]]
|}

[[Category:SCC]]
[[Category:SVN]]

Diff Teststand

2019-06-26T12:52:18Z

Bryan: Added TortoiseSVN diff settings for TestStand 2014 & 2016 - These may work with other versions but I don't have them to verify.

In order to use a [[Source Code Control Tools|SCC tool]] with [[Teststand|teststand]] sequence files, it's possible to use SeqFileDifferApp.exe deliverd by [[NI|NI]] in the <Teststand>\bin folder. 

For [[TortoiseSVN client to Subversion|TortoiseSVN]] the following settings can be used<ref>http://lavag.org/topic/12386-tortoisesvn-diff-with-teststand-sequences/page__view__findpost__p__74269</ref>:
<pre>"C:\Program Files\National Instruments\TestStand 4.2\Bin\SequenceFileDiffer.exe" %base %mine</pre>

For later versions<ref>Verified with 32-bit versions of TestStand 2014 and 2016.</ref> of (32-bit) TestStand, the following settings can be used for [[TortoiseSVN client to Subversion|TortoiseSVN]]:
<pre>"C:\Program Files (x86)\National Instruments\shared\TestStand\FileDifferLauncher.exe" %base %mine</pre>

References/Notes:

[[Category:SCC]]
[[Category:Teststand]]

Linux

2019-03-26T16:26:00Z

Bryan: Corrected link to scientificlinux.org.

[https://en.wikipedia.org/wiki/Linux Linux] is a family of open source software and operating systems with many flavors and distributions available for download online.
==Supported Distributions==
Below is a list of officially supported Linux distributions. The Base version of LabVIEW is not supported on Linux, but Full and Professional versions of LabVIEW are supported.
* [https://www.centos.org/ CentOS] version 7.x
* [https://www.opensuse.org/#Leap OpenSUSE Leap] versions 42.2 and 42.3
* [https://www.redhat.com/en Red Hat Linux] versions 6.x and 7.x
* [https://www.scientificlinux.org/ Scientific Linux]

LabVIEW can be installed on most Red Hat-based Linux distributions, but issues may arise during installation. Installation on Debian-based distributions is more involved and requires more in-depth knowledge of Linux operating systems. Several instructions can be found on the internet for installing LabVIEW on non-supported distributions.
==External Links==
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kG1MSAU&l=en-US NI.com - LabVIEW and Linux Compatibility]
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P7nVSAS&l=en-US NI.com - How to install LabVIEW on Linux]

[[Category:LabVIEW for Linux]]

Alliance program

2019-03-19T13:20:40Z

Bryan: Added external link to NI Alliance Partner Directory link on NI.com;

The National Instruments Alliance Partner Program is a business development relationship between National Instruments and other companies that can provide the technical expertise and know-how to offer products, services, and systems complementary to NI products.

The program includes business relationships between NI and more than 500 consultants, system integrators and developers worldwide. The program combines the wide variety of NI measurement and automation products with the specific industry expertise of consultants and systems integrators. NI Alliance Partners educate customers, make product recommendations, help customers meet short development schedules, provide turnkey systems and develop and market specialized add-on packages based on NI software and hardware.

The NI Alliance Partner program has three levels – Associate, Certified and Select.

== See also ==
*[[list of alliance program partner companies]]
== External links ==
*[http://www.ni.com/alliance/ Alliance program details on ni.com]
*[https://partners.ni.com/directory/ Alliance partner directory on ni.com]

Alliance program

2019-03-19T12:38:10Z

Bryan: Added external link to NI Alliance Directory on NI.com

LabVIEW Learning Materials

2019-03-13T10:49:34Z

Bryan: Removed dead links where updated URLS couldn't be found.

{{see also|category:LabVIEW fundamentals}}
==Learning LabVIEW ==
Many useful learning resources are available for LabVIEW: online help, online reference manuals, and LabVIEW code examples. Articles, ready made applications, and technical notes are available on the [[National Instruments]] Web site and in the [http://zone.ni.com NI Developer Zone].

===Formal Training===
Formal training on LabVIEW is available from several providers. Offerings differ based on prior LabVIEW experience level and the preferred delivery method. Common delivery methods include:

* In-person instructor-led
* Remote instructor-led (usually through a web conference)
* Online self-paced (usually through a combination of pre-recorded lecture videos and exercise solution videos)
* Self-paced with a manual

National Instruments has a [http://sine.ni.com/tacs/app/fp/p/ap/ov/pg/1/sn/n8:28/ suite of courses] ranging from beginner to advanced as well as several specialty topics such as LabVIEW Real-Time and LabVIEW Connectivity. National Instruments offers all common delivery methods mentioned above except online self-paced. Other LabVIEW training providers such as [http://www.sixclear.com/ Sixclear] provide this online self-paced environment. Sixclear's same curriculum is also delivered through in-person instructor-led training. [http://www.durability.com/Divisions/Automation/Training/LabVIEW101.asp Durability] is another provider of in-person instructor-led training.

Recommended training courses for those with no knowledge of LabVIEW are the [http://sine.ni.com/tacs/app/fp/p/ap/ov/pg/1/sn/n8:28/ National Instruments Core 1 and Core 2] courses, the [http://www.sixclear.com/labviewtraining/ Sixclear LabVIEW Fundamentals I and II] courses, or the [http://www.durability.com/Divisions/Automation/Training/LabVIEW101.asp Durability LabVIEW 101 and 102] courses. All sets of courses are geared to a user with little to no LabVIEW experience and teach the proficiencies outlined by the [http://sine.ni.com/nips/cds/view/p/lang/en/nid/14438 Certified LabVIEW Associate Developer (CLAD)] exam as well as simple DAQ and instrument control.

Common arguments justifying formal training revolve around the idea that the sum cost of developers' time is greater than the cost of training because:
* the LabVIEW graphical programming paradigm is appreciably different than traditional text-based programming
* costly mistakes commonly occur when moving from simple LabVIEW applications to more complex applications, especially when developing parallel loop applications

===Alternatives to Formal Training===

National Instruments maintains a list of [http://www.ni.com/reference/books/labview.htm LabVIEW reference books] as an alternative to formal training.

Another alternative to formal training are half-day "LabVIEW Hands-On" workshops offered by National Instruments. Recommended follow-ups are the "G Programmer's reference manual" and the LabVIEW "User Manual" found in the LabVIEW documentation.

== External Links ==

Some online tutorials:

*[http://blog.sixclear.com/ VI High LabVIEW Video Tutorial Blog by Sixclear]
*[http://www.ni.com/labview/skills-guide/en/ Some NI courses, including videos] (requires an active support contract with NI)
*[http://vishots.com/category/labview-tutorials/ VI Shots LabVIEW Video Tutorials]
*NI Tutorials (including videos and exercises) - http://zone.ni.com/devzone/cda/tut/p/id/7466
*More links at NI's site - http://www.ni.com/training/labview.htm
*Software Engineering with LabVIEW (generally requires some LabVIEW knowledge) - http://zone.ni.com/devzone/cda/tut/p/id/7117
*Connexions Tutorial (written by NI) - http://cnx.org/content/col10241/latest/
*LabVIEW Tutorials - http://www.upscale.utoronto.ca/GeneralInterest/LabView.html
*Videos of NI's LabVIEW Core 3 course (8 full lessons) - http://www.youtube.com/playlist?list=PL3E1DD4C18D357331
*Tutorial videos (some are free) - http://www.fafiles.com/
*Learning LabVIEW - http://learnlabview.blogspot.com/
*LabVIEW Tutorial Basics (BEKA, German) - http://www.fu-net.de/lv/lv01/
*LabVIEW Tutorial Advanced Techniques (BEKA, German) - http://www.fu-net.de/lv/lv02/

[[Category:LabVIEW fundamentals]]

Diff LabVIEW

2019-03-12T10:46:37Z

Bryan: Expanded to include LVCompare settings based on LabVIEW vs Windows OS bitness.

In order to use a [[Source Code Control Tools|SCC tool]] with [[LabVIEW|LabVIEW]] files directly from the Windows Explorer, [http://www.altap.cz Altap Salamander] or similar file browser, it's possible to use LVCompare.exe deliverd by [[NI|NI]] in the <LabVIEW>\Shared folder. For [[TortoiseSVN client to Subversion|TortoiseSVN]] the following settings can be used for both LabVIEW VIs (Extension: .vi) or Controls (Extension: .ctl):

(TortoiseSVN -> Settings -> Diff Viewer -> Advanced -> Add...)

If running 32-bit LabVIEW under 64-bit Windows:
<pre>Filename/Extension: .vi
Program: "C:\Program Files (x86)\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" -nobdcosm -nobdpos %mine %base</pre>

If running 32-bit LabVIEW under 32-bit Windows or 64-bit LabVIEW under 64-bit Windows:
<pre>Filename/Extension: .vi
Program: "C:\Program Files\National Instruments\Shared\LabVIEW Compare\LVCompare.exe" -nobdcosm -nobdpos %mine %base</pre>

[[Category:SCC]]

LVM File Extension

2019-03-11T13:59:14Z

Bryan: Undo revision 6770 by Bryan (talk)

The '''LVM File Extension''' (''*.lvm''), or LabVIEW Measurement File, is a text-based file format for one-dimensional data that is used with the [[Read LabVIEW Measurement File]] and [[Write LabVIEW Measurement File]] Express VIs. The ''.lvm'' file is designed so it is easy to parse and easy to read when imported into a spreadsheet program, such as Microsoft Excel, or a text editor, such as Notepad. It supports multiple data sets, grouping of data sets, and the addition of data sets to existing files. The file format is not designed for high-performance or for very large data sets, as is the case with all text-based formats.

See [[LabVIEW Measurement File]].

==See Also==
*[[Technical Data Management File]]

[[Category:LabVIEW file extensions]]

LVM File Extension

2019-03-11T13:58:10Z

Bryan: Undo revision 6769 by Bryan (talk)

The '''LVM File Extension''' (''*.lvm''), or LabVIEW Measurement File, is a text-based file format for one-dimensional data that is used with the [[Read LabVIEW Measurement File]] and [[Write LabVIEW Measurement File]] Express VIs. The ''.lvm'' file is designed so it is easy to parse and easy to read when imported into a spreadsheet program, such as Microsoft Excel, or a text editor, such as Notepad. It supports multiple data sets, grouping of data sets, and the addition of data sets to existing files. The file format is not designed for high-performance or for very large data sets, as is the case with all text-based formats.

See [[LabVIEW Measurement File]].

==See Also==
*[[TDM_File_Extension|Technical Data Management File]]

[[Category:LabVIEW file extensions]]

LVM File Extension

2019-03-11T13:26:47Z

Bryan: Removed previously created link to TDM file extension - I don't think the .TDM extension was supposed to be the intent.

LVM File Extension

2019-03-11T13:23:34Z

Bryan: Updated link to TDM File Extension

The '''LVM File Extension''' (''*.lvm''), or LabVIEW Measurement File, is a text-based file format for one-dimensional data that is used with the [[Read LabVIEW Measurement File]] and [[Write LabVIEW Measurement File]] Express VIs. The ''.lvm'' file is designed so it is easy to parse and easy to read when imported into a spreadsheet program, such as Microsoft Excel, or a text editor, such as Notepad. It supports multiple data sets, grouping of data sets, and the addition of data sets to existing files. The file format is not designed for high-performance or for very large data sets, as is the case with all text-based formats.

See [[LabVIEW Measurement File]].

==See Also==
*[[TDM_File_Extension|Technical Data Management File]]

[[Category:LabVIEW file extensions]]

[[Category:LabVIEW file extensions]]

Virtual Instrument

2019-03-06T12:03:46Z

Bryan: Added link to VI Icons.

The '''VI''', or Virtual Instrument, is the basic building block of programs written in the [[G]] Language. It is similar to a function or subroutine in other programming languages. It includes the [[Front Panel]] (containing [[Controls]] and [[Indicators]]), the [[Block Diagram]] (containing Control Terminals, Wires, and Structures and various other [[GObject]] nodes), the VI's [[Icon]] and its [[Connector Pane]] (as well as compiled executable code which is hidden behind the scenes).

The term Virtual Instrument is a play off of the fact that LabVIEW applications are designed for writing software that simulates the functionality of instruments -- rather than being a physical instrument on a laboratory bench, they are virtual and exist in software.

==The VI File Format==
VIs are saved as ''*.vi'' files in a proprietary binary format defined by [[National Instruments]], the makers of [[LabVIEW]]. By default, a VI contains two kinds of code: the graphical source code that you edit and a compiled version of this code that LabVIEW uses to run the VI.

The graphical source code includes the:
*[[Front Panel]]
*[[Block Diagram]]
*[[Connector Pane]]
*[[VI_Icons|Icon]]

The compiled version includes the:
*[[Compiled Code]]
*[[Inplaceness Information]]

When you edit the source code of the VI, LabVIEW automatically recompiles the VI to reflect your changes in the compiled version of the code. LabVIEW also automatically recompiles all VIs that call the changed VI, resulting in unsaved changes to the calling VIs. If the calling VIs are stored in [[Source Code Control|source code control]], these pending unsaved changes force you to check out the VIs when you update their subVIs.

To avoid this problem, Starting in [[LabVIEW 2010]], [[LabVIEW]] allows you to separate compiled code from the graphical source code of a VI, thereby creating source-only VIs. After you separate the compiled code from a VI, LabVIEW still compiles the VI when you modify subVIs. However, LabVIEW stores the recompiled version of the code in a [[Compiled Object Cache|compiled object cache]] rather than in the VI in [[Source Code Control|source code control]]. Because the VI in [[Source Code Control|source code control]] does not change, you no longer have to check the VI out of source control when you change subVIs.

==See Also==
*[[Separating Compiled Code]]
*[[NI LabVIEW Compiler]]

[[Category:LabVIEW fundamentals]]
[[Category:LabVIEW fundamentals]]

[[Category:LabVIEW fundamentals]]

CTL File Extension

2019-03-05T11:48:08Z

Bryan: Added links to Type Def and Strict Type Def articles.

The '''CTL File Extension''' (''*.ctl''), or Control, is the file extension of LabVIEW controls or type definitions. Controls are stored either ''in'' their parent [[VI]] or in these dedicated files. When created in a ''.ctl'' file the control can be customized and be assigned special behavior: [[Type Definition]] or [[Strict Type Definition]].

See [[Control]].

[[Category:LabVIEW file extensions]]

Fun stuff

2019-03-04T16:31:23Z

Bryan: Removed internal link that was deleted back in 2013.

*[[Project management tarot deck for the G programmer]]
*[[Labtoons]]

[[Category:LabVIEW ecosystem]]

Linux

2019-02-25T11:43:19Z

Bryan: Added Scientific Linux and sorted lists in alphabetical/logical order.

[https://en.wikipedia.org/wiki/Linux Linux] is a family of open source software and operating systems with many flavors and distributions available for download online.
==Supported Distributions==
Below is a list of officially supported Linux distributions. The Base version of LabVIEW is not supported on Linux, but Full and Professional versions of LabVIEW are supported.
* [https://www.centos.org/ CentOS] version 7.x
* [https://www.opensuse.org/#Leap OpenSUSE Leap] versions 42.2 and 42.3
* [https://www.redhat.com/en Red Hat Linux] versions 6.x and 7.x
* [https://https://www.scientificlinux.org/ Scientific Linux]

LabVIEW can be installed on most Red Hat-based Linux distributions, but issues may arise during installation. Installation on Debian-based distributions is more involved and requires more in-depth knowledge of Linux operating systems. Several instructions can be found on the internet for installing LabVIEW on non-supported distributions.
==External Links==
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kG1MSAU&l=en-US NI.com - LabVIEW and Linux Compatibility]
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P7nVSAS&l=en-US NI.com - How to install LabVIEW on Linux]

[[Category:LabVIEW for Linux]]

Category:LabVIEW for Linux

2019-02-22T15:24:02Z

Bryan: Created page with "Articles in category "LabVIEW for Linux""

Articles in category "LabVIEW for Linux"

Linux

2019-02-22T15:23:45Z

Bryan: Updated Category

[https://en.wikipedia.org/wiki/Linux Linux] is a family of open source software and operating systems with many flavors and distributions available for download online.
==Supported Distributions==
Below is a list of officially supported Linux distributions. The Base version of LabVIEW is not supported on Linux, but Full and Professional versions of LabVIEW are supported.
* [https://www.redhat.com/en Red Hat Linux] versions 6.x and 7.x
* [https://www.centos.org/ CentOS] version 7.x
* [https://www.opensuse.org/#Leap OpenSUSE Leap] versions 42.2 and 42.3

LabVIEW can be installed on most Red Hat-based Linux distributions, but issues may arise during installation. Installation on Debian-based distributions is more involved and requires more in-depth knowledge of Linux operating systems. Several instructions can be found on the internet for installing LabVIEW on non-supported distributions.
==External Links==
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P7nVSAS&l=en-US NI.com - How to install LabVIEW on Linux]
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kG1MSAU&l=en-US NI.com - LabVIEW and Linux Compatibility]

[[Category:LabVIEW for Linux]]

Linux

2019-02-22T15:19:48Z

Bryan: Updated and partially rewritten.

[https://en.wikipedia.org/wiki/Linux Linux] is a family of open source software and operating systems with many flavors and distributions available for download online.
==Supported Distributions==
Below is a list of officially supported Linux distributions. The Base version of LabVIEW is not supported on Linux, but Full and Professional versions of LabVIEW are supported.
* [https://www.redhat.com/en Red Hat Linux] versions 6.x and 7.x
* [https://www.centos.org/ CentOS] version 7.x
* [https://www.opensuse.org/#Leap OpenSUSE Leap] versions 42.2 and 42.3

LabVIEW can be installed on most Red Hat-based Linux distributions, but issues may arise during installation. Installation on Debian-based distributions is more involved and requires more in-depth knowledge of Linux operating systems. Several instructions can be found on the internet for installing LabVIEW on non-supported distributions.
==External Links==
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P7nVSAS&l=en-US NI.com - How to install LabVIEW on Linux]
* [https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000kG1MSAU&l=en-US NI.com - LabVIEW and Linux Compatibility]

[[Category:Linux]]

TortoiseSVN client to Subversion

2019-02-22T14:03:22Z

Bryan: Updated link to JKI's blog announcement for TSVN tool.

TortoiseSVN is a free Subversion client integrated as a Windows shell extension. [http://tortoisesvn.net/]

After downloading and installing TortoiseSVN, one can: [[Point to an existing repository]] [[Add a directory to the repository]] [[Configure TortoiseSVN to work with LabVIEW]]

 

JKI has released a [https://blog.jki.net/news/announcing-tortoisesvn-tool-for-labview-v2-2-0 TortoiseSVN Tool for LabVIEW] that helps integrate TortoiseSVN with typical LabVIEW workflows.

[[Category:SCC]]
[[Category:SVN]]

Functions Palette/Programming/Synchronization/Queue Operations

2019-02-21T17:33:59Z

Bryan: Main part was taken from NI.com. Added image and additional text from/link to NI.com knowledge base article on queues from which the original wording came.

==Location in palette==
Functions >> Synchronization >> Queue Operations
[[File:QueuePalette.png|thumb|Queue Operations Palette]]
==Concept==
(From [http://www.ni.com NI.com])

A queue maintains a first in/first out (FIFO) order of data items. For instance, the customers waiting in line at a fast food restaurant are in a queue.

A queue is useful in producer/consumer situations, where one portion of code is creating data to be used by another portion. The advantage of using a queue is that the producer and consumer rates do not have to be identical. If consumption is slower than production, the queue will become full and the producer code will be forced to wait until the consumer has dequeued an element before a new element can be queued up.

Unlike an array, it is not possible to randomly access elements in a queue. It is strictly a buffer that provides you the ability to enqueue (add/insert) and dequeue (subtract/remove) elements. The only way to view all the elements in a queue is to dequeue them one by one. You cannot perform data manipulation to all the elements in a queue either.
==Example use cases==
[[Queued_State_Machine|Queued State Machines]] (Also known as Queue Driven State Machines, or QDSMs).
==External Links==
#[https://knowledge.ni.com/KnowledgeArticleDetails?id=kA00Z000000P7OfSAK&l=en-US NI.com - What Is a Queue]

[[Category:Synchronization]]
[[Category:Synchronization]]

File:QueuePalette.png

2019-02-21T17:14:18Z

Bryan:

Queue Operations Palette

Use svn directories

2019-02-20T11:54:22Z

Bryan: Changed steps to numbered list. Added deprecation info on feature.

Use "_svn" directories instead of ".svn" directories so that LabVIEW doesn't index the directories when building up palettes.

== How to use _svn directories ==
'''Note:''' As of version 1.4.0 and later, the setting below is no longer available via TortoiseSVN >> Settings. However, an alternative method, (also known as the SVN_ASP_DOT_NET_HACK) is described in TortoiseSVN's release notes located [https://tortoisesvn.net/docs/release/TortoiseSVN_en/tsvn-admins-aspdotnethack.html here].

#Open Windows explorer.
#Right click on a directory and select "TortoiseSVN...Settings" from the pop-up menu.
#On the "General" page in the "Settings - Tortoise SVN" dialog check the "Use '_svn' instead of '.svn' directories" box.
#Click OK.
#TortoiseSVN will prompt you to restart the computer.

[[Category:SCC]]
[[Category:SVN]]

For loop

2019-02-04T12:42:56Z

Bryan:

[[File:ForLoop.PNG|thumb|For Loop - Will execute "your code" ten times.]]
[[File:ForLoop Indexing.png|thumb|For Loop With Indexed Input - Will execute "your code" ten times.]]
[[File:ForLoop Indexing Conditional.png|thumb|For Loop With Conditional Terminal - Will execute until first TRUE element, which would be at index 4. The remaining elements will not be indexed.]]
== Using a For Loop ==
The LabVIEW For Loop is a structure that will execute code contained within a finite number of times. The number of times that the loop will execute is initially determined by the numeric value written to the "N" terminal of the loop, or by the size of an array wired as an input to the loop (when indexing is enabled for the input tunnel). The latter method of specifying the number of iterations is similar to the For-Each structure in many text-based programming languages.

Outputs from a For Loop will be an array by default unless alternate behavior for the tunnel is selected by right-clicking on the tunnel and selecting a behavior under "Tunnel Mode".

== How do I stop a For Loop? ==
In earlier versions of LabVIEW, there was no way to stop the execution of a For Loop until the requisite number of iterations have been met. In those earlier LabVIEW versions, a [[While Loop]] would have to be used, in addition to having input and/or output tunnels with indexing enabled.

In later versions of LabVIEW, a conditional terminal was made available to For Loop, which functions similar to that which is used in a [[While Loop]]. The conditional terminal can be made visible by right-clicking on the border of a For Loop and selecting "Conditional Terminal". This conditional terminal is useful if a condition has been met that would make further iterations of the loop unnecessary. A simple example of this could be if indexing a 10 element array in search of a particular value, then finding the desired value at the fourth element. The loop could then be stopped without having to continue to iterate through the remaining elements.

== Why doesn't my For Loop return a value? ==
As a good programming rule in LabVIEW, NEVER output a value from a For Loop with indexing disabled. When the loop does not execute (0 iteration) a non indexing output stays undefined and will hold any garbage left there by previous memory usage. This is because the wire output from the For Loop has no code or data source to get the value from when the loop does not execute. Instead, use a shift register (SR) to output the value and at the left SR enter a default value for the case when the loop does not execute. When the For Loop does not execute this default value of the left SR is passed to the right SR. Similarly passing a [[Refnum]] through a For Loop that never executes (0 iterations) destroys the reference. Either pass the reference using a SR as described above or wire around the loop. Note that [[While Loop]] always execute at least once so the outputs are always defined.

== External Links ==
[http://www.ni.com/white-paper/7588/en/ NI.com Tutorial on For Loops and While Loops]

[[Category:Structures]]

Talk:For loop

2019-02-04T12:37:27Z

Bryan:

I think adding some images to this page would help.--[[User:MichaelAivaliotis|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis|talk]]) 05:27, 2 February 2019 (UTC)

I added three images with descriptions in the captions as well as a link to NI's page on For and While loops for additional information.--[[User:Bryan|Bryan]] ([[User talk:Bryan|talk]]) 12:37, 4 February 2019 (UTC)

For loop

2019-02-04T12:29:44Z

Bryan: Added images and an external link to NI's tutorial on While and For Loops.

[[File:ForLoop.PNG|thumb|For Loop (Will execute "your code" ten times.)]]
[[File:ForLoop Indexing.png|thumb|For Loop With Indexed Input (Will execute "your code" ten times.)]]
[[File:ForLoop Indexing Conditional.png|thumb|For Loop With Conditional Terminal (Will execute until first TRUE element, which would be at index 4.)]]
== Using a For Loop ==
The LabVIEW For Loop is a structure that will execute code contained within a finite number of times. The number of times that the loop will execute is initially determined by the numeric value written to the "N" terminal of the loop, or by the size of an array wired as an input to the loop (when indexing is enabled for the input tunnel). The latter method of specifying the number of iterations is similar to the For-Each structure in many text-based programming languages.

Outputs from a For Loop will be an array by default unless alternate behavior for the tunnel is selected by right-clicking on the tunnel and selecting a behavior under "Tunnel Mode".

== How do I stop a For Loop? ==
In earlier versions of LabVIEW, there was no way to stop the execution of a For Loop until the requisite number of iterations have been met. In those earlier LabVIEW versions, a [[While Loop]] would have to be used, in addition to having input and/or output tunnels with indexing enabled.

In later versions of LabVIEW, a conditional terminal was made available to For Loop, which functions similar to that which is used in a [[While Loop]]. The conditional terminal can be made visible by right-clicking on the border of a For Loop and selecting "Conditional Terminal". This conditional terminal is useful if a condition has been met that would make further iterations of the loop unnecessary. A simple example of this could be if indexing a 10 element array in search of a particular value, then finding the desired value at the fourth element. The loop could then be stopped without having to continue to iterate through the remaining elements.

== Why doesn't my For Loop return a value? ==
As a good programming rule in LabVIEW, NEVER output a value from a For Loop with indexing disabled. When the loop does not execute (0 iteration) a non indexing output stays undefined and will hold any garbage left there by previous memory usage. This is because the wire output from the For Loop has no code or data source to get the value from when the loop does not execute. Instead, use a shift register (SR) to output the value and at the left SR enter a default value for the case when the loop does not execute. When the For Loop does not execute this default value of the left SR is passed to the right SR. Similarly passing a [[Refnum]] through a For Loop that never executes (0 iterations) destroys the reference. Either pass the reference using a SR as described above or wire around the loop. Note that [[While Loop]] always execute at least once so the outputs are always defined.

== External Links ==
[http://www.ni.com/white-paper/7588/en/ NI.com Tutorial on For Loops and While Loops]

[[Category:Structures]]

File:ForLoop Indexing Conditional.png

2019-02-04T12:26:31Z

Bryan:

For Loop showing usage of available conditional terminal.

File:ForLoop Indexing.png

2019-02-04T12:24:03Z

Bryan:

For Loop with indexed input.

File:ForLoop.PNG

2019-02-04T12:10:52Z

Bryan: Category:Structures

== Summary ==

[[Category:Structures]]

For loop

2019-01-30T17:53:22Z

Bryan: Rewritten to provide additional information on For Loops, behavior and ways of stopping executions in later LabVIEW versions.

== Using a For Loop ==
The LabVIEW For Loop is a structure that will execute code contained within a finite number of times. The number of times that the loop will execute is initially determined by the numeric value written to the "N" terminal of the loop, or by the size of an array wired as an input to the loop (when indexing is enabled for the input tunnel). The latter method of specifying the number of iterations is similar to the For-Each structure in many text-based programming languages.

Outputs from a For Loop will be an array by default unless alternate behavior for the tunnel is selected by right-clicking on the tunnel and selecting a behavior under "Tunnel Mode".

== How do I stop a For Loop? ==
In earlier versions of LabVIEW, there was no way to stop the execution of a For Loop until the requisite number of iterations have been met. In those earlier LabVIEW versions, a [[While Loop]] would have to be used, in addition to having input and/or output tunnels with indexing enabled.

In later versions of LabVIEW, a conditional terminal was made available to For Loop, which functions similar to that which is used in a [[While Loop]]. The conditional terminal can be made visible by right-clicking on the border of a For Loop and selecting "Conditional Terminal". This conditional terminal is useful if a condition has been met that would make further iterations of the loop unnecessary. A simple example of this could be if indexing a 10 element array in search of a particular value, then finding the desired value at the fourth element. The loop could then be stopped without having to continue to iterate through the remaining elements.

== Why doesn't my For Loop return a value? ==
As a good programming rule in LabVIEW, NEVER output a value from a For Loop with indexing disabled. When the loop does not execute (0 iteration) a non indexing output stays undefined and will hold any garbage left there by previous memory usage. This is because the wire output from the For Loop has no code or data source to get the value from when the loop does not execute. Instead, use a shift register (SR) to output the value and at the left SR enter a default value for the case when the loop does not execute. When the For Loop does not execute this default value of the left SR is passed to the right SR. Similarly passing a [[Refnum]] through a For Loop that never executes (0 iterations) destroys the reference. Either pass the reference using a SR as described above or wire around the loop. Note that [[While Loop]] always execute at least once so the outputs are always defined.

[[Category:Structures]]

[[Category:Structures]]

Strict Type Definition

2019-01-25T12:14:34Z

Bryan: Updated link to NI URL for TypDefs and their creation to match same format as was used on TypeDef LabVIEW Wiki page.

A strict type definition [STD] is like a [[Type Definition|type definition]] with well-defined appearance.

<center>[[Image:Type_Def_Status.png]]</center>

Well-defined appearance means that all instances of STD's share the appearance of that STD, e.g. their properties cannot be changed (except of label, caption and enable-state).

This is handy whenever the size, color etc. needs to be fixed. Think of sophisticated screen designs or stacked STDs. STDs are created by saving as this type of control - similar to 'simple' type definitions.

==See Also==
* [[Type Definition]]

==External Links==
* [http://zone.ni.com/reference/en-XX/help/371361B-01/lvhowto/creating_type_defs/ Creating Type Definitions and Strict Type Definitions]

[[Category:user interface]]

[[Category:User interface]]

User:Bryan

2019-01-25T12:07:44Z

Bryan: Created page with "[https://lavag.org/profile/404-bryan/ Profile on LAVA]"

[https://lavag.org/profile/404-bryan/ Profile on LAVA]

VI Icon

2019-01-21T11:56:26Z

Bryan: Typo correction, "LabVIEW" capitalization, and addition of text regarding icon images and sharing across spoken languages.

{{update}}

== VI Icon Importance ==
The icon you use to represent your subVI can tell you or other developers a lot about what the subVI does without ever having to open the subVI. Taking the time to create at least simple text VI icon is a requirement when sharing code between developers. The use of images in VI icons can also enhance their meaning when text can't be used because of length or in cases where code is shared across different spoken languages. National Instruments keeps an [http://www.ni.com/devzone/idnet/library/icon_art_glossary.htm Icon Art Glossary] to help developers who are less experienced making easy to recognize icons.

== How to Make icons smaller than the entire square ==
Sometimes it is desirable to make a LabVIEW subVI's icon smaller than the normal 32x32 pixels. National Instruments has done this with several primitives and has made it possible for end users to make custom icons of any size for a subVI. It is good practice to ensure that terminals used line up logically with the borders of the smaller VI created.

Starting with a typical icon editor 
[[Image:Typical_icon_editor.png]] 
 
Clear the default icon from the 256 icon, then click on the "Show Terminals" checkbox. Draw a box, around the terminals you wish to have displayed on your custom icon. 
[[Image:Icon_editor_with_small_icon.png]] 
Fill the 256 color icon with a color of your choice, as well as any words or symbols you wish to use to describe your subVI's work, then copy the subVI to the black and white icon by selecting the black and white icon and pressing the copy from 256 color button on the right. 
[[Image:Icon_editor_with_all_small_icons.png]] 

You can even make irregularly shaped icons. The white area outside will be transparent in your diagrams. Interestingly, if the border you define is not contiguous, the inside of your icon will also be transparent (you can see a wire go all the way to its connection point (visible as a little cross in the "show terminals" icon view). You can actually have multiple non-transparent areas in your icons if you wish.

== Other icon tricks ==
===Double Click===
There are certain tools in the icon editor that are "double-clickable". Double clicking on the selection, filled box, and empty box tool icons in the editing palette will apply that tool to the entire icon square. Double clicking on the font tool will bring up a font dialog for selecting font name, size, color, justification, and style (bold, italics, etc).

[[Image:Double_Clickable_Icon_Editor_tools.png]]

===Move text===
While typing a text into the Icon Editor the text is movable by using the arrow keys on the keyboard.

== Alternative Icon Editors ==
As of LabVIEW 8.0 a custom icon editor could be built and called from LabVIEW to edit icons of VIs. The relevant information to replace the built in VI icon editor is available [http://forums.lavag.org/index.php?s=&showtopic=3320&view=findpost&p=12920 here].

[[Category:LabVIEW fundamentals]]
[[Category:Calling a VI]]

LabVIEW object-oriented programming

2019-01-21T11:43:04Z

Bryan: Added definition for LVOOP.

LVOOP (pronounced "el vee oop") is the native implementation of by-value object orientated programming that appeared in LabVIEW 8.20. LVOOP stands for '''L'''ab'''V'''IEW '''O'''bject '''O'''riented '''P'''rogramming.

*See the [[LVOOP Frequently Asked Questions]] page, here on the LabVIEW Wiki
*NI has a comprehensive LabVIEW Object-Oriented Programming FAQ for their native LVOOP (native by-value OOP) [http://zone.ni.com/devzone/cda/tut/p/id/3573 here]. It includes links to many other online resources, including the NI Week presentations that the NI R&D team have given to customers.
*There are multiple example programs that ship with LV. They are located in <labview>exampleslvoop
*The National Instruments LVOOP FAQ references the [http://zone.ni.com/devzone/cda/tut/p/id/3574 LVOOP White Paper] several times. If you're an experienced LabVIEW developer, you'll probably enjoy it more than other forms of documentation.
*Christina Rogers (National Instruments R&D) has some excellent discussion about refactoring code, specifically the Getting Started Window, to use LabVIEW classes. See her blog at [http://eyesonvis.blogspot.com/ http://eyesonvis.blogspot.com/] and look at the posts in August 2006.
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=216094&requireLogin=False The LVOOP Design Patterns] is a work-in-progress that [http://forums.lavag.org/Aristos-Queue-m5877.html Aristos Queue] (National Instruments R&D) is working on to help new LVOOP customers choose architectures appropriate to different types of software projects.

== See Also ==
*[http://www.ni.com/white-paper/3573/en/ NI White Paper: LabVIEW Object-Oriented Programming FAQ]
*[http://www.ni.com/white-paper/3574/en/ NI White Paper: LabVIEW Object-Oriented Programming: The Decisions Behind the Design]

[[Category:GOOP]]
[[Category:GOOP]]
[[Category:GOOP]]
[[Category:GOOP]]
[[Category:GOOP]]

[[Category:GOOP]]

LabVIEW object-oriented programming

2019-01-18T12:04:52Z

Bryan: Added references to some NI Whitepapers on LVOOP

LVOOP (pronounced "el vee oop") is the native implementation of by-value object orientated programming that appeared in LabVIEW 8.20.

*See the [[LVOOP Frequently Asked Questions]] page, here on the LabVIEW Wiki
*NI has a comprehensive LabVIEW Object-Oriented Programming FAQ for their native LVOOP (native by-value OOP) [http://zone.ni.com/devzone/cda/tut/p/id/3573 here]. It includes links to many other online resources, including the NI Week presentations that the NI R&D team have given to customers.
*There are multiple example programs that ship with LV. They are located in <labview>exampleslvoop
*The National Instruments LVOOP FAQ references the [http://zone.ni.com/devzone/cda/tut/p/id/3574 LVOOP White Paper] several times. If you're an experienced LabVIEW developer, you'll probably enjoy it more than other forms of documentation.
*Christina Rogers (National Instruments R&D) has some excellent discussion about refactoring code, specifically the Getting Started Window, to use LabVIEW classes. See her blog at [http://eyesonvis.blogspot.com/ http://eyesonvis.blogspot.com/] and look at the posts in August 2006.
*[http://forums.ni.com/ni/board/message?board.id=170&message.id=216094&requireLogin=False The LVOOP Design Patterns] is a work-in-progress that [http://forums.lavag.org/Aristos-Queue-m5877.html Aristos Queue] (National Instruments R&D) is working on to help new LVOOP customers choose architectures appropriate to different types of software projects.

== See Also ==
*[http://www.ni.com/white-paper/3573/en/ NI White Paper: LabVIEW Object-Oriented Programming FAQ]
*[http://www.ni.com/white-paper/3574/en/ NI White Paper: LabVIEW Object-Oriented Programming: The Decisions Behind the Design]

[[Category:GOOP]]

LabVIEW object-oriented programming FAQ

2019-01-18T12:01:56Z

Bryan: Added definition for acronym.

This is a stub page for Frequently Asked Questions (FAQ) about LVOOP. Please feel free to add to the list of FAQ and answer any of the questions that have been posted.

You may find many questions already answered on the [http://zone.ni.com/devzone/cda/tut/p/id/3573 LVOOP FAQ on NI's website]. That FAQ will be updated by NI for new versions of LabVIEW and new OO tools as they become available.

== Why is class data private? ==

In general object-oriented programming terms, attributes (like methods) can have private, protected, or public visibility. In practice individual object-oriented programming languages have differing capabilities when it comes to specifying visibility. In the UML attributes are generally assumed to have private visibility unless otherwise specified. (Operations, on the other hand, are assumed to be public unless otherwise specified.) Generally, OOP style guides say never to give attributes public visibility, and the so-called “Law of Demeter” in its strong form limits attribute visibilities to private. In other words, access to data in a class from outside the class is always through accessor methods (‘set’ or ‘get’) methods. In LVOOP this is the only choice, a decision designed to promote good code designs with minimal coupling. (See further here: [http://zone.ni.com/devzone/cda/tut/p/id/3574]). (Note that LabVIEW 8.5 introduces a “Create Accessor” dialog box to simplify the creation of accessor methods. For more information on this dialog box see the LabVIEW 8.5 Upgrade Notes here: [http://digital.ni.com/manuals.nsf/websearch/7A60FDCEA6D2D8C4862572FD00159F5A].)

== What are the differences between public, protected, and private class members? ==

In Object-Oriented Programming terms these generally mean:

A private feature (UML abbreviation -) is accessible only from the defining class. A public feature (+) is accessible from outside the class. A protected feature (#) is (in C++, for example) accessible from the defining class and any of its child classes. The UML also has an abbreviation for package (~) visibility. The exact meaning of the different visibilities varies among different programming languages.

In 2009 LabVIEW introduced ''Community'' scoping to classes (and other project libraries.) Community scoped items are the same as private items, except they are visible to external entities specifically designated as "Friends of This Library." Some important things to keep in mind with community scoping are:

* Friendship is a one-way permission granted by a class giving external entities access to community scoped items. If Class A makes Class B a friend, Class B has access to Class A's community scoped items, but Class A does not have access to Class B's community scoped items.

* Child classes are not automatically granted access to a parent's community scoped items.

== Why are there no class constructor and destructor? ==

== Are objects by value or by reference? ==

== What does LVOOP mean? ==
LVOOP (pronounced "el vee oop") stands for '''L'''ab'''V'''IEW '''O'''bject-'''O'''riented '''P'''rogramming.

[[Category:GOOP]]

== How can I create by reference objects? ==

== How can I create active objects? ==

== Are there any add on tools for LVOOP? ==

== What does the "Dynamic Dispatch" connector pane terminal setting do? ==

== My LVOOP class control has a black border, what does that mean ? ==

A LVOOP class has a default value that is determined by the default value of the private data control in the .lvclass file. However, a control on a vi front panel, or a constant on a block diagram can also have a default value that is different from the default data for the class as a whole. When this happens the control (or constant) is given a black border. It can just as easily be a non-default value of the class itself, so if your private data cluster contains a numeric whose default value is 5, this control may have the numeric with a default value of 6.

When there is a class heirarchy, it is possible for a parent class method to process an instance of a child class. Similarily, it is possible to set the default value of a parent class control or constant to be an instance of a child class. This will also result in a black border around the parent class control or constant. When this happens with a member vi of the parent class, the parent class becomes dependent on the child class in addition to the normal dependency of the child on the parent. This can be confusing and awkward to locate.

To change the default value of a class control run a VI such that a non-default value ends up in an indicator, then do one of the following: A) Right click on that indicator and choose "Make Current Value Default" or B) Right click on that indicator and choose "Change to Constant" (the current value of a control/indicator always becomes the value of the constant)

[[Category:GOOP]]

Application builder

2019-01-10T15:24:35Z

Bryan: SouthPaw moved page Application builder to Application Builder: Capitalization of "Builder"

#REDIRECT [[Application Builder]]

Application Builder

2019-01-10T15:24:34Z

Bryan: SouthPaw moved page Application builder to Application Builder: Capitalization of "Builder"

{{TOCnestright}} 

= Introduction =

The application builder (AB) is a part of the LabVIEW Project environment, it has the possibilities to distribute your code in various ways: 

*Executables 
*DLLs 
*Source distributions 
*Web services 
*Installers 

Depending on the LabVIEW version you have one or more of the above options might be missing. 

 

= Manual =

{{Stub}} 

= Advanced =

The application builder has several interesting advanced uses 

== Automatic building ==

You can use a VI inside vi.lib that can build without user interaction. The VI is located in <''vi.lib>\AppBuilder\BuildTargetBuildSpecification.vi''. This VI takes a project path and optionally a build and target name as parameters. 

== Symbolic paths ==

Inside the application builder LabVIEW uses several symbolic paths to have envorinment dependent variables. 

{| cellspacing="1" cellpadding="1" border="1" style="width: 708px; height: 104px;"
|-
! scope="col" | Symbolic path 
! scope="col" | Contents 
! scope="col" | Usage 
|-
| NI_AB_PROJECTNAME 
| Name of the project 
| Automatically place the build in a folder that is named after the project 
|-
| NI_AB_TARGETNAME 
| Name of the (Real-Time) target 
| 
|}

 

 

 

[[Category:Building executables]]

Invoke Node

2019-01-10T12:22:20Z

Bryan:

The '''Invoke Node''' is used to perform a method on a VI using [[VI Server]], very similar to the [[Call By Reference]] Node. '''Invoke Node''', however, does not need a strictly typed reference and as such is not bound to the VI's connector pane and is free to call '''any VI'''. On the other hand, as the connector pane of the callee is unknown at editing time, one must use several calls to '''Invoke Node''' in order to set control values, run the VI and retrieve its results. 
When using the '''Invoke Node''' it is very common to stumble upon an error:
== VI is not in appropriate state for the invoke node ==
This is a known behaviour, but I wouldn't call it an error. It's just how LabVIEW works. A lot of the methods for a VI reference can not be executed for VIs which are either in a reserved state or already running. When a VI is running is rather obvious but a reserved state means that the VI is either part of a running hierarchy of VIs (usually your application) or a strict typedefed VI reference is open to it. The reasons for this are not so simple but it comes down to protecting the VI from influences from different caller types. The Run method of the '''Invoke Node''' (amongst others) is asynchronous as it starts the VI but not necessarily waits for termination of the VI. An implicit reference to the VI as an icon in your block diagram or an explicit one in the form of a strict typedef to be used with the Call by Reference Node are synchronous as far as the caller is concerned.

If you are unable to resolve that error message, you may eventually try to use the Call by Reference Node instead. If you need for whatever reasons to use the Run method you MUST make sure that the VI is not an explicit part of your application by not adding its icon anywhere in your app (and not opening a strict typedefed reference to it either).

[[Category:Application control]]
[[Category:VI Scripting]]
[[Category:VI Server]]

Debugging Executables

2019-01-10T12:19:35Z

Bryan: /* Connecting to the Executable */

{{TOCright}}
Executables created in LabVIEW can be debugged after having been compiled into an executable, (*.exe). However, this is only able to be done if "Enable debugging" was enabled in the build specification when the application was compiled with the LabVIEW [[Application builder]].

= Build Specification Settings =
Under the "Advanced" category in the Build Specification:

* '''Enable debugging'''
** ''Enabled'' - "Builds in" the ability to connect to and debug the application to be compiled. This ability can then be enabled/disabled in the application at any time by modifying the "DebugServerEnabled" key in the [AppName].ini file after it has been compiled.
** ''Disabled'' - Completely disables any ability to connect to and debug the application once built. This ability can not be enabled even if the "DebugServerEnabled" key has been added and set to ''True'' in the [AppName].ini file.

*'''Wait for debugger on launch'''
** ''Enabled'' - If "Enable debugging" has been enabled, the built application can be accessed for debugging, but the application does not automatically run when launched. The application will have to be manually started by clicking on the run arrow.
** ''Disabled'' - The application will begin running immediately when the application is launched when "DebugServerEnabled" is enabled.

= Application Configuration File =
It should be noted that changes to the values of the following keys in the configuration file for the built application will be ignored if "Enable Debugging" was not checked in the [[Application builder]] when compiled.

=== Key/Value Example ===
:DebugServerEnabled=''True''
:DebugServerWaitOnLaunch=''False''

= Connecting to the Executable =
In order to debug an executable that has been compiled with the proper settings (see above), the application must already be launched either on the local computer or on a computer accessible via a network connection.

# In LabVIEW, select the '''Operate''' >> '''Debug Application or Shared Library...'''
# Enter the machine name or IP address of the computer that is running the application. If the application is running on the local machine, enter ''localhost''.
# If the "Application or shared library" drop-down doesn't show the name of the application that you are looking for and the application has been configured properly, click on "Refresh".
# Select the application that you wish to debug and click on "Connect".

At this point, the application should "download" and you should be able to use the LabVIEW debugging tools in the application.

[[Category:Debugging]]

Debugging Executables

2019-01-10T12:18:54Z

Bryan: Slight reformatting and addition of config file key/val pairs.

{{TOCright}}
Executables created in LabVIEW can be debugged after having been compiled into an executable, (*.exe). However, this is only able to be done if "Enable debugging" was enabled in the build specification when the application was compiled with the LabVIEW [[Application builder]].

= Build Specification Settings =
Under the "Advanced" category in the Build Specification:

* '''Enable debugging'''
** ''Enabled'' - "Builds in" the ability to connect to and debug the application to be compiled. This ability can then be enabled/disabled in the application at any time by modifying the "DebugServerEnabled" key in the [AppName].ini file after it has been compiled.
** ''Disabled'' - Completely disables any ability to connect to and debug the application once built. This ability can not be enabled even if the "DebugServerEnabled" key has been added and set to ''True'' in the [AppName].ini file.

*'''Wait for debugger on launch'''
** ''Enabled'' - If "Enable debugging" has been enabled, the built application can be accessed for debugging, but the application does not automatically run when launched. The application will have to be manually started by clicking on the run arrow.
** ''Disabled'' - The application will begin running immediately when the application is launched when "DebugServerEnabled" is enabled.

= Application Configuration File =
It should be noted that changes to the values of the following keys in the configuration file for the built application will be ignored if "Enable Debugging" was not checked in the [[Application builder]] when compiled.

=== Key/Value Example ===
:DebugServerEnabled=''True''
:DebugServerWaitOnLaunch=''False''

= Connecting to the Executable =
In order to debug an executable that has been compiled with the proper settings (see above), the application must already be launched either on the local computer or on a computer accessible via a network connection.

# In LabVIEW, select the '''Operate''' >> '''Debug Application or Shared Library...'''
# Enter the machine name or IP address of the computer that is running the application. If the application is running on the local machine, enter ''localhost''.
# If "Application or shared library" drop-down doesn't show the name of the application that you are looking for and the application has been configured properly, click on "Refresh".
# Select the application that you wish to debug and click on "Connect".

At this point, the application should "download" and you should be able to use the LabVIEW debugging tools in the application.

[[Category:Debugging]]

Debugging

2019-01-09T21:15:40Z

Bryan: /* Advanced Debugging */

== Debugging Basics ==
[[File:BD Toolbar.gif|center|thumb|506x506px|Block Diagram Toolbar ]]
Basic debugging tools come integrated into every block diagram window in the toolbar. See [http://www.ni.com/getting-started/labview-basics/debug Debugging Tools in LabVIEW] .<ref>"Debugging Tools in LabVIEW" by National Instruments ([http://www.ni.com/getting-started/labview-basics/debug]http://www.ni.com/getting-started/labview-basics/debug)
</ref>
* '''Broken Run Button''' - appears broken when the VI you are creating or editing contains errors
* '''Highlight Execution''' - displays an animation of the block diagram execution when you run the VI
* '''Retain Wire Values''' - save the wire values at each point in the flow of execution so that when you place a probe on the wire you can immediately retain the most recent value of the data that passed through the wire
* '''Step Into''' - opens a node and pauses
* '''Step Over''' - executes a node and pauses at the next node
* '''Step Out''' - finishes executing the current node and pauses

== Breakpoints ==
[[File:BreakpointButton.gif|left|frameless|24x24px]]
Like other software languages, breakpoints allow the developer to pause the execution of the code at a specified point. This is helpful when the developer knows the code works to that point but the wants to use the other debugging to past that point to discover the problem. See more on [https://zone.ni.com/reference/en-XX/help/371361J-01/lvhowto/breakpoints/ Managing Breakpoints].<ref>"Managing Breakpoints" by National Instruments (http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/breakpoints/)</ref>

== Probes ==
[[File:ProbeButton.gif|left|frameless|24x24px]]
Use [[Probes]] to check intermediate values on a wire as a VI runs. Use the Probe tool if you have a complicated block diagram with a series of operations, any one of which might return incorrect data. Use the Probe tool with execution highlighting, single-stepping, and breakpoints to determine if and where data is incorrect. If data is available, the probe immediately updates and displays the data during execution highlighting, single-stepping, or when you pause at a breakpoint. When execution pauses at a node because of single-stepping or a breakpoint, you also can probe the wire that just executed to see the value that flowed through that wire.<ref>"Using the Probe Tool" by National Instruments [http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/using_the_probe_tool/ (http://zone.ni.com/reference/en-XX/help/371361R-01/lvhowto/using_the_probe_tool/])
</ref>

== Conditional Disable Structure/Conditional Symbols ==
More to come

== Suspend When Called ==
More to come

== Debug Window ==
More to come

== Error Handling ==
More to come

== Desktop Execution Trace Toolkit ==
More to come

== Advanced Debugging ==
* [[Debugging_Executables|Debugging Executables]]
More to come

== Articles ==
[https://forums.ni.com/t5/WAsatch-Front-LabVIEW-WAFL-User/Basics-of-Debugging-LabVIEW/gpm-p/3816405 Basics of Debugging LabVIEW] - by Quentin Alldredge, Q Software Innovations, LLC

== References ==
<references />

[[Category:Debugging]]

Debugging Executables

2019-01-09T21:13:07Z

Bryan: Created page with "{{TOCright}} Executables created in LabVIEW can be debugged after having been compiled into an executable, (*.exe). However, this is only able to be done if "Enable debugging..."

{{TOCright}}
Executables created in LabVIEW can be debugged after having been compiled into an executable, (*.exe). However, this is only able to be done if "Enable debugging" was enabled in the build specification when the application was compiled.

== Build Specification Settings ==
Under the "Advanced" category in the Build Specification:

* '''Enable debugging'''
** ''Enabled'' - "Builds in" the ability to connect to and debug the built application. This ability can then be enabled/disabled by setting the appropriate key in the [AppName].ini file after it has been compiled.
** ''Disabled'' - Completely disables any ability to connect to and debug the application once built. This ability can not be enabled even if the appropriate keys have been added and set in the [AppName].ini file.

*'''Wait for debugger on launch'''
** ''Enabled'' - If "Enable debugging" has been set, this setting allows the built application to be launched and accessed, but the application does not automatically run. The run arrow will have to be clicked to start running the application.
** ''Disabled'' - The application will begin running immediately when the application is launched.

== Debugging an Executable ==
In order to debug an executable that has been compiled with the proper settings (see above), the application must already be launched either on the local computer or on a computer accessible via a network connection.

# In LabVIEW, select the '''Operate''' >> '''Debug Application or Shared Library...'''
# Enter the machine name or IP address of the computer that is running the application. If the application is running on the local machine, enter ''localhost''.
# If "Application or shared library" drop-down doesn't show the name of the application that you are looking for and the application has been configured properly, click on "Refresh".
# Select the application that you wish to debug and click on "Connect".

At this point, the application should "download" and you should be able to use the LabVIEW debugging tools in the application.

[[Category:Debugging]]

NaN

2019-01-09T18:32:17Z

Bryan: /* External links */ Add: correct/additional references to IEEE 754 Standard. Remove: Broken link to IEEE 754 Standard. Change: Reorganized external links.

'''NaN''' is the notation in LabVIEW for the floating-point value ''Not-a-Number''. LabVIEW implements the [http://grouper.ieee.org/groups/754/ IEEE-754 standard] for floating-point calculations, which specifies unique values for the outputs of mathematical operations which have no meaningful numerical result. A few examples of calculations which produce NaN are:

*division of zero by zero
*square root of a negative number
*division of an infinity by an infinity
*logarithm (any base) of a non-positive number
*any calculation which includes NaN as one of its operands

The last example above implies that any calculation sequence which generates NaN as an intermediate step will propagate NaN through all subsequent calculations. While this is generally true, there are exceptions (the LabVIEW '''Power of X''' primitive returns one for zero raised to NaN).

One salient feature of the NaN value is that all comparison operations involving NaN return '''FALSE''', including the equality operator (in other words, NaN != NaN). LabVIEW provides the '''Not A Number/Path/Refnum?''' primitive, which is the proper way to test for NaN.
<center>
{| class="wikitable FCK__ShowTableBorders" align="center"
|-
! Not A Number/Path/Refnum? primitive
|-
| [[Image:Nanfunc.png|center]]
|}
</center>
Floating-point controls, indicators, and block diagram constants support the direct entry of NaN (case-insensitive). Similarly, string-to-numeric and numeric-to-string primitives convert or format NaN without regard to format specifiers.

== Use Cases ==

*indicating "missing" data in data-tables in files.
*used for lifting the "plotting pen" in graph, for instance if a value would be out of its allowed range.

== External links ==

*IEEE pages:
**[http://ieeexplore.ieee.org/servlet/opac?punumber=2355 754-1985 - IEEE Standard for Binary Floating-Point Arithmetic]
**[http://ieeexplore.ieee.org/servlet/opac?punumber=4610933 754-2008 - IEEE Standard for Floating-Point Arithmetic]
*Wikipedia entries:
**[http://en.wikipedia.org/wiki/NaN Wikipedia entry on NaN]
**[http://en.wikipedia.org/wiki/IEEE_754 Wikipedia entry on IEEE 754]

OS Open Document

2019-01-09T18:13:17Z

Bryan: Fix: Broken Link

{{ PrivateEvent
| description =Triggered when the user opens a non-LabVIEW file with LabVIEW
| minLVVersion = 8.2
| maxLVVersion =
| class = Application
| OS1 =w
| OS2 =l
| OS3 =
| OS4 =
| NowPublic =No
| Notes = See this [https://lavag.org/topic/4851-associating-my-exe-with-a-specific-file-extension-type/?page=1 discussion]. Supposedly only works with LabVIEW 8.2
}}

Open Source Code

2019-01-07T20:25:32Z

Bryan: /* Articles */

== Open Source Repositories ==

=== GitHub ===
* [https://github.com/trending/labview Trending LabVIEW Projects on GitHub]
* [https://github.com/search?q=labview&type=Repositories All LabVIEW Projects on GitHub]

=== GitLab ===
* [https://gitlab.com/search?utf8=%E2%9C%93&search=labview LabVIEW Projects on GitLab]

=== BitBucket ===
* [https://bitbucket.org/lavag/ LAVA projects on BitBucket]

==Forums and Discussion Groups==
[https://forums.ni.com/t5/Git-User-Group/gp-p/grp-2368 Git User Group - NI Community]

[https://forums.ni.com/t5/Mercurial-User-Group/gp-p/5107 Mercurial User Group - NI Community]

==Articles==

[https://devs.wiresmithtech.com/blog/open-source-labview-how-to-contribute/ Open Source LabVIEW-How to Contribute] - James McNally, Wiresmith Technology

Open source software projects are making huge contributions around the world. They allow communities to pool their resources and achieve progress that couldn’t be reached by individual teams in silos.

While there are open source projects in LabVIEW, it feels like a resource that we aren’t great at using as a community. Every project I’ve seen seems to handle things quite differently, and it can be hard to track down where to work.

[https://github.com/NISystemsEngineering/GitHub-Hands-on/blob/master/Basic%20Concepts/Basic%20Concepts.md Git Basic Concepts for LabVIEW] - developed by NI Systems Engineering

How to use GitHub with LabVIEW Code.
* [https://forums.ni.com/t5/Reference-Design-Content/Getting-Started-Git-and-GitHub-setup/ta-p/3544824 Getting Started with Git and GitHub]
* [https://forums.ni.com/t5/Reference-Design-Content/Getting-Started-Git-GitHub-Development-Workflow/ta-p/3544823 Git/GitHub Development Workflow]

[https://opensource.org/ Open Source Initiative]

Not an article, per-se, however it is a full website promoting the open source cause. Includes lots of information about licensing.

[https://forums.ni.com/t5/LabVIEW-Development-Best/Using-Subversion-SVN-with-LabVIEW/ba-p/3479672 Using Subversion (SVN) with LabVIEW]

[[Category:Open Source Code]]