DSC 8.0 Run-Time custom installation

Hello,
I have developed an application using DSC 8.0 features and it runs fine on my development computer. I have a couple of questions regarding deploying a buillt executable on customer computer.
1. Can application exe be located in a folder different as DSC RTS installation?
2. Can DSC Run-Time 8.0 be installed in location different as default? I started an installation process of DSC RTS 8.0, but the Browse... button to select custom destination is disabled.
Ideally, I would like to achieve that application executable ( and all folder hiearchy needed ) would be separate from DSC RTS ( as when building pure LV code). If this is not possible, than 2 options exists:
a: to install application structure to default DSC RTS location or
b: to install DSC RTS to a custom location of my application ( prefered )
Please, can you explain me what option do I have.
I can not find a document that would describe a complete procedure for deploying DSC application with all possiblle options that could happen, as we all know that DSC applications are usually preety complicated and consists of many parts deployment can be very frustrating. This is a request for NI folks to put together one complete document ( kind of " Deployment Bible" ) for version 8.0
Regards,
ROMP

Matt:
Please try the following and let me know what you find.
Open your project from the project explorer
Right-click on your application and select Properties
Click on Advanced in the Category list
Disable Enable Enhanced DSC Run-Time Support
I am curious to know what you find.
Regards,
Rudi N.

Similar Messages

Installing LabVIEW DSC 8.6 Run Time on Windows XP Embedded flash memory

I'm trying to install LabVIEW DSC 8.6 Run Time on an embedded PC running Windows XP Embedded. This has a small local disk (c), so I would like to install DSC Run Time on a secondary flash memory drive (d). The installer tells me that I don't have enough free space on drive c, but I cannot browse to select drive d. What do I need to do to get this installed?
Thanks,
Josh

The DSC module can't easily be installed to external flash memory. You'll want to move any extra data onto the flash drive to free up space on the internal memory for installing the DSC module.
Mark E.
National Instruments
Schedule a Free 1-Hour online LabVIEW Tutorial with an NI Applications Engineer

Problems bundling visa run time with installer

I am trying to build an installer for an application that makes VISA read/writes through a serial port. I have tried to create an installer for this application but I keep getting a cryptic error that then terminates LV. I am experiencing the same problem as described in this thread:
http://forums.ni.com/ni/board/message?board.id=170&message.id=228510&query.id=494979#M228510
I am developing with LV8.2 on XP SP2. I would like to bundle the VISA Run Time so that I can communicate via VISA R/Ws. After reading the above mentioned thread it didn't seem like there was ever a real resolution to the problem. I am bundling the VISA Run Time engine just fine with other projects and I have deleted and started over several times with the installer inside this project, but I keep getting the same error, see attached document.
So are there any ideas short of me having to reinstall LV or VISA?
Thanks in advance!
Dave
Attachments:
LV Error.doc ‏32 KB

Thanks for the reply.
I would agree that the project is corrupted. I think I proved to myself that this was the case when I created a new project and magically everything worked just fine. The project was created under the exact same release of LV by the same PC so I am just trying to understand why the project was corrupted while trying to build the installer.
I guess I have my solution now I'm into the deep dark hole of trying to understand why the error occured. I know once I go down this path there is no returning.......
Thanks!

CVI Run time engine installation

Hi,
We are using TestStand extensively and in our installation package will be
installing the CVI RTE (run-time engine). Where can I find exactly which
files (DLL's especially) are installed by the CVI RTE setup.exe?
Iain

Iain,
The CVI RTE installer installs CVIRT.dll and CVIRTE.dll in your Windows\System
directory (Win98/95) or Windows\System32 directory (Win2000/NT). It also
creates a CVIRTE directory in the same.
You can get the latest CVI RTE installer from ftp://ftp.ni.com/support/labwindows/
It consists of 2 floppy disks.
By default, the TestStand 1.0.x engine installer utility will install the
CVI 5.0.1 RTE. You can have the TS engine installer install the latest CVI
RTE by replacing the CVIRTE directory in your TestStand\Setup\Engine\ directory
*before* running the TS Engine Installation Wizard.
Hope this helps,
Paul
"Iain Simpson" wrote:
>>Hi,>>We are using TestStand extensively and in our installation package
will be>installing the CVI RTE (run-ti
me engine). Where can I find exactly
which>files (DLL's especially) are installed by the CVI RTE setup.exe?>>Iain

Pdfcreator invokes LabVIEW run-time engine installer!

Okay, so I'm a desktop tech, know little about LabView, but can at least install it. We also use pdfcreator on our desktops. For some reason, however, whenever pdfcreator is used (for ANYTHING, not just LabView stuff), a windows installer fires up, "please wait while windows configures NI LabVIEW Run-Time Engine 7.0." The installer proceeds, then gets stuck while trying to find the msi. Well I don't HAVE the proper MSI apparently, because my version is 7.1.1! When I put in the 7.1.1 Run-Time CD (the only one I have) and point it to the msi it seems to be looking for, it still fails (apparently due to different versions).
So first, why is pdfcreator invoking this installer in the first place (they seem to have nothing to do with each other!)
Second, why is the installer looking for the Run-Time for 7.0, instead of 7.1.1?
Help!
Thanks,
Wiltony

Well, I fixed it. I eventually used the NI Software Add/Remove item, and chose "repair" for NI LabVIEW run-time 7.0, which called for the appropriate 7.1.1 device driver discs (strange). After it completed, everything worked fine.
Wiltony

Setting Time Server Search Order in DSC Run-Time

Hello,
can somebody help me with explanation how can I set the Time Server Search Order in DSC 8.6 Run-Time System? I can set it in development environment, but how can I transfer this to the Run-Time machine?
I want to synchronise a system clock of the machine to another machine acting as the time server, running NI Time Syncronization service.
Is it better to use standard Windows XP sync routines instead of NI ?
Thanks a lot,
romp

Hi David,
after trying NI approach ( I've got some tips from support, you should edit the Registry ) I found it just don't work well, so I have disable it completely and move to Microsoft mechanisms for clock synchronising. Looks like NI still didn't work this out as it should....it's a shame aince this is very fundamental stuff.
romp

Installing VISA run-time with distribution

Is there a way to seamlessly (transparent to the end-user) integrate the VISA run-time engine installation into an installation of a Labview app created with App Builder?
I am trying to avoid the user having to run two different install programs (the app install and the VISA install).
I am doing some serial port communications, using the VISA VI's in my app. Also, does VISA need to be configured beforehand, or can I just load a customized 'visaconf.ini' file with the serial ports aliases?
Thanks.

Hi,
There isn't a way to automatically include the VISA installer on the LabVIEW app installer. You can use some batch files to make the LabVIEW app installer execute other installers.
The following knowledge base gives some suggestions and points some of the problems you might encounter when using the LabVIEW 6.1 App Builder.
How Do I Distribute National Instruments Drivers with Applications Built in LabVIEW 6.1?
Hope this helps
DiegoF
National Instruments.

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

How to install Vision run-time engine to a desktop PC converted to real-time target

Hi, all
I don't know how can I install the vision run-time engine to a desktop PC which I converted to a real-time target. The same problem applies to installing real-time run-time engine and labview run-time engine to the real-time target. The only way to install software to real-time target is through "add/remove software" in MAX for remote system, but it is not for all types of run-time engine installation.
I am also confused about how to activate those run-time engines for the desktop PC as real-time target.
Please help and great thanks.
Wei

Hi turtle,
Here is a link that explains how to set up a desktop PC as a real-time target. The section for Formatting & Setup should help you the most.
NI Developer Zone Tutorial: Requirements for Desktop PCs as LabVIEW Real-Time Targets
Justin D.
Applications Engineer
National Instruments

How to prevent prompt to install CVI Run-Time Engine?

The LabVIEW laptop for my client got messed up, so I spent several hours making it forget everything it ever knew about NI software. I started by uninstalling all NI applications, then manually deleted all the folders that the uninstaller leaves behind, then ran a couple of registry cleaners to sweep out as much NI as possible, and finally ran regedit to see what was left. In the end there were only some legacy drivers that regedit would not let me delete.
Then I installed 8.6.1 from DVD, carefully selecting only the options we needed; LabVIEW core, cRIO, FPGA, PID, and the minimum set of drivers the installer would let me get away with. Note that no Labwindows/CVI option boxes were checked. When the installation was complete, I rebooted the machine and launched LabVIEW, which immediately prompted me to install the LabWindows/CVI 8.5.1 (not 8.6.1) Run-Time Engine. I dutifully fed it my 8.6.1 DVD, which caused LabVIEW to crash. After 3 reboot/retry cycles with the same result, I decided to appeal to the forum for help.
What is causing LabVIEW to think I need the CVI Run-Time Engine (and a down-rev version, at that), and how do I convince LabVIEW that I do not?
Jeff

Thanks for the reply! OK, so LabVIEW needs the CVI RTE even though I'm not using any CVI features. I can live with that. I downloaded LabWindows/CVI Run-Time Engine 8.5 from the NI web site and tried to install it. After I confirmed that I accepted whatever that license agreement says, the installer told me that "No software will be installed or removed."
Then I opened LabVIEW, and it went through the same "The feature you are trying to use..." popup and tried to install the CVI RTE. The installation failed as usual, and LabVIEW crashed.
A few minutes ago I found and ran CVTRTE.msi on the 8.6.1 distribution DVD. I selected the "repair" option, which completed successfully. After rebooting, I launched LabVIEW only to be greeted with the now-hated NI LabWindows/CVI 8.5.1 Run-Time Engine installer.
The part of this that is so infuriating is that there appears to be no way for anyone to make a computer forget everything NI so you can start with a clean slate.
Jeff
Attachments:
NoCanDo.jpg ‏28 KB

BOE XI v3.1 Custom Installation

Running a Custom installation of BOE XI v3.1 is forcing the use of MySQL as our CMS database. One of the first installation screens has us choosing "Custom" or "New" installation.
But there is no possibility of choosing an existing database server with the "Custom" install.
According the installation guide, pg. 73, we should be able to use an existing database server for the CMS with a Custom installation.
We would like to use SQL Server and have set up the database and ODBC. There is no problem configuring this when we try a "New" installation, the problem only occurs with the "Custom" installation.

Yes, I think we did select "Enable servers upon installation". On the "Please select which features you would like to Install" screen, when selecting to install "Central management Server", we expanded the Central Management Server and for MySql selected "Entire feature will be Unavailable". Look at page 69, step 3 of XI3.1 installation guide for Windows.
Mike
Edited by: Michael Isaac on Feb 25, 2009 3:24 PM

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

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 .

Adobe 8.2 custom installation

Hello everyone,
I'm trying to prepare a custom installation of Adobe 8.2. With the 9, I normally download the .exe file and then uncompress it to get the MSI file and the Setup.ini. Now, when I download the 8.2, I already get an MSI file, and I am unable to modify it using the Adobe Customization 8 software. It says I need to have a Setup.ini file, to I created an empty one and the Adobe Customization software wrote on it. It still doesn't work so I'm suspecting some other files are required to make the MSI run the custom installation.
Does anybody knows how to make this work? All I basically need is Adobe 8.2 silent install without auto-update and desktop shortcut.
I downloaded it on: http://get.adobe.com/fr/reader/otherversions/, I couldn't find the .exe I could uncompress and get the "usual" files.
Thanks,
Greg

Ian,
I'm not sure if it could help but see those links to exes. I haven't found
any exe for 8.2.0. I have never needed to deploy a patched version of Adobe
including an update, I've always waited for the .exe release, but if it
could help in any way, here's the list of direct links I use for Adobe 8.
Adobe 8.0
http://ardownload.adobe.com/pub/adobe/reader/win/8.x/8.0/enu/AdbeRdr80_en_US.exe
Adobe 8.1
http://ardownload.adobe.com/pub/adobe/reader/win/8.x/8.1.2/enu/AdbeRdr812_en_US.exe
MSP thing
http://ardownload.adobe.com/pub/adobe/reader/win/8.x/8.2.1/misc/AdbeRdrUpd821_all_incr.msp
Greg

Necessity of a run time engine

Can anyone tell me whats the detailed concept behind the necessity of installing the labview run time engine along with a labview application to make it work?
veena.

"Veena" wrote in message
news:[email protected]..
> What i wanted to know was what does a run time engine exactly does and
> whats its necessity? I havent explored the versions compatibility
> parts...am new to labview and exploring various things theoretically
> and practically, since I cant find a particular place or book that
> gives a overall view, and theres only manuals available for now...
> Veena
I'm taking a guess here, Labview is an interpreted language and that means
it needs something to convert the labview code into machine instructions,
the converter is the Labview runtime engine.
I think even if you create a *.exe file you need the runtime engine to run
it. I don't have the full d
evelopment version though so don't quote me on
that.
If you look in the help index for run-time engine you will find this answer
"Using the LabVIEW Run-Time Engine
If you create a system using LabVIEW that runs applications or shared
libraries, then you must install the LabVIEW Run-Time Engine. The LabVIEW
Run-Time Engine includes the libraries and other files necessary to execute
LabVIEW-built applications and shared libraries. All client computers
running LabVIEW-built applications and shared libraries must also have the
LabVIEW Run-Time Engine installed.
The LabVIEW Run-Time Engine also includes a browser plug-in that allows
clients to view and control VI front panels remotely using a browser.
All applications and shared libraries built with a particular version of
LabVIEW will share the same LabVIEW Run-Time Engine installation, so only
one installation is required. If you use applications or shared libraries
that you create with different versions of LabVIEW (for example, 5.1,
6.0,
and so on), you must have the Run-Time Engine for each version of LabVIEW
installed on the system.
You can find an installer for the LabVIEW Run-Time Engine on your LabVIEW
CD. "

DSC 8.0 Run-Time custom installation

Similar Messages

Maybe you are looking for