LabVIEW Wiki - User contributions [en]

LabVIEW 2020

2026-03-30T19:34:59Z

Rolfk: Added Transport Layer Security Functions as new feature

{{prevnext|LabVIEW 2019|LabVIEW Versions|LabVIEW 2021}}
{{LabVIEW Version
|version=LabVIEW 2020
|logo=File:LV2020.png
|release=May 2020
|release_sp1=January 2021 (SP1)
|change_0=Interfaces
|change_1=Partially broken wires
|change_2=Publish web services to NI Web Server
|change_3=Repairing packages
|change_4=Clear variant data types
|change_5=Transport Layer Security Functions}}

==New features in LabVIEW 2020==
{{ambox|text=This is a subset of new features in LabVIEW 2020 that were mentioned on [https://twitter.com/labview Twitter] and [https://www.facebook.com/labview/ Facebook]. See the Upgrade Notes for a complete list of changes.}}
* Interfaces - Expanded object-oriented programming to introduce interfaces as a companion feature to classes.
* Clear Variant Data right-click menu option<ref name="fb-clear-variant-data"/> - Clears data from Variant controls and indicators.
* Enum to Array of Enums function<ref name="fb-enum-to-array-of-enums"/> - Creates an array with all possible Enum values.
* Create NI GUID function<ref name="fb-create-ni-guid"/> - Adds a native GUID function to LabVIEW.
* Remove <code> (no error)</code> from Error Control (hidden INI key)<ref name="fb-remove-no-error-from-error-control"/> - Set <code>NI.LV.RemoveNoError=TRUE</code> to remove the <code> (no error)</code> suffix from Error Controls.
* Build Path Relative Path Input<ref name="fb-build-path-relative-path-input"/> - The default type for the second input of the Build Path function was changed to relative Path instead of String.
* Break Bad Wire Branches Only<ref name="fb-break-bad-wires-only"/> - Wires only break for broken branches instead of all branches.
* Class Dialog Improvements<ref name="fb-class-dialog-improvements"/> - The dialog for creating new classes was changed to provide more features.
* Double Click Array To Cluster<ref name="fb-double-click-array-to-cluster"/> - The property dialog for the Array To Cluster function can now be opened by a double-click.
* Set Text Icon for Project Libraries<ref name="fb-edit-icons"/> - The Project Library configuration dialog has a new ''Set Text Icon...'' button, which provides a way to quickly set the text, text color and background color for the library icon.
* Range Limits for Type<ref name="fb-range-limits-for-type-vi"/> - Returns the maximum and minimum values for a given data type.
* Generate Checksum Values<ref name="fb-generate-checksum-values"/> - Adds native functions to calculate SHA-2 and SHA-3 checksums to LabVIEW.
* Hide Event Data Node and Iteration Terminal<ref name="fb-hide-event-data-node-and-iteration-terminal"/> - It is now possible to hide Event Data Nodes in Event Structures and Iteration Terminals on For- and While loops.
* Multi-Error Support<ref name="fb-multi-error-support"/> - Collect multiple error values on a single error wire (adds a new subpalette for handling multiple errors).
* Hide Last Item for Rings when running<ref name="fb-hide-last-item-for-rings"/> - Adds an option to hide the last item from a ring control.
* Transport Layer Security Functions (TLS) for TCP/IP communication

==Application icon design==
The application icon was changed for LabVIEW 2020 SP1:

[[File:LV2020SP1.png]]

==External links==
* [https://www.ni.com/en-us/shop/labview/release-details.html LabVIEW Release Details]
* [https://www.ni.com/pdf/manuals/374715n.html LabVIEW 2020 Readme]
* [https://www.ni.com/pdf/manuals/374715p.html LabVIEW 2020 SP1 Readme]
* [https://www.ni.com/pdf/manuals/371780t.pdf LabVIEW 2020 Upgrade Notes]
* [https://www.ni.com/en-us/support/documentation/bugs/20/labview-2020-sp1-bug-fixes.html LabVIEW 2020 SP1 Bug Fixes]
* [https://www.ni.com/en-us/support/documentation/bugs/20/labview-2020-known-issues.html LabVIEW 2020 Known Issues]
* [https://www.ni.com/en-us/support/documentation/bugs/20/labview-2020-sp1-known-issues.html LabVIEW 2020 SP1 Known Issues]
* [https://youtu.be/rXLxo9zuBSc What’s new in LabVIEW 2020] by Tom’s LabVIEW Adventure

==References==
<references>
<ref name="fb-clear-variant-data">[https://www.facebook.com/labview/videos/313204460045993 Clear Variant Data] by Darren Nattinger</ref>
<ref name="fb-enum-to-array-of-enums">[https://www.facebook.com/labview/videos/283647629401421 Enum to Array of Enums] by Darren Nattinger</ref>
<ref name="fb-create-ni-guid">[https://www.facebook.com/labview/videos/570111097012827 Create NI GUID.vi] by Darren Nattinger</ref>
<ref name="fb-remove-no-error-from-error-control">[https://www.facebook.com/labview/videos/615411719411123 Remove (no error) From Error Control] by Darren Nattinger</ref>
<ref name="fb-build-path-relative-path-input">[https://www.facebook.com/labview/videos/299469061159932 Build Path Relative Path Input] by Darren Nattinger</ref>
<ref name="fb-break-bad-wires-only">[https://www.facebook.com/labview/videos/672708713385685 Break Bad Wires Only] by Darren Nattinger</ref>
<ref name="fb-class-dialog-improvements">[https://www.facebook.com/labview/videos/3102767176494288 Class Dialogue Improvements] by Darren Nattinger</ref>
<ref name="fb-double-click-array-to-cluster">[https://www.facebook.com/labview/videos/349473259602855 Double Click Array To Cluster] by Darren Nattinger</ref>
<ref name="fb-edit-icons">[https://www.facebook.com/labview/videos/350338116077871 Edit Icons] by Darren Nattinger</ref>
<ref name="fb-range-limits-for-type-vi">[https://www.facebook.com/labview/videos/690573941892844 Range Limits for Type VI] by Darren Nattinger</ref>
<ref name="fb-generate-checksum-values">[https://www.facebook.com/labview/videos/1254380881613189 Generate Checksum Values] by Darren Nattinger</ref>
<ref name="fb-hide-event-data-node-and-iteration-terminal">[https://www.facebook.com/labview/videos/372715580702001 Hide Event Data Node and Iteration Terminal] by Darren Nattinger</ref>
<ref name="fb-multi-error-support">[https://www.facebook.com/labview/videos/191762282418740 Multi-Error Support] by Darren Nattinger</ref>
<ref name="fb-hide-last-item-for-rings">[https://www.facebook.com/labview/videos/842160236599572 Hide Last Item for Rings] by Darren Nattinger</ref>
</references>

{{stub}}

[[Category:LabVIEW Versions]]

LabVIEW 6i

2023-11-10T08:44:00Z

Rolfk: Add event structure as new feature

{{prevnext|LabVIEW Real-Time|LabVIEW Versions|LabVIEW 7 Express}}
{{LabVIEW Version
|version=LabVIEW 6i
|logo=File:LV7.png
|release=August 2000 (6.0)
|release_sp1=February 2001 (6.0.2)
|release_sp2=January 2002 (6.1)
|change_0="Internet Ready"
|change_1=DataSocket Improvements
|change_2=Waveform Data Type
|change_3=Modern Control Style
|change_4=New Controls (Tab Control and Multicolumn Listbox)
|change_5=Event Structure
|change_6=Error Case Structure
|change_7=Polymorphic VIs}}

==Download Links ==
Links are to National Instrument's website. A valid license from NI is required for all downloads.
*[http://www.ni.com/download/labview-development-system-6.0.2/641/en/ LabVIEW Development System 6.0.2 for Windows/ME/2000/98/95/NT]
*[http://www.ni.com/download/labview-development-system-6.0.2/632/en/ LabVIEW Development System 6.0.2 for Linux]
*[http://www.ni.com/download/labview-run-time-engine-6.0.2/697/en/ LabVIEW Run-Time Engine 6.0.2 (All Languages) for Windows/2000/98/95/NT]

==Documentation==
Links are to National Instrument's website.
* LabVIEW 6.0
** [http://www.ni.com/pdf/manuals/321778c.pdf Release Notes]
** [http://www.ni.com/pdf/manuals/321780c.pdf Upgrade Notes]
* LabVIEW 6.1
** [http://www.ni.com/pdf/manuals/321778d.pdf Release Notes]
** [http://www.ni.com/pdf/manuals/321780d.pdf Upgrade Notes]

[[Category:LabVIEW Versions]]

Linx Toolkit Hardware Compatibility List

2020-08-19T09:24:18Z

Rolfk:

This is a list of tested hardware that works with the [[LINX]] Toolkit that ships with the [[LabVIEW Community Edition]].

== Raspberry Pi ==
* Raspberry Pi 4 Model B
** '''SoC''': Broadcom BCM2711B0, Quad-Core Cortex-A72 (ARMv8-A), 64-bit @ 1.5GHz
* Raspberry Pi 3 Model B+
* Raspberry Pi 3 Model A+
** '''Soc''': Broadcom BCM2837B0, Quad-Core Cortex-A53 (ARMv8), 64-bit @ 1.4GHz
* Raspberry Pi 3 Model B
** '''Soc''': Broadcom BCM2837, Quad Core Cortex-A53, (ARMv8) 64bit CPU @ 1.2GHz
* Raspberry Pi 2 Model B v1.2
** '''Soc''': Broadcom BCM2837, Quad Core Cortex-A53, (ARMv8) 64bit CPU @ 900MHz
* Raspberry Pi 2 Model B
** '''Soc''': Broadcom BCM2836, Quad Core Cortex-A7 (ARMv7) 32bit CPU @ 900MHz

== Beaglebone Black ==
* Processor: AM335x 1GHz ARM® Cortex-A8

== Successful manual installation of runtime (no direct Linx support yet) ==
[https://forums.ni.com/t5/LINX/Successfully-running-LabVIEW-on-a-RockPi-S-512MB/m-p/4064100 NI Forum post with instructions for arm64 Debian OS]
* Rock Pi S: Rockchip RK3308 Quad-core ARM Cortex-A35 (ARMv8-A) @ 1.3GHz

== External links ==
* [https://www.raspberrypi.org/ Raspberry Pi]
* [https://www.beagleboard.org/ BeagleBoard]
* [https://www.arduino.cc/ Arduino]

DLL/shared library

2008-05-07T07:38:20Z

Rolfk:

The first question would be if you really need to do this. While it is a powerful tool it is also tedious work to have to interface to external code through DLLs/shared libraries.

For the rest of this text I will refer to shared libraries but this should be always read to mean DLLs too, which is the term Windows uses for shared libraries.

With the Import Library Wizard in LabVIEW 8.2 a lot of the actual work of interfacing has been automated but this is just an automatic tool and it can not do everything for you. Especially for more complex shared library interfaces it simply has to fail for particular functions and those are also the ones that are likely to take up hours and hours of fiddling, testing and learning about how a C compiler actually puts variables into memory.

The shared library interface in all OSes so far was designed for and around what C needs and can provide. Therefore one needs to know some basic principles about C and for more complex interfaces also relatively intimate knowledge about how a C compiler actually puts up things in memory and such. This is a very steep learning curve for someone not already familiar with C.

An extra difficulty is that the shared library interface has none of the more modern features like automatic type checking and parameter validation like what ActiveX and .Net provide for instance. This means that one single error in the configuration of the Call Library Node or a bug in the shared library itself can and usually will have fatal consequences sooner or later. This can in the best case show as a Protection fault error dialog at runtime of that function, but can also cause so subtle damage that LabVIEW will only crash at some later point when trying to access information that was destroyed earlier on. One possibility is for instance that it will often crash when you try to close LabVIEW since it tries to deallocate resources that have been destroyed by a misbehaving shared library or configuration thereof earlier on.

DLL/shared library

2008-05-07T06:56:14Z

Rolfk: New page: The first question would be if you really need to do this. While it is a powerful tool it is also tedious work to have to interface to external code through DLLs/shared libraries. For th...

The first question would be if you really need to do this. While it is a powerful tool it is also tedious work to have to interface to external code through DLLs/shared libraries.

For the rest of this text I will refer to shared libraries but this should be always read to mean DLLs too, which is the term Windows uses for shared libraries.

With the Import Library Wizard in LabVIEW 8.2 a lot of the actual work of interfacing has been automated but this is just an automatic tool and it can not do everything for you. Especially for more complex shared library interfaces it simply has to fail for particular functions and those are also the ones that are likely to take up hours and hours of fiddling, testing and learning about how a C compiler actually puts variables into memory.

The shared library interface in all OSes so far was designed for and around what C needs and can provide. Therefore one needs to know some basic principles about C and for more complex interfaces also relatively intimate knowledge about how a C compiler actually puts up things in memory and such. This is a very steep learning curve for someone not already familiar with C.

An extra difficulty is that the shared interface has none of the more modern features like automatic type checking and parameter validation like what ActiveX and .Net provide for instance. This means that one single error in the configuration of the Call Library Node or a bug in the shared library itself can and usually will have fatal consequences sooner or later. This can in the best case show as a Protection fault error dialog at runtime of that function, but can also cause so subtle damage that LabVIEW will only crash at some later point when trying to access information that was destroyed earlier on. One possibility is for instance that it will often crash when you try to close LabVIEW since it tries to deallocate resources that have been destroyed by a misbehaving shared library or configuration thereof earlier on.

External Code

2008-05-07T06:41:18Z

Rolfk:

*[[DLL/shared library]]
*[[Excel]]
*[[Word]]
*[[ActiveX]]
*[[.Net]]
*[[Shell Command]]

LabVIEW configuration file/Miscellaneous

2007-05-18T11:14:27Z

Rolfk:

{{LabVIEW configuration back}}
[[Category:Development Environment]]
This is a list of Miscellaneous LabVIEW ini File settings.

{{ labviewconfigurationkey
| keyname = MRUFolders
| example = MRUFolders=TRUE
| datatype = b
| description = MRUFolders:Most recently used folders. Every time you select a file in a file dialog in LabVIEW, that location (folder) becomes the new top item in the location area (left side of the dialog) of the Windows file dialog.
| permitted_values = TRUE, FALSE
| default = FALSE
| LV1 = 8.2
| OS1 = w
}}
== BldApp.RemovePolyVIsandTypedefs ==
Example: <code>BldApp.RemovePolyVIsandTypedefs=FALSE</code> 
Description: Setting this to <code>TRUE</code> stops the LabVIEW Application Builder from agressively removing polymorphic VIs and typedefs that it thinks are not required 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>TRUE</code> 
LabVIEW Versions: 7.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: By default, the LabVIEW 7.x Application Builder does not include type definitions and unused instances of polymorphic VIs into executable in order to decrease size of application. This setting can be changed in the LabVIEW 7.1 applciation Builder in the Application Settings page.
If a VI in your build calls an external VI that uses a type definition in order to pass parameters, and the AppBuilder is unaware of this external VI, it will end in tears.
Also there is one other issue which makes this setting very important. In LabVIEW 7.x, by disconnecting typedefs from controls they did loose their default data and return to LabVIEWs default default data. This could be a major problem if you used strict typedefed clusters on front panels to provide certain default data when unwired and those default data did not match LabVIEWs default default data. This has been mostly fixed in newer LabVIEW versions from 8.0 on. 

== cleanupVisa ==
Example: <code>coerceFromVariant=TRUE</code> 
Description: Force variants to automatically coerce to any data type that they are connected to 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: Tread carefully, as using this function removes coercion notifivation, and does not useerror handling 

== cleanupVisa ==
Example: <code>cleanupVisa=TRUE</code> 
Description: Automatically close VISA sessions - do not require the use of the ''VISA Close'' VI 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== dropThroughClicks ==
Example: <code>dropThroughClicks=FALSE</code> 
Description: Allow drop-through clicks 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>TRUE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== ExternalNodesEnabled ==
Example: <code>ExternalNodesEnabled=FALSE</code> 
Description: Enables use of [[External Nodes]] 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: 6.x?, 7.x: <code>TRUE</code> 8.x: <code>FALSE</code>? 
LabVIEW Versions: 6.x?, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== ExternalNodeDebugging ==
Example: <code>ExternalNodeDebugging=FALSE</code> 
Description: Shows External Nodes for what they are: sequence diagrams 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== hotMenus ==
Example: <code>hotMenus=FALSE</code> 
Description: Use hot menus 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>TRUE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== openInRun ==
Example: <code>openInRun=TRUE</code> 
Description: When opening VIs in the development environment, open them in ''run mode'' 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== readOnlyLock ==
Example: <code>readOnlyLock=TRUE</code> 
Description: Treat read-only VIs as locked 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: It is important to set this to <code>TRUE</code> when using source code control outside of the LabVIEW environment, so LabVIEW will not allow a VI that is not checked out to the user to be edited 

== showBDConstName ==
Example: <code>showBDConstName=TRUE</code> 
Description: Show auto-constant labels 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== ShowTipStrings ==
Example: <code>ShowTipStrings=FALSE</code> 
Description: Display Tip Strips during execution 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>TRUE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]][[Image:logo.Sun.png]] 
Notes: None 

== skipNavigatorDialog ==
Example: <code>skipNavigatorDialog=TRUE</code> 
Description: Skip the navigation dialog on development environment launch 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== suppressFileDlgForMissingVIs ==
Example: <code>suppressFileDlgForMissingVIs=TRUE</code> 
Description: Suppresses the file dialog for when loading a VI that has missing SubVIs 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== useNativeFileDialog ==
Example: <code>useNativeFileDialog=FALSE</code> 
Description: Use the OS native file dialogs 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>TRUE</code> 
LabVIEW Versions: 5.x, 6.x, 7.x, 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None 

== XNodeWizardMode ==
Example: <code>XNodeWizardMode=FALSE</code> 
Description: Allows contextual menus on [[XNodes]] to facilitate debugging 
Datatype: Boolean 
Permitted Values: <code>TRUE</code> or <code>FALSE</code> 
Default Value: <code>FALSE</code> 
LabVIEW Versions: 8.x 
OS's Supported: [[Image:logo.Windows.png]][[Image:logo.Mac.png]][[Image:logo.Linux.png]] 
Notes: None