Linux VI with Runtime Engine Only

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...
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?
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?
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.
Any ideas are greatly appreciated.
Wiebe.

"shoneill" <[email protected]> wrote in message news:[email protected]...
Wiebe,I wrote that the binary code is OS dependent, not independent.  Please re-check my post (and your reference to my post to rule out cheeky editing.... )Regarding running a linux VI on linux without the development
You're right. Let's blame it on the language barier (on my side), and today being fryday. Still I don't see why assembler code can't be the same on two exactly the same i386 processors. The OS stuff should be handled in the runtime engine, and the add's mul's, call's etc. are the same. But I haven't given in much thought, and never tried anything like that. I'm sure their will be some problems.
environment, I wouldn't know since I've never used LV on linux (yet).  I thought the original duscussion was about running a VI from one platform on another without requiring the development environment to re-compile. 
It was about running a VI on Linux with only the rte. And what's needed to make this happen.
Can't you just build a wrapper VI to call the VI from a built application (provide path and hey presto, it can be called dynamincally.....no?)I also agree that a bit more multi-platform support would ultimately help NI, but I can understand
Yes, if we had an application builder for Linux, we could make a wrapper. It would solve the licensing problem. Perhaps someone can make a Linux application wrapper/vi starter for LV8.2 (we'd be happy with any version though)?
About the support.. Somehow someone forget to put all the Linux documentation on ni.com.
the thinking behind it.  Not that I agree, I just understand Further, I believe the run-time is required to prevent each and every LV application being huge.  But sometimes I wish we could distribute without theis run-time Stigma (or better - have the choice).You've raised an interesting point by questioning the existance of the run-time engine......Shane.Message Edited by shoneill on 02-09-2007 04:01 PM
Someone ought to make a virtual machine that can execute LabVIEW's executable code inside a vi, and simulate the runtime engine at the same time : ) It will take some time though...
Regards, Wiebe.

Similar Messages

System Level Exception, error -17502 when running VI with RunTime Engine

My sequence conains a single Labview VI. The sequence functions correctly with the Labview RunTime engine NOT selected in the "Advanced Setttings" tab. When I enable the check box to always run the VI with the Runtime Engine, TestStand generates the following error "System Level Exception, error -17502. My teststand version is 3.5, with LV 8.2.
Thanks
Peter V.

Hi,
Are you sure you have LV 8.2 RTE on your system?
Regards
Ray Farmer
Regards
Ray Farmer

Using TS 2.0 and LV 8.6 with Runtime Engine

Hi All,
I just got a project to use an old version of TS and a new version of LV. Can I use LV 8.6 VIs that are not built in TS 2.0 using only the 8.6 RT Engine? I have installed all of TS 2.0 and the LV 8.6 RTE, but it does not run and it generates an error. I don't have enough LV liscences for each machine and I don't have the LV 8.6 App Builder. The LV adapter is configurable with a LVGUITRS and a LVRTS, but I can't seem to find anything on how to configure TS with a newer RTE.
Help ;-)
Jim

Jim,
I just wanted to clarify something.
As a member of the TestStand R&D team, I can confirm that we have done extensive testing with LabVIEW 8.6 for all supported versions of TestStand (3.5, 4.0, 4.0.1, 4.1). All versions of TestStand 3.5 and above will work with any version of LabVIEW 8.0 and above.
When TestStand releases, NI specifies the minimum version of LabVIEW in the TestStand Release Notes.
When LabVIEW releases, NI specifies the minimum version of TestStand in the LabVIEW Upgrade Notes.
Message Edited by Josh W. on 11-10-2008 05:04 PM
Josh W.
Certified TestStand Architect
Formerly blue

Run Linux script with Runtime.exec

Hi there!
I want to run some Linux script files out of a Java application.
I'm currently using a code like this:
Runtime rt = Runtime.getRuntime();
Process p=rt.exec("//home//scriptFile1");But this isn't working. Although I'm getting no exeption, the file isn't executed.
It looks like he's doing something, but he's definitly not processing the file.
I think the problem is probably, that in scriptFile1, I call some other script files (which call itself some other script files).
E.g. like this:
scriptFile1:
scriptFile2
binary1
binary2
scriptFile3Any ideas?
Thank you!

Hi! I now get at least some error messages, when I call the script file:
knoppix@Knoppix:~/Desktop$ java Main
start
ERROR>/media/hda5/scripts/startds_2: line 1: stop: command not found
ERROR>/media/hda5/scripts/startds_2: line 3: dspp_2: command not found
ERROR>/media/hda5/scripts/startds_2: line 5: killcan: command not found
ERROR>/media/hda5/scripts/startds_2: line 7: canpdemsimeit: command not found
ERROR>/media/hda5/scripts/startds_2: line 9: demsimeit: command not found
ERROR>/media/hda5/scripts/startds_2: line 11: guidemsimeit: command not found
ERROR>/media/hda5/scripts/startds_2: line 13: MCAbrowser: command not found
ExitValue: 0These "lost" commands are all located in the same directory as the script I call, so I wonder why.
I could adjust every command by adding in front of it the absolute path in the script file. That would work. But maybe I can pass in some other way the directory, in which he should search for the commands. That would save me a lot of work...
I will RTFM but if anyone has currently an idea: please post...
THX

DSC runtime engine problems

Hi,
I recently started a project which involves DSC runtime engine. This being my first contact with runtime engines, i obviously ran into some problems. Hope someone can shed some light. Here goes: I developed a project on my work laptop on which I have LV / DSC 8.6 installed. The project is then built into an EXE application and then run on a desktop computer with DSC runtime engine.The desktop computer receives data from a PLC through an OPC server (which is not NI OPC server). At first, I imported a csv file containing the list of variables in my project with the correct path of the OPC server from the desktop. When I ran the EXE application on the desktop, I got an error (PSP Led was red) saying that the variables could not be read / written. This was because the variables were not declared in the Distributed System Manager. And so my first question is this: is there a way to import my list of variables from a csv file or something similar, and if so, how can i achieve this? Because so far, all I was able to do was to manually enter only one variable at a time in the Distributed System Manager, and after about 50 of them I decided I would really hate to enter almost 800...
My next question regards the Citadel Database. As I told you before, I entered a few variables in the system manager and played with them for a brief amount of time. I set them T / F, I got the correct readings from OPC server, my PLC leds light up, the works. Now I wanted to see my actions in the Citadel DB, but when i ran MAX, there was no Citadel DB, only Default DB, and I could not find any of those variables which I entered and chaged states. Is there a problem with the Citadel DB not showing up? Am I not declaring correctly the variables in the System Manager? (i followed the help directions to the letter). Anyone has an idea as to why I cannot see the varaibles in my DB?
And now for a final problem.. In the LV front panel, i have some boolean buttons which are set to switch when pressed Mechanical Action. When I have the PLC connected sometimes when I press a button, it remains stuck on the TRUE state, thus screwing up my logic scheme (e.g. for a feed mill conveyor motor I have two buttons - start, stop. If i sometimes press the start button and it gets stuck, i can no longer SHUT DOWN that conveyor, which is really a big problem. I found a so-called 'fix' - right click on the stuck button and select Reinitialize to default value, but I was looking for an answer to understand this problem, not a silly little fix).
Hope I have been clear enough and you have not got tired of reading so much,
Cheers,
Sabin

Hi Andrew and thanks for the reply!
I don't think I deployed the library file, because I didn't know exactly how to do it. In the Source Files Property Page on Build Specifications I only selected VIs. I never selected lvlib files, so this may be the case. On the Source File Settings I saw that .lvlib files had the property Include if referenced and I thought that was the property which deployed the library. I will change the build specifications at once and keep you updated, but it could take 1 or 2 more days, because the computer with DSC runtime is in another city, and I have to get there first maybe tomorrow.
I have several buttons set on Mechanical Action Switch Until Released. They are all Shared Variables which are connected through OPC server to memory locations in the PLC CPU. In my LV Block Diagram, they are NOT connected to anything. They are just located in a While Loop, to get their state. The preffered action is that when I press a button on my Front Panel, I get to change a memory location in my PLC and then something happens in Ladder Logic. So, the boolean values are just there, in my Block Diagram, alone and not connected to anything. Do you have an idea as to why I get that kind of behaviour (I mean the buttons get stuck on True state)?
And finally, someone told me that the Citadel 5 might be missing because of incorrect option checking at install. However, I remeber that on the desktop, I installed the DSC runtime engine FULL INSTALL, I mean I checked each and every tick box, everything, examples and the like. One thing I was told was to insert the install CD once again and perform a re-install. I will of course try this, but let's not consider this for a second. Do you have another idea as to why the Citadel DB wouldn't show up?
And no, in the EXE Build Specifications, I did not check the option Enable Enhanced DSC Run-Time support. What does it do? Could you please elaborate?
Looking forward to your answer,
Sabin

Run labview exe in other way than runtime engine?

Hi guys
This might be stupid question, but can I run labview's *.exe in other way than in the runtime engine? In these days in have done *exe and installer with runtime engine and give it to the end-user. It does not matter how tiny ur code is, user have to install 40 conponents and then restart computer... How annoying. Is there eny other way? Can i use other programming languages some how?
-AA-

If the runtime is only one out of 40 components, it should not make a big difference for you.
I always tell my users to download and install the runtime engine directly from NI. This needs to be done only once per PC and per runtime version, at which point you can distribute a small installer.
There is also an idea to simplify all this. Please support it.
(It is not reasonable to be able to build an executable with embedded runtime, that would make a LabVIEW 2009 executable 100+MB in size. (We had that back in LabVIEW 4.0, where each 20kb VI turned into a 3+MB executable, which was significant in the days of 1GB drives.)
Message Edited by altenbach on 12-16-2009 11:42 AM
LabVIEW Champion . Do more with less code and in less time .

Customizable Runtime Engine

Hi,
I am using LabVIEW 8.6 and I am interested to understand how to customize the LabVIEWRun time engine. Basically to shrink its size.
I just create a sample program and installer with and without Runtime Engine.
The VI and the projec is attached.
The Sizes are,
VI         ->      6.9 KB ( Just a UI with a loop)
EXE                                      -> 151.0 KB
Installer without Runtime Engine    ->   10.4 MB
Installer with Runtime Engine ->   74.7 MB
I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
Thanks,
Pandiarajan R
Certified LabVIEW Architect
Attachments:
RTE.zip ‏122 KB

Pandiarajan wrote:
I understand the Rutime engine includes the support for all the LabVIEW features (Web service, trace, tdms, etc).But while distributing the application developed in LabVIEW we may need the support for only the features the Application developed/configured for. Right?
Though transfering a 100 MB is not a problme now a days, I am just wondering, how it can be customized.
Besides the options then you create the installer no. I think NI could have done it, but they do not dare. If the installer was more modular it would have resulted in a lot of extra support work for NI. As people hate to read read documentation. It is much more convenient to phone NI support and yell at them. So NI has taken the all or nothing approach. As a self defense. And I can not blame them. But I have to admit a modular RT setup would have been nice.
Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
(Sorry no Labview "brag list" so far)

RunTime Engine and Tdms Files

Hello,
I have built a application with Labview 8.2.0, NI DAQmx 8.3 and NI USI TDMS
Plugin 1.0.
My appli work very good on my developpement computer, but when I install the
appli on computer with RunTime Engine 8.2.0, NI DACmx 8.3 and NI USI TDMS
Plugin 1.0, I have a error. If I use RunTime Engine 8.2.1, NI DACmx 8.5 and NI
USI TDMS Plugin 1.0, I have a error to.
The error is 2500.
How I can use my appli with a run time ????!!
Thanks

Hello,
I suggest you to reinstall everything on the second machine, because what you did seemed to be the right thing to do, you must install the same run-time version as your LV version (what you did at first) and every soft or plugin you VI needs.
I really think it will work... (I hope)
Regards
Richard Keromen
National Instruments France
#adMrkt{text-align: center;font-size:11px; font-weight: bold;} #adMrkt a {text-decoration: none;} #adMrkt a:hover{font-size: 9px;} #adMrkt a span{display: none;} #adMrkt a:hover span{display: block;}
>> Découvrez, en vidéo, les innovations technologiques réalisées en éco-conception

Install MAX with only LabVIEW runtime engine

Hi,
I want to know if it is possible to install MAX from the Device Driver CD, when only LabVIEW RunTime engine is installed. There is no full installation of LabVIEW on that PC. That's MAX 3.1.1.3004 with LabVIEW RunTime Engine 7.1.
Patrick.

Dear Patrick,
The device driver CD usually does not have a single installation of MAX, but you can install MAX by installing most of the other drivers such as NI-DAQ, NI-488.2, NI-Serial, etc. MAX does not require LabVIEW, so you can have MAX and LabVIEW Run-Time without LabVIEW. Have a great day!
Sincerely,
Marni S.

Cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported

Hi,
I am new to using third party labview drivers. I have a labview driver for Chroma 63600 loads that I want to use in TestStand 2012.
However when I load the vi. I get an error 'cannot load Runtime engine verion 7.0, only 8.0 and later versions are supported'
I have Labview Runtime Engine version 7.0 Installed on my Windows 7 machine.
Could anyone please let me know, How I could resolve this issue?
Please see attached driver for Chroma Loads
Solved!
Go to Solution.
Attachments:
chr63600_LabView_V11.zip ‏866 KB

To avoid more confuison,Here is the scenario,
The version that was on the driver attached is from the driver manufacturer.
I do not have any version of labview INSTALLED on my system. I am using the driver in Test Stand 2012 using a labview adapter.
I make sure I match the VI version and the run time engine version on TestStand 2012 to load the VI.
But for this specific driver, I was not successful in loading the VI at all.
As I understood that only 8.0 OR LATER are supported on TS 2012, I have asked to upconvert the driver to work with 8.2.1 Labview runtime engine.
I have now got a.LLB file of the driver mass compiled in Labview 2012 from discussion boards( and also attached here). I have tried the mass compiled LLB file on TS2012 but still have issues loading the VI as it moans about different version of SUB VIs.
However I am still trying to fix this version incomaptibilies. Any help would be much appreciated

Call a sequence of VIs (not .exe)) in VB. only LV runtime engine Installed

I am try to reuse my labview vis in VB enviroment. I would like to call a sequecne of vi from VB just like in LV with Call By Reference. This is a production enviroment, only Labview runtime engine installed in the computer. I realize that I can call labview exe file from VB, but then I have to compile every vis (more than hundreds) and have to reference every vis servers in VB.

Actually, the runtime engine can run any VI--not just ones built into an application. The problem will be getting data in and out of the functions.
If you have much of the code already written in LV why are you messing around with VB? Wouldn't the easiest solution be to write the entire application in LV? Just wondering.
Mike...
Certified Professional Instructor
Certified LabVIEW Architect
LabVIEW Champion
"... after all, He's not a tame lion..."
Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

Unable to install LV Runtime Engine 7.1.1 with LabVIEW Professional 8.5.1

I installed LabVIEW Professional Sys. for Windows (XP) 8.5 and then the 8.5.1 update. Somewhere in the original installation, LV Run-time Engine 7.1 was installed. But I need LV RTE 7.1.1. So I attempted to install RTE 7.1.1. Problem: The LV RTE installer aborts with the following message:
"Installation aborted. Newer version already installed."
Why do I need 7.1.1? I must run some commercial LV executables that were compiled with LV 7.1.1 and will not run under 7.1.

Well, I have to correct myself. MAX indicated that LV RTE 7.1 (not 7.1.1) was installed. My complied LV app indicated that 7.1.1 was not installed. I checked Windows Add New Programs and selected "National Instruments Software" I found that LV RTE 7.1.1 was, in fact, installed. So I selected LabVIEW Runtime Engine 7.1.1 and clicked Repair. After rebooting, My app works correctly. Again, MAX incorrectly displays LV RTE 7.1 (not 7.1.1). My app works, so I don't care.

Runtime engine can't load vi with lvdatetimerec.ctl

Hello everybody,
i have trouble with TS 3.5 / LV 11.0
I programmed a small vi that calculates the time difference between now and a time stamp. To pass the timestamp from Teststand i use a Control (lvdatetimerec.ctl) and the matching VIs to do the task.
Unfortunally i can't load the vi into Teststand using the Runtime Engine. I get the message "Unable to load VI "xx.vi" with the Run-Time Engine. It is possible that the version of the VI or one of its subVIs is not the same as the ..."
It is certainly the same and there is no problem until i include a constant or control of that type.
Do anybody have an idea?
Best regards
Thomas
Attachments:
TimeDiff.vi ‏7 KB

Try to recompile your vi hierarchy in LabVIEW (hold Ctrl and click Run), then save it, then try again in TestStand with LabVIEW runtime.
Runtime engine does not support dynamic compiling, this vi may looks fine in LabVIEW, but TestStand will complain that it is broken.
Sergey Kolbunov
CLA, CTD

App won't install with the prerequisite SAP Crystal Reports Runtime Engine

On installing with the following prerequisite checked:
SAP Crystal Reports Runtime Engine for .NET Framework 4.0
.. received this error:
Crystal Reports for .NET Framework 4.0\CRRuntime_32bit_13_0.msi
has changed since it was initially published.
Should I NOT use the prerequisite, and instead, use a merge module?

I ran a program with the exact same name, 2 weeks ago, on my VS 2010 Dev machine:
CRforVS_13_0.exe. (284 Meg)
Today, I followed your link, and downloaded the file with the same name, but different size: (1.5 Meg). I mean, a really major difference in size!
Because creating and testing installation packages is very time consuming, I want to verify what you have stated so that I completely understand before I change what currently works, which is for the client machine to separately install the CR runtime, to what you're proposing in including a prerequisite to my install package.
-> I should run this latest exe. It will add a prerequisite to the prerequisite list in Visual Studio 2010. The installation of this prerequisite will work, as the earlier one did not. And it will work for both 32- and 64-bit client machines.
Therefore, I can eliminate the need for the client machine to install the CR run time separately.
Please confirm, and then I will make the necessary changes, and do the install tests on client machines.
(Also, FYI the merge module did not work for me on a 32-bit client machine. So I removed it.)
Thanks, Peg

Computer with labview runtime engine (v8.2) cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What do I have to do?

I am trying to run an exectutable on a computer that has the labview v8.2 runtime engine. The error I am getting is: Cannot find sub-VI NI_AALBase.lvlib:Mean.vi. What is the easiest solution?

the matrix,
I would try reinstalling the LabVIEW 8.2 Run-Time Engine. You may also want to try creating a very simple project in your development environment that has a VI with just the Mean.vi, try building an executable and then running it on the machine that just has the 8.2 RTE.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Linux VI with Runtime Engine Only

Similar Messages

Maybe you are looking for