Installing Test Executive 5.0 in LabVIEW 6.0.2

I'm trying to install Test Executive 5.0 in LabVIEW 6.0.2. However, I run into problems. When i Try to mass compile the test executive folder I get a lot of errors (see attached file), and I don't get the executive in the tools menu.
Could someone tell me what needs to be done?
Thanks,
/Martin
Attachments:
mass_compile_TestExec.txt ‏32 KB

I use Test Executive 5.1 with LabView 6.1 (after doing a mass compile) and have no problems.
It looks to me like Test Executive isn't installed correctly so some VIs are missing or in not the expected place. Try reinstalling Test Executive. Don't move any of its VIs after you install it.
You get a ### Bad VI message for a VI if any of its subVI's are missing. There's probably a lot of other reasons for Bad VI, but a bad install seems like the most likely reason. A install may be bad if it's incomplete or simply if you install it to a new location and the VIs that use it are still referencing the old location.
Test Stand is a much more powerful product (and I use it on other applications), but for an existing application with a limited budget, we upgraded LabView,
the PC and Windows, but we didn't replace Test Executive with Test Stand. Going to Test Stand, you not only have the cost of the Test Stand software, you also have the development cost of rewriting some code for Test Stand. Depending on your application and how much you customized Test Executive, the development cost may be significant.

Similar Messages

When running labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. Could someone explain this error?

I have a set of vi's that work when run under labview. However, when calling these vi's from labview's test executive I recieve runtime error: Call to step "PRE-RUN" failed. in Assign Connector Pane.vi->Call Test.vi->Execute Pre-Run.vi->Test Executive. Could someone explain this error to me? (or ideally tell me how to fix it?) Thanks.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

When running labview's test executive I recieve runtime error

When running labview's test ( Measurement & Automation Explorer) executive I recieve runtime error ms vc++
win95 labview6.0
<<<<>>>>
Mensaje publicado mediante http://noticias.ipbusiness.com,
las news a través de web.

Hello,
There are any number of possible causes to this problem. Which version of Test Executive are you using? Have you upgraded your Test Executive recently? The latest version is 5.1.1. If you have changed anything about Test Executive on your computer recently, I recommend you perform a mass compile of all your VI libraries, as having different versions of the VIs on your system could often result in the "Call to Step XYZ Failed" errors. Also, are you using any DAQ or Analysis VIs in your steps? We have seen problems where the use of DAQ or Analysis VIs in the sequence can cause intermittent "Call to Step...Failed" errors. There are some KnowledgeBase entries on our website that discuss this problem. Are you using the Test Executive in the VI environment, or
as an executable? Again, there are some problems with using Test Executive as an executable that result in these errors, and there are also KnowledgeBase entries that discuss these problems.
If you have a pared-down application that demonstrates the problem, feel free to send me your VIs and your .seq file and I will try to reproduce the problem.
Alternatively, I would suggest you visit www.ni.com/teststand to learn about TestStand, our state-of-the-art Test Sequencing software that completely outperforms Test Executive. It is very easy to use and much more powerful, and we have a top-notch support team available dedicated exclusively to supporting TestStand. As you are probably aware, we are no longer developing Test Executive, and instead are concentrating our efforts on making TestStand the penultimate solution for all our customers' test sequencing needs.
I appreciate your patience on this issue. Please let me know if I can offer further assistance.
Have a pleasant weeken
d.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

How to get labview test executive

Dear all,
i have known the labview test executive recently, but i don't know how to get it. would you please tell me?
Thanks!
Jimmy
Best regards

Hello,
i just got to know the information from the ni site. i am very interesting in it. i review its manual downloaded from the ni site. i think its library is very helpful to our system which was developed by labview. How can i got the library? i have TestStand. Can i get it from the TestStand? Thanks!
B.R
Jimmy

A scalable test executive with build in video monitoring

Hi,
Is anyone interested in test executive? Check out IMCS, a scalable
test executive framework with build in video monitoring for only $99.
It can call external LabVIEW vi or DLL functions. It can be used in
lab testing, product testing and many more. Here is the link to IMCS:
http://www.hytekautomation.com/Products/IMCS.html
Thanks.
Irene

i tested mine out and it works... have you downloaded flash player osx yet?
i installed it from the get go... maybe this could be the issue your having.
http://www.adobe.com/support/flash/downloads.html

Install many executable on the same PC with different names

Hello,
I'm trying to install several executables with different names in the same computer but at the end of install process the message is : "an higher or existing version is already installed in this computer"
I create the Executable and Setup with LabVIEW Application Builder and install the executable in the same Program Files root directory with a different sub-directory for each executable as this : Program Files-->MyProject-->SubProjet1 with exe1/SubProject2 with exe2 etc...
My OS is WinXP pro SP2 and I work with LabVIEW 8.5.
Thanks and regards,
Armindo PINTO

Hi Armindo,
Thank you for using the NI forums!
From what I understand, you are trying to create multiple executables of a vi project to co-exist on the same PC. Any time you re-use the LabView 8.x project file, it will generate
install package with the same product ID number. That means, if the
deployed PC has the previous version installed, which had been
generated from the same project file, the new install package will
remove the previous version and overwrite it with the new version. Or as in your case, not allow you to install lower versions of the executable. That
means, the previous version will be no longer available on the deployed
PC. If you are creating an upgraded version to the product this is
fine.
However, if you need to re-use the LabView 8.x project
file and generate a new product, which can potentially co-exist with
the previous on the end user PC, you need to generate a new installer
with a different product ID number. One of the way to do it:
Copy existing project file (e.g. "name1.lvproj") under a different name (e.g. "name2.lvproj")
Open the new instance of the project
Expand the "Build Specifications"
Right click on the installer specification, e.g. "name1 Installer"
Select "Duplicate" from the menu
You can now delete the instance "name1 Installer" and rename the "Copy of name1 Installer" to a suitable name, e.g. "name2 Installer"
Make changes that are needed between the two versions, for example:
Select a new source VI
Build a new exe file
Reflect the new exe file in the "name2 Installer"
Make
any other changes needed in "name2 Installer", for example different
documentation files included in install, change in the target install
directories, changes in the start menu shortcuts. etc.
Build the install.
Please let me know if this solves the issue, and let me know how you get on.
Kind regards,
Ashish Naik
Field Sales Engineer
National Instruments UK

How to fix sequence editor error when using Test Executive 5.1.1 with Labview6.0?

I had a test sequence that was built with Test Executive 5.1.1 and Labview 5.1.1. The sequence test step vi used Test Shell to allow the user to edit and config the test. After upgrading the test step vi from Labview 5.1.1 to Labview6.0 by mass compiling all vi to Labview6.0, an error occurred while editing the test vi. The error is as following:"Sequence Editor Error: Config Test Vi Callback.vi: Could not config test vi. Make sure the path to the vi is valid." I am sure the vi path is valid, does anybody has any idea why the path was not seen? How can this bug be fixed? Any hints or suggestion would be helpful.

That's really a TestStand question. You should post to the TestStand Discussion forum. TestStand Discussion Forum

LV Test Executive reloading

Is there anyone having a problem to run the test sequences in Labview Test
Executive V5.1 ? I must reload the Test Executive every 4 or 5 full test
execution. Otherwise, Test Executive can not communicate with instruments
in ATE and the test sequence displayed all false error measurements. I don't
know if it could be the case of memory leaking !
I am working with labVIEW 5.0.1 for Windows 98
Thanks in advance.

Check to see how you are opening and closing VISA references. If you keep
opening references without closing them afterward, you can see this sort
of problem. I use TestStand instead of Test Executive but what I do is open
references to all instruments in a setup step and then close them in a cleanup
step.
"vanhoa dao" wrote:
>>Is there anyone having a problem to run the test sequences in Labview Test>Executive
V5.1 ? I must reload the Test Executive every 4 or 5 full test>execution.
Otherwise, Test Executive can not communicate with instruments>in ATE and
the test sequence displayed all false error measurements. I don't>know if
it could be the case of memory leaking !>I am working with labVIEW 5.0.1
for Windows 98>>Thanks in advance

Illegal operation occures running a 'Write Digital Line' vi in Test Executive

I'm switching a single line of a PCI DIO 96.

Hi,
I have a PC set up with Labview 5 and Test executive 5.1. I'm trying to create a vi that can be run in test exec that will allow me to control any of the DIO lines of a PCI DIO 96. When I put the vi in a sequence and try to exit the edit screen the Test exec stops and an 'illegal operation' window appears.
I have also tryed this with the DIO example that comes with labview 'Write 1 point to digital line.vi' and the same occurs.
I hope this explains it better.
Many thanks
Rob

How can I call a LabVIEW executable from within another LabVIEW executable?

I have a customer requirement for two LabVIEW executables. Based on their current setup, they need to run executable "A" or "B", both of which are under independent revision control. I have created a third "selection" executable that allows the operator to choose between one of the two, but I am receiving errors when I attempt to call a LabVIEW executable from within a LabVIEW executable using either the "System exec" VI or the "Run Application" VI. If I call a non-LabVIEW executable (such as Windows Explorer) everything works fine.

> I have a customer requirement for two LabVIEW executables. Based on
> their current setup, they need to run executable "A" or "B", both of
> which are under independent revision control. I have created a third
> "selection" executable that allows the operator to choose between one
> of the two, but I am receiving errors when I attempt to call a LabVIEW
> executable from within a LabVIEW executable using either the "System
> exec" VI or the "Run Application" VI. If I call a non-LabVIEW
> executable (such as Windows Explorer) everything works fine.
As with the other poster, I suspect a path problem. You might try the
path out in a shell window, and if it works, copy the complete absolute
path to LV to see if that works. LV is basically passing the comma
nd to
the OS and doesn't even know what is in it, so you should be able to get
it to work.
The other poster commented on subpanels, which is a good suggestion, but
without going to LV7, an EXE can have open more than one VI. You can
use the VI Server and the Run method to fire up another top-level VI.
The decision is whether you want both to be in unique processes.
Greg McKaskle

I need information on how to install and execute the export/import utility

Hi there,
I am migrating an application from Weblogic 10 to Weblogic 10.3. I need to import a desktop from a .portal file in Weblogic 10.3. I know how to do the process of installing and executing this tool in WebLogic 10, but I don't know how to do it on the 10.3 version, because it's different and I haven't found any information about this process on the internet.
Could you please tell me what do I have to do? or give me a document that can I follow the steps from?
Thanks & Regards
Franco Utreras.

Hi Franco,
If you will post your Query in http://forums.oracle.com/forums/forum.jspa?forumID=573 (WebLogic Portal Specific Forum)...then you may get more Accurate, Quick and Experties Answers.
Thanks
Jay SenSharma
http://jaysensharma.wordpress.com (WebLogic Wonders Are Here)

(WebLogic 10.3)how to install and execute the export/import utility (xip)

Hi there,
I am migrating an application from Weblogic 10 to Weblogic 10.3. I need to import a desktop from a .portal file in Weblogic 10.3. I know how to do the process of installing and executing this tool in WebLogic 10, but I don't know how to do it on the 10.3 version, because it's different and I haven't found any information about this process on the internet.
Could you please tell me what do I have to do? or give me a document that can I follow the steps from?
Thanks & Regards
Franco Utreras.

Do you mean how to create a new desktop portal or propagation?
Creating desktop
[http://download-llnw.oracle.com/docs/cd/E13155_01/wlp/docs103/portals/creating_staging.html#wp1018386|http://download-llnw.oracle.com/docs/cd/E13155_01/wlp/docs103/portals/creating_staging.html#wp1018386]
Propagation
[Using Workshop Propagation Tool |http://download-llnw.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/propTool.html]
[Using ANT|http://download-llnw.oracle.com/docs/cd/E13155_01/wlp/docs103/prodOps/scripts.html]
AFAIK, the upgrade is pretty straightforward and I've done it before using the documentation available at [http://download-llnw.oracle.com/docs/cd/E13155_01/wlp/docs103/upgrade/upgrade_process.html#wp1065081|http://download-llnw.oracle.com/docs/cd/E13155_01/wlp/docs103/upgrade/upgrade_process.html#wp1065081]
Cappa

Problems with Labivew 2013 / 14 install - Ni Variable Engine error and Labview does not close, processes do not stop when I run Vis.

Hi All,
I am hoping at all my problems are relateded to a problem I am experancing, when I look into my windows 7 (64bit) event viewer near every time I boot up I get an error regarding the NI Variable Engine which reads.
The description for Event ID 0 from source NI Variable Engine cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
C:\Program Files (x86)\National Instruments\Shared\Tagger\ni_tagger_plugin_mxs.dll: Failure to load plugin: Unexpected Error: Unable to get the Interface from the plug-in.
and a second which is the same apart fomr the last line
Unable to load the MXS configuration plugIn: Failed to get MAX Configuration interface for Tagger: 0x80040318
I have tried uninstalling all labview things and I have tried repairing all labivew programs. Along with this I got this error when I installed Labview 2013 so I thougth why not try 2014 and I still get the same problems. I also shoudl point out I use bot 32 bit and 64 bit versions of labivew. I have installed labview on many machines before but never encountered this problem. That being said this was a new clean windows install.
Along with thiese errors labview heardly ever shuts down properly when I close the program it just freezes and needs forshed shut down.
Apart form this I noticed that when I run any of my Vis which I have never had problems with in the past and I stop the program somtiems processes keep using CPU such as "lktsrv.exe"
I really need to get this sorted out because its morstly the crushing and processes not stopping which is rather annoying.
I shoudl also say that these problems are both in the 32bit and 64 bit versions of labview not difference. and no difference if its 2013 or 2014
Cheers

Hi GajanS,
Thanks for your reply sorry I havetn noticed anybody had replied as I stopped hoping for any responce before then.
I have attached a screenshot of the four processes that seems to be giving me a problem.
I have actually managed to find the program causing labivew to crash was in fact my antivirus software which I have now removed and have no more problems with labview crashing on shutdown.
After removing it I tried the repair feature again for all my labview programs but sadly the one persistant problem remaining is still the four processes using around 13% processor each. I have found out this happens sometime after booting up regardless of if I run labivew or not. So it does not directly seem related to the running of any labview applications but rather a bug in the labview software.
the processes are:
lktsrv.exe
tagsrv.exe
nidmsrv.exe
lkads.exe
as shown in the task manager.
I would relaly help if I can get this sorted out.
Cheers
Attachments:
Screenshot 2015-03-24 21.50.00.png ‏12 KB

Installing both Vision Builder 2012 and LabView 2012 on same Computer

am new to NI Vision Builder Automation Inspection 2012 (Which I am supposed to learn and use for part inspection) as well as LabView (Which I need not know at this time)
When I was presented (to work with) a 1722 Camera and the computer, Labview 2012 was already installed but not Vision Builder.
The IT folks installed the Vision builder without uninstalling LabView.
I have my problems getting upto speed with my inspection work, but is any of it attributed to both systems being on the computer?
Can I (Must I) uninstall LaView??
Thanks

LabVIEW and Vision Builder run fine on the same computer. I have several versions of each on mine with no problems.
Bruce
Bruce Ammons
Ammons Engineering

Pda execute other exe from Labview

I'm looking for ways to execute an exe from Labview PDA that is stored on the PDA (another PDA application)... I'm running WM5.0 ... .any ideas ...
Greycat

Hey Greycat.
That is a great question! So as you noticed there is no equivalent to System Exec in LabVIEW PDA, so you cannot launch an application that way. I would think that there would be a DLL that could be called on the PDA that will allow you to launch applications. However, after several Google searches I was not able to come up with any specific code or DLLs. Once you found that DLL hoewever, you shouldn't have problems launch an EXE. I am assuming that these are not other LabVIEW PDA built EXEs, which is a shame since you might be able to open a VI reference to that VI.
Andy F.
Message Edited by Andy F. on 04-25-2006 06:52 PM
National Instruments

Installing Test Executive 5.0 in LabVIEW 6.0.2

Similar Messages

Maybe you are looking for