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

Similar Messages

How to install LV runtime engine and run .vi's in linux

I am attemtpting to load run time engine and run a .vi on Linux system.
Here is what I have done so far.
1. I don't have rpm on my system (gentoo) so I used the app on the install cd called INSTALL.norpm to install
labview70-rte-7.0.1.i386.rpm. It looks like it worked, there are a lot of files copied to /usr/local. A couple of .so files and a directory called Labview-7.0 (12M of files).
2. Made a test vi on other linux box that has full development system installed (also gentoo but i have rpm on this system).
    Do I need this application builder i keep hearing about to make an .exe or can I run vi's with this run time engine?
    What is the syntax to run a vi in linux? ./test.vi   ????
    Is application builder a seperate program that I must purchase?
When I attemp to run a vi I get garbage printing to the console, not unlike when you cat a binary file.
Any help would be appreciated. Is there instructions somewhare??? A manual perhaps that explains rte install and operation.
D.A.M.

You need the application builder to create an exe. The rte by itself will not run a VI. The exe does require the rte. It is possible to create a "loader" program that you can use to run separate VIs but the loader program must be created with the app builder. The app builder is a separate add-on or if you buy the professional version of LabVIEW, it comes included with that.

How do CVI7.0 runtime engine and TestStand3.0 runtime engine work in a test system?

I developed code modules from CVI 7.0, and test sequence from TestStand 3.0. Now I want to deploy all to a test system. Should I create distribution kits for CVI and TestStand, and install to a target PC? Do each kit include the RTE? How do the runtime engine work in a system?

hp7550,
I saw your post earlier entitled "what is a run-time engine?". It looks like this post is addressing the same issue.
To answer your questions, it is not necessary to create a distribution kit for your CVI code modules. You can simply install the CVI Run-time Engine, which you can find if you go to www.ni.com and click on the Drivers and Updates link on the left-hand side.
Then you will need to deploy your TestStand system using Tools >> Deploy TestStand System in the Sequence Editor. That tool will go out and gather all the CVI code modules your sequence calls - unless you are calling a DLL or something dynamically inside of a code module; in which case, you need to add that dynamically called DLL (or code module) to your TestStand workspace.
To install the TestStand Run-time Engine, make sure the Install TestStand Engine option is checked on the Installer Options tab of the deployment utility. You can customize what gets installed with the engine by clicking on the Engine Options.
For more information on deployment, see Chapter 14 of the TestStand Reference manual (Help >> Search the TestStand Bookshelf...).
To answer your last question a run-time engine simply gives you access to the compiled code that corresponds to the functions you used from the CVI or TestStand libraries during development.
I hope that helps.
Best Regards,
Matt P.
Applications Engineer
National Instruments

DAQ 6008 and tdms file

Hello,
how can I make a recording an analog input in first .tdms file (for example in 1 second) followed by a recording in another file (for example in 1 second)?

The simplest would be to configure the DAQmx Streaming feature to write your analog reads to a TDMS file. You can use a DAQmx Read property node to set the number of samples to put into each TDMS file. A new file will automagically be created once that number of samples have been streamed.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Runtime.exec() and batch files

I am having a problem on Windows 2000 while trying to execute a batch file with the Runtime.exec() method. Basically, the exit value returned from the call to Runtime.exec(), returned specifically by the waitFor() method in the Process class, is always zero, even if the batch file fails miserably. After looking into batch files further, it seems to me that the only way to get the exit value of the commands run in the batch file back to the Runtime.exec() call is to put "EXIT %ERRORLEVEL%" in the batch file. What this actually does is exit the command(cmd) shell that the batch file was running in with the exit code of the last command run. This is all great when calling the batch file with a Runtime.exec() call, but when you run it in a cmd window, the window closes when the batch file completes, because the call to EXIT exits the entire shell. I guess i'm just wondering, am i correct in assuming the exit value returned to the java process is going to be the exit value of the shell in which the batch file is running? I need to have the exit value actually indicate whether the batch file ran successfully or not, and if i have to put in the EXIT %ERRORLEVE% (which exits the cmd shell with the exit value of the last command run), then i'll do that, but if someone knows a better way of doing this, i am all ears. Thanks in advance

To run any command from java code, the method is
Runtime.getRuntime().exec( myCommandString )
Where, myCommandString is something like "/full/pathname/command".
If the pathname contains spaces (specifically in Windows), e.g. "c:\program files\windows\notepad", then enclose it in quotes within the quoted string. Or pre-tokenize them into elements of an array and call exec(String[] cmd) instead of exec(String cmd).
From JDK1.3 there are two new overloaded Runtime.exec() methods. These allow you to specify starting directory for the child process.
Note, there is a gotcha associated with reading output from commands. When the runtime exec's the process, it passes to it 3 streams, for stdin, stdout, and stderr; the out and err are buffered but the buffer size isn't very big. When your process runs, it reads (if needed) from in, and writes to out and err.
If it doesn't write more than the buffer-size, it can run to completion.
But if it tries to write more data to one or the other stream than the buffer can hold, the write blocks, and your process hangs, waiting for you to empty the buffer so it can write some more.
So after the exec call, get the streams, and read from them in a loop until they both hit end-of-stream (don't block on either one, just read whatever is available from each, each loop iteration).
Then when the streams have ended, call the process.waitFor() method to let it finish dying.
Now, here is a code snippet how you achieve this.
String strCommand = "cmd.exe /c " + strCommand;
// For Solaris / unix it will be
// String strCommand = "/usr/cobra/sol/runInstaller.sh";
boolean bWait = true;
//execute the command
try
     Runtime r = Runtime.getRuntime();
     Process pr = r.exec(strCommand);
     Process pr = r.exec(callAndArgs);
     BufferedInputStream bis =new BufferedInputStream(pr.getInputStream ());
     int c=0;
     /** Outlet for IO for the process **/
     while (c!=-1)
          c=bis.read();
     /**Now wait for the process to get finished **/
     if(bWait == true)
          pr.waitFor();
          pr.destroy();
catch(Exception e)
     System.out.println("Could not execute process " + strCommand);
     return(false);

Runtime engine files 8.2

Hi,
Since most users of my written program are users with "restricted right" acounts under Windows XP I copied the Runtime engine files of LV7.11 manualy by copying the
"Program Files\National Instruments\LabVIEW 7.1\Shared\LabVIEW Run-Time\7.1" files to the harddisk and run a build executable from that directory. Since this application looks in its own directory for support-files this worked fine for LV7.1.
Last week I converted my program to the LV8.2 version. When I tried to copy the RTE8.2 file in the same way as I did before, the program would start-up. It asks for a NIINI32.DLL file. When I include this file it does not return any errors, but the program doesn't start. Can anyone tell me whether their is a different way to run a exe-file build by LV-application builder by copying files manual in stead of running the RTE-installer?
Thanks in advance,

I know that NI did the run time engine to minimize space when installing multiple application. But i'm agree with you, we should have another way to build executable without the runtime engine. Some people dont know what it the runtime engine and uninstall it. afther that they just cant use the program anymore. The other reason, it that a VI use just some Kbyte and the run time engine that include almost everything, need some Mbyte.
If somebody know, please tell us......
Benoit Séguin
Software Designer

Can the runtine engine and an application be run directly from a CD?

Can an application be run directly from a CD without installing the runtime engine and application onto the computer?

It depends on what library functions the application is using and what version of LabVIEW it was built in. In LV 7 and earlier you could just put the run-time files (the ones in Program Files\National Instruments\Shared\LabVIEW Run-Time...(lvrt.dll is the most crucial of the files, a full list can be found here on the developer zone)) in the same folder as the application and it would run without any problems in most cases.
In 7.1/7.1.1 math functions had to be installed as well if you had used any of those and could be a problem, otherwise it still worked (we do this still with apps that use serpdrv instead of VISA).
With LV8 it is still possible, but the chance of the application depending on some function that you do not get included this way is much higher, I would just test it and see how it goes.
MTO

What is minimum runtime engine size when installed on XP embedded OS

I hope to build move an existing Labview 8.6 application to a Windows XP embedded machine and would like to know if their are any tools available to help minimize the hard disk memory requirement, specifically can the runtime engine installation be micro managed so that absolutely nothing that is not required by the application is installed?
If not, is their some way to install the runtime engine and then remove unused items, for instance one .dll file at a time?
I would appreciate any guidance.
Thanks,
Bernie

I believe NI does not officially support running LV apps on XPe, but if you search, you should find some references to it. In any case, I doubt you will find anything relating to the size of the RTE. You can probably safely remove some of the support files (e.g. language files, which take up some space), but I've never done it and it isn't necessarily safe.
In older versions, you could simply use all the files from the RTE folder if you didn't require any drivers, but I believe that doesn't work since ~8.0.
Try to take over the world!

Can I extract the orginal VI's from an executable created by Runtime Engine?

I have an executable program created using the Labview Runtime engine and need to edit the subVI's contained within. Unfortunately, I don't have the original VI's the program was created with.
Is there any way I can extract those VI's?
Thanks,
Mike C.

First, LabVIEW 7.2 never existed.
Second, if you can't rename an exe into *.llb and open it in LabVIEW 7.1.1 (the latest official LabVIEW version before 8.0) and see a list of VIs then it's not a LabVIEW 7.1 or earlier executable file. What it may or may not be is another question!
But even if you can do that, all you can determine from this are the original VI names. Theoretically you can also copy the VIs out with the Librarian VIs, but those VIs lack all source code, front panel, and even icon resources so if you place them on a diagram, you see a simple block with a question mark, can't double click it to open the front panel and definitely can't view the diagram because they are all gone! And it even only works if the LabVIEW version that was used to create the executable is the same than the version you try to open those stripped VIs in, since the compiled (binary) code is about the only thing left in the VI and has to match the version of LabVIEW in order for LabVIEW to consider it valid. Anything else would certainly cause crashes as the compiled code would attempt to call into LabVIEW functions that have been added later on or got changed between versions.
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

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.

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 .

TDMS file viewer used in a dialog

I would like to use TDMS file viewer inside a dialog VI. The problem occurs if I change VI properties - Window Appearance - Window Behaviour to MODAL (It should be modal).
When I click the button and run TDMS file viewer both windows (my VI and TDMS file viewer) become modal and "lock" each other: I cannot control any of them.
Is there a possibility to use TDMS file viewer as a dialog ?
Thanks in advance,
Ljubo.
Solved!
Go to Solution.
Attachments:
Dialog_diagram.jpg ‏23 KB

Hi James,
I tried your VI. It works unless I change VI's properties. I would like it to be a dialog VI. Why ? This VI should be a small part of an application which is used to analyze a set of TDMS files. When this VI is called no other window should get focus. User should have a possibility to check briefly all the properties (acquired signals are not so important in that case). Using TDMS File Viewer is the most simple way to do it because it can read TDMS files with different set of properties and because it show all the proerties in a nice "tree structered" diagram.
So I set VI's properties as it is mentioned in my post: Window Appeareance = Dialog.
In that case VI window and TDMS File Viewer window are modal and they "lock" each other.
Your VI is attached (property "Window Appearance" is set to "Dialog").
Regards,
Ljubo.
Attachments:
TDMS Viewer.vi ‏13 KB

Windows Runtime Engine

Hi,
running a job using Windows Runtime Engine and a script in VBScript will cause no action, in job log and system log no entry. It seems this runtime is not working.
The dispatcher is configured and running. All jobs with java runtime engine are running properly.
Any ideas what needs to be configured?
Thanks for replies

Hi Ralf,
could you please provide more information: Do you try to test-run the job?
I remember having had this problem, too.
I think I solved it by reading the error messages in the DOS prompt when starting a test.

Does arch install library and header files into system when using abs?

In traditional make way, when compiling a package, I must install some library or header file or tool packages to satisfy its depends, but after compilation, I do "make install", and run it. At runtime, library and header file and tool packages are not needed....
This make a lot of unuseful packages are left in the system.....
In arch linux , when I using abs to make a package, does these packages are left in the system ?
How abs separates the compile-time depends and the runtime depends ????
Last edited by iamybj (2010-03-22 01:24:57)

tomk wrote:
The PKGBUILD has a depends array and a makedepends array. Anything that's required at runtime goes in the depends array, and must be installed for the application to run successfully. Anything that's only required at buildtime foes in the makedepends array, and can be removed from the system after the application has been built.
man PKGBUILD and various wiki pages for more details.
Anything that's only required at buildtime foes in the makedepends array, and can be removed from the system after the application has been built.
==================
Who remove them ? user or the abs ??
I think the best method is file dependence , not package dependence.....
Software is arranged by package. but its dependence is file. When Install a package, pacman check its file dependence, and install the packages which include those files....
If a not explicit installed package 's file does not required by any other packages , it can be removed automatically !
In this situation ,pacman can find packages that not needed after compilation, and remove them.
Last edited by iamybj (2010-03-22 03:15:06)

What is needed to run a .llb file using a runtime engine?

I would like to run a .llb file on a computer that doesn't have LabVIEW installed. Is that possible? If so, what is needed to do that? I have tried to install a runtime engine, but can't get it to work. The .llb file is currently running on LabVIEW version 6.0 on another computer, but I don't know with what version of LabVIEW the .llb file was created. The computer on which I would like to run the .llb file has Windows XP.
Thank you for any help!

Mathan wrote:
You have to create an executable with the help of project explorer.
The user has LabVIEW 6 (as he noted in the original message). LabVIEW 6 has no project explorer.
To OP: I am assuming the LLB contains a top-level VI that can be run. Otherwise, this is a moot question. If you want to open the VI and view it, then you need the development version on the target machine. If you want to run the top-level VI in the LLB then you must create an application that you can copy over to the other computer. The other computer requires the LabVIEW Runtime Engine in order to run the executable. To build the application you need the Application Builder. This is a separate product from LabVIEW, but was included with certain LabVIEW editions.. If you do not see a menu option for building the application then you do not have the Application Builder. You would need to contact your local NI sales office to see if you can still buy a copy. I doubt you will be able to, but it's worth a try.
EDIT: Sorry for the duplicate info. I got sidetracked while composing the message, and did not see the additional responses from Dennis.
Message Edited by smercurio_fc on 08-18-2009 09:51 AM

RunTime Engine and Tdms Files

Similar Messages

Maybe you are looking for