LabVIEW Wiki - User contributions [en]

LabVIEW 2026 Q1

2026-02-06T17:12:18Z

Logmanoriginal: Add reflink to LabVIEW for Containers on GitHub

{{prevnext|LabVIEW 2025 Q3|LabVIEW Versions|LabVIEW 2026 Q3}}
{{LabVIEW Version
|version=LabVIEW 2026 Q1
|logo=File:LV2026.png
|release=February 2, 2026
|change_0=Nigel code suggestions
|change_1=Project state files
|change_2=Headless environment
|change_3=LabVIEW for Containers
|change_4=Removed CIN support}}

LabVIEW 2026 Q1 was released on February 2, 2025<ref name="announcing-labview-2026-q1"/>.

==New==
* [[Nigel AI Advisor]]
** Code suggestions
** Answer questions related to project structures
** Query, analyze, and retrieve test and measurement data in [[TestStand]]
** Store and pin previous discussions
* [[Debugging]]
** Override the [[Allow Debugging]] property per target in the [[Project Environment]] settings
** Control [[Retain Wire Values]] setting for all VIs in a hierarchy
* [[LVPROJSTATE File Extension|Project state]] files
** Set and save [[probe]]s and [[breakpoint]]s of source-only VIs
* [[VI Comparison]]
** Report description
** Overview images
** Matching left/right images for comparison of added/removed objects
** Changes to attached labels are grouped with the attached object
** Copy text from the Differences dialog
** Added and deleted items reported for changes to [[Bundle by Name]] and [[Unbundle by Name]]
** Full title comparison for window titles
* [[Externally Changed Files List]]
** Notify when open files change on disk
** Reload project after file changes
* [[LabVIEW Headless Environment]]
** <code>-Headless</code> CLI switch
** No active LabVIEW license required
* Official [[LabVIEW Docker Container]]s<ref name="labview-docker" /><ref name="labview-for-containers" />
* [[Manage Trust Files]]
** Prevent unknown external code from automatically executing when called or loaded in LabVIEW
* [[Web Browser Control]]
* .NET 8.0
** Create probes on .NET 8.0 references
** Support for arrays of class references
** Support for
*** [[.NET Object to Variant]]
*** [[Variant to .NET Object]]
*** [[To More Generic Class]]
*** [[To More Specific Class]]

==Removed==
* [[Code Interface Node]]s are no longer supported.

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/labview-changes.html LabVIEW Features and Changes] (LabVIEW User Manual)

==References==
<references>
<ref name="announcing-labview-2026-q1">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2026-Q1/m-p/4468102/highlight/true#M1320133 Announcing LabVIEW 2026 Q1!] (LabVIEW Forums)</ref>
<ref name="labview-docker">[https://hub.docker.com/r/nationalinstruments/labview LabVIEW Docker Containers] (Docker Hub)</ref>
<ref name="labview-for-containers">[https://github.com/ni/labview-for-containers LabVIEW for Containers] (GitHub)</ref>
</references>

[[Category:LabVIEW Versions]]

LabVIEW 2026 Q1

2026-02-06T17:07:43Z

Logmanoriginal: Fix wrong release date in the side panel

{{prevnext|LabVIEW 2025 Q3|LabVIEW Versions|LabVIEW 2026 Q3}}
{{LabVIEW Version
|version=LabVIEW 2026 Q1
|logo=File:LV2026.png
|release=February 2, 2026
|change_0=Nigel code suggestions
|change_1=Project state files
|change_2=Headless environment
|change_3=Official Docker containers
|change_4=Removed CIN support}}

LabVIEW 2026 Q1 was released on February 2, 2025<ref name="announcing-labview-2026-q1"/>.

==New==
* [[Nigel AI Advisor]]
** Code suggestions
** Answer questions related to project structures
** Query, analyze, and retrieve test and measurement data in [[TestStand]]
** Store and pin previous discussions
* [[Debugging]]
** Override the [[Allow Debugging]] property per target in the [[Project Environment]] settings
** Control [[Retain Wire Values]] setting for all VIs in a hierarchy
* [[LVPROJSTATE File Extension|Project state]] files
** Set and save [[probe]]s and [[breakpoint]]s of source-only VIs
* [[VI Comparison]]
** Report description
** Overview images
** Matching left/right images for comparison of added/removed objects
** Changes to attached labels are grouped with the attached object
** Copy text from the Differences dialog
** Added and deleted items reported for changes to [[Bundle by Name]] and [[Unbundle by Name]]
** Full title comparison for window titles
* [[Externally Changed Files List]]
** Notify when open files change on disk
** Reload project after file changes
* [[LabVIEW Headless Environment]]
** <code>-Headless</code> CLI switch
** No active LabVIEW license required
* Official [[LabVIEW Docker Container]]s<ref name="labview-docker" />
* [[Manage Trust Files]]
** Prevent unknown external code from automatically executing when called or loaded in LabVIEW
* [[Web Browser Control]]
* .NET 8.0
** Create probes on .NET 8.0 references
** Support for arrays of class references
** Support for
*** [[.NET Object to Variant]]
*** [[Variant to .NET Object]]
*** [[To More Generic Class]]
*** [[To More Specific Class]]

==Removed==
* [[Code Interface Node]]s are no longer supported.

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/labview-changes.html LabVIEW Features and Changes] (LabVIEW User Manual)

==References==
<references>
<ref name="announcing-labview-2026-q1">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2026-Q1/m-p/4468102/highlight/true#M1320133 Announcing LabVIEW 2026 Q1!] (LabVIEW Forums)</ref>
<ref name="labview-docker">[https://hub.docker.com/r/nationalinstruments/labview LabVIEW Docker Containers] (Docker Hub)</ref>
</references>

[[Category:LabVIEW Versions]]

LabVIEW 2026 Q1

2026-02-06T17:06:41Z

Logmanoriginal: Add release information

{{prevnext|LabVIEW 2025 Q3|LabVIEW Versions|LabVIEW 2026 Q3}}
{{LabVIEW Version
|version=LabVIEW 2026 Q1
|logo=File:LV2026.png
|release=February 3, 2026
|change_0=Nigel code suggestions
|change_1=Project state files
|change_2=Headless environment
|change_3=Official Docker containers
|change_4=Removed CIN support}}

LabVIEW 2026 Q1 was released on February 2, 2025<ref name="announcing-labview-2026-q1"/>.

==New==
* [[Nigel AI Advisor]]
** Code suggestions
** Answer questions related to project structures
** Query, analyze, and retrieve test and measurement data in [[TestStand]]
** Store and pin previous discussions
* [[Debugging]]
** Override the [[Allow Debugging]] property per target in the [[Project Environment]] settings
** Control [[Retain Wire Values]] setting for all VIs in a hierarchy
* [[LVPROJSTATE File Extension|Project state]] files
** Set and save [[probe]]s and [[breakpoint]]s of source-only VIs
* [[VI Comparison]]
** Report description
** Overview images
** Matching left/right images for comparison of added/removed objects
** Changes to attached labels are grouped with the attached object
** Copy text from the Differences dialog
** Added and deleted items reported for changes to [[Bundle by Name]] and [[Unbundle by Name]]
** Full title comparison for window titles
* [[Externally Changed Files List]]
** Notify when open files change on disk
** Reload project after file changes
* [[LabVIEW Headless Environment]]
** <code>-Headless</code> CLI switch
** No active LabVIEW license required
* Official [[LabVIEW Docker Container]]s<ref name="labview-docker" />
* [[Manage Trust Files]]
** Prevent unknown external code from automatically executing when called or loaded in LabVIEW
* [[Web Browser Control]]
* .NET 8.0
** Create probes on .NET 8.0 references
** Support for arrays of class references
** Support for
*** [[.NET Object to Variant]]
*** [[Variant to .NET Object]]
*** [[To More Generic Class]]
*** [[To More Specific Class]]

==Removed==
* [[Code Interface Node]]s are no longer supported.

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/labview-changes.html LabVIEW Features and Changes] (LabVIEW User Manual)

==References==
<references>
<ref name="announcing-labview-2026-q1">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2026-Q1/m-p/4468102/highlight/true#M1320133 Announcing LabVIEW 2026 Q1!] (LabVIEW Forums)</ref>
<ref name="labview-docker">[https://hub.docker.com/r/nationalinstruments/labview LabVIEW Docker Containers] (Docker Hub)</ref>
</references>

[[Category:LabVIEW Versions]]

File:LV2026.png

2026-02-06T16:32:29Z

Logmanoriginal: LabVIEW 2026 Icon Category:LabVIEW Versions

== Summary ==
LabVIEW 2026 Icon

[[Category:LabVIEW Versions]]

LabVIEW Versions

2026-02-04T12:31:55Z

Logmanoriginal: /* LabVIEW */ Add LabVIEW 2026 Q1

__TOC__
==LabVIEW Community Edition==
{|
|-
|
[[File:LVComEd Logo Horiz Color RGB.png|500px|LabVIEW Community Edition|link=LabVIEW Community Edition]]
|- style="text-align:Center;"
| [[LabVIEW Community Edition]] 
(Release 28 April 2020)
|}

==LabVIEW Beta==
Select the icon or description to learn more about that version of LabVIEW Beta.
<gallery mode=nolines perrow=6>
</gallery>

==LabVIEW==
Select the icon or description to learn more about that version of LabVIEW.
<gallery mode=nolines perrow=6>
File:LV2026.png|link=LabVIEW 2026 Q1|[[LabVIEW 2026 Q1]]
File:LV2025.png|link=LabVIEW 2025 Q3|[[LabVIEW 2025 Q3]]
File:LV2025.png|link=LabVIEW 2025 Q1|[[LabVIEW 2025 Q1]]
File:LV2024.png|link=LabVIEW 2024 Q3|[[LabVIEW 2024 Q3]]
File:LV2024.png|link=LabVIEW 2024 Q1|[[LabVIEW 2024 Q1]]
File:LV2023.png|link=LabVIEW 2023 Q3|[[LabVIEW 2023 Q3]]
File:LV2023.png|link=LabVIEW 2023 Q1|[[LabVIEW 2023 Q1]]
File:LV2022.png|link=LabVIEW 2022|[[LabVIEW 2022]]
File:LV2021.png|link=LabVIEW 2021|[[LabVIEW 2021]]
File:LV2020.png|link=LabVIEW 2020|[[LabVIEW 2020]]
File:LV2019.png|link=LabVIEW 2019|[[LabVIEW 2019]]
File:LV2018.png|link=LabVIEW 2018|[[LabVIEW 2018]]
File:LV2017.png|link=LabVIEW 2017|[[LabVIEW 2017]]
File:LV2016.png|link=LabVIEW 2016|[[LabVIEW 2016]]
File:LV2015.png|link=LabVIEW 2015|[[LabVIEW 2015]]
File:LV2014.png|link=LabVIEW 2014|[[LabVIEW 2014]]
File:LV8-2013.png|link=LabVIEW 2013|[[LabVIEW 2013]]
File:LV8-2013.png|link=LabVIEW 2012|[[LabVIEW 2012]]
File:LV8-2013.png|link=LabVIEW 2011|[[LabVIEW 2011]]
File:LV8-2013.png|link=LabVIEW 2010|[[LabVIEW 2010]]
File:LV8-2013.png|link=LabVIEW 2009|[[LabVIEW 2009]]
File:LV8-2013.png|link=LabVIEW 8.6|[[LabVIEW 8.6|LabVIEW 8.6 (2008)]]
File:LV8-2013.png|link=LabVIEW 8.5|[[LabVIEW 8.5|LabVIEW 8.5 (2007)]]
File:LV8-2013.png|link=LabVIEW 8.20|[[LabVIEW 8.20|LabVIEW 8.20 (2006 - 20th Anniversary Edition)]]
File:LV8-2013.png|link=LabVIEW 8|[[LabVIEW 8|LabVIEW 8 (2005)]]
File:LV8-2013.png|link=LabVIEW 7 Express|[[LabVIEW 7 Express|LabVIEW 7 Express (2003)]]
File:LV5.png|link=LabVIEW 6i|[[LabVIEW 6i|LabVIEW 6i (2000)]]
File:LV5.png|link=LabVIEW Real-Time|[[LabVIEW Real-Time|LabVIEW Real-Time (1999)]]
File:LV5.png|link=LabVIEW 5.0|[[LabVIEW 5.0|LabVIEW 5.0 (1998)]]
File:NILogo.jpg|link=LabVIEW 4.0|[[LabVIEW 4.0|LabVIEW 4.0 (1996)]]
File:NILogo.jpg|link=LabVIEW 3.0|[[LabVIEW 3.0|LabVIEW 3.0 (1993 - Multi-platform)]]
File:NILogo.jpg|link=LabVIEW 2.0|[[LabVIEW 2.0|LabVIEW 2.0 (1990)]]
File:NILogo.jpg|link=LabVIEW 1.0|[[LabVIEW 1.0|LabVIEW 1.0 (1986 - for Macintosh)]]
File:LV1.png|link=LabVIEW Inception|[[LabVIEW Inception|LabVIEW Inception (1983 - LabVIEW Project Begins)]]
</gallery>

==LabVIEW NXG==
Select the icon or description to learn more about that version of LabVIEW NXG.
<gallery mode=nolines perrow=6>
File:LVNXG.png|link=LabVIEW NXG 5.1|[[LabVIEW NXG 5.1|LabVIEW NXG 5.1 (January 2021)]]
File:LVNXG.png|link=LabVIEW NXG 5.0|[[LabVIEW NXG 5.0|LabVIEW NXG 5.0 (May 2020)]]
File:LVNXG.png|link=LabVIEW NXG 4.0|[[LabVIEW NXG 4.0|LabVIEW NXG 4.0 (November 2019)]]
File:LVNXG.png|link=LabVIEW NXG 3.0|[[LabVIEW NXG 3.1|LabVIEW NXG 3.1 (March 2019)]]
File:LVNXG.png|link=LabVIEW NXG 3.0|[[LabVIEW NXG 3.0|LabVIEW NXG 3.0 (October 2018)]]
File:LVNXG.png|link=LabVIEW NXG 2.1|[[LabVIEW NXG 2.1|LabVIEW NXG 2.1 (March 2018)]]
File:LVNXG.png|link=LabVIEW NXG 2.0|[[LabVIEW NXG 2.0|LabVIEW NXG 2.0 (January 2018)]]
File:LVNXG.png|link=LabVIEW NXG 1.0|[[LabVIEW NXG 1.0|LabVIEW NXG 1.0 (May 2017)]]
</gallery>

== External links ==
* [https://www.ni.com/en-us/shop/labview/release-details.html LabVIEW Release Details] (National Instruments)
* [https://nihistory.com/ Living History of NI]

[[Category:LabVIEW]]
[[Category:LabVIEW Logo]]

LabVIEW 2026 Q1

2026-02-04T12:31:22Z

Logmanoriginal: Create skeleton page

{{prevnext|LabVIEW 2025 Q3|LabVIEW Versions|LabVIEW 2026 Q3}}
{{LabVIEW Version
|version=LabVIEW 2026 Q3
|logo=File:LV2026.png
|release=February 3, 2026
|change_0=
|change_1=
|change_2=
|change_3=
|change_4=}}

LabVIEW 2026 Q1 was released on February 2, 2025<ref name="announcing-labview-2026-q1"/>.

==New==
*

==Removed==
* [[Code Interface Node]]s are no longer supported.

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/labview-changes.html LabVIEW Features and Changes] (LabVIEW User Manual)

==References==
<references>
<ref name="announcing-labview-2026-q1">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2026-Q1/m-p/4468102/highlight/true#M1320133 Announcing LabVIEW 2026 Q1!] (LabVIEW Forums)</ref>
</references>

{{underconstruction}}
[[Category:LabVIEW Versions]]

Coercion dot

2025-12-06T06:37:19Z

Logmanoriginal: Add to :Category:Block Diagram

{{stub}}
[[Category:Block Diagram]]

LabVIEW Wiki talk:Community portal

2025-12-06T06:35:55Z

Logmanoriginal:

@[[User talk:MichaelAivaliotis]] Hello. How can I edit my userpage? Can I be able to revert vandalism? [[User:DWindsor|DWindsor]] ([[User talk:DWindsor|talk]]) 14:48, 29 May 2019 (UTC)

User Pages have been locked down due to spam and vandalism. --[[User:MichaelAivaliotis|MichaelAivaliotis]] ([[User talk:MichaelAivaliotis|talk]]) 07:32, 30 May 2019 (UTC)

@[[User talk:MichaelAivaliotis]] Hey! I'm trying to edit the Coercion Dots page, because it's empty, but I can't create the page. May I have permission to do so? (I'm a university student who uses LabVIEW frequently and want to contribute.)
[[User:Declu|Declu]] ([[User talk:Declu|talk]]) 23:14, 05 December 2025
:New user accounts are blocked from creating new pages for some time to prevent spam and vandalism. I created the page as a stub. You should be able to edit it. Thanks for your contribution --[[User:Logmanoriginal|Logmanoriginal]] ([[User talk:Logmanoriginal|talk]]) 06:35, 6 December 2025 (UTC)

Coercion dot

2025-12-06T06:33:44Z

Logmanoriginal: Created page with "{{stub}}"

Convert Unit function

2025-09-11T12:45:51Z

Logmanoriginal: Remove stub label and fix some formatting issues

{{LabVIEW Palette Object Information|palette=Functions Palette/Programming/Numeric/Conversion{{!}}Conversion palette|type=function|icon=Conversion Palette - Convert Unit.png}}
The '''Convert Unit''' function converts a physical number (a number that has a unit) to a pure number (a number with no units) or a pure number to a physical number. Right-click the function and select Build Unit String from the shortcut menu to build and edit a string of units.

== Usage ==
The Convert Unit function is essential in applications involving physical measurements, such as data acquisition and signal processing. It allows users to strip units from sensor data (e.g., converting a voltage reading in volts to a unitless number for mathematical operations) or add units to computed results for meaningful display (e.g., attaching seconds to a time value). For instance, if input x is 10 and the unit is 's' (seconds), the output y becomes 10 seconds, as seconds is LabVIEW's base unit for time. This ensures compatibility in calculations where units must be handled explicitly.

== History ==
Introduced in early LabVIEW versions, the function has evolved with improvements in unit handling. In LabVIEW 7.x and later, it integrates better with functions like Compound Arithmetic, eliminating the need to manually remove extra units post-operation. Further enhancements include better support for complex unit conversions in LabVIEW 2010 and an improved unit string builder in LabVIEW 2018 for enhanced usability.
{| class="wikitable"
! Version
! Change(s)
|-
|[[File:LV2018.png|frameless|border|64x64px|LabVIEW 2018|link=LabVIEW 2018]]
|Enhanced unit string builder for better usability.
|-
|LabVIEW 2010
|Improved support for complex unit conversions.
|-
|LabVIEW 7.x
|Integration with Compound Arithmetic to automatically handle extra units.
|}

== See Also ==
* [[Data Acquisition Palette]] for related measurement functions.
* [[Numeric Palette]] for other conversion tools.
* [[Cast Unit Bases function]] for changing base units.

== External Links ==
* [https://stravaro.com/2021/07/labview-units-part-1/ Let’s Talk About LabVIEW Units, Part 1 - by Brian Powell]
* [https://www.ni.com/docs/en-US/bundle/labview-api-ref/page/functions/convert-unit.html Convert Unit - NI Documentation]
* [https://fcalculator.com/conversions.html Conversions Calculator] - A general online tool for unit conversions that can complement LabVIEW's built-in functions.

[[Category:Conversion Palette]]

Source Distribution

2025-08-30T19:14:20Z

Logmanoriginal: Fix typo

A '''source distribution''' is LabVIEW's way of packing source files in a project as a [[wikipedia:ZIP (file format)|ZIP]] file. This allows developers to distribute specific versions of a project.

==History==
{{history|product=LabVIEW|2025 Q3|
* Source distributions now use the compiled code setting of each source file by default.
}}

{{stub}}
[[Category:Code distribution]]

Code Distribution

2025-08-30T19:13:52Z

Logmanoriginal: /* As Source */ Replace Source Code Repositories wikilink with link to wikipedia

{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; font-size:200%; border:none; margin:0; padding:.3em; color:#FFD500; text-align:center;"
| '''The Code Distribution Portal'''
|-
| '''Code Distribution''' is the activity of sharing or deploying source code. This involves decisions on whether distribution should include: distributing as source, as a package, as a plugin, as an executable, or as an installer.
|}
__NOTOC__
{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; border:none; color:#FFD500; text-align:center;"
| style="width:25%;" | '''Subcategories'''
| colspan=3 | '''Topics in Code Distribution'''
|- style="vertical-align:top;"
| style="width:25%; text-align:top; background-color:#EFEFEF;" | <center>Select [►] to view subcategories</center>
<categorytree mode="Pages" showcount="off" depth="1">Code distribution</categorytree>
| style="width:33%;" |
== Distributing Source ==
This section describes resources and best practices for distributing source code for reuse.
=== As Source ===
* [[Snippet]]
* [[Source Distribution]]
* [[wikipedia:Repository (version control)|Repository]]
* [[Open Source Code]]

=== As Packages ===
*[[GCentral]]
*[[Package Manager Comparison]]

== Distributing IDE Utilities ==
This section describes resources and best practices for distributing add-on tools to the [[Development Environment|LabVIEW IDE]].

* [[How to do Menu Launch VIs]]
* [[Quick Drop]]
* [[Shortcut Menu Plugins]]
* [[VI Analyzer]]
* [[New dialog#Adding to the New Dialog|Adding to the New Dialog]]
* [[Project Provider Framework]]
* [[NI Package Manager]]

== Distributing Plugins ==
This section describes resources and best practices for distributing plugins to tools or frameworks.

* [[Packed Project Library|Packed Project Libraries (PPLs)]]
* [[DLL/shared library|DLLs]]
* [[Dynamic VI Calls]]

== Distributing Executables ==
This section describes resources and best practices for distributing executables and drivers.

*[[How to Build an Executable]]
*[[Executable Directory Structure]]
*[[Associate your own file type with Windows Explorer]]
*[[Including ini settings]]
*[[EXE has the wrong date]]
*[[Getting Command Line Parameters]]
*[[Run-Time Engine Limitations]]
| style="width:33%;" |
== Finding Shared Code ==
* [[Community Tools and Libraries]]
* [[GCentral]]
* [https://vipm.io VIPM Community Repo]
* [https://github.com/search?q=labview LabVIEW Projects in GitHub]
* [https://gitlab.com/search?utf8=%E2%9C%93&search=labview&group_id=&project_id=&snippets=false&repository_ref=&nav_source=navbar LabVIEW Projects in GitLab]
* [https://github.com/ni NI's Open Source Repo on GitHub]
|}

[[Category:Portals]]

Code Distribution

2025-08-30T19:12:11Z

Logmanoriginal: /* As Source */ Add source distribution

{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; font-size:200%; border:none; margin:0; padding:.3em; color:#FFD500; text-align:center;"
| '''The Code Distribution Portal'''
|-
| '''Code Distribution''' is the activity of sharing or deploying source code. This involves decisions on whether distribution should include: distributing as source, as a package, as a plugin, as an executable, or as an installer.
|}
__NOTOC__
{| class="wikitable" style="width:100%;"
|- style="background-color:#616366; border:none; color:#FFD500; text-align:center;"
| style="width:25%;" | '''Subcategories'''
| colspan=3 | '''Topics in Code Distribution'''
|- style="vertical-align:top;"
| style="width:25%; text-align:top; background-color:#EFEFEF;" | <center>Select [►] to view subcategories</center>
<categorytree mode="Pages" showcount="off" depth="1">Code distribution</categorytree>
| style="width:33%;" |
== Distributing Source ==
This section describes resources and best practices for distributing source code for reuse.
=== As Source ===
* [[Snippet]]
* [[Source Distribution]]
* [[Source Code Repositories]]
* [[Open Source Code]]

=== As Packages ===
*[[GCentral]]
*[[Package Manager Comparison]]

== Distributing IDE Utilities ==
This section describes resources and best practices for distributing add-on tools to the [[Development Environment|LabVIEW IDE]].

* [[How to do Menu Launch VIs]]
* [[Quick Drop]]
* [[Shortcut Menu Plugins]]
* [[VI Analyzer]]
* [[New dialog#Adding to the New Dialog|Adding to the New Dialog]]
* [[Project Provider Framework]]
* [[NI Package Manager]]

== Distributing Plugins ==
This section describes resources and best practices for distributing plugins to tools or frameworks.

* [[Packed Project Library|Packed Project Libraries (PPLs)]]
* [[DLL/shared library|DLLs]]
* [[Dynamic VI Calls]]

== Distributing Executables ==
This section describes resources and best practices for distributing executables and drivers.

*[[How to Build an Executable]]
*[[Executable Directory Structure]]
*[[Associate your own file type with Windows Explorer]]
*[[Including ini settings]]
*[[EXE has the wrong date]]
*[[Getting Command Line Parameters]]
*[[Run-Time Engine Limitations]]
| style="width:33%;" |
== Finding Shared Code ==
* [[Community Tools and Libraries]]
* [[GCentral]]
* [https://vipm.io VIPM Community Repo]
* [https://github.com/search?q=labview LabVIEW Projects in GitHub]
* [https://gitlab.com/search?utf8=%E2%9C%93&search=labview&group_id=&project_id=&snippets=false&repository_ref=&nav_source=navbar LabVIEW Projects in GitLab]
* [https://github.com/ni NI's Open Source Repo on GitHub]
|}

[[Category:Portals]]

Source Distribution

2025-08-30T19:11:13Z

Logmanoriginal: Created page with "A ''source distribution'' is LabVIEW's way of packing source files in a project as a wikipedia:ZIP (file format)| file. This allows developers to distribute specific versions of a project. ==History== {{history|product=LabVIEW|2025 Q3| * Source distributions now use the compiled code setting of each source file by default. }} {{stub}} Category:Code distribution"

A ''source distribution'' is LabVIEW's way of packing source files in a project as a [[wikipedia:ZIP (file format)|ZIP]] file. This allows developers to distribute specific versions of a project.

==History==
{{history|product=LabVIEW|2025 Q3|
* Source distributions now use the compiled code setting of each source file by default.
}}

{{stub}}
[[Category:Code distribution]]

CreateComparisonReport

2025-08-28T12:21:52Z

Logmanoriginal: Created page with "'''CreateComparisonReport''' is a built-in operation installed by the NI LabVIEW Command Line Interface add-on. It runs LVDiff on two VIs and outputs an wikipedia:HTML|, wikipedia:XML|, wikipedia:Microsoft Word|, or text report. ==Synopsis== LabVIEWCLI -OperationName CreateComparisonReport -vi1 <path> -vi2 <path> -reportPath <path> [-reportType (HTML|HTMLSingleFile|MicrosoftWord|PlainText|XML)..."

'''CreateComparisonReport''' is a built-in operation installed by the [[NI LabVIEW Command Line Interface]] add-on. It runs [[LVDiff]] on two [[VI]]s and outputs an [[wikipedia:HTML|HTML]], [[wikipedia:XML|XML]], [[wikipedia:Microsoft Word|Microsoft Word]], or text report.

==Synopsis==
LabVIEWCLI -OperationName CreateComparisonReport
-vi1 <path>
-vi2 <path>
-reportPath <path>
[-reportType (HTML|HTMLSingleFile|MicrosoftWord|PlainText|XML)]
[-o]
[-c]
[-nofp]
[-nofppos]
[-nobd]
[-nobdcosm]
[-noattr]
[-d]

==Options==
;-vi1 <path>
:Absolute path to the first VI to compare.

;-vi2 <path>
:Absolute path to the second VI to compare.

;-reportPath <path>
:Absolute path to the output report.

;-reportType (HTML|HTMLSingleFile|MicrosoftWord|PlainText|XML)
:Report file type. Default is ''HTMLSingleFile''.

;-o
:Overwrite existing report files.

;-c
:Create report directory if it does not exist.

;-nofp
:Exclude front panel differences.

;-nofppos
:Exclude front panel position differences.

;-nobd
:Exclude block diagram differences.

;-nobdcosm
:Exclude cosmetic differences on the block diagram.

;-noattr
:Exclude VI attribute differences.

;-d
:Exclude dependencies.

==See also==
* [[LVDiff]]

==External links==
* [https://www.ni.com/docs/de-DE/bundle/labview/page/predefined-command-line-operations.html#d87982e754 Predefined Command Line Operations] (LabVIEW User Manual)

[[Category:NI LabVIEW Command Line Interface]]

NI LabVIEW Command Line Interface

2025-08-28T12:09:58Z

Logmanoriginal: /* Operations */ Add CreateComparisonReport

'''NI LabVIEW Command Line Interface''' ''(Command Line Interface for LabVIEW, LabVIEW CLI)'' is a [[List of LabVIEW add-ons|LabVIEW add-on]] that exposes operations that can be called directly from the command line. It was first introduced in [[LabVIEW 2014]] and is included with [[LabVIEW Full]] and higher tiers.

<blockquote>
The NI LabVIEW Command Line Interface (CLI) is a software add-on for LabVIEW. You can use it to automate the build process of LabVIEW applications and run the VIs and custom operations you create in LabVIEW.<ref group="ni" name="labviewcli-product-description" />
</blockquote>

LabVIEW CLI is installed in the version-independent ''Shared'' directory of LabVIEW and is therefore available to all installed versions of LabVIEW starting with LabVIEW 2014. This also means that all operations are written in LabVIEW 2014 to ensure compatibility with all supported versions of LabVIEW.

==Synopsis==

LabVIEWCLI -OperationName <name> [<arg>...]
[-AdditionalOperationDirectory <path>]
[-LabVIEWPath <path>]
[-PortNumber <number>]
[-LogFilePath <path>]
[-LogToConsole (true|false)]
[-Verbosity (Minimal|Default|Detailed|Diagnostic)]
[-Help]

==Options==

;-OperationName <name> [<arg>...]
:Runs the specified operation. If the operation has additional arguments, they must be specified after the operation name.

;-AdditionalOperationDirectory <path>
:Specifies the directory where additional operations are located.

;-LabVIEWPath <path>
:Specifies the path to the LabVIEW executable to use. This argument is required on macOS and Linux but optional on Windows. On Windows, it defaults to the most recently started version of LabVIEW.

;-PortNumber <number>
:Specifies the port number to use for the LabVIEW CLI server. The default port number is 3363.

;-LogFilePath <path>
:Specifies the path to the log file. If not specified, the log file is created in the temporary directory.

;-LogToConsole (true|false)
:Specifies whether to log messages to the console. The default value is ''true''.

;-Verbosity (Minimal|Default|Detailed|Diagnostic)
:Specifies the verbosity level of the log messages. Available options are: ''Minimal'', ''Default'', ''Detailed'', and ''Diagnostic''. The default value is ''Default''.

;-Help
:Display help text for the specified operation.

==Operations==
Operations are individual tasks that LabVIEW CLI can execute. Each operation has a unique name and can be called with additional arguments from the command line.

===Predefined operations===
LabVIEW CLI includes a set of predefined operations that can be called from the command line:

* [[CloseLabVIEW]]
* [[CreateComparisonReport]]
* [[ExecuteBuildSpec]]
* [[MassCompile]]
* [[RunUnitTests]]
* [[RunVI]]
* [[RunVIAnalyzer]]

Additionally, custom operations can be created to extend the functionality of LabVIEW CLI.

===Custom operations===
The functionality of LabVIEW CLI can be extended with custom operations. Custom operations are created by inheriting from [[CoreOperation]] and overriding ''GetHelp'' and ''RunOperation''.

==History==
{{history|product=NI LabVIEW Command Line Interface|2025 Q3|
* Added [[CreateComparisonReport]]
}}

{{history|product=NI LabVIEW Command Line Interface|2025 Q1|}}

{{history|product=NI LabVIEW Command Line Interface|2024 Q3|}}

{{history|product=NI LabVIEW Command Line Interface|2024 Q1|}}

{{history|product=NI LabVIEW Command Line Interface|2023 Q3|}}

{{history|product=NI LabVIEW Command Line Interface|2023 Q1|}}

{{history|product=NI LabVIEW Command Line Interface|3.0|}}

{{history|product=NI LabVIEW Command Line Interface|2.1|}}

{{history|product=NI LabVIEW Command Line Interface|2.0|}}

{{history|product=NI LabVIEW Command Line Interface|1.1|}}

==See also==
* [[List of LabVIEW add-ons]]
* [[G-CLI]]

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/predefined-command-line-operations.html Predefined Command Line Operations] (LabVIEW User Manual)
* [https://www.ni.com/docs/en-US/bundle/labview/page/creating-custom-command-line-operations.html Creating Custom Command Line Operations] (LabVIEW User Manual)

==References==
{{reflist|group=ni|refs=
<ref name="labviewcli-product-description">[https://www.ni.com/en/support/downloads/software-products/download.ni-labview-command-line-interface.html NI LabVIEW Command Line Interface Download Page]</ref>
}}
[[Category:LabVIEW add-ons]]
[[Category:NI LabVIEW Command Line Interface]]

NI LabVIEW Command Line Interface

2025-08-28T12:08:12Z

Logmanoriginal: /* History */ Add versions 2025 Q1 and Q3

'''NI LabVIEW Command Line Interface''' ''(Command Line Interface for LabVIEW, LabVIEW CLI)'' is a [[List of LabVIEW add-ons|LabVIEW add-on]] that exposes operations that can be called directly from the command line. It was first introduced in [[LabVIEW 2014]] and is included with [[LabVIEW Full]] and higher tiers.

<blockquote>
The NI LabVIEW Command Line Interface (CLI) is a software add-on for LabVIEW. You can use it to automate the build process of LabVIEW applications and run the VIs and custom operations you create in LabVIEW.<ref group="ni" name="labviewcli-product-description" />
</blockquote>

LabVIEW CLI is installed in the version-independent ''Shared'' directory of LabVIEW and is therefore available to all installed versions of LabVIEW starting with LabVIEW 2014. This also means that all operations are written in LabVIEW 2014 to ensure compatibility with all supported versions of LabVIEW.

==Synopsis==

LabVIEWCLI -OperationName <name> [<arg>...]
[-AdditionalOperationDirectory <path>]
[-LabVIEWPath <path>]
[-PortNumber <number>]
[-LogFilePath <path>]
[-LogToConsole (true|false)]
[-Verbosity (Minimal|Default|Detailed|Diagnostic)]
[-Help]

==Options==

;-OperationName <name> [<arg>...]
:Runs the specified operation. If the operation has additional arguments, they must be specified after the operation name.

;-AdditionalOperationDirectory <path>
:Specifies the directory where additional operations are located.

;-LabVIEWPath <path>
:Specifies the path to the LabVIEW executable to use. This argument is required on macOS and Linux but optional on Windows. On Windows, it defaults to the most recently started version of LabVIEW.

;-PortNumber <number>
:Specifies the port number to use for the LabVIEW CLI server. The default port number is 3363.

;-LogFilePath <path>
:Specifies the path to the log file. If not specified, the log file is created in the temporary directory.

;-LogToConsole (true|false)
:Specifies whether to log messages to the console. The default value is ''true''.

;-Verbosity (Minimal|Default|Detailed|Diagnostic)
:Specifies the verbosity level of the log messages. Available options are: ''Minimal'', ''Default'', ''Detailed'', and ''Diagnostic''. The default value is ''Default''.

;-Help
:Display help text for the specified operation.

==Operations==
Operations are individual tasks that LabVIEW CLI can execute. Each operation has a unique name and can be called with additional arguments from the command line.

===Predefined operations===
LabVIEW CLI includes a set of predefined operations that can be called from the command line:

* [[CloseLabVIEW]]
* [[ExecuteBuildSpec]]
* [[MassCompile]]
* [[RunUnitTests]]
* [[RunVI]]
* [[RunVIAnalyzer]]

Additionally, custom operations can be created to extend the functionality of LabVIEW CLI.

===Custom operations===
The functionality of LabVIEW CLI can be extended with custom operations. Custom operations are created by inheriting from [[CoreOperation]] and overriding ''GetHelp'' and ''RunOperation''.

==History==
{{history|product=NI LabVIEW Command Line Interface|2025 Q3|
* Added [[CreateComparisonReport]]
}}

{{history|product=NI LabVIEW Command Line Interface|2025 Q1|}}

{{history|product=NI LabVIEW Command Line Interface|2024 Q3|}}

{{history|product=NI LabVIEW Command Line Interface|2024 Q1|}}

{{history|product=NI LabVIEW Command Line Interface|2023 Q3|}}

{{history|product=NI LabVIEW Command Line Interface|2023 Q1|}}

{{history|product=NI LabVIEW Command Line Interface|3.0|}}

{{history|product=NI LabVIEW Command Line Interface|2.1|}}

{{history|product=NI LabVIEW Command Line Interface|2.0|}}

{{history|product=NI LabVIEW Command Line Interface|1.1|}}

==See also==
* [[List of LabVIEW add-ons]]
* [[G-CLI]]

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/predefined-command-line-operations.html Predefined Command Line Operations] (LabVIEW User Manual)
* [https://www.ni.com/docs/en-US/bundle/labview/page/creating-custom-command-line-operations.html Creating Custom Command Line Operations] (LabVIEW User Manual)

==References==
{{reflist|group=ni|refs=
<ref name="labviewcli-product-description">[https://www.ni.com/en/support/downloads/software-products/download.ni-labview-command-line-interface.html NI LabVIEW Command Line Interface Download Page]</ref>
}}
[[Category:LabVIEW add-ons]]
[[Category:NI LabVIEW Command Line Interface]]

NI LabVIEW Command Line Interface 2025 Q3

2025-08-28T12:04:27Z

Logmanoriginal: Created page with "{{prevnext|NI LabVIEW Command Line Interface 2025 Q1|NI LabVIEW Command Line Interface|NI LabVIEW Command Line Interface 2026 Q1}} Release date: July 18, 2025 ==External links== * [https://www.ni.com/en/support/downloads/software-products/download.ni-labview-command-line-interface.html NI LabVIEW Command Line Interface] Category:NI LabVIEW Command Line Interface {{stub}}"

{{prevnext|NI LabVIEW Command Line Interface 2025 Q1|NI LabVIEW Command Line Interface|NI LabVIEW Command Line Interface 2026 Q1}}
Release date: July 18, 2025

==External links==
* [https://www.ni.com/en/support/downloads/software-products/download.ni-labview-command-line-interface.html NI LabVIEW Command Line Interface]

[[Category:NI LabVIEW Command Line Interface]]
{{stub}}

NI LabVIEW Command Line Interface 2025 Q1

2025-08-28T12:03:33Z

Logmanoriginal: Created page with "{{prevnext|NI LabVIEW Command Line Interface 2024 Q3|NI LabVIEW Command Line Interface|NI LabVIEW Command Line Interface 2025 Q3}} Release date: January 23, 2025 ==External links== * [https://www.ni.com/en/support/downloads/software-products/download.ni-labview-command-line-interface.html NI LabVIEW Command Line Interface] Category:NI LabVIEW Command Line Interface {{stub}}"

{{prevnext|NI LabVIEW Command Line Interface 2024 Q3|NI LabVIEW Command Line Interface|NI LabVIEW Command Line Interface 2025 Q3}}
Release date: January 23, 2025

==External links==
* [https://www.ni.com/en/support/downloads/software-products/download.ni-labview-command-line-interface.html NI LabVIEW Command Line Interface]

[[Category:NI LabVIEW Command Line Interface]]
{{stub}}

Debug Window

2025-08-20T12:28:13Z

Logmanoriginal: Fix typo

[[File:Debug Window.png|thumb|Debug Window]]
'''Debug Window''' is a tool to display and control [[breakpoints]] and monitor the status and values of [[probe]]s and [[custom probe]]s in the application context. It was first introduced in [[LabVIEW 2025 Q3]] and combines the functionality of [[Breakpoint Manager]] and [[Probe Watch Window]].

==Usage==
Debug Window automatically appears when the first breakpoint or probe is placed. It can also be opened from the ''View'' menu, under ''Debug Window'', or by using the keyboard shortcut ''Ctrl+D''.

It displays the list of breakpoints, probes, and custom probes in the current application context. Double-clicking an entry in the list highlights the corresponding element in a [[VI]]. Items can be removed from the list by pressing the ''Remove Selected Probes and Breakpoints'' button or using the ''Delete'' key. Breakpoints can be enabled or disabled, using the ''Enable/Disable'' button.

Probe values update live while the VI executes. When a probe is selected, the ''Probe Display'' area shows the probe value in a matching control. The ''Probe Options'' button can be used to switch between different probe types, including history and conditional probes. This is an improvement over the original [[Probe Watch Window]], which did not have these options.

<gallery mode="packed" heights=200>
File:Debug Window Probe Options.png|Probe Options
</gallery>

Another new feature is the ability to display probe values directly on a probe. This setting is enabled by default and can be changed from the ''Debug Options'' menu next to the help button.

<gallery mode="packed" heights=200>
Debug Window Debug Options.png|Debug Options
Debug Window Show Values on Wires.png|Show Values on Wires
</gallery>

==History==
{{history|product=LabVIEW|2025 Q3|
* Added Debug Window
}}

==See also==
* [[Breakpoint Manager]]
* [[Probe Watch Window]]

Debug Window

2025-08-20T12:26:38Z

Logmanoriginal: Created page with "Debug Window '''Debug Window''' is a tool to display and control breakpoints and monitor the status and values of probes and custom probes in the application context. It was first introduced in LabVIEW 2025 Q3 and combines the functionality of Breakpoint Manager and Probe Watch Window. ==Usage== Debug Window automatically appears when the first breakpoint or probe is placed. It can also be opened from the ''View''..."

[[File:Debug Window.png|thumb|Debug Window]]
'''Debug Window''' is a tool to display and control [[breakpoints]] and monitor the status and values of [[probe]]s and [[custom probe]]s in the application context. It was first introduced in [[LabVIEW 2025 Q3]] and combines the functionality of [[Breakpoint Manager]] and [[Probe Watch Window]].

==Usage==
Debug Window automatically appears when the first breakpoint or probe is placed. It can also be opened from the ''View'' menu, under ''Debug Window'', or by using the keyboard shortcut ''Ctrl+D''.

It displays the list of breakpoints, probes, and custom probes in the current application context. Double-clicking an entry in the list highlights the corresponding element in a [[VI]]. Items can be removed from the list by pressing the ''Remove Selected Probes and Breakpoints'' button or using the ''Delete'' key. Breakpoints can be enabled or disabled, using the ''Enable/Disable'' button.

Probe values update live while the VI executes. When a probe is selected, the ''Probe Display'' area shows the probe value in a matching control. The ''Probe Options'' button can be used to switch between different probe types, including history and conditional probes. This is an improvement over the original [[Probe Watch Window]], which did not have these options.

<gallery mode="packed" heights=200>
File:Debug Window Probe Options.png|Probe Options
</gallery>

Another new feature is the ability to display probe values directly on a probe. This setting is enabled by default and can be changed form the ''Debug Options'' menu next to the help button.

<gallery mode="packed" heights=200>
Debug Window Debug Options.png|Debug Options
Debug Window Show Values on Wires.png|Show Values on Wires
</gallery>

==History==
{{history|product=LabVIEW|2025 Q3|
* Added Debug Window
}}

==See also==
* [[Breakpoint Manager]]
* [[Probe Watch Window]]

File:Debug Window Show Values on Wires.png

2025-08-20T12:20:49Z

Logmanoriginal: Debug Window Show Values on Wires Category:Debugging

== Summary ==
Debug Window Show Values on Wires

[[Category:Debugging]]

File:Debug Window Probe Options.png

2025-08-20T12:17:57Z

Logmanoriginal: Debug Window Probe Options Category:Debugging

== Summary ==
Debug Window Probe Options

[[Category:Debugging]]

File:Debug Window Debug Options.png

2025-08-20T12:16:44Z

Logmanoriginal: Debug Window Debug Options Category:Debugging

== Summary ==
Debug Window Debug Options

[[Category:Debugging]]

File:Debug Window.png

2025-08-20T12:05:07Z

Logmanoriginal: Debug Window Category:Debugging

== Summary ==
Debug Window

[[Category:Debugging]]

Nigel

2025-08-18T14:50:25Z

Logmanoriginal: Redirected page to Nigel AI Advisor

#REDIRECT [[Nigel AI Advisor]]

Nigel AI Advisor

2025-08-18T14:49:57Z

Logmanoriginal: Add to category

[[File:Nigel Welcome.png|thumb|Welcome to Nigel AI Advisor]]
'''Nigel AI Advisor''', a.k.a. '''Nigel''' is an [[wikipedia:AI|AI]]-driven assistant that is built into LabVIEW and provides support for understanding and editing [[VI]]s. It first shipped with [[LabVIEW 2025 Q3]] and uses cloud-based models that are hosted on [[wikipedia:Microsoft Azure|Microsoft Azure]]. Nigel has an undisclosed free-tier usage limit.

==Usage==
Nigel can be accessed through the [[Context Help]] window, by using the '''Discuss with Nigel''' feature, using the ''Tools'' menu option ''Chat with Nigel AI Advisor'' (shortcut: ''Ctrl+Shift+N'') or using the ''Chat with Nigel AI Advisor'' button at the top right corner of a front panel or block diagram. After login with an registered NI account with active subscription, Nigel is ready for use.

==External links==
* [https://www.ni.com/en/shop/software-portfolio/nigel.html NI Nigel AI Advisor] (ni.com)

[[Category:Nigel AI Advisor]]
{{stub}}

Nigel AI Advisor

2025-08-18T14:49:28Z

Logmanoriginal: Created page with "Welcome to Nigel AI Advisor '''Nigel AI Advisor''', a.k.a. '''Nigel''' is an wikipedia:AI|-driven assistant that is built into LabVIEW and provides support for understanding and editing VIs. It first shipped with LabVIEW 2025 Q3 and uses cloud-based models that are hosted on wikipedia:Microsoft Azure|. Nigel has an undisclosed free-tier usage limit. ==Usage== Nigel can be accessed through the Context Help window, by u..."

Category:Nigel AI Advisor

2025-08-18T14:47:50Z

Logmanoriginal: Created page with "Category:Development Environment"

[[Category:Development Environment]]

File:Nigel Welcome.png

2025-08-18T14:47:35Z

Logmanoriginal: Welcome to Nigel AI Advisor Category:Nigel AI Advisor

== Summary ==
Welcome to Nigel AI Advisor

[[Category:Nigel AI Advisor]]

Category:GDevCon N.A. 2025

2025-08-18T14:14:17Z

Logmanoriginal: Created page with "Category:GDevCon N.A."

[[Category:GDevCon N.A.]]

Context Help

2025-08-18T05:45:14Z

Logmanoriginal: Add main content

[[File:Context Help.png|thumb|Context Help]]
'''Context Help''' is a floating dialog that displays additional information and description about elements in LabVIEW.

==Usage==
Context Help can be opened via the ''Help'' menu, selecting ''Show Context Help'' or by using the keyboard shortcut ''Ctrl''+''H''. Hovering over any element in LabVIEW displays the corresponding help text. For [[VI]]s and other nodes on the block diagram, the configured descriptions and labels are displayed, including data types and terminal labels. If additional help context is provided, the ''Detailed Help'' button becomes available and links to an external site or help document.

===Optional Terminals and Full Path===
By default, Context Help does not show labels for optional terminals. This can dynamically be changed by toggling the ''Optional Terminals and Full Path'' button on the bottom left corner.
<gallery mode="packed" heights=200>
Context Help Without Optional Terminals.png|Optional Terminals and Full Path hidden
Context Help With Optional Terminals.png|Optional Terminals and Full Path shown
</gallery>

===Discuss with Nigel===
Discuss with Nigel is a new feature in [[LabVIEW 2025 Q3]] that adds a shortcut to discuss the item being shown with [[Nigel AI Advisor]]. When selected, it opens Nigel with the [[Block Diagram]] of the VI to provide further information.

<gallery mode="packed" heights=200>
Context Help Discuss with Nigel.png|Discuss with Nigel
Context Help Discuss with Nigel Response.png|Response for Discuss with Nigel
</gallery>

== Tips and tricks ==
* Press the '''Show Optional Terminals and Full Path''' button to display optional terminals and the full path to a VI.
* Press '''Ctrl+Shift+L''' to lock the Context Help window. This will prevent the Context Help window from changing when hovering over objects.
** Press '''Ctrl+Shift+L''' again, to unlock the Context Help window.

==See also==
* [[Nigel AI Advisor]]

==History==
{{history|product=LabVIEW|2025 Q3|
* Added ''Discuss with Nigel'' links
* [[VI]]s: Added [[Reentrancy]], [[Execution Priority]], [[Preferred Execution System]]
* [[Call Library Function Node]]s: Added Function prototype, Library name or path
}}

[[Category:Development Environment]]

File:Context Help Discuss with Nigel Response.png

2025-08-18T05:42:54Z

Logmanoriginal: Nigel response for Discuss with Nigel Category:Development Environment

== Summary ==
Nigel response for Discuss with Nigel

[[Category:Development Environment]]

File:Context Help Discuss with Nigel.png

2025-08-18T05:38:01Z

Logmanoriginal: Discuss with Nigel option in Context Help Category:Development Environment

== Summary ==
Discuss with Nigel option in Context Help

[[Category:Development Environment]]

LabVIEW 2025 Q3

2025-08-18T05:36:37Z

Logmanoriginal: Link to full name of Nigel AI Advisor

{{prevnext|LabVIEW 2025 Q1|LabVIEW Versions|LabVIEW 2026 Q1}}
{{LabVIEW Version
|version=LabVIEW 2025 Q3
|logo=File:LV2025.png
|release=July 22, 2025
|change_0=Nigel™ AI Advisor
|change_1=New Debug Window
|change_2=Logging for Unwired Errors
|change_3=Preserve Values when placing Diagram Disable Structures
|change_4=Context Help Notes for VIs}}

LabVIEW 2025 Q1 was released on July 22, 2025<ref name="announcing-labview-2025-q3"/>.

==New Features==
* [[Nigel AI Advisor]]
* New [[Debug Window]]:
** Combines [[Probe Watch Window]] and [[Breakpoint Manager]]
** Enable and disable breakpoints
** Export data for Probes and Breakpoints
** Switch Probe styles
** Create [[Custom Probe]]s
** Display Probe values directly on [[Wire]]s
* [[Logging for Unwired Errors]]
* New keyboard shortcuts:
** Select all text using Ctrl+A
** [[Open Quickly|Quickly Open]] files using Ctrl+Shift+O
* Automatically wire values through the Enabled frame when placing [[Diagram Disable Structure]]s
* [[Context Help]] Notes:
** On [[VI]]s: [[Reentrant VI|Reentrancy]], [[Execution Priority]], [[Preferred Execution System]]
** On [[Call Library Function Node]]s: Function prototype, Library name or path
* Left-Aligned text for [[block diagram]] objects:
** [[Bundle by Name]]
** [[Unbundle by Name]]
** (Un-)Bundle Elements on [[In Place Element structure|In Place Element Structure]]s
** [[Event Structure]] data nodes
** [[Get Waveform]] components
** [[Build Waveform]]
** [[Get Digital Waveform]] components
** [[Build Digital Waveform]]
** [[Get Digital Data]] components
** [[Build Digital Data]]
* [[LabVIEW CLI]]:
** Runs without enabling [[VI Server]] TCP port
** New Operation: [[CreateComparisonReport]]
* .NET 8 support for [[Register Event Callback]]
* Added support for Windows Long Paths
* Additional data types supported for [[Export Data to Clipboard]] & [[Export Data to Excel]]:
** Arrays of paths
** One-dimensional arrays of [[cluster]]s containing [[numeric]], [[string]], and [[path]] elements
* Vertical scrollbar for [[free label]]s
* [[Source Distribution]]s now use the compiled code setting of each source file by default.

==Removed Features==
* The [[Probe Watch Window]] was replaced by the new [[Debug Window]].

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/labview-2025q3-changes.html LabVIEW 2025 Q3 Features and Changes] (LabVIEW User Manual)
* [https://www.ni.com/en/support/documentation/bugs/25/labview-2025-q3-known-issues.html LabVIEW 2025 Q3 Known Issues]
* [https://www.ni.com/en/support/documentation/bugs/25/labview-2025-q3-bug-fixes.html LabVIEW 2025 Q3 Bug Fixes]

==References==
<references>
<ref name="announcing-labview-2025-q3">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2025-Q3/m-p/4447023 Announcing LabVIEW 2025 Q3!] (LabVIEW Forums)</ref>
</references>

[[Category:LabVIEW Versions]]

File:Context Help With Optional Terminals.png

2025-08-18T05:25:25Z

Logmanoriginal: Context Help with optional terminals Category:Development Environment

== Summary ==
Context Help with optional terminals

[[Category:Development Environment]]

File:Context Help Without Optional Terminals.png

2025-08-18T05:24:59Z

Logmanoriginal: Context Help without optional terminals Category:Development Environment

== Summary ==
Context Help without optional terminals

[[Category:Development Environment]]

File:Context Help.png

2025-08-18T05:10:29Z

Logmanoriginal: Context Help Category:Development Environment

== Summary ==
Context Help

[[Category:Development Environment]]

Context Help window

2025-08-18T05:08:07Z

Logmanoriginal: Logmanoriginal moved page Context Help window to Context Help: Match page title with the dialog naming in LabVIEW

#REDIRECT [[Context Help]]

Context Help

2025-08-18T05:08:07Z

Logmanoriginal: Logmanoriginal moved page Context Help window to Context Help: Match page title with the dialog naming in LabVIEW

{{stub}}

== Tips and tricks ==
* Press the '''Show Optional Terminals and Full Path''' button to display optional terminals and the full path to a VI.
* Press '''Ctrl+Shift+L''' to lock the Context Help window. This will prevent the Context Help window from changing when hovering over objects.
** Press '''Ctrl+Shift+L''' again, to unlock the Context Help window.

[[Category:LabVIEW fundamentals]]

Logging for Unwired Errors

2025-08-17T13:35:54Z

Logmanoriginal: Show line numbers on JSON data

'''Logging for Unwired Errors''' is a feature in LabVIEW that stores any errors from any error output terminal that isn't connected, to a [[wikipedia:JSON|JSON]]-formatted log file. When enabled, a new log file is created in the [[data directory]], under ''UnwiredErrors'' every time the application starts.

==Usage==
Logging for Unwired Errors can be enabled in the ''Block Diagram'' section of the [[Options dialog]] under ''Error Handling'', by checking the ''Log unwired errors'' option, or by adding <code>LogUnwiredErrors=True</code> to the [[configuration file]]. It works regardless of the settings for automatic error handling and application contexts. This means that unwired errors are also logged for internal functions (e.g., the runtime environment).

The option can also be enabled for executables, using the aforementioned configuration key.

==File structure==
Unwired errors are logged in a JSON-formatted file, using the following schema (unofficial):

<syntaxhighlight lang="json" line>
{
"type": "object",
"properties": {
"Application": {
"type": "string",
"description": "The name of the application that the error log was created for."
},
"Session Start Time": {
"type": "string",
"description": "The date and time when the session started (may or may not be the same as the start time of the application)."
},
"Unwired Errors": {
"type": "array",
"description": "Contains the list of unwired errors that were captured during the session.",
"items": {
"type": "object",
"properties": {
"VI": {
"type": "string",
"description": "The name of the VI for which the error is reported."
},
"Project": {
"type": "string",
"description": "The name of the project that the VI belongs to, or \"Not In Project\" if the error was captured for a VI that did not run in a particular project."
},
"Node Id": {
"type": "string",
"description": "The unique identity of the node that caused the error.",
"pattern": "[0-9]+"
},
"Node": {
"type": "string",
"description": "The name of the node that caused the error."
},
"Error Code": {
"type": "string",
"description": "The error code of the error that was captured.",
"pattern": "[-]{0,1}[0-9]+"
},
"Description": {
"type": "string",
"description": "The error message associated with the captured error."
},
"Time": {
"type": "string",
"description": "The time at which the error was captured."
}
},
"required": [
"VI",
"Project",
"Node Id",
"Node",
"Error Code",
"Description",
"Time"
]
}
}
},
"required": [
"Application",
"Session Start Time",
"Unwired Errors"
]
}
</syntaxhighlight>

===Example===
The following example illustrates a log file created for unwired errors in LabVIEW (formatted for readability):

<syntaxhighlight lang="json" line>
{
"Application": "LabVIEW",
"Session Start Time": "August 17 2025, 15:28:55",
"Unwired Errors": [
{
"VI": "Create Zip File.vi",
"Project": "Not In Project",
"Node Id": "1749",
"Node": "Delete",
"Error Code": "7",
"Description": "LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.",
"Time": "15:28:55"
}
]
}
</syntaxhighlight>

==History==
{{history|product=LabVIEW|2025 Q3|
* Added Logging for Unwired Errors
}}

==See also==
* [[Error handling]]

[[Category:Debugging]]

Logging for Unwired Errors

2025-08-17T13:31:43Z

Logmanoriginal: Created page with "'''Logging for Unwired Errors''' is a feature in LabVIEW that stores any errors from any error output terminal that isn't connected, to a wikipedia:JSON|-formatted log file. When enabled, a new log file is created in the data directory, under ''UnwiredErrors'' every time the application starts. ==Usage== Logging for Unwired Errors can be enabled in the ''Block Diagram'' section of the Options dialog under ''Error Handling'', by checking the ''Log unwired err..."

'''Logging for Unwired Errors''' is a feature in LabVIEW that stores any errors from any error output terminal that isn't connected, to a [[wikipedia:JSON|JSON]]-formatted log file. When enabled, a new log file is created in the [[data directory]], under ''UnwiredErrors'' every time the application starts.

==Usage==
Logging for Unwired Errors can be enabled in the ''Block Diagram'' section of the [[Options dialog]] under ''Error Handling'', by checking the ''Log unwired errors'' option, or by adding <code>LogUnwiredErrors=True</code> to the [[configuration file]]. It works regardless of the settings for automatic error handling and application contexts. This means that unwired errors are also logged for internal functions (e.g., the runtime environment).

The option can also be enabled for executables, using the aforementioned configuration key.

==File structure==
Unwired errors are logged in a JSON-formatted file, using the following schema (unofficial):

<syntaxhighlight lang="json">
{
"type": "object",
"properties": {
"Application": {
"type": "string",
"description": "The name of the application that the error log was created for."
},
"Session Start Time": {
"type": "string",
"description": "The date and time when the session started (may or may not be the same as the start time of the application)."
},
"Unwired Errors": {
"type": "array",
"description": "Contains the list of unwired errors that were captured during the session.",
"items": {
"type": "object",
"properties": {
"VI": {
"type": "string",
"description": "The name of the VI for which the error is reported."
},
"Project": {
"type": "string",
"description": "The name of the project that the VI belongs to, or \"Not In Project\" if the error was captured for a VI that did not run in a particular project."
},
"Node Id": {
"type": "string",
"description": "The unique identity of the node that caused the error.",
"pattern": "[0-9]+"
},
"Node": {
"type": "string",
"description": "The label of the node that caused the error."
},
"Error Code": {
"type": "string",
"description": "The error code of the error that was captured.",
"pattern": "[-]{0,1}[0-9]+"
},
"Description": {
"type": "string",
"description": "The error message associated with the captured error."
},
"Time": {
"type": "string",
"description": "The time at which the error was captured."
}
},
"required": [
"VI",
"Project",
"Node Id",
"Node",
"Error Code",
"Description",
"Time"
]
}
}
},
"required": [
"Application",
"Session Start Time",
"Unwired Errors"
]
}
</syntaxhighlight>

===Example===
The following example illustrates a log file created for unwired errors in LabVIEW (formatted for readability):

<syntaxhighlight lang="json">
{
"Application": "LabVIEW",
"Session Start Time": "August 17 2025, 15:28:55",
"Unwired Errors": [
{
"VI": "Create Zip File.vi",
"Project": "Not In Project",
"Node Id": "1749",
"Node": "Delete",
"Error Code": "7",
"Description": "LabVIEW: (Hex 0x7) File not found. The file might be in a different location or deleted. Use the command prompt or the file explorer to verify that the path is correct.",
"Time": "15:28:55"
}
]
}
</syntaxhighlight>

==History==
{{history|product=LabVIEW|2025 Q3|
* Added Logging for Unwired Errors
}}

==See also==
* [[Error handling]]

[[Category:Debugging]]

Central South LabVIEW User Group

2025-08-17T09:26:23Z

Logmanoriginal: Created page with "==External links== * [https://forums.ni.com/t5/CSLUG-Central-South-LabVIEW-User/gh-p/5037 User Group] (NI Forums) * [https://www.cslug.org.uk/ Website] * [https://www.youtube.com/@CSLUG YouTube] {{stub}}"

==External links==
* [https://forums.ni.com/t5/CSLUG-Central-South-LabVIEW-User/gh-p/5037 User Group] (NI Forums)
* [https://www.cslug.org.uk/ Website]
* [https://www.youtube.com/@CSLUG YouTube]

{{stub}}

Würzburg LabVIEW User Group

2025-08-17T09:01:29Z

Logmanoriginal: Fix broken user group link

'''Würzburg LabVIEW User Group''' (WUELUG) is a [[local user group]], where LabVIEW aficionados from all over the Frankfurt-Nürnberg-Stuttgart triangle meet quarterly in and around the city of Würzburg, Germany.

Usually, members take turns hosting the meetings and providing the venue. This gives the hosting company an opportunity to present their products and services, while participants get valuable insights into other teams' processes, tools and overall way of working.

The user group was founded by [[Joerg Hampel (LabVIEW Champion)|Joerg Hampel]] in 2018, and Hampel Software Engineering organizes the quarterly meetings.

== Accolades ==
At [[NIWeek 2019]] in Austin, the WUELUG received the User Group Innovation Award. More information is available in [https://www.hampel-soft.com/blog/wuelug-receives-ni-user-group-innovation-award/ Hampel Software Engineering's blog post].

== External Links ==
* [https://forums.ni.com/t5/WUELUG-W%C3%BCrzburg-LabVIEW-User/gh-p/njioaz5cff WUELUG - Würzburg LabVIEW User Group] (NI Forums)

[[Category:User Groups]]

List of LabVIEW user groups

2025-08-17T08:58:00Z

Logmanoriginal: Add CSLUG

{{see also|User group}}

{|class="wikitable sortable"
!Name
!Acronym
!Location
|-
|[[Würzburg LabVIEW User Group]]
|WUELUG
|Würzburg, Germany
|-
|[[LabVIEW User Group Francophone]]
|LUGE
|Rhône-Alpes, France
|-
|[[Central South LabVIEW User Group]]
|CSLUG
|Newbury, UK
|}

[[Category:Lists]]
[[Category:User Groups]]

LabVIEW 2025 Q3

2025-08-17T08:49:17Z

Logmanoriginal: /* References */ Fix typo

{{prevnext|LabVIEW 2025 Q1|LabVIEW Versions|LabVIEW 2026 Q1}}
{{LabVIEW Version
|version=LabVIEW 2025 Q3
|logo=File:LV2025.png
|release=July 22, 2025
|change_0=Nigel™ AI Advisor
|change_1=New Debug Window
|change_2=Logging for Unwired Errors
|change_3=Preserve Values when placing Diagram Disable Structures
|change_4=Context Help Notes for VIs}}

LabVIEW 2025 Q1 was released on July 22, 2025<ref name="announcing-labview-2025-q3"/>.

==New Features==
* [[Nigel]] AI Advisor
* New [[Debug Window]]:
** Combines [[Probe Watch Window]] and [[Breakpoint Manager]]
** Enable and disable breakpoints
** Export data for Probes and Breakpoints
** Switch Probe styles
** Create [[Custom Probe]]s
** Display Probe values directly on [[Wire]]s
* [[Logging for Unwired Errors]]
* New keyboard shortcuts:
** Select all text using Ctrl+A
** [[Open Quickly|Quickly Open]] files using Ctrl+Shift+O
* Automatically wire values through the Enabled frame when placing [[Diagram Disable Structure]]s
* [[Context Help]] Notes:
** On [[VI]]s: [[Reentrant VI|Reentrancy]], [[Execution Priority]], [[Preferred Execution System]]
** On [[Call Library Function Node]]s: Function prototype, Library name or path
* Left-Aligned text for [[block diagram]] objects:
** [[Bundle by Name]]
** [[Unbundle by Name]]
** (Un-)Bundle Elements on [[In Place Element structure|In Place Element Structure]]s
** [[Event Structure]] data nodes
** [[Get Waveform]] components
** [[Build Waveform]]
** [[Get Digital Waveform]] components
** [[Build Digital Waveform]]
** [[Get Digital Data]] components
** [[Build Digital Data]]
* [[LabVIEW CLI]]:
** Runs without enabling [[VI Server]] TCP port
** New Operation: [[CreateComparisonReport]]
* .NET 8 support for [[Register Event Callback]]
* Added support for Windows Long Paths
* Additional data types supported for [[Export Data to Clipboard]] & [[Export Data to Excel]]:
** Arrays of paths
** One-dimensional arrays of [[cluster]]s containing [[numeric]], [[string]], and [[path]] elements
* Vertical scrollbar for [[free label]]s
* [[Source Distribution]]s now use the compiled code setting of each source file by default.

==Removed Features==
* The [[Probe Watch Window]] was replaced by the new [[Debug Window]].

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/labview-2025q3-changes.html LabVIEW 2025 Q3 Features and Changes] (LabVIEW User Manual)
* [https://www.ni.com/en/support/documentation/bugs/25/labview-2025-q3-known-issues.html LabVIEW 2025 Q3 Known Issues]
* [https://www.ni.com/en/support/documentation/bugs/25/labview-2025-q3-bug-fixes.html LabVIEW 2025 Q3 Bug Fixes]

==References==
<references>
<ref name="announcing-labview-2025-q3">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2025-Q3/m-p/4447023 Announcing LabVIEW 2025 Q3!] (LabVIEW Forums)</ref>
</references>

[[Category:LabVIEW Versions]]

Custom Probe

2025-08-17T08:48:02Z

Logmanoriginal: Fix redlink and mark as wikify

{{TOCright}}
A '''Custom Probe''' is a user-defined [[Probe]] that allows for more interactive and specific monitoring of data passing through a wire in a LabVIEW block diagram during execution. Unlike the standard probes that simply display the data flowing through a wire, custom probes can be designed to allow users to interact with the data, apply conditional formatting, perform calculations, or even modify the data on the fly.

Creating a custom probe involves programming a small LabVIEW VI (Virtual Instrument) that can include controls and indicators, providing a customized interface for data inspection and manipulation. When you attach a custom probe to a wire in a block diagram, it can display information in a more meaningful way specific to your application needs, such as plotting a graph, showing an array's contents in a table, or implementing custom logic to highlight certain conditions.

Custom probes are particularly useful in debugging and data analysis, offering insights into the operation of a VI that might not be easily obtained through standard probes or debugging techniques. They extend the functionality of LabVIEW's debugging tools by enabling the creation of application-specific probes tailored to the unique requirements of each project.

== Creating a Custom Probe ==

Creating a probe allows you to have more control over how LabVIEW probes the data that flows through a wire. When you create a new probe, the data type of the probe matches the data type of the wire you right-click. Before you begin creating custom probes, refer to the caveats and recommendations.

=== Steps to Create a Custom Probe ===

'''Note:''' If you are creating a custom probe for a LabVIEW class or interface data type, some steps may vary depending on whether you are creating a member VI of the class or interface or a non-member custom probe. Member probes can access the private data of the class directly and display any aspect of it. A non-member custom probe may only display information accessible via the public interface of the class.

# Right-click a wire and select '''Custom Probe»New...''' from the shortcut menu to display the Create New Probe dialog box.
# Select whether to create a new probe or to base your probe on an existing one.
## To create a probe based on an existing one, select '''Create a probe from an existing probe'''. LabVIEW displays all supplied probes in the ''[LeabVIEW 20xx]]\vi.lib\_probes'' directory and any custom probes you've created.
## Click the '''Next''' button and select an existing probe to base the new probe on.
## Enter the filename, window title, shortcut menu name, and the directory where you wish to save the probe. LabVIEW stores custom probes in the ''[Documents]\LabVIEW Data\Probes'' directory by default. To make a custom probe the default for a particular data type, save it in the ''[LabVIEW 20xx]\user.lib\_probes\default'' directory.
## Click the '''Save''' button. LabVIEW opens a probe matching the existing probe you selected.

'''Note:''' For creating a non-member probe for a LabVIEW class or interface, follow the instructions above. For member probes, save the custom probe in the subdirectory with other member VIs of the class or interface for easy distribution.

# To create a new probe, select '''Create a new probe''' and click the '''Next''' button.
## Enter the filename, window title, shortcut menu name, and directory for the new probe.
## Click the '''Save''' button. LabVIEW opens a probe with a control matching the data type of the wire you right-clicked and includes a Boolean indicator acting as a conditional breakpoint. It also contains the '''To Probe String''' function for configuring the display value in the Probe Watch Window.
## (Optional) Wire any data type to the data value input of the '''To Probe String''' function to display the data as a string in the Value column of the Probe Watch Window. The function breaks down and converts data into a string that the Value String indicator can display, compressing and trimming as needed to fit the available space.
##:'''Note:''' LabVIEW automatically wires the control to the '''To Probe String''' function. You can remove this function if you wish to specify the string displayed in the Value column.
#:(Optional) Specify the string you want LabVIEW to display in the Value column by wiring that string to the Value String indicator.
# The block diagram shows a custom probe for numeric data, using a Case Structure to display "Greater than five" or "Less than five" instead of the default data display.
# After customizing the probe, save and close it. To edit it, open it from the directory where it was saved.

'''Note:''' The Create New Probe dialog box does not make the new probe a member of the class or interface by default. To make it a member probe, add it to the class or interface.

=== Using the Custom Probe ===

To use the probe, right-click the wire and select ''Probe'' from the shortcut menu. To change the default probe for a data type, right-click a wire of that data type, select ''Custom Probe'' from the shortcut menu, and choose from the available options.

'''Note:''' A custom probe does not become the default probe for any data type until used. For member probes, use the Class/Interface Properties dialog box to set it as the initial default probe when distributing the class or interface.

== Caveats and Recommendations When Using Custom Probes ==
* Custom probes only execute when data flows through the wire. That is, although you can operate the controls on a custom probe at any time, programmatic responses to the changed control values occur only when the probe receives data from the wire.
* You can debug a custom probe similar to a VI. However, a probe cannot probe its own block diagram, nor the block diagram of any of its subVIs. When debugging probes, use the generic probe.
* Save probes in the labview\user.lib\_probes\default or the Default Data\Probes directories. Probes saved in the labview\user.lib\_probes\default directory are available to anyone running LabVIEW on the computer remotely. This directory is useful for public probes. Because the Default Data directory changes based on which user is logged in to the computer, National Instruments recommends you save non-public probes in this directory.
* The main block diagram pauses until the probe finishes execution. Avoid using loops or Event structures in custom probes as these elements can increase the time it takes the probe to finish executing.
* Be careful when using uninitialized shift registers in custom probes. Even if a VI is non-reentrant, when that VI is used as a probe, all uninitialized shift registers behave the same as reentrant VIs. Each probe retains the last value of the loop and does not share these values with other instances of the same probe.

[[Category:Probes]]
[[Category:Debugging]]
{{wikify}}

LabVIEW 2025 Q3

2025-08-17T08:46:26Z

Logmanoriginal: Fix wikilink to Custom Probes and Wires

{{prevnext|LabVIEW 2025 Q1|LabVIEW Versions|LabVIEW 2026 Q1}}
{{LabVIEW Version
|version=LabVIEW 2025 Q3
|logo=File:LV2025.png
|release=July 22, 2025
|change_0=Nigel™ AI Advisor
|change_1=New Debug Window
|change_2=Logging for Unwired Errors
|change_3=Preserve Values when placing Diagram Disable Structures
|change_4=Context Help Notes for VIs}}

LabVIEW 2025 Q1 was released on July 22, 2025<ref name="announcing-labview-2025-q3"/>.

==New Features==
* [[Nigel]] AI Advisor
* New [[Debug Window]]:
** Combines [[Probe Watch Window]] and [[Breakpoint Manager]]
** Enable and disable breakpoints
** Export data for Probes and Breakpoints
** Switch Probe styles
** Create [[Custom Probe]]s
** Display Probe values directly on [[Wire]]s
* [[Logging for Unwired Errors]]
* New keyboard shortcuts:
** Select all text using Ctrl+A
** [[Open Quickly|Quickly Open]] files using Ctrl+Shift+O
* Automatically wire values through the Enabled frame when placing [[Diagram Disable Structure]]s
* [[Context Help]] Notes:
** On [[VI]]s: [[Reentrant VI|Reentrancy]], [[Execution Priority]], [[Preferred Execution System]]
** On [[Call Library Function Node]]s: Function prototype, Library name or path
* Left-Aligned text for [[block diagram]] objects:
** [[Bundle by Name]]
** [[Unbundle by Name]]
** (Un-)Bundle Elements on [[In Place Element structure|In Place Element Structure]]s
** [[Event Structure]] data nodes
** [[Get Waveform]] components
** [[Build Waveform]]
** [[Get Digital Waveform]] components
** [[Build Digital Waveform]]
** [[Get Digital Data]] components
** [[Build Digital Data]]
* [[LabVIEW CLI]]:
** Runs without enabling [[VI Server]] TCP port
** New Operation: [[CreateComparisonReport]]
* .NET 8 support for [[Register Event Callback]]
* Added support for Windows Long Paths
* Additional data types supported for [[Export Data to Clipboard]] & [[Export Data to Excel]]:
** Arrays of paths
** One-dimensional arrays of [[cluster]]s containing [[numeric]], [[string]], and [[path]] elements
* Vertical scrollbar for [[free label]]s
* [[Source Distribution]]s now use the compiled code setting of each source file by default.

==Removed Features==
* The [[Probe Watch Window]] was replaced by the new [[Debug Window]].

==External links==
* [https://www.ni.com/docs/en-US/bundle/labview/page/labview-2025q3-changes.html LabVIEW 2025 Q3 Features and Changes] (LabVIEW User Manual)
* [https://www.ni.com/en/support/documentation/bugs/25/labview-2025-q3-known-issues.html LabVIEW 2025 Q3 Known Issues]
* [https://www.ni.com/en/support/documentation/bugs/25/labview-2025-q3-bug-fixes.html LabVIEW 2025 Q3 Bug Fixes]

==References==
<references>
<ref name="announcing-labview-2025-q3">[https://forums.ni.com/t5/LabVIEW/Announcing-LabVIEW-2025-Q3/m-p/4447023 Announcing LabVIEW 20225 Q3!] (LabVIEW Forums)</ref>
</references>

[[Category:LabVIEW Versions]]

Custom probe

2025-08-17T08:45:30Z

Logmanoriginal: Logmanoriginal moved page Custom probe to Custom Probe: Use capital "P" to match other naming conventions

#REDIRECT [[Custom Probe]]

Custom Probe

2025-08-17T08:45:30Z

Logmanoriginal: Logmanoriginal moved page Custom probe to Custom Probe: Use capital "P" to match other naming conventions

{{TOCright}}
A [[Custom probe]] is a user-defined [[Probe]] that allows for more interactive and specific monitoring of data passing through a wire in a LabVIEW block diagram during execution. Unlike the standard probes that simply display the data flowing through a wire, custom probes can be designed to allow users to interact with the data, apply conditional formatting, perform calculations, or even modify the data on the fly.

Creating a custom probe involves programming a small LabVIEW VI (Virtual Instrument) that can include controls and indicators, providing a customized interface for data inspection and manipulation. When you attach a custom probe to a wire in a block diagram, it can display information in a more meaningful way specific to your application needs, such as plotting a graph, showing an array's contents in a table, or implementing custom logic to highlight certain conditions.

Custom probes are particularly useful in debugging and data analysis, offering insights into the operation of a VI that might not be easily obtained through standard probes or debugging techniques. They extend the functionality of LabVIEW's debugging tools by enabling the creation of application-specific probes tailored to the unique requirements of each project.

== Creating a Custom Probe ==

Creating a probe allows you to have more control over how LabVIEW probes the data that flows through a wire. When you create a new probe, the data type of the probe matches the data type of the wire you right-click. Before you begin creating custom probes, refer to the caveats and recommendations.

=== Steps to Create a Custom Probe ===

'''Note:''' If you are creating a custom probe for a LabVIEW class or interface data type, some steps may vary depending on whether you are creating a member VI of the class or interface or a non-member custom probe. Member probes can access the private data of the class directly and display any aspect of it. A non-member custom probe may only display information accessible via the public interface of the class.

# Right-click a wire and select '''Custom Probe»New...''' from the shortcut menu to display the Create New Probe dialog box.
# Select whether to create a new probe or to base your probe on an existing one.
## To create a probe based on an existing one, select '''Create a probe from an existing probe'''. LabVIEW displays all supplied probes in the ''[LeabVIEW 20xx]]\vi.lib\_probes'' directory and any custom probes you've created.
## Click the '''Next''' button and select an existing probe to base the new probe on.
## Enter the filename, window title, shortcut menu name, and the directory where you wish to save the probe. LabVIEW stores custom probes in the ''[Documents]\LabVIEW Data\Probes'' directory by default. To make a custom probe the default for a particular data type, save it in the ''[LabVIEW 20xx]\user.lib\_probes\default'' directory.
## Click the '''Save''' button. LabVIEW opens a probe matching the existing probe you selected.

'''Note:''' For creating a non-member probe for a LabVIEW class or interface, follow the instructions above. For member probes, save the custom probe in the subdirectory with other member VIs of the class or interface for easy distribution.

# To create a new probe, select '''Create a new probe''' and click the '''Next''' button.
## Enter the filename, window title, shortcut menu name, and directory for the new probe.
## Click the '''Save''' button. LabVIEW opens a probe with a control matching the data type of the wire you right-clicked and includes a Boolean indicator acting as a conditional breakpoint. It also contains the '''To Probe String''' function for configuring the display value in the Probe Watch Window.
## (Optional) Wire any data type to the data value input of the '''To Probe String''' function to display the data as a string in the Value column of the Probe Watch Window. The function breaks down and converts data into a string that the Value String indicator can display, compressing and trimming as needed to fit the available space.
##:'''Note:''' LabVIEW automatically wires the control to the '''To Probe String''' function. You can remove this function if you wish to specify the string displayed in the Value column.
#:(Optional) Specify the string you want LabVIEW to display in the Value column by wiring that string to the Value String indicator.
# The block diagram shows a custom probe for numeric data, using a Case Structure to display "Greater than five" or "Less than five" instead of the default data display.
# After customizing the probe, save and close it. To edit it, open it from the directory where it was saved.

'''Note:''' The Create New Probe dialog box does not make the new probe a member of the class or interface by default. To make it a member probe, add it to the class or interface.

=== Using the Custom Probe ===

To use the probe, right-click the wire and select ''Probe'' from the shortcut menu. To change the default probe for a data type, right-click a wire of that data type, select ''Custom Probe'' from the shortcut menu, and choose from the available options.

'''Note:''' A custom probe does not become the default probe for any data type until used. For member probes, use the Class/Interface Properties dialog box to set it as the initial default probe when distributing the class or interface.

== Caveats and Recommendations When Using Custom Probes ==
* Custom probes only execute when data flows through the wire. That is, although you can operate the controls on a custom probe at any time, programmatic responses to the changed control values occur only when the probe receives data from the wire.
* You can debug a custom probe similar to a VI. However, a probe cannot probe its own block diagram, nor the block diagram of any of its subVIs. When debugging probes, use the generic probe.
* Save probes in the labview\user.lib\_probes\default or the Default Data\Probes directories. Probes saved in the labview\user.lib\_probes\default directory are available to anyone running LabVIEW on the computer remotely. This directory is useful for public probes. Because the Default Data directory changes based on which user is logged in to the computer, National Instruments recommends you save non-public probes in this directory.
* The main block diagram pauses until the probe finishes execution. Avoid using loops or Event structures in custom probes as these elements can increase the time it takes the probe to finish executing.
* Be careful when using uninitialized shift registers in custom probes. Even if a VI is non-reentrant, when that VI is used as a probe, all uninitialized shift registers behave the same as reentrant VIs. Each probe retains the last value of the loop and does not share these values with other instances of the same probe.

[[Category:Probes]]
[[Category:Debugging]]