Clearing Test Stand engine's internal cache

I am trying to clear the TEST STAND ENGINE'S internal cache of past sequence files in a custom Operator Interface I am developing using VB.NET. The scenario is as follows. The Test Stand OI application is instantiated from a desktop shortcut that also has the sequence file as a parameter. I am using only the "Single Pass" entry point.
The problem is other sequence files appeared to be executing in addition to the sequence file passed in as a command line argument. I checked this by creating an event handler for the openseqfile event and putting a VB.NET debugger breakpoint at its start. In the case I checked the seq open event fired 3 times. Once for each of the last 3 different sequence files I tried to run. I checked each of the files as they were being opened and the 1st file opened was the one I passed in. The second file opened was the one I ran prior to the current application instantiation. I checked that file an the "e.file.IsExecuting" property was TRUE! How could that file be executing when the application starts when it is not even the file I want to run?
The third file was a file I ran 2 instances ago and its "IsExecuting" property was false and its "CanUnload" property was true. I was able to remove that particular file with "Me.AxApplicationmgr.GetEngine().ReleaseSeqenceFileEx(e.file)" in the event handler.
What is the proper way to remove (clear) the interneal cache. So only the single file I want is opened? Thanks

You should call ApplicationMgr.OpenSequenceFile instead of Engine.GetSequenceFileEx (see TestStand Reference Manual>> Chapter 9 Creating and Customizing Operator Interfaces >> Using the TestStand API With TestStand UI Controls).
If you want to close the file explicitly, call ApplicationMgr.CloseSequenceFile. If you don't close the file, the ApplicationMgr will close the file automatically when your application shuts down.
When you call ApplicationMgr.OpenSequenceFile, the file appears in controls that display the list of open files and your application receives an ApplicationMgr.DisplaySequenceFile event for the file.
If you can't use the ApplicationMgr methods, then I think the place to call Engine.ReleaseSequenceFileEx would be in the ApplicationMgr.QueryShutdown event (also see TestStand Reference Manual>> Chapter 9 Creating and Customizing Operator Interfaces >> Using the TestStand API With TestStand UI Controls).

Similar Messages

Test Stand: TestStand Engine Process

I'm looking into an application (written by someone else of course) which calls a "Test Stand Engine" to execute a test.
First thing is what is this "Test Stand Engine" ?
I have been using Test Stand GUI (Test Stand Sequence Editor) to execute such test cases in the past so I never knew what do they mean by Test Stand Engine.
The problem i'm looking into is simple.
They say that Test Stand Engine is being executed as part of a thread and my task is to make it execute in a process.
But I Can't find the actual call to test stand engine itself.
I'm on Windows box and all I can see in Task Manager => Process is TSAUTO~1.EXE which is same whether I run GUI or my application with Test Stand Engine.
What should I look for in my application code to find the "Test Stand Engine"?
Any Help?
Nirvana

Hi,
just to clarify that - there's two approaches to making an operator interface with TestStand.
1) Use the TestStand UI controls and manager controls or 2) Go directly to the TestStand Engine.
Option 1 actually overwraps the calls to the TestStand Engine anyway to make it easier to implement an operator interface. That's not to say that going directly to the TestStand Engine ActiveX automation server is difficult, but you have to do certain things, like shutting down in a sepcific way.
Your best other resource is the TestStand help (rather than the bookshelf pdf's) and have a look at the topic about "Writing an application with the teststand engine"
As Dennis says - you might get more help on the TestStand forums rather than the LabVIEW ones though.
Thanks
Sacha Emery National Instruments (UK)
Message Edited by SachaE on 02-22-2007 10:26 AM
// it takes almost no time to rate an answer
Attachments:
teststandHelpSection.JPG ‏55 KB

How To Trigger Test Stand To Assign Step = Error

Hi everyone, I have a LabVIEW VI step in my sequence and I have an abort button the user can select to abort the user interface VI. I want the "abort button" boolean to pass back to test stand that abort button = TRUE and I want the sequence step to be set to an "ERROR." Is there a command to send to the Test Stand Engine to flag this step as an error?
Thanks so much!
Solved!
Go to Solution.

Hi
Glad It was helpful.
There are two ways in which you could achive this..
1. Use this expression: RunState.Engine.TerminateAll()
But be wary, this will terminate all the current excutions and the report indicates the status as "terminated"
or
2. Use this expression: RunState.Execution.Terminate()
or
3. You can add a Goto step (comes with teststand. You can find it under Flow Control section of the insertion palette) and select Cleanup as the destination step.
This way you can run some clean up steps before closing the execution. (eg, Shutting down any hardware, etc.,)
Deepak

Test Stand Deployment; Internal Error Code 1

Hi,
I get the following message from the deploymeny tool when trying to deploy my system...
Internal error code 1 Processing VIs...
An installer was not created due to an error
I have mass compiled everything and all the VIs are working, my workspace processes okay and the sequences run okay in the Run time Engine adaptor of Test Stand.
Any ideas what could be causing this? I have Test Stand 4.0.0 and labview 8.5.
Many thanks
Matt

Hi Rick, see below cut and paste from this file, does this help?
08:55:43tarting Log.
08:55:45tarting Analysis
08:55:45tarting to process workspace file
08:55:56one processing workspace file
08:55:56:Finished Analysis
08:55:57:Building...
08:55
08:57:01:Internal error code 1 Processing VIs...
08:57:01:Could not process LabVIEW VIs. Fix any broken VIs before rebuilding. LabVIEW error:
Error copying files.
Source:
Destination: <Not A Path>
Librarian Path Location.vi
<Call Chain>Error 1 occurred at ABAPI Dist Copy Non-VI Files.vi -> ABAPI Dist Build LLB Image.vi -> ABAPI Copy Files and Apply Settings.vi -> TestStand - Build VI Distribution 8 AX Wrapper.vi -> TestStand - Build VI Distribution 8 AX Wrapper.vi.ProxyCaller
Possible reason(s):
LabVIEW: An input parameter is invalid. For example if the input is a path, the path might contain a character not allowed by the OS such as ? or @.
=========================
NI-488: Command requires GPIB Controller to be Controller-In-Charge.
08:57:01:An installer was not created due to an error
08:57:01:The build is finished
08:57
08:57:01:Aborted
08:57:01:---------------------------------------
Many Thanks
Matt

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.

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?

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

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])

Error when closing test stand

when i try to close test stand after i run a test, i got the error in the
attached file.
this error appear only if i dont close the sequence file before i exit test
stand and only after i run a test.
please help me.
advanced thank's.
[Attachment error.jpg, see below]
[See first answer for additional information]

Hello Avi,
The error is caused by TestStand not being able to finish the LoginLogout sequence before its time limit. These limits are set under Configure >> Station Options >> Time Limits. They will allow you to interrupt a sequence that is taking too long to shut down.
The real problem may be in the LoginLogout sequence, in the file \Components\User\Callbacks\FrontEnd\FrontEndCallbacks.seq (or substitute "NI" for "User" in the path). If something in that sequence doesn't finish executing within 10 seconds, due to an extreme slowdown or a problem with the sequence, you will see this error. If you have modified that sequence, this could be the cause. You will need at least two steps in the sequence, one for Login and another for Logout. They should
reference frontend.dll. If you have a modified callback in your User directory, trying copying the default callback from the NI directory.
Also, make sure that you complete or terminate other sequences before trying to close TestStand, or you will see a similar error message.
Good luck and feel free to ask if you have further questions.
Steven Reasoner
Applications Engineering
National Instruments

What is test stand ? Why is it used, how to get going ?

Hello All,
I am LabVIEW user and very new to test stand, have few basic questions,
1. Why teststand was introduced ?
2. In LabVIEW we write VI's and build a project to execute a big task, how is this done in teststand?
3. I did download some of the pdf from NI website, but not able to visualise what needs to be done,
Pls do share if you have more insight to Teststand.
Thanks

Hey systemcrash,
I will try and answer your questions the best I can:
1. http://www.ni.com/teststand/whatis/
TestStand is an automated test executive (ATE). It is an off the shelf solution which makes your life easier. It handles report generation, user management, sequencing (i.e. test flow), result collection, pass/fail analysis, common User Interface, database logging, etc... Basically, all the crap you don't want to develop in LabVIEW. But it gives you consistency and commonality for all your tests. If you look at the layers of the test system TestStand would be at the top like this:
TestStand
LabVIEW (or other software)
Hardware Drivers
Instruments
UUT (unit under test)
2. In TestStand you have the development environment (Sequence Editor) and the User Interface. They can both execute tests. The User Interface is an application written in LabVIEW (or other programming languages, ships with TestStand) which gets deployed to a test station so that testers can execute your test. It does not have the ability to edit the test (in TestStand tests are called Sequence Files). However, the Sequence Editor can edit the tests and would be used on the development machine. There is a deployment utility in TestStand which allows you to create an installer. In that installer you would include the TestStand Engine, the User Interface and all the dependencies for your test (Sequence File). Then the user just opens the User Interface and runs it.
3. NI does offer TestStand courses which can be helpful. I recommend going through these PDFs though first:
http://www.ni.com/pdf/manuals/373200c.pdf
http://www.ni.com/pdf/manuals/323436a.pdf
You will get more out of the classes if you have starting playing around with it first.
Hope this helps.
Regards,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Configure Event Callbacks in test stand using labview

Hi,
I was going through Full OI - Configure Event Callbacks.vi in the test stand example. Can you please explain me how the vi works and what is techniwue behind it?
When i open the individual VI's in the reference, I could see more that 1 control in the front panel. But Only the user parameter is wired in the vi? Why is it so?
Regards
Gopal

Hi Gopal,
When the TestStand Engine fires events, this VI specifies how your Operator Interface will respond. For example, let's examine the first event callback registered in Full OI - Configure Event Callbacks.vi , Exit Application. When the TestStand Engine receives the message to shutdown, and then finishes its neccessary shutdown procedures, it will send a message to the Operator Interface. For the Operator Interface to receive this message, it must "listen" for it. In LabVIEW, this is done by Registering an Event Callback. See the links below for details on how to implement this.
The answer to your specific question is in step 7 of the first link below. When TestStand sends the message to LabVIEW, there is information that is always passed. The other input controls contain this information. To create a VI that always includes these controls, right-click on the VI Ref input to the Reg Event Callback Property Node, and then select Create Callback VI.
Here are two references that talk about handling ActiveX callbacks in LabVIEW in general:
Registering and Handling .NET and ActiveX Events
Register Event Callback (Not in Base Package)
Cheers,
David Goldberg
National Instruments
Software R&D

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

Test Stand 2010 Deployment tool Error

Dear All,
Whilst attempting to deploy a Test Stand system I am coming across the following error:
Error: Unable to find all subVIs from saved VIs. Either a subVI is missing or the VI is not saved in the current LabVIEW version.
The call chain to missing VIs:
1 - initialise_resistor_card.vi
2 - pipx40 Initialize.vi (missing)
I have the Teststand Adaptor set to Labview Run-time Engine --> "Auto detect using VI version"
This is a new feature in Test Stand 2010 right? So is the deployment tool also able to inherit the ability to auto detect the version of runtime engine to use on a deployed machine?
Any ideas?
Regards
There is no problem with the VI within the sequence.
I've encountered this before before with the deployment tool and usually mass compilling or opening and closing the VIs heirarchy helps, but in this case I just can't get the deployemnt tool to process these VIs.

Hello,
So it would appear that the VIs giving the problem are within .llb .
If I open and save them again within the .llb and mass compile the .llb then the same happens, but if I take the VI out of the llb then the problem goes away?
Is there any known issues with the Deployment Utility failing to find VIs with llbs? I notice TS 2010 deployment utility introduces the idea of a Packed Project library option rather than the old SupportVIs folder, could using this be the issue?
Regards
Matt

Clearing Test Stand engine's internal cache

Similar Messages

Maybe you are looking for