Call a VI whith the Run-Time Engine in TestStand

Hi,
I'm using TestStand 4.2.1. On the same PC I've installed LabVIEW Run-Time Engine 2009 (9), 2010, ...
On another PC I developped a series of VI with LabVIEW 2010. My client want VI in the 2009 version, that's why I use a Run-Time Engine.
I placed an action step, selected my VI and the adapter was not able to load the VI (as viewed in the attachment).
Before I had selected the right Run-Time Engine (in Configure -> Adapters), and I saved the VI in the 2009 version (instead of 2010).
What is the problem ?
Another problem is that in an other VI I use an XML library (the default in LabVIEW), How convert the entire library in the 2009 version ?
Thanks for your help
Attachments:
Erreur VI.png ‏975 KB

Hi,
One way to check if vi's are compiled in LV2009 is to select menu item 'View VI Hierarchy' from the top level vi. Then select 'View>Full VI Path in Label' and 'Always Show Labels'. Check that none of the VI's are in the LV2010 paths.
To fix, you may have to create a project (File>New Project from your top level VI - Add the VI to the project when prompted). Right click on the Build Specifications and create a new 'Source Distribution'. Check that under 'Additional Exclusions' that VI's in vi.lib, user.lib, and instr.lub are not excluded. This should package up all of the VI's into a library that will run in the LV2009 RTE.
Thanks,
Jim

Similar Messages

Is it possible to choose the serial port if only the run time engine is installed

I have an application, which communicates over the serial port. When I use the full version of Labview I can change the serial port without any problem from Com1 to Com2 (similar to the example “Hardeware input output -> serial -> Labview serial vi"). When I build an application and try to run this program on a computer where only the run time engine 6.1 is installed, it is not possible to choose the serial port. Since there is no “Measurement and Automation Explorer” available on the run time engine and no directory C:\VXIpnp is created, when the run time engine is installed, I do not see a way, how I can satisfy the computer with the information it needs for configuring
the different ports. Any suggestions?

Hi Daniel,
Before LV6.1 there was LV5.1 In LV5.1 the way to Spedify a resource was to use a string control with correct VIsa Resource Class identifier. For eg. "GPIB0::11" or "ASRL1::INSTR". With Introduction of VISA Resource Name Control and linking with MAX, These names are Available from Pull Down List and Can be Aliased, meaning ASRL1 which is Serial Port 1 can be called COM1 and so on. However the old method still works with all 6.1 Controls. Only thing is you have to make sure you Dont Conflict the Class Names ie Use "GPIB::.." instead of "ASRL..." when addressing Serial Port VI's.
To solve your Problem I would Build a Menu ring with COM1 to COM4 in the Pull Down List.
Next, If I use the Traditonal Serial Port VI wich accepts the Integer as Seria
l Port #. I just Wire the Menu Ring to this VI.(Remember COM1 is 0, COM2 is 1 for this VI)
If I use VISA Config Serial Post. I build an Array Constant with Corresponding VISA Class Names So in our case a String Array Constant of 4 elements "ASRL1::INST" to "ASRL4::INST". I Use Index Array Function With the Index Wired to my Menu Ring. The Array Input Terminal Wired to the Array Constant. The Output of this Array will be correct Visa Class Name Based on slection of my Menu Ring. I can Wire this as Input to my VISA Config Serial Port Vi.
I have attached a Small VI to Illustrate this.
Drawback: You must Predefine what Ports you will Want to Use. Basically you define all the cases.
I hope this Answers your Q!
Good Luck
Mache
Good Luck!
Mache
Attachments:
Serial_Port_Select.vi ‏36 KB

How to specify a different directory for the Run-Time Engine?

With LV 7.1 it's become even more difficult to create installation sets in third-party tools without having to include the full run-time engine separately.
If you use any of the advanced analysis VIs you have to install the run-time engine (no use in including files in the same directory as the built application) and if you do and you use the old serial VIs you get a problem because the application will load the run-time from the main run-time installation and then look for serpdrv in that directory, not in the application folder...
So - being forced to use the installer builder in the application builder and include the run-time engine in the installation kit I wonder whether it is possible to specify where the run-time should be installed?
By default it will go in a directory called National Instruments in the program files folder, however that is not ideal due to the fact that the users have no relation to the fact that our application needs something from NI...and may end up deleting the directory ("National Instruments? - what do I need that for...let me delete it...). We would like to be able to specify that the run-time is installed silently in a directory named with our company name instead.
MTO

When you create the stand alone, in options you can actually set the temp directory and default directory. You can change it there OR in goto options and check for libraries/directories. You can change it there too.
Kudos always welcome for helpful posts

Will hardware drivers work with the run-time engine or only a full version of Labview?

Hello.
I'm trying to get a quatech I/O card to work. The instructions with the drivers we were given state "you must have labview installed before installing these drivers".
A program I wrote on my machine works fine with those drivers and does toggle outputs on the card, but when I build it into an executable on our test unit (doesn't have a full version of Labview, just the Run-Time engine) the card doesn't work.
We installed the run-time engine on the unit, then the drivers.
I guess my question is: Do most drivers work with both the full version of Labview and the run-time engine? Or do I need to somehow 'convert' these drivers to work with the run-time engine?
Th
anks for your help!
Dave Neumann
[email protected]

Dave:
I can't determine which dll is required but if there are more than one that
shipped with the quatech I/O card try to placing one dll at a time in the
same directory as the exe so that you can determine which one is the
required one. If that doesn't do it then it may need more than jsut one of
the dlls so placing all that came with the quatech I/O card s/w driver
package in the same directory as the exe should do the trick.
Best of luck.
-Tom
"Neumannium" wrote in message
news:[email protected]..
> Tom,
>
> Thanks for your reply. One of the problems I'm having is figuring out
> which .dll I would need to include (I'm not a software guy).
>
> Would the .dll your speaking of be different th
an the one which is
> installed with the drivers? I'm looking at a .dll that is installed
> when you install the labview drivers for this card, but the run-time
> engine still doesn't want to get the card to work. (The file installed
> when I install the drivers is called 'daqlv32.dll' and I don't know
> how to find any other .dll's I might need)
>
> Actually, it appears the card 'is' being seen by the run-time engine,
> but I'm getting impulses rather than distinct changes of state.
>
> Anyway, thanks for the help.
>
> Dave Neumann
> [email protected]

Building an Application in Windows to be used in Linux (with the Run-Time Engine)

Hi All,
I have an LabVIEW project I have developed in a Windows environment. I can create an Application (.exe) using the Build Specification -> Application Builder which works fine on the development platform.
I now want to distribute the application to a Linux Environment. The OS is openSUSE v10.3 (with GNOME). I have downloaded the two rpm files needed for the run-time engine and installed them, as per here:http://digital.ni.com/softlib.nsf/websearch/97E14BA3E0C14A89862572C300567733?opendocument&node=13207...
Now, the question is; how do I create an Application in Windows which can be used on the Linux Box? According to the Application Builder instructions, it's simply a case of removing the .exe extension in the Target File Name options, however, this gives an error "Invalid Extension."
If I do create an exe and manually remove the extention is doesn't work on the Linux enviroment (typing ./application).
Has anyone had experiance of this?
Many Thanks for Any Help,
Oliver
Windows XP SP 2
Labview 8.2.1
openSUSE v10.3 (with GNOME)
LabVIEW Run-time Engine Version 8.2.1 for Linux

The cross-platform nature of LabVIEW refers more to the code than to the executable.
LV (given the appropriate development version) can compile the same source code into a Windows (using LV for Windows), Linux (using LV for Linux) or Mac (using LV for Mac) program.
This means you will still have three versions of your program, one for each platform.
If you want to distribute VIs (without block diagrams), you will also need different versions of these as without the block diagram, they cannot be re-compiled for a new platform.
Shane.
Say hello to my little friend.
RFC 2323 FHE-Compliant

Installing the run-time engine as a non-administrator

I want to distribute a stand-alone application to end-users that are not administrator of their computer. When they try to install the RTE without administrator privileges, the installer cannot continue because it cannot write to the C:\ base directory. How can I fix the run-time engine installer to work without administrator privileges?

On the second screen of the installer, the user can choose an alternative target location. Have you tried that?
(sorry, I don't know how well this will work). What is the runtime version?
(For your reference, this document describes planned changes in the folder structure for future LabVIEW versions.)
LabVIEW Champion . Do more with less code and in less time .

Path where to install the run time engine (on Linux)

I have a cluster of Linux computers where I would like to run compiled LABview (8.20 at the moment) applications build
with the application builder.
Therefore I would like to install the LABview run time engine on a NFS mount file system seen from each computer. But
the installation procedure of the run time engine does not propose to
choise the installation directory, but force the installation
in /usr/local/lib.
I try to workaround this problem and have copied the /usr/local/lib/LABview.8.2 directory to my NFS filesystem and
made the 'necessary' links.
Unfortunatly it doesn't run and fails because the
liblvrt.so.8.2 library can not access patched versions of the
libOSMesa.so.4
and libGL.so.1 librairies but uses the standard ones in /usr/X11R6/lib.
Even by setting my LD_LIBRARY_PATH correctly to access the patched librairies versions it does not run because the
liblvrt8.2 library seems to be linked with the following
'rpath' (given by the command 'strings liblvrt.so.8.2 |
grep patchlib')
$ORIGIN/LabVIEW-8.2/patchlib:$ORIGIN/patchlib:/usr/X11R6/lib:/usr/lib:$ORIGIN:$ORIGIN/LabVIEW-8.2/linux:$ORIGIN/linux:$ORIGIN/resource
which prevents to access the patched librairies versions if the $ORIGIN is not set. Therefore I tried to set $ORIGIN as an
environment variable but it doesn't change anything.
Therefore my question is: Did somebody have already had this type of problem, what is $ORIGIN and how I can set it ?
Thanks in advance.

Sir,
Please could tell me the distribution you use ?
Cordially,
Pierre R...
Certified LabVIEW Developer

The program doesn't find the run time engine

I create an executable before normaly and after like an installer. When I try it into computer with full LabView licence the program works, but if I install it into a different pc, it requires me to install the run time engine, but the run time engine is installed into the pc. What kind of error can generate this problem?
Solved!
Go to Solution.

Hi vsara
Mike is correct, you need the VISA runtime to use VISA functions in an executable. If you don't want to install it as a standalone you can include it in your installer as an additional installer.
Best Regards
David
Message Edited by Davidek on 10-23-2009 04:18 AM
Message Edited by Davidek on 10-23-2009 04:19 AM

You may not need to install the Run Time Engine...

I know this has been mentioned before, but after a long search of the archives, I couldn't find the right person to give credit to - sorry!
If you have a simple exe, you may not need to install the runtime engine on the target machine at all - all you need to do is include some of the engine's files with the exe for it to work. Try it out: copy the following files & folders into the folder containing your exe:
..\National Instruments\shared\nicontdt.dll
..\National Instruments\shared\nicont.dll
..\National Instruments\shared\LabVIEW Run-Time\your_version\everything (including all sub-directories)
so, using 6.1 as an example, you exe's directory would like something like:
..\AppDirectory\MyApp.exe
..\AppDirectory\MyApp.ini
..\AppDirectory\My_Apps_DLLs,if_any
..\AppDirectory\nicontdt.dll
..\AppDirectory\nicont.dll
..\AppDirectory\lvapp.rsc
..\AppDirectory\lvjpeg.dll
..\AppDirectory\lvpng.dll
..\AppDirectory\lvrt.dll
..\AppDirectory\mesa.dll
..\AppDirectory\serpdrv
..\AppDirectory\models\heaps_of_stuff_in_here
..\AppDirectory\errors\more_stuff_in_here
..\AppDirectory\script\and_some_bits_in_here_too
Take all of this data to a machine without LabVIEW or the runtime installed, and try to run the exe - all going well, it will execute without any problems. This exe distribution method can be really useful, especially when distributing autorun presentations on CD-ROMs.
* DISCLAIMER: as far as I am aware, this method is NOT authorised or supported by NI - use it at your own risk!
cheers,
Christopher
PS: I'd like your feedback: please give this posting a rating
Christopher G. Relf
[email protected]
Int'l Voicemail & Fax: +61 2 8080 8132
Aust Voicemail & Fax: (02) 8080 8132
EULA
1) This is a private email, and although the views expressed within it may not be purely my own, unless specifically referenced I do not suggest they are necessarily associated with anyone else including, but
not limited to, my employer(s).
2) This email has NOT been scanned for virii - attached file(s), if any, are provided as is. By copying, detaching and/or opening attached files, you agree to indemnify the sender of such responsibility.
3) Because e-mail can be altered electronically, the integrity of this communication cannot be guaranteed.
Copyright © 2004-2015 Christopher G. Relf. Some Rights Reserved. This posting is licensed under a Creative Commons Attribution 2.5 License.

Yes, this method is not supported. However, this method is good if you wish to write your own installer for a LabVIEW Application. (Note: The method above does not install DataSocket, NI-Reports, or any of the 3D Graph controls.)
I would still suggest running the LabVIEW Run-time Engine installer so that more than one application can use it.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Why am I getting "Unable to load a labview run-time engine because teststand is shutting down" error?

After running a successfull TestUUT's in a custom UI. I exit my UI, then open it again and I get Error Code -17338.
See attached for detail .jpg
Collegues of mine suggest it's because I haven't closed a reference somewhere, but I have closed everything possible.
Any suggestions?

Perry,
Thanks for getting back to me today.
I have closed everything I know how to and compared to the Simple OI.
You mention closing the Application manager, but I don't see that happening anywhere. Do you mean closing the application, and engine, and etc...? I have never closed the "Application Manager" specifically and am not sure how.
I have attached an image of how I close things up.
Thanks,
Attachments:
CloseRefs.jpg ‏218 KB

What is the "EventLoggingEnumLogEntry" function in the run-time engine?

I have some code which isn't utilizing all of the processors on my system, but it should be, so I profiled the execution of the compiled executable code using "Intel VTune Amplifier". That program told me that my code is spending a lot time in synchronization or threading overhead, and that the main function that its constantly executing (>50%) is called "EventLoggingEnumLogEntry", and it's contained in lvrt.dll. It's also spending a fair amount of time executing a function "LvVariantCStrSetUI8Attr".
Can anyone tell me what these functions are and what in my LV code would activate them? I can't even start to find where the bottleneck is in my code with the information I currently have...
Thanks!

Joey,
Thanks for the reply!
I've already parrallelized the loops, and the problem is that each core is only using about 25-40% of its capacity. I can't figure out what is limiting the speed of execution on each core. One of the papers I read suggested that I can find the bottleneck using the Intel VTune program. I used that instead of the Labview native profiler because the LV profiler will tell me where my code is spending most of its time, but it doesn't tell me if there is some other bottleneck (like perhaps one thread is waiting for another or something like that). I had already taken the information in the profiler as far as I know how to, by finding and optimizing the most commonly executed code in my application.
There is an event structure in my application, but once I press the "GO" button, which kicks off the intensive computing, I have the event structure disabled by placing it within a case structure and using a boolean to keep LV from executing the event structure. Under certain conditions (like completion of the computing), the boolean will be flipped and enable the event structure, but that only happens AFTER the computation is complete. I've confirmed that LV is not executing the event structure with breakpoints.
Does the mere presence of the event structure, even without execution, cause LV to spend extra resources checking for events? I also tried seperating the application into two while loops - one containing the event structure, and one containing the processing code. When the first while loop terminates (again, when pressing the "GO" button), the second will execute with no case structure in the loop. That did not seem to relieve the bottleneck.
This thread is the first thread that I posted regarding this topic. One of the last replies includes some of my code, if you are curious to look at it.
Thanks!

Problem to install the Run-Time Engine 6.0.2 on a Windows XP

Hi,
A client tried to install our application on a new computer with Windows XP Pro. The application was developped on LabVIEW 6i, so he has to install the RTE 6.0.2, like it was on the old Windows 2000 computer.
The installation of this RTE is OK, but it disturbs completely the "Add/Remove Application" windows of the Control Panel (See attachment).
And then our application is very very slow !!!
Our client installed then the Service Pack 2 for XP, that didn't change anything.
Is there a possibility to use correctly a LabVIEW 6i-application on a Windows XP SP1 or SP2 ?
Now the client is thinking to transfer directly this application on a Windows 2003 server, is it possible ? Is there a already known problem to do it ?
The application is used to do the monitoring of geological movements and is therefore very sensitive and should run fine, without any trouble !!! We can't be unsure !
Many thanks in advance for any help.
Best regards,
Gerald Monin
Attachments:
RTE_XP_prob.gif ‏26 KB

Hi,
Regarding the blank space in the add/remove programs list, please look at the following link
http://digital.ni.com/public.nsf/websearch/9D43413E0F8289B586256DD50072EDFB?OpenDocument
Regarding the slow execution, I would suggest to upgrade the LV environment to 6.0.2 as well and create an installer with the RTE included to be sure to have the right version installed on the target machine. If not, then please give more info's about what is executing slower (the hole application, acessing HW,ports...).
Porting the application to windows server 2003 is not the best idea, because LV in general is not supporting it and lv 6i is released a long time before windows 2003 server was. But i know a lot of people which are using lv 7.1 on windows server 2003 successfuly.
I hope it helps!
Regards,
Evrem

Multiple app on same Run time engine

Hello
Can we run multiple application on same CVI run time engine?
We have thin client desktop and want to run application on different terminals. Is it possible?
Means on server there will be one application installed and 5 terminals will use same desktop application.
Thanks

Yes, you can call multiple instances of the Run-Time Engine.

Teststand error states that a vi failed to load in the Labview Run-Time Engine

I am getting an error in teststand that states that a vi failed to load in the Labview Run-Time Engine version '14.0.1'
If I look at the software loaded on my system with the NI Measurement and Automation Explorer I have Labview Run Time engines for version 2009, 2010, 2011, 2012, 2013, & 2014 on my system.
How do I get this VI to run on this system when it is called by test Stand?
Thank you

The RTE 14.0 was loaded as part of my deployment and after I ran this I got an update notice for the F1 patch which I also loaded.
I do not have labview loaded on this system, only the run time engines from running my deployment.
When I launch t he teststand sequence, when it calls the labview VI, I get the following error moessage:
Error: Failed to load VI 'C:\builds\RelayVoltageMeaure.vi' in the LabVIEW Run-Time Engine version '14.0.1'. LabVIEW: The VI is not executable. This error may occur because the VI is either broken or contains a subVI that LabVIEW cannot locate. Select File>>Open to open the VI and verify that you can run it. VI Path: C:\builds\RelayVoltageMeaure.vi[Error Code: -17600, Failed to load a required step's associated module. ]
I have attached the teststand sequence if this helps.
Thanks
Attachments:
QuantumDigitalBd.seq ‏13 KB

Call VI in EXE but have it execute in Development Environment not Run Time Engine

I am working on building a palette editor for distribution of a reusable code library for my company (I know the VIPM does this very well already). I have the code complete and am trying to create an executable that I can distribute that will call the code I wrote to update/create the palette .mnu files for the reuse library, which lives on the company network. I am using the Palette Editing VI's and it seems as though they cannot be built into an executable. So I wrote some code to dynamically call my palette modification code (I call it the Reuse Library Manager). When my executable calls the Reuse Library Manager dynamically I get a broken run arrow on the Reuse Library Manager front panel and the following reasons for the broken arrow:
It seems to me that the reason the Reuse Library Manager works when called in the development environment and not when called dynamically is because the dynamic call uses the run time engine for execution. This made me think of how in the VIPM it opens LabVIEW while it installs packages. If anyone knows, does the VIPM open LabVIEW in order to run the Palette Editing VI's or is it for another reason? If it is this reason how can I force the dynamically called VI's to run in the development environment by opening LabVIEW programmatically from an executable that is running in the run time engine?
Let me know where clarification is needed.
Message Edited by jmcbee on 04-28-2009 10:00 AM
CLA, CLED, CTD,CPI, LabVIEW Champion
Platinum Alliance Partner
Senior Engineer
Using LV 2013, 2012
Don't forget Kudos for Good Answers, and Mark a solution if your problem is solved.
Attachments:
Reuse.PNG ‏14 KB

Hi jmcbee,
In spite of years of using LV and building a resuable library of code, I've done very little with customizing the standard paletts, however,
Many times when deploying a new distributable I've seen a dialog like what you posted. In most cases the problem was solved by rebuilding distributable to include the missing VIs. In one case I added the VI-lib to the target-platform and made-sure VI-lib was in distributable's VI search-path.
There are two ways I know of to build distributables which include the VI-lib code,
1) Include all VI-lib VIs when building the distributable
- In LV 8x, uncheck "Exclude Files from VI lib" project-property.
- In LV 7.1 it's possible but I don't remember how! (probably a post on it around here.)
- This can add an enormous number of un-needed VIs (see this post.)
2) Re-write the VIs so that they are no-longer identified with VI-lib and get included "naturally".
- Open each VI diagram, select-all, paste in new/untitled diagram. In your case naming will be tricky, but it's doable.
- This is a great advantage in 8x as it allows LLBs to be built with File\Save As\Create Hierarchy.
In addition, here's a tool to call following "Open VI Reference" (if it returns an error.) This VI open all broken children making it much easier to identify specific missing parts (typically VI-lib.)
Luck/
Cheers!
"Inside every large program is a small program struggling to get out." (attributed to Tony Hoare)
Attachments:
Util.VI.OpenBroken.vi ‏57 KB

Call a VI whith the Run-Time Engine in TestStand

Similar Messages

Maybe you are looking for