Simple: dll and runtime engine

Do I need the LV runtime engine to be installed on the machine to access the functions from the .dll file built out from the LV project?
Solved!
Go to Solution.

Simple: Yes. And you will need the "correct" version!
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Similar Messages

Make the installer for my executable run the DAqcarddriver and runtime engine installer automatically

*Hi
I would like to know how to make the installer for my executable run the DAqcarddriver and runtime engine installer automatically
I would like to include run time engine and the drivers of my daqcard(AI16XE50),( and maybe Ni daq or anything else needed?) in order to make my application portable for other computers on OS win98 and winXP .
How can I do that
thank you in advance
Olivier

Olivier,
What version of LabVIEW are you using to build your application? On a remote computer you should only need the drivers you are using and the Run-Time Engine. You can attach installers to LabVIEW 8 installers, but for previous versions you will have to add it by opening the installer configuration page, configuring your installer and then configure the Advanced properties. This will allow you to attach a EXE to the installer which you can run. Also depending on the version of LabVIEW will affect the OS version that you will be able to install the RTE on. LabVIEW 7.0 is the last version that can be installed on Windows 98.
Please let me know if you have any further questions and please include the version of LabVIEW you are using. Thanks!
Andy F.
National Instruments

Exe in french and runtime engine in english can it run?

exe in french and runtime engine in english
also max version is english
can it run successfully?

Hello,
You can build your executable with the french version of LabVIEW and run your executable with the english Run-Time Engine. However, note that strings in menus (such as File, Edit, Project, Help, and so on) and pop-up menus depend upon the version of the LabVIEW Run-Time Engine you are using with the executable. If you use the english Run-Time Engine, the menus always appear in english, regardless of the language of your operating system.
Also, note that for standard dialog boxes, LabVIEW uses strings (such as Open, Close, Save, and so on) that are specific to the operating system. Some dialogs contain LabVIEW specific strings (for example, Select Cur Dir), which LabVIEW displays in french, german, or japanese, according to the operating system's regional settings.
So if you need french menus and LabVIEW resources in your executable, use the french version of the Run-Time Engine available here.
Good luck and have a nice day!
Shakhina P.
Applications Engineer
National Instruments

A simple DBMS and SQL engine parser

hi guys;
i'm about to start an interesting c++ project described below...what i need is that you give me links ,advice and resources that could help me in my project...thanks for helping ...
here is the description:
Assignment:
In a nutshell, this assignment asks you to create a parse-tree for sample test SQL statements and actually create the underlying data structures to hold the data i.e. you are creating an extremely rudimentary SQL Engine (front-end parser) and a DBMS (back-end data structures). Our SQL Engine can be thought of as a bare-bone compiler. To test the SQL Engine and the DBMS, you will create a sample database. Finally (non-programming part), you will read up on the ODBC driver.
Note that a real compiler and a DBMS have functionality that is way beyond what I am going to ask you to implement. In fact, your DBMS software creation may disregard issues regarding efficiency ? those that couple the DBMS to the OS i.e. page buffering, blocking, concurrency, etc. Ours will be a data-centric view i.e. we will only focus on how best to save the user data. Treat this as DBMS-101 (It is more like DBMS-1.01).
Functionality:
Your SQL-Engine/DBMS software must offer the following capability-
Data: You must design data structures that will allow me to create tables and delete (drop) tables, insert tuples into tables, delete tuples from the tables and modify tuples values in tables possibly based on some criteria. Querying of course is the most important and frequently performed activity, but do NOT worry about joining tables or complicated queries. Data Serialization is of course implied by retrieval.
Meta-Data/Data Dictionary: In addition, I should be able to look up names of all tables that exist or the table definitions that exist and so on.
Future Requirements: I am being vague on this so that I may or may not add some small functionality later.
Software Components:
SQL Engine: Create a basic parser. Your parser should be able to parse the limited SQL statements that have been provided in Appendix A.
?     Include the test cases you used for the parser. Software Architecture and Implementation documents should also be attached.
?     Have the parser create parse trees for the sample SQL statements in accordance with your proposed grammar. The input could come from command-line or a stored file.
?     Print the parse trees (In-order and Pre-order) for sample input to present proof of correctness.
?     That completes the front-end of our SQL-engine.
DBMS: Propose a data structure, which will house the actual database. The back-end of the program will ?walk? the parse tree and create/fill in the data-structures in the back-end DBMS accordingly.
?     Data Dictionary ? meta-data details. I.e. lists details about tables and fields.
?     Data Definition ? creation of tables.
?     Data Manipulation ? update/modify, storage and retrieval of records.
?     Disregard issues regarding efficiency ? those that couple the DBMS to the OS i.e. page buffer, blocking, etc.
Database: Create a sample database to test your SQL/DBMS software. You must attach database schemas, tables with inserted values in your final submission.

I have no comments on the parsing of the SQL language. Without looking at Appendix A, I can't tell what you are being asked to do. However I do have a suggestion for a rather bogus back end storage that seems to fit the spirit of the assignment.
Create a directory named DB and in it keep files that are named things like
int_Employee_ID
string10_Employee_Name
where you follow the naming convention
DataType_TableName_FieldName
What this does for you is this:
To create a table just create files with the names and the datatypes that youwant.
To delete a table just delet files that have that table name as the secon parameter
The data dictionay is essentially a dump of the filenames in the directory.
Given that the data type in encoded in the file name it is easy to locate the ith element in any file for reading or writing.
Yes, it is bogus. It requires that you make dozens of disk reads to pick up all the pieces of a single record. Good thing efficiency was not listed as a requirement. You would NOT want this structure if you were looking for speed, or making sure that no tranaction gets only halfway done during a power outage.
But since the assignment is NOT about building databases but rather about parsing SQL statements, this layout gives you a fairly transparent way to represent your data and allows you to do nice bogus things like to create your initial data all with a simple text editor.
Since there are no joins to be requested of your system, all your SQL queries will essentially boil down into building filters that will run one or more of these lists and essentially create a list of indicies for records in a single table.

Windows SDK SetTimer() and Runtime Engine

Does anybody knows what happens in the CVI RTE when you call the WIN32 SDK
function SetTimer and start the LW RTE with RunUserInterface. We have
In our application we use the SDK function SetTimer to create a timer with
an intervall of 10ms. Even if the Timer callback function is empty the CPU
usage climbs up to about 55% when starting the CVI user interface. Other
processes and threads have about 40% longer runtimes as before starting the
user interface.
For testing we wrote the following short code.
SetSleepPolicy (VAL_SLEEP_MORE);
TimeIdent=SetTimer(NULL,0,10,TimerProc);
RunUserInterface ();
Has anybody experienced a similar problem.
IVM Automotive
Michael Koch & Stefan Urich

I'll go see you in a minute..

"runtime engine" crash

I have a problem with a LabView executable compiled for LV 6.1: it works without problem on a PC which has just LV Runtime Engine 6.1 installed, but it crashes (without error message) on a different machine that has a full installation of LV 8.5 and Runtime Engines 8.5, 8.2, 8.0, 7.1, 7.0 and 6.1. On this 2nd machine I installed Runtime Engine 6.1 last, because I got the error message about the missing engine when I tried to run the executable in question. After having installed the Runtime Engine, I no longer get the error message, but after a brief moment (before the first GUI opens) the executable crashes quietly. Any suggestions on how to solve this issue (rebooting the PC didn't solve it BTW)? According to the information I found so far on the NI website, Runtime Engines of different LV versions are supposed to run in parallel without problem.
As for my config: MS Windows 2003, Standard Edition, SP2
Solved!
Go to Solution.

Matthias,
then i fear that you are running into compatibility issues with the OS. Windows Server 2003 was never tested with any LV Version.
Reading the ReadMe from LV 8.6 it states:
LabVIEW supports Windows Vista/XP/2000. LabVIEW does not support Windows NT/Me/98/95, any of the Windows Server editions, or Windows XP x64. LabVIEW does support Windows Vista x64.
Since your system runs on Windows Server 2003 (since you didn't answer my questionmark in the last post, i think that is a fact) you are lucky that the newer application runs.
Please note that "not supported" means: it was never tested and therefore it might work, but if not, NI does not supply any support.
So the only solution to your issue is to switch to an OS which LV RTE 6.1 was tested on; the newest OS i think was tested (although not sure) is Windows XP.
hope this helps,
Norbert
Message Edited by Norbert B on 03-05-2009 06:48 AM
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Several question s about runtime Engine, application builder and labview player

I am a little confused by all the options to distribute a program.
Please help bij answering (one of) the following questions:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
3. What is the advantage of the labview player above the runtime Engine?
All questions refer to the latest software versions of NI software
Thanks in advance,
Regards,
Ferry

ferry1979 wrote:
1. Does an application built with the application builder always need the LV runtime engine? The LV runtime engine is 33 Mb to download!
Yes, the runtime engine contains all the stuff that is common to all LabVIEW applications. This is not any different than e.g. the Visual basic runtime (VBrun...) or dforrt.dll for Fortran.
If you built the application, you can strip it a little bit by including the runtime with the installer and leaving out unneeded modules (see image from the 7.1 builder).
The advantage of a seperate runtime engine is that applications are very small. The runtime needs to be installed only once. On any broadband connection, 33MB is peanuts. I distribute everything without runtine, but tell people to download and install the runtime directly from NI.
(In LabVIEW 4, no runtime was needed, with the disadvantage that even the simplest program was multiple megabytes. Not an efficient solution).
(Maybe in a few years LabVIEW will be so prevalent that the LabVIEW runtime will be part of a standard OS install ;
2. Is there anyway to make a 'normal' executable that runs on a windows machine, without any supporting installed software?
No. See above.
3. What is the advantage of the labview player above the runtime Engine?
The two are quite different. The labview player is more a simple educational tool, because it lets users inspect the diagram. It is not designed for any serious application deployment.
Message Edited by altenbach on 08-21-2005 10:05 AM
LabVIEW Champion . Do more with less code and in less time .
Attachments:
runtime.png ‏24 KB

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

Labview 8 Application Builder and VISA Runtime Engine

Hi,
I am using Labview 8 Application Builder and everything is working fine except for 1 small thing. My program makes use of some of the VISA functions and when I build the application I'm having to include the VISA Runtime Engine Installer as a separate item on the CD to make the .exe file work.
What I would ideally like is for people who want to use the application to run the installer and that all necessary components (including the VISA Runtime Engine) are also installed in the one installation. At the moment they're having to do 2 installations and I would like to streamline this.
Is this possible?
Ken

Hi,
this How-To explains about making those selections and including the different drivers :
http://zone.ni.com/reference/en-XX/help/371361A-01/lvhowto/add_installers_to_build/
and this tutorial covers the screenshots a little more step by step.
http://zone.ni.com/devzone/conceptd.nsf/webmain/5ADBC06AC32E508A8625706E0062EBD1
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

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

USB/Serial Drivers and App Builder Installer Questions...are drivers included in the Installer with the LV runtime engine?

Hello all,
I'm wondering if someone can help me out with how drivers and all are treated with applications distributed with App Builder, used to create a stand alone, full install of app and labview engine with Installer.
What has happened is, my application was created using the NI branded USB to RS232...and USB to RS485, and they work great.
On the application when running..you fire it up, it finds the USB to serial device, and I have a dropdown that finds the available COM ports to use (along with setting parity, etc).
I've installed on different computers (without previous labview installs) with the installer. They all worked.
The customer has received the installer....and despite us telling them to use the NI branded USB/Serial interfaces..they are trying to work with a different USB/serial cable.
They say the COM ports aren't even showing up when they run the installed application.
So, I'm not sure where to start. Is this a driver issue? Does the App Builder Installer...install the drivers for the interfaces I was using with it? Is there a way for the person to find and install a driver on their own...or would I have to somehow find out a driver for what they use....then, basically redo the App Builder Installer build...to include that driver with the executable I send back out?
I guess I basically need a better understanding of how drivers for external access/communications are handled when you use App Builder to create a stand alone application complete with the labview runtime engine...and nothing else.
Thank you in advance,
cayenne

The main thing is that LV uses VISA to talk to serial port whether native on the machine or from USB dongles that you plug into the computer. It sounds to me like their dongles aren't working.
Can the customer see the ports in the Windows Device Manager? Can they access them through something like hyperterminal? How does your program find the USB/Serial devices?
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

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

Runtime Engine 6 and Windows XP

Hi all,
Ok, I created a vi in Labview 6.0i and compliled it. Installed Runtime
Engine 6 on an XP machine where I want to run the VI. The problme I'm
having is that the VI starts, but doesn;t seem to communicate with my
instruments on the GPIB bus. This vi runs fine on a Windows 2000
machine. Any Ideas?
Thanks
Andrew

I'll go see you in a minute..

Unable to determine the install root path for the LabVIEW Runtime Engine

Hi,
i have an issue with using a LabVIEW interop assembly in a .NET application. I get an exception "Unable to determine the install root path for the LabVIEW Runtime Engine" when calling the assembly.
The little test program is attached below. It's called dotNETHost.exe. If you excecute the programm a dialog with an button appears. Clicking the button shall open another dialog (the LabVIEW Interop component). But the only thing I get is the exception message. The ZIP folder also contains the complete exception meassage (ExceptionMessange.jpg & ExceptionDetails.txt).
The Interop Assembly was built with LabVIEW 2011. We use Visual Studio 2010 and .NET 4.0.. The dotNETHost.exe.config file is prepared as mentioned in Knowledge base - Loading .NET 4.0 assemblies.
The Interop assembly contains only one simple dialog (loop is finished by clicking OK) without calling any other VIs or other DLL's. In case of this there's also no support directory generated by the build process.
I have no idea why it doesn' work. I hope anyone can help me.
Thanks in advance
Kay
Attachments:
Debug.zip ‏75 KB

This may be unrelated, but Labview and .Net4.0 dont work well together. Not yet anyway. I had to compile my assembly in 3.5 to get it to work.
Please read the following:
http://zone.ni.com/reference/en-XX/help/371361H-01/lvhowto/configuring_clr_version/
http://digital.ni.com/public.nsf/allkb/32B0BA28A72AA87D8625782600737DE9
http://digital.ni.com/public.nsf/allkb/2030D78CFB2F0ADA86257718006362A3?OpenDocument
Beginner? Try LabVIEW Basics
Sharing bits of code? Try Snippets or LAVA Code Capture Tool
Have you tried Quick Drop?, Visit QD Community.

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

Simple: dll and runtime engine

Similar Messages

Maybe you are looking for