LabVIEW 2016 Readme for GNU/Linux

June 2016

This file contains important information about LabVIEW 2016 for Linux, including system requirements, installation instructions, known issues, and a partial list of bugs fixed.

Refer to the NI website for the latest information about LabVIEW.

Refer to the labview/readme directory for readme files about LabVIEW add-ons, such as modules and toolkits.

System Requirements

Dropping Support for 32-bit Linux Distributions

Installation Instructions

Product Security and Critical Updates

Supported Modules and Toolkits

Known Issues

Bug Fixes

Accessing the Help

Legal Information

System Requirements

LabVIEW 2016 for Linux has the following requirements:

Linux Run-Time Engine Development Environment
Processor Pentium III/Celeron 866 MHz (or equivalent) or later (32-bit)
Pentium 4 G1 (or equivalent) or later (64-bit)
Pentium 4M (or equivalent) or later (32-bit)
Pentium 4 G1 (or equivalent) or later (64-bit)
RAM 256 MB 1 GB
Screen Resolution 1024 x 768 pixels 1024 x 768 pixels
Operating System Linux kernel 2.6x or 3.x
GNU C Library (glibc) Version 2.11 or later for the Intel x86_64 architecture (64-bit)
Red Hat Enterprise Linux Desktop + Workstation 6.5 or later
openSUSE 13.2 or openSUSE LEAP 42.1
Scientific Linux 6.5 or later
CentOS 7
Disk Space 108 MB (32-bit)
98 MB (64-bit)
1.1 GB for the complete installation of each bitness.
2.2 GB for the complete installation of both 32-bit and 64-bit LabVIEW.
Color Palette N/A LabVIEW and the LabVIEW Help contain 16-bit color graphics. LabVIEW requires a minimum color palette setting of 16-bit color.
Temporary Files Directory N/A LabVIEW uses a directory for storing temporary files. NI recommends that you have several megabytes of disk space available for this temporary directory.
Adobe Reader N/A You must have Adobe Reader installed to search PDF versions of all LabVIEW manuals.
Note  NI recommends that you use Firefox 10.0 or later to view the LabVIEW Help.

LabVIEW Drops Support for 32-bit Linux Distributions in 2016

LabVIEW dropped support for Intel 32-bit versions of Linux distributions as of July 1, 2016. Versions of LabVIEW that ship after July 1, 2016 may install and execute on Intel 32-bit distributions, but official support is not provided.

Installation Instructions

Depending on whether you are installing LabVIEW for the first time or upgrading from a previous version, refer to one of the following documents for information about installing LabVIEW:

  • LabVIEW Installation Guide—Includes information about installing LabVIEW, modules and toolkits, drivers, and hardware.
  • LabVIEW Upgrade Notes—Includes information about protecting existing VIs and projects before you install a new version of LabVIEW, as well as upgrade and compatibility issues and a complete list of new features in LabVIEW 2016.

You can access the LabVIEW Installation Guide and the LabVIEW Upgrade Notes at as well as on the installation media.

Note  If you purchased this product with an NI Software Suite or NI Product Bundle, use the installation media that shipped with your purchase to install this product.

Product Security and Critical Updates

Visit for security information about NI products. Visit for information about critical updates from NI.

Supported Modules and Toolkits

LabVIEW 2016 for Linux supports the following modules and toolkits.

  • Control Design and Simulation Module1
  • MathScript RT Module2
  • VI Analyzer Toolkit

1 The Control Design and Simulation Module does not support the System Identification VIs, System Identification Assistant, and Control Design Assistant.

2 The MathScript RT Module does not support the libraries class of MathScript RT Module functions.

Refer to the NI website for information about drivers compatible with LabVIEW for Linux.

Known Issues

You can access the software and documentation known issues list online. Refer to the NI website for an up-to-date list of known issues in LabVIEW 2016.

Bug Fixes

The following items are the IDs and titles of a subset of issues fixed in LabVIEW 2016. This is not an exhaustive list of issues fixed in the current version of LabVIEW. If you have a CAR ID, you can search this list to validate the issue has been fixed.

ID Fixed Issue
333388 Incorrect highlight execution order with LVOOP property node
405304 Menu Item VIs can cause LabVIEW to crash
425622 Edit Events menu for Event Structures can delete the new event you are trying to create
434420 Leading zeros are not allowed in Numeric Case Selector values
518954 Unconstrained Downhill Simplex ignores some stopping conditions
519216 LabVIEW crash when closing subVI Icon Editor that was opened from VI Hierarchy
526175 Spreadsheet String to Array VI crashes when an empty string is wired to delimeter input
530595 Not a Refnum Primitive returns incorrect value when evaluating a specific type of "Invalid Refnum"
534553 Quit LabVIEW function closes VI if you choose cancel
539895 File Dialog Express VI alters error chain
544526 Fatal Internal Error 0x89B93EF0: "drawmgr2.cpp" when running Mac application for extended time
544533 Scripting dynamic events on an event structure returns Error 1
544907 Delaunay Triangulation hangs on certain input data
546555 Error 1025 when creating Override VI for an already open parent class
547120 Incorrect VI dataflow when using an Error Wire with a parallelized For Loop
549429 DAbort 0x34E86741 ConvertNum called with non-numeric
554381 Sort items in the Choose Implementation class dialog alphabetically
555758 Using the 'Unflatten From String Function' to unflatten an "invalid" string within LabVIEW x64 can cause the computer to become unresponsive
555788 Using "Fast File Format" to build an executable could result in error 2208 in some cases
555868 Using the Tree Control 'Drag Starting? Event' allows you to Delete the reference to the item you are dragging and can result in a LabVIEW crash
561615 In specific cases, building a LabVIEW executable with shared variables causes Error 1003 during the build
564219 Sometimes if RFmx continuously modifies the loading state of the UI thread, a race condition can occur and potentially cause a crash
567353 When an XNode output is wired to the Loop count of a Parallel For Loop the VI breaks
567369 LabVIEW crashes when getting the properties of a class containing a member VI with certain connector pane configurations
569362 In cases of extreme load on a TCP server, LabVIEW can miss new connection notifications, causing a timeout
569793 Rare persistent Error 56 at TCP Read
570547 Bluetooth Read, Write, and Close primitives have TCP icon
571421 In certain cases, dynamically calling a VI containing a SubVI can cause a memory leak. The size of the memory leak scales with the size of the SubVI and its dependencies
571556 Showing Visible Items on Waveform Chart probe does not resize chart in the probe window
571713 Scripting a Value Change event for an IVI Logical Name control crashes LabVIEW
571935 Closing a project library containing a class with unsaved changes does not prompt for save
573539 In some cases, DNS name resolution in LabVIEW can block other TCP calls
574048 Error 8 when trying to create an actor under an unsaved library
575278 Error 1019 when creating a message, if the actor contains a never-before-saved method
578899 LabVIEW 64-bit Development Environment has the potential to crash while running certain RFmx examples
580210 Remote debugging sessions that involve packed project libraries can stop unexpectedly
580212 Remote debugging VIs that were built without front panels can close the session unexpectedly
581199 Unflatten From String throws error 74, does not update indicators

Accessing the Help

Refer to the LabVIEW Help, accessible by selecting Help»LabVIEW Help from LabVIEW, for information about LabVIEW 2016.

Legal Information


© 2004–2016 National Instruments. All rights reserved.

Under the copyright laws, this publication may not be reproduced or transmitted in any form, electronic or mechanical, including photocopying, recording, storing in an information retrieval system, or translating, in whole or in part, without the prior written consent of National Instruments Corporation.

NI respects the intellectual property of others, and we ask our users to do the same. NI software is protected by copyright and other intellectual property laws. Where NI software may be used to reproduce software or other materials belonging to others, you may use NI software only to reproduce materials that you may reproduce in accordance with the terms of any applicable license or other legal restriction.

End-User License Agreements and Third-Party Legal Notices

For end-user license agreements (EULAs) and copyright notices, conditions, and disclaimers, including information regarding certain third-party components used in LabVIEW, refer to the Copyright topic of the LabVIEW Help.

U.S. Government Restricted Rights

If you are an agency, department, or other entity of the United States Government ("Government"), the use, duplication, reproduction, release, modification, disclosure or transfer of the technical data included in this manual is governed by the Restricted Rights provisions under Federal Acquisition Regulation 52.227-14 for civilian agencies and Defense Federal Acquisition Regulation Supplement Section 252.227-7014 and 252.227-7015 for military agencies.

IVI Foundation Copyright Notice

Content from the IVI specifications reproduced with permission from the IVI Foundation.

The IVI Foundation and its member companies make no warranty of any kind with regard to this material, including, but not limited to, the implied warranties of merchantability and fitness for a particular purpose. The IVI Foundation and its member companies shall not be liable for errors contained herein or for incidental or consequential damages in connection with the furnishing, performance, or use of this material.


Refer to the NI Trademarks and Logo Guidelines at for information on NI trademarks. Other product and company names mentioned herein are trademarks or trade names of their respective companies.


For patents covering the NI products/technology, refer to the appropriate location: Help»Patents in your software, the patents.txt file on your media, or the NI Patent Notice at