LabVIEW 2018 Toolkits and Modules

March 2018 This file contains important information about LabVIEW 2018 for Linux, including system requirements, installation instructions, known issues, and a partial list of bugs fixed for LabVIEW 2018. 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 Installation Instructions Product Security and Critical Updates Supported Modules and Toolkits Supported Drivers Known Issues Bug Fixes Accessing the Help Additions to the LabVIEW Help Legal Information System Requirements LabVIEW 2018 for Linux has the following requirements: Linux Run-Time Engine Development Environment Processor Pentium 4 G1 (or equivalent) or later Pentium 4 G1 (or equivalent) or later 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 openSUSE LEAP 42.2 openSUSE LEAP 42.3 Red Hat Enterprise Linux Desktop + Workstation 6.x Red Hat Enterprise Linux Desktop + Workstation 7.x CentOS 7 Disk Space 98 MB 1.1 GB for the complete installation 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 LabVIEW 2018 for Linux is available only in 64-bit. LabVIEW and LabVIEW Run-Time Engine require 64-bit processors which support SSE2 instructions. Installation Instructions Complete the following steps to install and activate LabVIEW for Linux. Are you installing LabVIEW for the first time? Insert and mount the LabVIEW installation media. As the root user in the mounted directory, enter sh ./INSTALL to install LabVIEW in the /usr/local directory. To install LabVIEW modules and toolkits, refer to the readme of each product for installation instructions. The VI Analyzer Toolkits installs with the LabVIEW Professional Development System for Linux. You can install NI device drivers from ni.com/linuxdrivers. Are you upgrading from a previous version of LabVIEW? Refer to the LabVIEW Upgrade Notes for information about protecting existing VIs and projects before installing a new version of LabVIEW, as well as upgrade and compatibility issues and a complete list of new features in LabVIEW 2018. 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 ni.com/security for security information about NI products. Visit ni.com/critical-updates for information about critical updates

From NI. Supported Modules and Toolkits LabVIEW 2018 for Linux supports the following modules and toolkits. Control Design and Simulation Module1 MathScript RT Module2 VI Analyzer Toolkit3 Application Builder3 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. 3 The VI Analyzer Toolkit and Application Builder install with the LabVIEW Professional Development System. For the LabVIEW Full Development System, you can purchase and install the VI Analyzer Toolkit and Application Builder with their own separate media. Refer to the readme of each product for more information about system requirements, installation instructions, and activation. Supported Drivers Refer to the NI website for information about drivers compatible with LabVIEW for Linux. To use hardware with LabVIEW 2018, install the latest version of the driver for the device. Refer to the readme of each driver for more information about system requirements and installation instructions. 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 2018. Bug Fixes The following items are the IDs and titles of a subset of issues fixed in LabVIEW 2018. 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 457851 Bundling class data is slower than bundling cluster data. 536763 Pop-up menus can appear only limited number of times before LabVIEW crashes. 630227 LabVIEW incorrectly allows dropping a shared variable into a cluster. 631802 Exporting typedef array of numerics to Excel may crash LabVIEW. 639000 LabVIEW crashes when updating the radix of a numeric control on an Actor Core VI that is running. 643107 Changing the line styles of multiple plots does not work as expecting in XY graphs. 645059 Uninitialized shift registers may cause incorrect type propagation. 648582 Cannot create Express VIs in certain localized versions of LabVIEW. 658587 Rescripting a message for an actor on a Linux RT target results in error 7. 664649 Accessing a DVR and deleting its reference in parallel can, in certain circumstances, cause LabVIEW to crash. 666823 VIs that use channel wires are broken when built into a packed project library. 670440 When dynamically registering events, LabVIEW may behave unexpectedly if an event is fired and unregistered before it is processed. 671753 The LabVIEW Application Builder has the potential to hang when building malleable VIs with subarray or substring inputs. 672120 Malleable VIs may not properly break after you rename

SolutionThe LabVIEW 32-bit is our first recommendation since it can be installed and used on either 32-bit or 64-bit operating systems, and it has wider compatibility with Modules and Toolkits, as well as greater support for 3rd-party Add-Ons. 32-bit Modules and Toolkits cannot be used with 64-bit LabVIEW.LabVIEW 64-bit does not provide any speed improvements over LabVIEW 32-bit, but it does allow the program access to more system memory at once. While most of our users find that the 32-bit version provides plenty of resources for their projects, some specialized application areas may require this extra memory. If your program is likely to handle very large arrays or to process images that are particularly high definition, you may find that LabVIEW 64-bit is the better option for you.In general, we recommend that developers start by working in LabVIEW 32-bit, and only move to LabVIEW 64-bit if they find that they need the additional memory that it provides.

We no longer support Internet Explorer v10 and older, or you have compatibility view enabled. Disable Compatibility view, upgrade to a newer version, or use a different browser. Register Login Help Turn on suggestions Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type. Showing results for Search instead for Did you mean: Topic Options Subscribe to RSS Feed Mark Topic as New Mark Topic as Read Float this Topic for Current User Bookmark Subscribe Mute Printer Friendly Page All Forum Topics Previous Topic Next Topic Does Application developed Using LabVIEW requires License to distribute it to other users Solved! Go to solution This application basically Modbus Device simulator it can run on any PC how i can confirm it requires license to execute on other user machine or can i distribute it freely to any userguide me on this ? You can create an installer in the Licensed version and distribute/Deploy to as many as possible if you are not using any toolkits which requires RTE License. ----------------------------------------------------------------------------------------------------------------Palanivel Thiruvenkadam | பழனிவேல் திருவெங்கடம் LabVIEW™ Champion |Certified LabVIEW™ Architect |Certified TestStand DeveloperKidlin's Law -If you can write the problem down clearly then the matter is half solved.----------------------------------------------------------------------------------------------------------------- All of your source code and compiled executables are your (or your company's) intellectual property.You are free to distribute your source code and executables as you see fit.You can even charge for them as long as you are:Not using the LabVIEW Community EditionNot charging for the required LabVIEW Runtime librariesNot distributing the LabVIEW development package, separately purchased add-ons, or toolkits Some NI and third party toolkits may have other licensing and distribution restrictions =========================== Engineer Ambiguously =========================== I think technically you have to put in a little readme regarding LV, but I can't remember what that is. Bill(Mid-Level