Test Stand Evaluation

Hi.
I would like to get some feedback regarding using Test Stand with Labview.
Currently I am using Delphi Interface as my Excecutive Engine and Active
X server to communicate with labview. The data logging, PLC I/O and Login/logout
are part of Delphi Inteface. The labview is used only to execute the actual
test. Now by switching to Test Stand, would that benefit me in any way.(For
instance: Does Test Stand(LV Server) allows me to run single or multiple
Vi's, without creating 'exe')?

There could be lots of advantages to switching to TestStand, but it depends on your application.
1. If you deploy your applications to several different environments or uses (board test, system test, service, field service, etc.) then TestStand allows you to customize different "process models" for each environment. The actual test code is contained in a sequence file. Since the process model is shared by all sequence files, it is a great place to put the common functions such as UUT identification and data logging. Even if you don't need different process models, keeping all this code in one place makes it easier to maintain. There is no compiling with TestStand, so you can change the process model and the changes will take effect in all your applications.
2.
TestStand allows you to easily call many different types of code, not just Labview. You can call CVI, DLL's, EXE's, and ActiveX. I recently saw an article about a way to call Perl code. Again, the value of this depends on your application.
3. If you want to integrate your application with a database, TestStand has great database tools. The database logging utility allows you to log data to any table format.
4. If you are loading test limits from an external source, TestStand makes it easy with a tool called Property Loader.
I suggest you get a free demo copy and try it out. TestStand is incredibly powerful.
Mark ([email protected])

Similar Messages

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

Integrate Vision Builder 2009 (VBAI), into Test Stand 4.2.1?

Does anyone know of an easy way to integrate Vision Builder 2009 (VBAI), into Test Stand 4.2.1?
earlier versions of Vision Builder seem to accomidate this very easily. But i have not found the same ease to make this work in the newest version. any ideas?
Thanks

Hi,
Thanks a lot for your support.
Well...yes I followed the instructions in the ReadMe.html file.
I have loaded the sequence "Vision Builder AI TestStand Examples.seq" into TestStand.
TestStand crashes after some delay when trying to select the first test step "Run Inspection once".
TestStand obviously has problems loading the Vision Builder API functions and the engine (whatever is necessary).
As I could not succeed testing VBAI 2010 from TestStand, I then tried the LabVIEW example which is also located
in the \examples folder.
I had no problems loading the "LabVIEW API Examples (Local).vi" into LabVIEW 2010 and execute it.
This example works without any problems with a simple USB Webcam.
I can test different "Inspections" and studied the API functions in this VI.
So the problem is only related to TestStand.
I am wondering whether TestStand has problems with the evaluation version of VBAI 2010.
When executing the LabVIEW example the VBAI engine asks me first if I want to evaluate the software (as it is not activated yet).
I never reach this point from TestStand. It crashes before.
Another point is that I am asking myself why the test step "Run Inspection Once" is the first test step the TestStand sequence.
Comparing the sequence of steps with the LabVIEW VI, you can see that there is a differnce in the initialisation sequence.
The LabVIEW VI launches "VBAI Interface - Launch VBAI Engine.vi" first before all other API VIs.
I could try to change the TestStand sequence and introduce additional initialisation steps before "Run Inspection Once".
I simply fear that TestStand crahses again before I have been able to change the sequence.
Ok...another thought...on your system it is working fine using the example TestStand sequence?
This means that the initialisation of the VBAI engine is automatically executed.
Which process is responsible to initialise the VBAI engine in TestStand?
Perhaps I have to configure something ...somewhere in TestStand.
Ok... that's it for now... i will try out a couple of things....
Thanks again for your support
Best regards,
Carsten

Redownload test stand 4.2

How do I redownload test stand 4.2. All that is available on the site is TS2010.
I am trying to build a driver deployment package and it error on build saying it can't find the install files. I had removed the install folder a while ago.
Thanks
Brian
Solved!
Go to Solution.

ftp://ftp.ni.com/evaluation/teststand/pc/

Is there a way to create a database with Test Stand?

Anyone know of a way to have Test Stand create a database? My company standard MS Office suite is Microsoft Access 2010, and TestStand does not support the .accmdb extension type(format), so I have to create new databases using old formats. I'm worried about backwards compatability down the road since good ole Microsoft doesn't seem to care about legacy formats.
I'm still a beginner with databasing, so any suggestions would be greatly appreciated.

TestStand 2012 SP1, and we are using a modified Generic Recordset (NI). The problem we are having right now is that the Build SQL instructions are not creating the database tables the way we are configuring them from the "Statements" and "Column/Parameters" tabs under Database Options.
What is happening is when we validate the schema, and drop all schema tables, it empties all the database tables, but then when you build using the TestStand generated sql file, we get errors(shown below) we are not understanding, and we can no longer write to the database and LabVIEW throws a "Data type mismatch in criteria expression" error like this
"Possible reason(s):
ADO Error: 0x80040E07
Exception occured in Microsoft JET Database Engine: Data type mismatch in criteria expression. in NI_Database_API.lvlib:Conn Execute.vi->TSData - Query Actions.vi->Retrieve Test Data.vi->ARA-63 Data Miner.vi->ARA-63 Data Miner.vi.ProxyCaller"
==================================================================================================== > CREATE TABLE UUT_RESULT ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, STATION_ID VarChar(255), BATCH_SERIAL_NUMBER VarChar(255), TEST_SOCKET_INDEX Long, UUT_SERIAL_NUMBER VarChar(255), USER_LOGIN_NAME VarChar(255), START_DATE_TIME DateTime, EXECUTION_TIME Double, UUT_STATUS VarChar(32), UUT_ERROR_CODE Long, UUT_ERROR_MESSAGE VarChar(255), PART_NUMBER VarChar(255), TSR_FILE_NAME VarChar(255), TSR_FILE_ID VarChar(64), TSR_FILE_CLOSED Bit, PART_NAME VarChar(255), PRG VarChar(255), Comment VarChar(255), Operator VarChar(255)) Command issued.
> CREATE TABLE STEP_RESULT ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, UUT_RESULT Long, STEP_PARENT Long, ORDER_NUMBER Long, STEP_NAME VarChar(255), STEP_TYPE VarChar(255), STEP_GROUP VarChar(32), STEP_INDEX Long, STEP_ID VarChar(32), STATUS VarChar(255), REPORT_TEXT VarChar(255), ERROR_CODE Long, ERROR_MESSAGE VarChar(255), CAUSED_SEQFAIL Bit, MODULE_TIME Double, TOTAL_TIME Double, NUM_LOOPS Long, NUM_PASSED Long, NUM_FAILED Long, ENDING_LOOP_INDEX Long, LOOP_INDEX Long, INTERACTIVE_EXENUM Long, CONSTRAINT STEP_RESULT_FK FOREIGN KEY (UUT_RESULT) REFERENCES UUT_RESULT (ID)) Command issued.
> CREATE TABLE STEP_SEQCALL ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, STEP_RESULT Long, SEQUENCE_NAME VarChar(255), SEQUENCE_FILE_PATH LongText, CONSTRAINT STEP_SEQCALL_FK FOREIGN KEY (STEP_RESULT) REFERENCES STEP_RESULT (ID)) Command issued.
> CREATE TABLE PROP_RESULT ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, STEP_RESULT Long, PROP_PARENT Long, ORDER_NUMBER Long, NAME VarChar(255), PATH LongText, CATEGORY Long, TYPE_VALUE Long, TYPE_NAME VarChar(255), DISPLAY_FORMAT VarChar(32), DATA Double, FORMATTED_DATA VarChar(255), CONSTRAINT STEP_NUMERICLIMIT1_FK FOREIGN KEY (STEP_RESULT) REFERENCES STEP_RESULT (ID)) Command issued.
> CREATE TABLE PROP_NUMERICLIMIT ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, PROP_RESULT Long, COMP_OPERATOR VarChar(32), HIGH_LIMIT Double, LOW_LIMIT Double, UNITS VarChar(255), STATUS VarChar(255), HIGH_LIMIT_FORMATTED VarChar(255), LOW_LIMIT_FORMATTED VarChar(255), CONSTRAINT STEP_NUMERICLIMIT2_FK FOREIGN KEY (PROP_RESULT) REFERENCES PROP_RESULT (ID)) Command issued.
> CREATE TABLE PROP_RESULT ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, STEP_RESULT Long, PROP_PARENT Long, ORDER_NUMBER Long, NAME VarChar(255), PATH VarChar(255), CATEGORY Long, TYPE_VALUE Long, TYPE_NAME VarChar(255), DISPLAY_FORMAT VarChar(32), DATA VarChar(255), FORMATTED_DATA VarChar(255), CONSTRAINT PROP_MULTINUMERICLIMIT1_FK FOREIGN KEY (STEP_RESULT) REFERENCES STEP_RESULT (ID), CONSTRAINT PROP_MULTINUMERICLIMIT1_FK FOREIGN KEY (PROP_PARENT) REFERENCES PROP_RESULT (ID)) Command failed with the following error...: Table 'PROP_RESULT' already exists. (-2147217900)
> CREATE TABLE PROP_NUMERICLIMIT ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, PROP_RESULT Long, COMP_OPERATOR VarChar(32), HIGH_LIMIT Double, LOW_LIMIT Double, UNITS VarChar(255), STATUS VarChar(255), HIGH_LIMIT_FORMATTED VarChar(255), LOW_LIMIT_FORMATTED VarChar(255), CONSTRAINT PROP_MULTINUMERICLIMIT2_FK FOREIGN KEY (PROP_RESULT) REFERENCES PROP_RESULT (ID)) Command failed with the following error...: Table 'PROP_NUMERICLIMIT' already exists. (-2147217900)
> CREATE TABLE PROP_RESULT ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, STEP_RESULT Long, PROP_PARENT Long, ORDER_NUMBER Long, NAME VarChar(255), PATH VarChar(255), CATEGORY Long, TYPE_VALUE Long, TYPE_NAME VarChar(255), DISPLAY_FORMAT VarChar(32), DATA VarChar(255), FORMATTED_DATA VarChar(255), CONSTRAINT PROP_RESULT_FK FOREIGN KEY (STEP_RESULT) REFERENCES STEP_RESULT (ID)) Command failed with the following error...: Table 'PROP_RESULT' already exists. (-2147217900)
> CREATE TABLE PROP_ANALOGWAVEFORM ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, PROP_RESULT Long, INITIAL_T DateTime, DELTA_T Double, INITIAL_X Double, DELTA_X Double, UPPER_BOUNDS VarChar(32), LOWER_BOUNDS VarChar(32), DATA_FORMAT VarChar(32), DATA LongBinary, ATTRIBUTES LongText, CONSTRAINT PROP_ANALOGWAVEFORM_FK FOREIGN KEY (PROP_RESULT) REFERENCES PROP_RESULT (ID)) Command issued.
> CREATE TABLE PROP_DIGITALWAVEFORM ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, PROP_RESULT Long, INITIAL_T DateTime, DELTA_T Double, UPPER_BOUNDS VarChar(32), LOWER_BOUNDS VarChar(32), TRANSITIONS LongBinary, DATA LongBinary, ATTRIBUTES LongText, CONSTRAINT PROP_DIGITALWAVEFORM_FK FOREIGN KEY (PROP_RESULT) REFERENCES PROP_RESULT (ID)) Command issued.
> CREATE TABLE PROP_ANALOGWAVEFORM ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, PROP_RESULT Long, INITIAL_X Double, DELTA_X Double, UPPER_BOUNDS VarChar(32), LOWER_BOUNDS VarChar(32), DATA_FORMAT VarChar(32), DATA LongBinary, ATTRIBUTES LongText, CONSTRAINT PROP_IVIWAVE_FK FOREIGN KEY (PROP_RESULT) REFERENCES PROP_RESULT (ID)) Command failed with the following error...: Table 'PROP_ANALOGWAVEFORM' already exists. (-2147217900)
> CREATE TABLE PROP_ANALOGWAVEFORM ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, PROP_RESULT Long, INITIAL_X Double, DELTA_X Double, UPPER_BOUNDS VarChar(32), LOWER_BOUNDS VarChar(32), DATA_FORMAT VarChar(32), DATA LongBinary, ATTRIBUTES LongText, CONSTRAINT PROP_IVIWAVEPAIR_FK FOREIGN KEY (PROP_RESULT) REFERENCES PROP_RESULT (ID)) Command failed with the following error...: Table 'PROP_ANALOGWAVEFORM' already exists. (-2147217900)
> CREATE TABLE PROP_BINARY ( ID COUNTER CONSTRAINT TABLE_CONSTRAINT PRIMARY KEY, PROP_RESULT Long, UPPER_BOUNDS VarChar(32), LOWER_BOUNDS VarChar(32), DATA_FORMAT VarChar(32), DATA LongBinary, CONSTRAINT PROP_BINARY_FK FOREIGN KEY (PROP_RESULT) REFERENCES PROP_RESULT (ID)) Command issued.

How to bring a VI front panel to the front (of all open windows) when the parent VI calls a sub-VI in Test Stand.

In Test Stand when I call a sub-VI front panel, the pop-up window goes behind all the windows and the user just waits for the screen. I want the pop-up to come to the front so that the user can know what to do. I couldn't find any property that I can set which would make the called VI go to the front.

What version of TestStand are you using? Here are the TestStand palettes in LabVIEW for TestStand 2.0 and 3.1. You can also set a VI to be modal in VI Properties>Window Appearance. Select Dialog or go to Cutomize and change the Window Behavior.
Message Edited by Dennis Knutson on 03-07-2006 10:32 AM
Attachments:
TestStand palettes.JPG ‏37 KB

I want to write a program in LabView then pass the test results to teststand to check if it pass or fail without displaying the test stand program,

I want to write a program in LabView and create an execute but I want to be able to pass test results to test stand to find it the unit pass ar fail the test then save the data to a database. How would i go about it.

What's confusing is your statement that you want to do this "without display the test stand program". You can minimize the TestStand UI to the task bar but if you don't want TestStand to be running, how can TestStand evaluate the result. Explain a little more please.
In the message body of your post, you just say you want to create a LabVIEW exe and pass the results to TestStand. What I would recomend is that instead of an exe, you create a dll and use TestStand's DLL adapter to call it and return the results. TestStand will evaluate it and do the logging.

Test Stand 3.5 install problem

I'm having problems installing Test Stand 3.5 Development Edition on a WinXP SP1 machine - would anyone have any suggestions.
I'm performing a custom install and selecting all components other than "Device Drivers".
The install fails on "NI TestStand 3.5 Support Files. Part 1 of 1" with "Error 1335. The cabinet file 'Cabs.m6' required for this installation is corrupt and cannot be used. This could indicate a network error, an error reading from the CD-ROM, or a problem with this package".
If I select abort at this point the install of the support files is rolled back and the remaining components apper to install correctly. I can now run Test Stand but am missing the help files. If I rerun setup it attempts to install the support files but fails with the same error.
I have tried uninstalling and reinstalling & have copied the CD contents to the local hard disk (without any problems) and installing from there. All this is to no avail.
I've also uninstalled and reinstalled an installation on a second machine using the same install media. This install succedded with no issues.

What is the difference between the two machines - where you've had successful and unsuccessful installs?
Like you've said sometimes this is caused by a faulty read from the CD drive, or faulty media, but as you've managed the install with the same media on the machine - then its not the media, and you've already tried the copy to hard disk from the CD without any luck.
What OS is on this other (working) machine?
Do you have administrator privileges on the machine where you can't install the software? Is the .NET framework 1.1 installed (I think this is part of Windows XP SP 2) so this could be the issue - as TestStand requires the .NET framework 1.1
Also - I've attached the readme which includes information to consider before installation - and known issues with the installation - check this and see if any of these could be the issue with this machine.
I hope this helps
Regards
Hannah
NIUK & Ireland
Attachments:
ReadMe.txt ‏51 KB

Is there a max number of parameters that can be passed to a C function in test stand v. 1.0.1

I have had an issue with test stand version 1.0.1 (yes, I know; it's quite old) and calling a C function thru an action step. when I call this function with 18 parameters, it seems to hang. I have called a function with 16 and it seems to work. Is this a limit of the software? I am calling the function from a windows DLL that we've created. When I try to pull the function from the dll into test stand I also get a { error...but I get that in the other function's call and it seems to work fine. Any ideas?

ok, upon re-reading what I posted I can clearly see your confusion. haha. I think there are two separate issues.
1) Are there a maximum number of parameters one can use when calling a C function from a DLL? Yes, i'm trying to call a C function from test stand.
2) when I select the "module" tab, and select which DLL contains my function, the prototype has no information associated with it (by clicking the reload prototype button). I'm not sure why, as I'm using a declspec to send the function information out of the dll, but that's another topic. So I click on the source file tab and point the window to the .cpp of my function (within the DLL's project workspace) and when it begins to parse the file, I get an error about mis-matched curly brackets and if I wish to continue, and skip the rest of the parsing.
I click "OK" and when I go back to the module tab, I am able to see all my functions, along with the parameters in the drop down menu below. I fill in all the parameters and everything looks ok; no syntax errors, or anything else seemingly suspicious. I then run my test stand code and when I get to the step which calls this function, the system hangs and cannot proceed.
Any thoughts as to what might cause these issues?

How to get the value of the global variable of test stand in labview User interface?

Hi.
Can anyone Please share examples and tell me to how access the test stand global variable using labview user interface.
Solved!
Go to Solution.

I'm not surprised that what you are doing doesn't work. The Start Execution UI Message is triggered when the user clicks a button to start an execution. Realize that most executions go through a process model. So you could be looking at the sequence context of the process model and not your client sequence file.
I recommend reading that link I posted above. UI Messages are your best bet but you cannot just piggy back on an existing UI Message like this. They may not be getting sent at the time you need them to be. The only way to ensure you get what you want is to trigger one yourself at the right time.
Regards,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

How to call test Sequences developed by using CVI Test Execuitve toolkit in Test Stand?

There is a feature in TestSatnd which can convert CVI sequence to test Stand Sequences. But test stand is not recognising these sequences saying " not a valid CVI test sequence". Is there any version Issues, while converting these sequences to TestStand?

Hi Scott
In continuation of previous question..
As per the suggestion, when I am trying opening one sequence(.SQU) file,developed in CVI Test Executive V 1.0.1., in CVI Test Execcuitve V 2.0.1, Executive is throwing error.
The Pop Error is " Section [Sequence] missing from sequence file c:\xxx.squ"..
and when I am trying opening these sequence file in sequence editor, the tool it self is crashing.
Please suggest!!
Is there any specific tokens which we need to add in .SQU files of V 1.0.1, so that V 2.0.1 can understand them? Just to check the possibility of manual updation of .SQU files.
Regards
Amit

Vi session strategy with LV 7 in Test Stand

Hi all, Im a producing a set of vi's(LV7.1) which will be strung together in a Open Visa, Write visa ..., Read visa , Close visa, over several instruments.
I wish later to use Test Stand(3.1) to slice these routines, but I am not sure how test stand handles the session references when I break the flow.
Im thinking of a first step that initialises all instruments , then later steps that grab the session references and perform tests.
Do I need to store the sessions as varables in Test Stand?, or is there a better way?.Is there any examples that cover this topic?
thanks

I guess that a better way is NI Session Manager.
NI Session Manager is the software component (of NI TestStand) from which you obtain instrument sessions. Session Manager returns a reference to the session object with the name you specify. If the session object you specify does not yet exist, Session Manager creates it and returns a reference to the new session.
Session Manager also allows you to close all opened sessions automatically.
"Only a life lived in the service to others is worth living..." - Albert Einstein
Attachments:
SMgrRef.chm ‏121 KB

Is there any way I can convert a Test stand sequence and corresponding vi's to an executable?

I need some creative ideas on how I can convert a test stand sequence into an executable in the shortest possible time. I know that beats the entire purpose of using TestStand but I need to have a way to do this. Is there no other way i can accomplish this without writing a sequencer in LabVIEW and rewriting all of my code in LabVIEW??

There is no way i know or can think of to move all components from a TestStand application into a single EXE. Running TS in an application means that you should/must work highly unitized during developement and deployment.
In general:
-> Custom UI will become "The EXE" for the enduser. This involves the link for startup on desktop/start menu.
-> TS Engine, ActiveX Server, will be attached to the UI.EXE OS process when launched by the UI. Will never be part of the UI.EXE.
-> TS Compontens (e.g. process model, language files, ..). Will never be part of the UI.EXE.
-> Custom Components (e.g. modified process model components, reporting, ...). Very unlikely(never) to become part of the UI.EXE.
-> Custom Sequences. Will never be part of the UI.EXE, but extension can be changed to other than .seq.
-> Code modules called by custom sequences. Unlikely (but possible) to be part of the UI.EXE. Should be implemented and tested to run within the RTE (runtime engine) of the appropriate programming language. It is not par design, that the deployment system has the development environment of that programming language installed.
-> License information. TS requires at least the Base Deployment License installed and activated (requires NI License Manager software). RTE of modules might also include licensing and possibly activation fees.
Why is there the requirement to have a single, monolythic EXE (hard to handle!) at all? If it is about the deployment process, you know that you can provide a single MSI (Microsoft Installer) with all required components using the TestStand Deployment Utility?
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

How can I get Test Stand to print failues only?

Rather than getting a large report file with hundreds of passes and only one failure, how do I configure Test Stand to only print the failures to the report?

Hi,
the engine callbacks are simply a sequence that gets called when a particular thing happens (i.e. Post Step).
There's three types
SequenceFile (for steps that execute in that sequence file whether it's a client sequence file or a process model)
ProcessModel (for steps that execute in the client sequence file run under this process model, but NOT the steps in the ProcessModel)
Station (for all steps on that installation - found in the StationCallbacks.seq sequencefile)
If the engine callback appears in more than one of the three places, then the lowest one (seq file->proc model->station listed lowest to highest)is used.
In your case, you could use any of them depending on your architecture.
Personally, r
emoving from the resultlist is easier than working out whether to add to it, but that gets tricky when you have steps which loop.
If you decide to make up your own add, then the PostStepFailure is the callback sequence to use (go to edit->sequencefilecallbacks). You'll have to add a new element to the resultlist, and start fleshing it out with the result container of the step (which you still have access to as a parameter) plus the TS container.
This would go into the Runstate.Caller.Locals.ResultList[x]
Also, don't forget to disable the result collection on all the steps in the test sequence, plus all the ones in your poststepfailure callback, since you're doing your own.
I'm attaching what I've done so far as an example - not quite finished, but it's done the TS container. Just now need to do the actual result container.
I'll keep working on it but for now you can see what I'm getting at.
Hope that gives you a kick start with the callbacks bit
Sacha Emery
National Instrumen
ts (UK)
// it takes almost no time to rate an answer
Attachments:
collect_only_failures.seq ‏31 KB

Can I open the (.squ) sequence files using NI test stand 4.0 version?

I have the sequence files created using ATETool Kit test Executive. But I have NI 4.0 test stand. I want to open the sequence files using NI 4.0 test stand. Can i do that?

Hi,
I am not familiar with ATETool kit Test Executive, but I doubt NI TestStand will open this. As you have both, have you tried it?
TestStand does have a conversion tool for converting NI TestExecutive sequence files into TestStand sequence files.
Maybe you could write a conversion tool to make the conversion for you if you have many ATETool kit Test Executive files.
Regards
Ray Farmer
Regards
Ray Farmer

Test Stand Evaluation

Similar Messages

Maybe you are looking for