Utility to switch TestStand runtime engines

The development version of TestStand 2.0 comes with a version switch utility to change versions of TestStand between TestStand 1.x and TestStand 2.x. If a machine only has runtime engines installed, is there a utility to switch runtime engines between TestStand 1.x and 2.x?

The problem now is that the run-time installer will not allow a different TestStand run-time engine to be installed on the target machine since it already has a TestStand run-time engine. Unlike the full development installer, the run-time installer will not allow the TestStand directory to be changed so that more than one version of the run-time engine can be used. So, the version switch utility cannot be used unless there is a way to have two different TestStand run-time engines on the same machine (without any TestStand development software installed). Is there any way to get around this ? Am I misunderstanding something here ?

Similar Messages

Originally purchased TestStand 2.0; can I use 4.0 runtime engine?

After a hard drive crash, is there benefit in downloading the latest TestStand run-time engine, or should I try to find the 2.0 RunTime Engine? Are there any license issues?
Solved!
Go to Solution.

I don't believe that any of the run-times are downloadable and trying to run a version 2 sequence with a 4.0 run-time would not work.
There are a lot of license issues and you should probably contact NI directly with your serial number.

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

Runtime engine can't load vi with lvdatetimerec.ctl

Hello everybody,
i have trouble with TS 3.5 / LV 11.0
I programmed a small vi that calculates the time difference between now and a time stamp. To pass the timestamp from Teststand i use a Control (lvdatetimerec.ctl) and the matching VIs to do the task.
Unfortunally i can't load the vi into Teststand using the Runtime Engine. I get the message "Unable to load VI "xx.vi" with the Run-Time Engine. It is possible that the version of the VI or one of its subVIs is not the same as the ..."
It is certainly the same and there is no problem until i include a constant or control of that type.
Do anybody have an idea?
Best regards
Thomas
Attachments:
TimeDiff.vi ‏7 KB

Try to recompile your vi hierarchy in LabVIEW (hold Ctrl and click Run), then save it, then try again in TestStand with LabVIEW runtime.
Runtime engine does not support dynamic compiling, this vi may looks fine in LabVIEW, but TestStand will complain that it is broken.
Sergey Kolbunov
CLA, CTD

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

TestStand Deployment Engine Serial Number

Is there a way to get the Serial Number/License of a TestStand Deployment Engine that is installed on a PC?
The NI License Manager does not report the Serial Number of the Deployment Engine.
I have even tried to search the Window Registry.
We have over 100 TestStand Deployment Licenses in our installed software database. Split between BASE and DEBUG Deployment.
But I can’t find any way to tell/verify which license is on which machine. Just about all are on XP machine that are in need of replacement.
Just about all are TestStand 4.1
Omar

First of all I'm sorry that NI convinced you that a Debug deployment license was a viable option... I actually didn't know people would purchase those. That's funny.
So the license files are stored in %ALLUSERSPROFILE%\National Instruments\License Manager\Licenses. I was hoping the serial number would be in there. But it's not.
One thing you might want to consider to manage this a whole lot easier is to talk NI into giving you a VLM that you can put on a server and adding all your deployment licenses to it. We do this and it has saved us thousands, if not 10s of thousands of dollars. Now we can manage all the deployment licenses on the VLM. It has also forced us to follow the NI license agreement a lot closer than we were.
Sometimes you can't have all the computers on the LAN. In this case you can just assign disconnected licenses but still have VLM manage it for you.
Your last option would be to set up your own spreadsheet and manage it in there.
We were in the same boat as you a few years ago. So we contacted NI and got a list of all the licenses we had purchased in the last 10 years and threw them up on VLM. Then we had IT go through and look for a specific license file with an activated code inside of it on all the machines on the LAN. We got that list and contacted each of the PC "owners" and had them switch to point to VLM. In most cases we found the licenses weren't needed anymore so we could transfer those.
Hope this helps,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

"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.

DSC runtime engine problems

Hi,
I recently started a project which involves DSC runtime engine. This being my first contact with runtime engines, i obviously ran into some problems. Hope someone can shed some light. Here goes: I developed a project on my work laptop on which I have LV / DSC 8.6 installed. The project is then built into an EXE application and then run on a desktop computer with DSC runtime engine.The desktop computer receives data from a PLC through an OPC server (which is not NI OPC server). At first, I imported a csv file containing the list of variables in my project with the correct path of the OPC server from the desktop. When I ran the EXE application on the desktop, I got an error (PSP Led was red) saying that the variables could not be read / written. This was because the variables were not declared in the Distributed System Manager. And so my first question is this: is there a way to import my list of variables from a csv file or something similar, and if so, how can i achieve this? Because so far, all I was able to do was to manually enter only one variable at a time in the Distributed System Manager, and after about 50 of them I decided I would really hate to enter almost 800...
My next question regards the Citadel Database. As I told you before, I entered a few variables in the system manager and played with them for a brief amount of time. I set them T / F, I got the correct readings from OPC server, my PLC leds light up, the works. Now I wanted to see my actions in the Citadel DB, but when i ran MAX, there was no Citadel DB, only Default DB, and I could not find any of those variables which I entered and chaged states. Is there a problem with the Citadel DB not showing up? Am I not declaring correctly the variables in the System Manager? (i followed the help directions to the letter). Anyone has an idea as to why I cannot see the varaibles in my DB?
And now for a final problem.. In the LV front panel, i have some boolean buttons which are set to switch when pressed Mechanical Action. When I have the PLC connected sometimes when I press a button, it remains stuck on the TRUE state, thus screwing up my logic scheme (e.g. for a feed mill conveyor motor I have two buttons - start, stop. If i sometimes press the start button and it gets stuck, i can no longer SHUT DOWN that conveyor, which is really a big problem. I found a so-called 'fix' - right click on the stuck button and select Reinitialize to default value, but I was looking for an answer to understand this problem, not a silly little fix).
Hope I have been clear enough and you have not got tired of reading so much,
Cheers,
Sabin

Hi Andrew and thanks for the reply!
I don't think I deployed the library file, because I didn't know exactly how to do it. In the Source Files Property Page on Build Specifications I only selected VIs. I never selected lvlib files, so this may be the case. On the Source File Settings I saw that .lvlib files had the property Include if referenced and I thought that was the property which deployed the library. I will change the build specifications at once and keep you updated, but it could take 1 or 2 more days, because the computer with DSC runtime is in another city, and I have to get there first maybe tomorrow.
I have several buttons set on Mechanical Action Switch Until Released. They are all Shared Variables which are connected through OPC server to memory locations in the PLC CPU. In my LV Block Diagram, they are NOT connected to anything. They are just located in a While Loop, to get their state. The preffered action is that when I press a button on my Front Panel, I get to change a memory location in my PLC and then something happens in Ladder Logic. So, the boolean values are just there, in my Block Diagram, alone and not connected to anything. Do you have an idea as to why I get that kind of behaviour (I mean the buttons get stuck on True state)?
And finally, someone told me that the Citadel 5 might be missing because of incorrect option checking at install. However, I remeber that on the desktop, I installed the DSC runtime engine FULL INSTALL, I mean I checked each and every tick box, everything, examples and the like. One thing I was told was to insert the install CD once again and perform a re-install. I will of course try this, but let's not consider this for a second. Do you have another idea as to why the Citadel DB wouldn't show up?
And no, in the EXE Build Specifications, I did not check the option Enable Enhanced DSC Run-Time support. What does it do? Could you please elaborate?
Looking forward to your answer,
Sabin

Runtime engine installatiion aborted

HI,
I am trying to install LV runtime engine 7.1 on a user's machine and
see the error "Installation aborted, A higher version of this product
is already installed". I checked the registry, C:\Program Files and
Control Panle --> Add remove programs for any traces of already
installed versions but couldn't find any. To the best of my knowledge,
I can say that this machine does not have any other versions of LV. I
attached a picture with the error messages. I am using windows 2000 and
was logged in as administrator, when this problem occured.
My question is does anyone know if the runtime engine installation
checks any particular registry settings for information about
previously installed versions and hence does not allow the user to
proceed with the installation.
Deepak

The Run-Time Engine installer shouldn't check to see if any previous or future versions have been installed. The reason is that multiple versions of the RTE can be installed on a given computer. This is actually necessary in many cases, since applications built with a certain version of LabVIEW require that version of the RTE to run.
I haven't heard of this specific error occurring. I would recommend downloading the following site and downloading a utility called msiblast.exe. This should detect any hidden installers for NI software on your machine. Remove any that you find. You might also check out this Microsoft knowledge base on the msicuu.exe utility that helps clean up installers. This utility could help clean up configuration settings for any Windows installers as well as registry information that might be left behind.
Let me know if either of these utilities helps out.
Jarrod S.
National Instruments

Runtime engine 8.0.1 does not install because higher version is installed

Hello,
I am trying to install Runtime Engine 8.0.1.
This is the message I get when installing Runtime Engine 8.0.1:
"A higher version of this product is already installed."
Yet I do not have another Runtime Engine version installed. According to the NI Add/Remove program, I have the following installed:
NI LabWindows/CVI 8.1 Run-Time Engine
NI Measurement & Automation Explorer 4.2.1
NI-488.2.2.5
NI-485x Software 1.0.1
NI-VISA Runtime 4.0
At some point, I un-installed:
NI LabWindows/CVI 8.1 Run-Time Engine
NI-488.2.2.5
but I ended up with the same results:
"A higher version of this product is already installed."
I checked my folders and deleted any trace of Runtime Engine folders. I therefore deleted:
C:\Program Files\National Instruments\Shared\LabVIEW Run-Time\
but I am still unable to install Runtime Engine 8.0.1.
Any idea?
Thanks,
Francois

Hi Francois,
If you have a newer version of the runtime engine installed, then it should be listed in MAX. However, you've already deleted that directory, so it may not be there anymore. The only way now to uninstall those versions of the runtime engine is to use a utility we have that I cannot post on the forum. If you can create a service request via email or phone then we would be able to help you get the newer versions fully uninstalled. You can create a service request at www.ni.com/ask.
If you do not have a support contract and cannot create a service request, then let me know and I will create one for you so you can call in.
Nick R
NI

System Level Exception, error -17502 when running VI with RunTime Engine

My sequence conains a single Labview VI. The sequence functions correctly with the Labview RunTime engine NOT selected in the "Advanced Setttings" tab. When I enable the check box to always run the VI with the Runtime Engine, TestStand generates the following error "System Level Exception, error -17502. My teststand version is 3.5, with LV 8.2.
Thanks
Peter V.

Hi,
Are you sure you have LV 8.2 RTE on your system?
Regards
Ray Farmer
Regards
Ray Farmer

What is runtime engine?

What is a runtime engine for CVI or TestStand? What is the structure of a runtime engine?

See the following link to the answer to this post:
http://exchange.ni.com/servlet/ProcessRequest?RHIVEID=101&RPAGEID=137&HOID=50650000000500000015760100&HIsQuestionPoster=No&HTHREAD=000095765&UCATEGORY_0=_8_&UCATEGORY_S=0

LV 6.0 runtime engine not found with labview 6.1

I recently upgraded to LabView 6.1.
Now when I try to run an exe built under 6.02, I get an error that the 6.0 (or compatable) runtime engine could not be found.
I have the developers version of labview 6.1 installed, and the labview runtime engine 6.1 installed.
Do I need to install 6.0 runtime too? (in that case do I need 5.1 ruintime instaled too for exe's built a log time ago)?
Shouldnt the 6.1 RTE be able to run older exe's?
I could find no solution searching this web site.
Thanks
Larry Junek, Certified LabVIEW Developer

Did you install 6.1 wheer 6.0 was?
You may have lost the 6.0 RTE you did not realize you where using.
Yes you need the version of RTE that matches the app.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Runtime engine 8.6.1 on Labview 11

Hello,
I have upgraded labview 10 to Lv 11. A program that used to work on Lv 10 is giving problems now. It asks for runtime engine 8.6 ( usually gets stucked preparing the installation ). Once i cancel this process, it loads all the vi's, and it seems to work, but I can't be sure until all the devices are connected, and it can't be done until september. My question is, do i really need to install runtime engine 8.6 to make it work properly, or it can work without it?
And if I downgrade to Labview 10, will i solve this issue??
Thanks in advance!!

This is actually strange behavior because the runtime engine 8.6.1, if it is installed on the computer, should be accesible both from LV2011 and from LV2010.
What do you mean by "downgrade to LabVIEW 2010? You may have multiple version of LabVIEW on the same computer. Did you uninstall LV2010 first? If you did, then it may happened that you uninstalled the runtime engine 8.6 at the same time.
Do you really need or don't need the engine depends of your application. In any case, it should not be a problem to download the runtime engine from ni.com and install it. http://joule.ni.com/nidu/cds/view/p/id/1244/lang/en
Sergey Kolbunov
CLA, CTD

How do I determine if a VI is running in the runtime engine or LabView Development Environment?

Is there a function or VI that I can call that will tell me if the program is running in the LabVIEW Runtime Engine or if it is running in the LabVIEW developement Environment? I am using LabView 8.5.
I have a menu item, File/Exit, and I would like to call the Exit LabVIEW vi if running in the runtime engine when that item is selected. However, in development, I don't want to shut down LabVIEW when I select that menu item.
Maybe there is a more appropriate way to exit the program. However, I am looking for something elegant. I'm sure I could find some other way to accomplish the same thing, but I'm looking for a clean way to do it.
Thanks

Here is a small VI with this exact function.
Attachments:
Is EXE.vi ‏9 KB

Utility to switch TestStand runtime engines

Similar Messages

Maybe you are looking for