Labview linux runtime engine

LabVIEW

Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.

• Subscribe to RSS Feed
• Mark Topic as New
• Mark Topic as Read
• Float this Topic for Current User
• Bookmark
• Subscribe
• Mute
• Printer Friendly Page

Linux VI with Runtime Engine Only

Re: Linux VI with Runtime Engine Only

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report to a Moderator

I have not read all the replies but I think noone has clarified this yet.

When «compiling» a program in labview. The builder is NOT making the code to machine code. It’s just smacking all the vi:s that the program needs into a llb in some way.

You can visualise this by renaming your executable to .llb and open it with labview.

The Runtime engine does simply what the development suite does execept that you have no editing options.

Re: Linux VI with Runtime Engine Only

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report to a Moderator

«Fox_Mccloud» wrote in message news:1171372209218-477378@exchange.ni.com.
Hello Guys. I have not read all the replies but I think noone has clarified this yet.When «compiling» a program in labview. The builder is NOT making the code to machine code. It’s just smacking all the vi:s that the program needs into a llb in some way.You can visualise this by renaming your executable to <applicatio_name>.llb and open it with labview.The Runtime engine does simply what the development suite does execept that you have no editing options.Cheers.//Beckman

This is not the compile proccess that you are describing. It’s the building an application proccess.

Each VI is compiled when you run it (or recompile it). When you run it, LabVIEW runs the machine code inside the VI.

When you build an application, the VI’s, with the compiled machine code inside them, are put inside an llb. That’s not compiling, that has been done already.

The way the rte and development env. execute compiled VI’s is exactly the same. But the rte needs compiled VI’s. The development env. can recompile the wires.

Re: Linux VI with Runtime Engine Only

• Mark as New
• Bookmark
• Subscribe
• Mute
• Subscribe to RSS Feed
• Permalink
• Print
• Report to a Moderator

To summaries, and close the thread with some new LV8.2 info:
«Wiebe@CARYA» wrote in message news:45cc3a7c$1@PYROS.natinst.com.
Hi,

We’re trying to start a VI on a Linux system, with only the runtime engine installed. But we’re having a few problems.

First, if the runtime engine installed without errors («rpm —install labview71-rte. i386.rpm» and «rpm —install labview-rte-aal. i386.rpm») how can I know for sure that it’s working? I can’t find any file that indicates that it is installed.

Must have done something wrong. Still clueless about this.

Is it possible (just like under windows) to start a VI with only the runtime engine? What should I call on the shell to start a VI?

This is only possible by building an executable. Until LV7.1, you can build an executable without a vi in it. When the exe is started from the command line with a vi as parameter, the main vi in the exe is not started, the parameterized VI is. Works both under Linux and windows.

Is it possible to run a windows VI under Linux, with only the runtime engine? I read somewhere on www.ni.com that to run a VI a rte of the LabVIEW version used to build the VI is needed. But is LV7.1 for Linux the same version as LV7.1 for windows? Is the Linux runtime engine capable of running the windows VI?

No it’s not. The compiled code needed to run a VI under windows and Linux differ. So the vi needs to be recompiled when the OS is switched. To recompile the VI, a development version of LV is needed.

In short, what we like to do is: Use windows to develop some VI’s with serial communication. Copy the VI’s to a Linux system. Start the VI’s.

One VMWare Linux or normal Linux desktop system (we used CentOS).
One (single board computer) SBC with Linux on it (we used CentOS, but LV should be picky about this).
Install LabVIEW Professional 8.2 on the desktop.
Install LabVIEW Runtime Engine 8.2 on the desktop.
Build a «splash screen» executable.
Put it on the SBC.
(Test it.)
Develop VI’s on the desktop, and copy them to the SBC.
Start the splash screen application, with the main VI as parameter.

Note that we used CentOS for a few reasons:

It is binary compatible with RedHat.
It has support for RPM’s. LV is supplied in RPM’s, so for Linux beginners it’s very easy.

The down side is that even the minimal install is 690 MB, without even an X server. It’s OK for our application, we have a 2 GB disk. But it should be possible to remove unnecessary stuff, and reduce Linux to 20-50 MB.
Any ideas are greatly appreciated.

Well, we finally got a LV8.2 Linux version (we have a software lease, and are alliance member).

Things changed a bit in LV8.2. It is no longer possible to build an executable without a VI in it. Also, the VI in the executable is started, even if the exe is started with another VI on the command line. So, to start a VI with only the runtime engine installed, one needs an exe with a «splash screen». A simple VI that hides it’s own front panel works fine.

Now the fun part starts. Getting the hardware to work.

Источник

Using the LabVIEW Run-Time Engine

You must install the LabVIEW Run-Time Engine on any computer on which you want to run any type of LabVIEW-built application. The LabVIEW Run-Time Engine includes the libraries and other files necessary to run basic application types built in LabVIEW.

Note��The LabVIEW Run-Time Engine is multilingual.

When you create build specification for an installer, the Application Builder includes the LabVIEW Run-Time Engine by default.

All types of applications built with one particular version of LabVIEW can share the same LabVIEW Run-Time Engine, so you need to install the LabVIEW Run-Time Engine for that version only once. However, if you want to run multiple LabVIEW-built applications created with different versions of LabVIEW on the same computer, you must install each version of the LabVIEW Run-Time Engine that corresponds with each version of LabVIEW used to create the application types. For example, if you want to run an application created in LabVIEW 7.0 and an application created in LabVIEW 8.0 on the same computer, the computer must have versions 7.0 and 8.0 of the LabVIEW Run-Time Engine.

Considerations for the LabVIEW Run-Time Engine

• (Windows) If you want to include the LabVIEW Run-Time Engine in an installer built with the Application Builder, remember that you must log on as an Administrator or a user with administrator privileges to run that installer. (Linux) When you install the LabVIEW Run-Time Engine on a target computer where you want to run an application that uses the Mathematics or Signal Processing VIs, enter yes when prompted to install the LabVIEW Run-Time Advanced Analysis Support package ( labview-rte-aal-1.1-1.i386.rpm ).
• Some VI Server properties and methods are not supported in the LabVIEW Run-Time Engine. Avoid using these properties and methods in the VIs you include in an application or shared library.
• Incorporate error handling into the VIs of the application because LabVIEW does not display automatic error handling dialog boxes in the LabVIEW Run-Time Engine.
• If the VI uses custom run-time menus, make sure the application menu items that the VI uses are available in the LabVIEW Run-Time Engine.
• When you close all front panel windows in an application, the application stops. If the VI you build into the application contains code that executes after the last front panel window closes, this code does not execute in the application. Avoid writing block diagram code that executes after the last front panel window closes.
• If you reference a VI in an application using the Call By Reference node, if a VI uses Property Nodes to set front panel properties, or if a front panel window appears to users, remove the checkmark in the Remove front panel checkbox for that VI from the Use default save settings section on the Source File Settings page of the Application Properties dialog box. If you remove the front panel window, the Call By Reference node or Property Nodes that refer to the front panel window will return errors that might affect the behavior of the application.

Источник

LabVIEW 32/64-bit vs Windows 32/64-bit

We recommend to use the LabVIEW 32-bit version, whatever is your Windows version (32/64-bit).

Installing LabVIEW

Linux TN (NFS, Installed centrally)

If you are part of the labview-users egrou p which can be requested via our support.

To be able to install LabVIEW on a Windows machine, you need administrator rights and your machine has to be able to connect to the CERN.CH domain.

For Internet Explorer, select «Save and run» to execute the installer

• LabVIEW 20xx (32-bit)
• LabVIEW 20xx Advanced Signal Processing Toolkit
• LabVIEW 20xx VI Analyzer Toolkit
• NI Device Drivers (if you use hardware)
• LabVIEW 20xx Mathscript RT module (if necessary)
• DIAdem 20xx SP2 (64-bit) (if necessary)

For activating ni products online, you need an account on ni.com, that can be created quickly if you don’t have one.

On a Linux system you need to make the script executable and run the installer as administrator/root.
Open the terminal and navigate to the location where you have stored the file (usually ~/Downloads)

cd ~/Downloads chmod +x ./install_lv_2012.sh sudo ./install_lv_2012.sh

If you are installing LabVIEW on a clean Linux 64 bit (such as SLC6 x64) system you might have to install some 32 bit compatibility libraries for it to run:

If you are not in the sudoers list or not running as root, you will not be able to install LabVIEW on Linux.

For more information take a look at Installation on Linux

The LabVIEW installer for Mac might complain that the installer is not from an identified developer and you need to navigate to System Preferences → Security & Privacy and click the button » Open Anyway » to authorise the packet/installer.

Once you installed LabVIEW .

Install also our RADE package, which adds integration to the CERN infrastructure and a selection of the best VI’s from the Open Source community.

Click on the RADE link for the details and for a quick overview:

1. RIO: provides GET, SET and Subscription for any RDA supported device. That means to see live data on the front panel of your LabVIEW application.
2. TGM: synchronise the actions in your application with the accelerator cycles.
3. RBAC: devices are usually protected by the Role Based Access method. Using RBAC you can use your role to control your device.
4. SQL: access data from the Logging and Measement databases. Petabytes of data are easily available for mathematical analysis in LabVIEW. Also access any other SQL DB.
5. eLogBook: add text and attachments directly from LabVIEW into the central eLogBooks (get an eLogBook login first and agree with the responsible of the logbook what you will write).
6. MTAlib: a selection of Open Source VI’s for better window management, more array functions (sort 2-D), delay function with Error-in and Error-out, etc.
7. PLC: communicate with your PLC by using one of the provided protocols: Libnodave, FetchWrite (or through OPC UA).

LabVIEW Run Time Engines (RTE)

The RTE is needed to execute compiled LabVIEW applications.

Each number indicates the compatible LabVIEW version.

For example, if an application was built using LabVIEW 2012 (32 bit on a 64 bit machine), you have to install the 32 bit 2012 runtime engine.

[1] To be able to install the LabVIEW RTE on a Windows machine, you need administrator rights and your machine has to be able to connect to the CERN.CH domain.

[2] If you are not in the sudoers list or not running as root, you will not be able to install the LabVIEW RTE on Linux.

Источник