Advenced Signal Processing 7.5 Run Time Engine in LVIEW 8.2 Installer

Hello,
I am trying ot create an installer using LVIEW 8.2 and I need to include the Advanced Signal Processing Toolkit run-time engine but this is not listed in the 'Additional installers'.
I have run and installed the Advanced Signal Processing Toolkit (7.5) and the run time engine on my machine.
How can I include this run time engine in my installer?

The Application Builder of LabVIEW cannot let you select the Advanced Signal Processing Runtime Engine like you select the LabVIEW runtime engine and other driver engines. You have to do it by yourself.
What the Advanced Signal Processing Runtime Engine installer does is to install the DLLs to the system32 folder. So what you need to do is to add the DLLs to your project and configure your installer to install the DLLs to the system32 folder.
See the attachement for more hints.
Attachments:
ASPTRuntime.doc ‏87 KB

Similar Messages

Installing Run Time engine question

Hi,
I am new to this and I am looking for information on how to set up a test system PC.
I have the 2014 developer software and one test seat but need to know how to install the labview 2014
runtime engine and anything else that I need in order to use this test system PC to run Labview and teststand
applications that I create with my development system PC...
Is there any tutorials or instructions out there that I can download that will tell me everything that I need to install and how on my target test system?
Thanks

the Installation instructions are on the Download Page
Installation Instructions
Close all NI software.
Run the LVRTE2014_f1Patchstd.exe self-extracting executable and follow the prompts.
Repeat these steps for all development systems where you want to install the LabVIEW 2014 Run-Time Engine (32-bit).
The installation files for the Run-Time Engine are automatically extracted to a directory on disk. The installer does not remove the files after installing, if you want to remove these files from disk, be sure to note their location during the unzipping process.
Jeff

Run-Time Engine error

I have created an automated test and had it running as an executable on a stand alone test computer. I updated my LabView software to 8.6.1. I just made some changes to the test and recompiled it. When I tried to run it on the stand alone computer it gave me an error about the LabVIEW 8.6.1 run-time engine missing. I thought when the project was built all the files that pertained to running it were also built into the folder. Has anyone run into this that could offer some advice.
Thanks
Chirs
Solved!
Go to Solution.

Did you create an installer or simply build the exe? If you only built the exe you will need to install the run-time engine on the target machine. If you created an installer you can include the installation of the run-time engine as part of the installer.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

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

NI Vision Run-Time Engine 8.2 - Error user is now getting when attempting install of built software

I've built an installer for an application using LabVIEW 8.2 and Vision8.2. I have sent this installer to someone for 6 months and they have had no problems completing the install.
Now the last time that I sent the installer, the user is getting the attached error during install.
"NI Vision Run-Time Engine 8.2
Error: Another installer or uninstaller is running.
Finish that installer or uninstaller and try again."
When the user clicks OK to this error, the user is then told to restart or finish uninstall. Since we do not know what uninstall is being asked for, the user restarted the computer and attempted running the software - to which he was prompted for LVWA.dll file and he did not know what to do from there.
I gave the installer to a second beta-tester - the same thing occurred.
The only thing 'of significance' that has changed in my software that I can think of that is Vision related is the inclusion in the software of the ability to read/write .TIF files. I have no clue whether that might have anything to do with the error.
Any help is appreciated. NI - I can post the installer ZIP to your ftp site if you want.
Sincerely,
Don
Attachments:
error.jpg ‏30 KB

Hello Don,
Have you tried uninstalling the previous Vision run-time
engine on the deployed computer before running the new installer? You
might also want to try running the Vision RTE separately from the installer to
see if you are able to manually run it on the target. Here is a document which explains the
procedure for both manually installing the RTE as well as how to include it in
the LabVIEW installer:How do I
Deploy LabVIEW 8.0 and 8.20 Applications with NI Vision 8.0 and 8.2?
I also found
a Knowledge Base that may be helpful addressing the error you mention in your
first post. I hope this helps.
How Do I
Correct the "Another Installer Is Already Running" Error Message?
Regards,
Vu D

Error -17600 when switching from LabVIEW Development System to LabVIEW Run-Time Engine in Adapter Configuration

I receive an error message (code -17600) while loading my test sequence after switching from LabVIEW Development System (2009 f3) to LabVIEW Run-TIme Engine using the Adapter Configuration.
ErrorCode: -17600,
Failed to load a required step's associated module.
LabVIEW Run-Time Engine version 9.0.1f3.
When I switch back to the LV development system, everything is OK, and the sequence loads and runs perfectly.
My TestStand Engine Version is 2012 f1 (5.0.0.262).
I'd appreciate any help on this issue.
Roman

Hi Roman,
There are a couple of things you can try:
1) Determine if the LabVIEW RunTime Engine is corrupted in some way. Create a new simple VI with no sub-VIs, using the same LabVIEW Development system you used for mass-compiling the VIs. Create a TestStand step that calls this VI and ensure it runs correctly. Now switch your LabVIEW adapter to use the RuntimeEngine and choose the "Auto detect using VI version" option.
Check if the simple VI is loadable and runs without errors in TestStand.
If the step generates the same error, you should try a re-install of the LabVIEW development system.
If not, its most likely that there is some VI you are using that is not loadable in the LabVIEW Runtime Engine because:
1) Some sub-VI is still not saved in the right version or bitness. Open the VI heirarchy of the top-level VI that you are calling from TestStand and examine the paths of all the sub-VIs to check if they were in the folder you masscompiled and re-save any that are outside this directory.
Also, when you try to close the top level VI, do you get a prompt to save any unsaved files? If so, they could be the sub-VIs that are not saved in the right version. Save all of them.
Check if you are loading any VIs programatically and if these are compiled and saved in the right version as well.
2) There is some feature you are using in your LabVIEW code that is not supported in the LabVIEW RunTime Engine. To check this, add your top-level VI to a LabVIEW project and create a new build specification and create a new executable from this VI.
    Right-click "Build Specifications" and choose "New->Application(EXE)".
    In the Application Properties window, select Source Files and choose the top level VI as the start-up VI.
    Save the properties.
    Right-click on the newly created build specification and choose Build.
Run this executable (it will be run using the LabVIEW RunTime) and check if the VI has a broken arrow indicating that it cannot be loaded and run in the LabVIEW Runtime Engine.
You might need to examine your code and find the feature which is not supported in the LabVIEW RunTime and find an alternative.
Another thing i forgot to mention the last time around is if you are using 64-bit LabVIEW with 32-bit TestStand, then executing code using LabVIEW RTE from TestStand will not work since the 64-bit LabVIEW RTE dll cannot be loaded by the 32-bit TestStand process.
If none of the above steps resolve the issue, consider sharing your LabVIEW code so i can take a look.
Regards,
TRJ

Error on installation of LabVIEW Run-Time Engine 8.5.1: "This application has requested the Runtime to terminate it in an unusual way"

Hi,
a colleague in India cannot install the LabVIEW Run-Time Engine 8.5.1 on Windows XP. On attempting to install, an error box is shown, which says:
(window title)
Microsoft Visual C++ Runtime library:
(message box text)
Runtime error!
Program: C:\National Instruments Downloads\LabVIEW 8.5.1\Runtime Engine\setup.exe
This application has requested the Runtime to terminate it in an unusual way.
Please contact the application's support team for more information.
http://img529.imageshack.us/my.php?image=runtimeerrorvt7.jpg
I didn't find any relevant clues for this in NI forums. A search at Google brought me to http://support.microsoft.com/kb/884538/en-us, offering a HotFix to solve the problem. Unfortunately, the installation of this HotFix does not solve the problem.
Do you know this behavior and do you have any ideas how the problem can be solved?
Thanks in advance.
Best regards
Manuel
Message Edited by Manuel Häderle on 10-07-2008 10:41 AM
Solved!
Go to Solution.

Hi there
log in as administrator and kill all processes not needed and try again. I've seen cases where one of these free download tweak applications (like "Memory Defragmentation" and stuff like that) caused that error.
Best regards
chris
CL(A)Dly bending G-Force with LabVIEW
famous last words: "oh my god, it is full of stars!"

Labview Executable with VISA functions in Run Time Engine

Hi Everybody
I designed a gui to communicate using VISA GPIB. I created an executable for the gui. I also installed LabView Run Time Engine on the desired machine. I recieved couple of errors, for which I copied the files visa32.dll, NIVISV32.dll and serpdrv to the folder with the executable.
I recieved the following error, ' Initialization of NIVISV32.dll failed. The process interminating abnormally.'
Are there any drivers I should install in addition to the Run Time Engine? If so, where can I find these drivers?
Thank you
Jackie

I installed NI-VISA with similar version as my development installation, and LV runtime engine. Labview still crashed.
I noticed certain library functions in full labview that is not present in the NI-VISA + LV run time directory, such as _visa.llb etc.
Do I need to copy these additional library functions too? Will Run Time Engine read these library functions?

How can I uninstall Labview run time engine from the machine?

I understand that Labview has not given any provision to show customized 'License Agreement screen'. Isn't it? This is the main cause of my problem. Since I want to show our own license agreement (LA) screen, I made the one using Labview. To show this license agreement screen, I first install a small application which has only this LA screen with Labview run time engine. The customer can see License Agreement Screen with Labview Run Time Engine on his machine. If My customer accepts the LA, I will install the main application further by calling another setup.EXE file.
If my customer selects 'Do Not Agree' to the LA, I will quit the installation process. Here I also want to 'uninstall' Labview Run Time Engine
from his machine since he doesn't accept License. I would like to know how to uninstall Labview run time engine from his machine?
Another way which I could think is to run the LA screen from the CD with Labview run time engine on the CD. I will start installing the main S/W to the customer's machine with LABview Run Time Engine only after he accepts License agreement. I would like to know how to run the Labview application from CD without installing run time engine on the target machine?
Can anyone suggest solution to my problem?
Thanks,
Chander

J-Tek,
I would suggest re-installing the Run-time Engine and then uninstalling it after a reboot. Also, you can download a program called Msicuu.exe (for NT, 2000, XP or Msicu.exe for 9x) to help clean up the registry for uninstalled programs.
Randy Hoskin
Applications Engineer
National Instruments
http://www.ni.com/ask

Run time engine and NI-DAQmx installation order

Greetings Fellow Developers:
I'm looking at a product manual that contains instructions to install NI-DAQmx, a product software installer created with LabVIEW 2009 SP1 Full and then the LabVIEW 2009 Run Time Engine in that order.
This does not seem correct--particularly if a LabVIEW 8 (or previous) Run Time Engine is already installed.
Since I need to test installation of my builds before distribution I'll need to install them on machines that have never had any NI products and also on machines that may have previous Run Time Engines.
I feel the correct order is to install the Run Time Engine, NI-DAQmx and THEN the application. Prior to running the application the USB device should be plugged in so the 'add hardware wizard' can install the USB driver(s).
What is the consensus on this?
Warm Regards,
Saturn
Solved!
Go to Solution.

Hello Saturn,
Could you point out the location of the product manual that explains this order? Typically, when installing National Instruments products, in particular LabVIEW, we recommend installing LabVIEW, drivers, and toolkits in that order. So, installing the LabVIEW 2009 Run-Time Engine, DAQmx, and then your application should be the proper installation process.
Regards,
Roman Sandoval | National Instruments | RF Systems Engineer

Does Vision Development Module obviate the need for the Vision Run Time Engine?

I have several computers with the full version of Labview (8.0.1 and\or 8.2) as well as the most recent version of the Vision Development Module (VDM 8.2.1), all fully registered and activated. In addition, I have one computer we have designated the "build" computer which has the professional version of LV 8.2 as well as LV 8.0.1 Full version w/ Application Builder (we have delayed migrating certain applications to 8.2 for various reasons). Instead of distributing applications as source distributions to these computers (uncompiled VIs), we would like to use our build computer to compile applications that make use of the Vision image processing VIs. I know that all of these computers have the appropriate LV run time engines installed, but I was wondering if I need to install (and thus purchase) the Vision Run Time Engine for each of these computers. I know that when you install VDM, you also get a copy of the vision RTE (in C:\Program Files\National Instruments\Vision\Run-Time Engine). Does this mean the engine is already installed and ready to run compiled applications? Or do we need to pay for the engine on each computer?

The Development module includes the RTE for that machine.
For the other machines, you will need to purchase the Vision RTE and install and activate for each machine. See the KB article below for more details.
http://digital.ni.com/public.nsf/websearch/F1699570F78FECBB86256B5200665134?OpenDocument
Ed
Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

Run time engine, Error of type 1002208

Hi,
I want to build an exe using LV 8.6 development (project builder).    When I finished the project in LV8.6 development, it works ok. But When I copy the project (include the exe file) to the computer installed only run-time engine (standard) and Measurement & Automation Explorer, V4.0.0.3010, The screen indicates " VI has an error of type 1002208, The full development version of LV is required to fix the errors."    Is there anything wrong when I build the application? Thank you.
Hsien
Solved!
Go to Solution.

Hi Dennis,
  When i built the application, I didn't build an installer into the project. I pretty much followed the HELP in LV 8.6 example: Build a stand-alone application.
The vi is mainly to read the TC signal and voltage signal from the computer connected to a scxi-1000 chassis and modules (scxi-1102 etc.)    Yes, the vi called the sub vi (like DAQmx Created Channel [AI Temperature-Thermocouple].vi; DAQmx read.vi etc.). When I built the exe file, I have placed these vis into "always included" under "source file" category. Thank you.
Regards,
Hsien

Getting LabVIEW load error code 59 using LabVIEW 2010 with a Run Time Engine.

I use a vi compiled with a run time engine to run separate vi’s in my application directory. Once a file association is made with this exe file any Vi in my application directory is available to be loaded as needed. This is a process that has been very successful for me over the years and would prefer to continue using this process. Most of my applications are running in LabVIEW 8.6 and have moved them to 2009. First indications are in 2009 this process is still working. However, I plan to go on to 2010 before upgrading my test stations.
In 2010 I get the error 59: “The source file’s compiled code has been separated, and this version of LabVIEW does not have access to separated compiled code.”
The same dialog box also presents, (Hex 0x626) “Cannot open a VI with separated compiled code in a Run Time Engine that has no access to the VIObjCache.”
What can I do in the build that will get around this error?
Thank you

Thank you for the solution. I am sure this works until the next vi in the vi library gets this option selected.
The bigger issue is I was doing something that National Instruments did not support. When I started in the days of LV 4.0 it was recommended to me that I use this method as virtually all my applications were for in house projects. This is still my preference because it gives the most versatility and allows modifications of single files rather than compiling the entire application.
The final solution I ended up with for those who may be having the same issues. My recommendation for what it is worth, is to compile the application as an executable. This is from what I can tell the only acceptable and supported method. Using this method the problem is solved.
I have accepted this as the solution. I still don't like it. I could list the reasons why but it is a mute point.
Thanks again for taking the time to respond to this issue and offer the solution you found.

Error involving Report Generation Toolkit and Labview Run Time Engine

Developed an application using LabVIEW 6.1 and LabVIEW Report Generation Toolkit for Microsoft Office 1.0.1. From there, tried to build a shared application for use with the LabVIEW Run Time Engine. The Run Time version functions properly until "New Report.vi" is called and then an error is generated, code 7, calling out "Open VI Reference in New Report.vi" could not be found. When building the application, I did include the "NI Reports Support" in the advanced installer options. The machine used for original development and application build is running Windows XP Pro and Office XP. Any suggestions??

I am having the exact same problem but with LV 6.1 and M/S WORD 2000. It appears that the "New Report.vi" is trying to open "C:\APP.DIR\Word_Open.vi" and "C:\APP.Dir\Word_Open_Document.vi" by reference. The "OFFICE 2000.TXT" says that "_exclsub.llb and _wordsub.llb must be added as support files when building an application or a dynamic link library with the application builder." I added them as Support Files and I copied them to the "C:\TESTER\" where the TESTER.EXE is and I still get ERROR 7 in "NEW REPORT.VI" at VI OPEN REFERENCE.
Do I need to make a "C:\TESTER\DATA\" sub-dir and put the support files there?
I am building on MY COMPUTER on F: Drive on a network and transporting files to the real Tester.
I displayed my App.Property of APP.DI
R at start up and it is C:\TESTER\ ! How would my application know that "Word_Open.vi" and "Word_Open_Document.vi" are actually inside the _wordsub.llb?
Any ideas ?
Greg Klocek

Can't install run-time engine on Ubuntu 8.04. Get /bin/sh failed to load.

Simply receive a message when trying to install the LabView run-time engine .rpm file that says /bin/sh failed to load (or is required, I forget exactly). I checked, I have BASH installed, and /bin/sh is a shortcut to an executable on my machine. Is this a bug in the installer, or is there something else I need?

LabVIEW installation is not supported on Debian based Linux systems (of which Ubuntu is the most popular). However, many people have had success installing to various flavors of Ubuntu. You can search these forums using the key Ubuntu and find the problems they had and how they solved them. If you cannot find an answer to your problem, let us know.
This account is no longer active. Contact ShadesOfGray for current posts and information.

Advenced Signal Processing 7.5 Run Time Engine in LVIEW 8.2 Installer

Similar Messages

Maybe you are looking for