Open Test Executive

I'm in need of a test executive but I don't want to buy Teststand
because I think it is too expensive and will be over-kill for what I
want to do. Does anyone know of or has created a test executive they
could share with me?

look at the Test Sequencer.vi in the example finder
- James
Using LV 2012 on Windows 7 64 bit

Similar Messages

Can't open an Executable From Click Button

Hi, Everyone!
I've broken a learning module into several small project
files to match the client's standards. I've set up click buttons
within each file to open each of the published movies for the
module. Everything works as expected.
Now I need to create a standalone course using the same
files. I've published each file as a Standalone executable. I've
modified the open action on the click buttons to "Open URL or File"
and selected the appropriate .exe file as the target. I've
republished the files with the new click action. When I open an
executable and click a button to open another executable, I get an
error message stating that the page cannot be displayed.
What am I doing wrong? Can anyone help?
Thanks,
Bob Browne

Hi Bob
For starters, did you try simply exporting all related files
as .EXE files and test that way before making any changes? If so,
what were your results? I've seen before where once Captivate was
successfully linking to another movie, simply changing from .SWF to
.EXE format just worked.
Just a thought... Rick

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

What role is required to open and execute query in BE query designer

Hi,
Am new to BE, need to know what role should i be assigned with to open and execute a query in query designer.
OPEN dialobox displays "NO role availabe".
Is this a problem of role assignment or am i missing some steps
thanks
srikanth

IN Enterprise portal plz check whether these roles are present or not.
pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/Roles/com.sap.ip.bi.business_explorer_showcase
pcd:portal_content/com.sap.gm.cnt/core/VCRole
pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/Roles/com.sap.ip.bi.bi_showcase
pcd:portal_content/administrator/content_admin/content_admin_role
pcd:portal_content/com.sap.pct/platform_add_ons/com.sap.ip.bi/Roles/com.sap.ip.bi.business_planning_showcase
pcd:portal_content/every_user/general/eu_role
in BW front end , you have to create role with the auth objects S_RS_COMP, S_RS_COMP1, S_RS_MPRO, S_RS_ICUBE auth objects.
include the t-codes if necessary. RSRT you can include.
Hope this would help you.

Opening unix executable files

What application in Leopard can I use to open unix executable files?

It seems to be a file type that is given to any file (of any sort) that has had its Execute permission set. Plain text, TIFF and font files are all showing this oddness.
You can open them via the right (command) click context menu for the file and use Open with, or use GetInfo in the same menu to set the opening program, provided you know what sort of file it's likely to be.
You can remove the Execute permission using the Unix chmod command in the Terminal, but a simpler solution is to install the FileUtilsCM context menu (free) from http://www.abracode.com/free/cmworkshop/file_utils.html
See thread http://discussions.apple.com/thread.jspa?messageID=6125826&#6125826 for related info.
DN
Message was edited by: dcnicholls

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.

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

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

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

Test executive and Test stand deployment cost

Hello,
would some NI support engineer kindly answer below questions ? i would be obliged.
we have been running customized Test executive built from Test executive toolkit. We are now making decision as to whether We should migrate to test stand or keep the existing structure? Here are some questions:
1) in case We switch to test stand, do We still need to buy runtime engine license ?
2) can we call executables in Test stand ?
3) stating from ground zero, what is the deployment cost estimate between Test stand and customized test executive scenarios, from end user point of view ?
-Ahmed

Hi Ahmed,
To answer your questions:
1) You will need to have a deployment (runtime) license for all the machines that you plan on running your application on. However, you will only need a full development license for the computer that you are actually developing the application on. You can see a full explanation of the different types of TestStand license in the document "When Should I Purchase a License for my TestStand System?"
2) In regards to calling executables, TestStand has a builtin step to call executables making it extremely easy to do. You can download an evaluation copy of TestStand here to see how easy it is to use as well as see the simple Call Executable Step.
3) In regards to price comparison between TestStand and a customized test application, this really depends on the project. Each project can have a different cost. However, you can take a look at this cost analysis to get a general idea of one example of cost comparison. This is just an example and also compares an older version of TestStand.
For more specific information about cost, please contact a sales representative at (888) 280-7645.
Thanks,
Caroline Tipton
Data Management Product Manager
National Instruments

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

Coverting an application from test executive to test stand.

I have used LabWindows CVI and the "test executive" toolkit to develop production test applications. The production operators who use the programs like the look and feel of the interface.
I want to convert to Test Stand so that I can support solutions written in languages other than CVI. How do I modify the test stand user inteface so that I get an identical operator interface?

Hi Tom,
You can also convert your CVI test executive sequence files into Teststand sequence files. Under the Tools menu in the TS Sequence Editor you will find a wizard that performs the task for you. It will take the CVI callback functions and generated the equivilant TS Callback sequence calls. You may still have to make some manual changes, but you wont have to completely regenerate your original test sequences from scratch.
Regards
Ray Farmer
Regards
Ray Farmer

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

Windows Powershell and HP Open Test Architect (TDApiOle80)

I'm not sure that this is the correct forum to place this in. Please feel free to move it if needed...
I have a task to create a new script using powershell and the OTA. When trying to log into quality center via the open test architecture in powershell I get this error.
At my computer char:22+ $td.InitConnectionEx $qualityCenterLink+ ~~~~~~~~~~~~~~~~Unexpected token '$qualityCenterLink' in expression or statement.
At my computer char:11+ $td.Login $qualityCenterUsername, $qualityCenterPassword+
~~~~~~~~~~~~~~~~~~~~~~
This is the code that I am using.
$td = New-Object -ComObject "TDApiOle80.TDConnection"
$td.InitConnectionEx $qualityCenterLink
$td.Login $qualityCenterUsername, $qualityCenterPassword
This code currently works in a script written with VBscript. I am just modifying the td variable to use powershell instead of vbscript. Do you all have any idea what it is that is causing this not to run? Also, Is powershell compatible with the OTA? I am assuming
so only because the OTA is a COM package.

it appears it doesn't like the formatting. It doesn't know how to handle the varibles
Powershell thinks thinks these are 2 variable next to each other
$td.InitConnectionEx $qualityCenterLinkmaybe put $td.InitConnectionEx($qualityCenterLink)$td.Login $qualityCenterUsername, $qualityCenterPasswordPowershell thinks thinks these are variable next to each other, with a comma separating two of themmaybe put $td.Login ($qualityCenterUsername, $qualityPasswrod)Maybe you can do $td | get-member, may that will show you how the arguments should look. I have neverused the OTA, just guessing here.

How to find open query executed once on SQL server

Hi Experts ,
Is there any way to identify that open query executed once on Db server using any DMv's ? we are planning enabale opimized for ad-hoc queries on SQL server ?
Shivraj Patil.

Hi,
You can use below query to find the plans that have been used only once.
SELECT text, cp.objtype, cp.size_in_bytes
FROM sys.dm_exec_cached_plans AS cp
CROSS APPLY sys.dm_exec_sql_text(cp.plan_handle) st
WHERE cp.cacheobjtype = N'Compiled Plan'
AND cp.objtype IN(N'Adhoc', N'Prepared')
AND cp.usecounts = 1
ORDER BY cp.size_in_bytes DESC
OPTION (RECOMPILE);
additionally you can also refer below articles.
http://sqlmag.com/database-performance-tuning/sql-server-plan-cache-junk-drawer-your-queries
Plan cache and optimizing for adhoc workloads
Please mark solved if I've answered your question, vote for it as helpful to help other users find a solution quicker
Praveen Dsa | MCITP - Database Administrator 2008 |
My Blog | My Page

Open Test Executive

Similar Messages

Maybe you are looking for