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

Similar Messages

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

Executable not working - Looking for LabVIEW Run-Time Engine

This has been one of those days.
I'm trying to create my .exe file to place onto another computer. I've done this before with success. But that was then and this is now.
I believe I have all the files I need in my LLB, and I believe I did my application distribution correctly and I believe I built the DLL correctly. But when I took the resulting .exe file and placed it on another computer and attempted to run it, it gave me the error message: "Unable to locate LabVIEW Run-Time Engine. Program requires a version 7.1 (or compatible) LabVIEW Run-Time engine. You should have already realized this, you moron."
Anyone have any idea where I went wrong or what step I might have missed? This has been a crazy, non-stop, massive brain fart of a day and I can't seem to remember what I'm missing here.
Amateur programmer for over 10 years!

Hi.
Whenever you want to use executables or .dll's created with LabVIEW you must make sure that the LabVIEW runtime engine of the SAME version as the LabVIEW version used to create the files, is installed in the target computer.
There are basically 2 ways to get the run-time engine installed on a computer:
1. (the one I prefer): Download the correct version of the LabVIEW run-time engine installer from www.ni.com/downloads, or more specifically from
http://digital.ni.com/softlib.nsf/websearch/369618104E25B08E86256F54006A4E2F?opendocument&node=132050_US
for the latest one. Once you have the installer for the run-time engine, just install it in the target computer. I prefer this option because the run-time engine is installed independently, so if you then uninstall your program, the run-time engine remains.
2. Create an installer for your program that includes the run-time engine. To include the run-time engine, when you are creating your application, go to the "installer settings" tab, click on "Advanced" and make sure there is a checkmark on "include LabVIEW run-time engine". This way when you install your program in the target computer, the run-time engine will also be installed.
Just as a note, any computer with LabVIEW on it, will also have the run-time engine.
Good luck.
Alejandro

System requirement for Labview run-time engine 8.6

Hello
is there any system requirements for LabVIEW Run-time engine 8.6? for example, same system requirements for LabVIEW 8.6? Internet Explorer 5 is fine? or Internet Explorer 6.0 or higher is fine? Does it work for Firefox on an Athena Linux mechine?
Thanks
Cynitha
Solved!
Go to Solution.

The system requirements can be found in the Release Notes. Pages 2 and 3 indicate the specific requirements for the Run-Time Engine per platform.

Business Rule err The following value is not valid for the run time prompt.

Hyperion Planning v 9.3.3
I have created a new BR with 2 local variables (created at the time of the BR), Variables are set as run time prompts. They are created as "Member" (not Members). The BR basically does a calc dim on dense and Agg on Sparce other than the prompt on Entity and Version dimensions. The entity variable has a limit on level 0 of the dimension. The Version variable limits to the input (Submit and Sandboxes)
The BR is associated in Planning with an input web form. Entity and Version are in the page. Is set to Run on Save and Use members on form.
If the run time prompts Hide boxes are checked, an empty Prompt pops up with only a Submit button. Click the button and an error comes up: "The following value is not valid for the run time prompt it was entered for:. But it does not indicate what member - just ends in the :.
The BR will run sucessfully only if the Run-time prompt is not hidden - "Hide" in the BR is unchecked. So the syntax and logic of the BR is correct and security should not be an issue.
The client wants no prompt. In production we have similar situations in which the BR works with the Web Forms without a prompt.
What am I doing wrong - I have tried restarting the Planning service and the EAS service.

My preferred method of doing this is:
1. In business rule, do not hide the run-time prompts. This makes it easy to validate the business rule as you are building it. I only use Global Variables.
2. On the form, have business rule set to run on save, use members on data form and hide prompt.
Check that in the business rule, for the variables (Run-Time prompts), that they are all in use. If not, delete them from the business rule. Are all your variables global? Are some local and some global? This could be the issue.
Deanna

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

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]

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

Has NI plans to develop CVI for WinCE run time engine?

Has NI plans to develop CVI for WinCE run time engine?

At this point, LabWindows/CVI does not have plans to support Windows CE. There are many reasons we do not have plans for support, but two main reasons are:
Windows CE uses a different kernel from other Windows operatings systems.
Windows CE does not support the full WinAPI.
National Instruments
Product Support Engineer

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

How can i do different colors for the category in business graphics

Hi everybody,
i have a business graphics and i need different colors for the category. my business graphics is a gantt.
for example
category1
category2
category2
and so on.
Is there a solution for this? How can i do it?
Best regards,
Markus

Sorry.
In my opinion, this requirement can not be resolved.
Generally, we use Business Graphic with Category, we just follow:
DATA:lr_graph TYPE REF TO cl_wd_business_graphics.
lr_graph = cl_wd_business_graphics=>new_business_graphics(
    bind_series_source = 'NODE_DYN'
    chart_type = cl_wd_business_graphics=>e_chart_type-BARS
    height = 340
    width = 750
*     BIND_TOOLTIP = 'GRAPH.TT'
    id = 'GRAPH' ).
DATA: lr_bgr_cs TYPE REF TO cl_wd_category.
lr_bgr_cs = cl_wd_category=>new_category(
view = wd_this->mr_view
bind_description = 'NODE_DYN.CATEGORY').
lr_graph->set_category( lr_bgr_cs ).
If we go to SE24, to check the class "CL_WD_CATEGORY", we cannot find any method or attribute about how to manipulate the "Category Font Color"...
Maybe,any other expert can give you fantastic solution, hope. Best wishes.

How do I set up voicemail for the first time?

I feel like i am losing my mind. I CANNOT find simple instructions (even in the manual) on how to set up my husband's voicemail on the BB 8800. There are all kinds of questions and answers about voicemail, but I just need to know how to set it up for the first time. The message you get when you call the phone is "This user has not yet set up voicemail" (or something to that effect).
PLEASE HELP!
Solved!
Go to Solution.

This is simple in deed! Go to Call Log -> click Menu and select Options -> Voice Mail. Now in the Access Number put your carriers Voice Mail Box number. Some carrier requires access password which you can also put in the.
Let know if this helps.
tanzim
If your query is resolved then please click on “Accept as Solution”
Click on the LIKE on the bottom right if the post deserves credit

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

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

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

Similar Messages

Maybe you are looking for