Wait time in Test Stand

I have an application in TS where I need to measure a leak rate. How do I set a "wait time" in Test Stand sequence so I can measure the same test point after certain elapsed time.

I don't think TestStand has a wait function. You would be better off doing this inside your test step code. Measure, wait, measure again. Both measurements can be returned to TestStand for further processing. Or just calculate the leak rate in your test step code and just return the rate to TestStand for numerical limits testing.
- tbob
Inventor of the WORM Global

Similar Messages

Modules execcution times in test stand

Hello Everyone:
Maybe some can help me.
I wrote a test sequence using Test Stand program with LabView and using Field Point for hardware. There is one issue that has been notice on the test results and that is the execution time of each of the modules.
This question has been ask is Why does the execution time of the modules varies from one test to the next.
We also notice that if we run a same unit several times we do not get the same results, they are very close but never the same and that includes the module execution times.

Hello Toro,
That is a great question. Depending on what controller and modules you have, the execution times of the modules vary from one to another. There is an excellent tutorial that explains this really well, below you will find a link to it:
http://zone.ni.com/devzone/conceptd.nsf/webmain/a14d3c3314a0e24a86256dbe00664943?OpenDocument
If you don't have a real time module, then by switching to one, you are going to see a significant change in the accuracy of the times displayed. Please let me know if you have any further questions.
LA

Test Stand LabView adapter 8.6 run time will not run 8.5 VIs

I’m trying to run a script I developed with a dev computer on
a regular PC set up with a Test Stand User Gui, and run times for Test Stand
and Labview.
With the Test Stand Labview adapter set to 8.6.1 all of my
ENA(Agilent Network Analyzer) calls fail for “VI Version is too early to
convert to the current LabVIEW version.” The ENA library is written in 8.5. If I set the adapter to 8.5.1 then all of the
VIs developed in 8.6 fail. In addition
it will not run any VIs that I save back to 8.5. I installed a demo Labview development
version (2010?) and everything ran fine with the adapter set to Development
System.
I am not sure what to try next to get it to run on the
regular PC, any hints.
Test Stand = 4.2
LabView = 8.6
Running in windows XP
Solved!
Go to Solution.

One of the many things I tried was saving the ENA library to 8.6, but I could not get it work.
This is the Original library I installed and was trying to Convert (8.0 upgrade agena.zip)
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=001CE83736F3674BE0440003BA7CCD...
I am about to try this one. (8.2.1 Upgrade)
http://sine.ni.com/apps/utf8/niid_web_display.download_page?p_id_guid=74D1F1D4EB5268E8E04400144FB7D2...
I am pretty new to labview so I am not sure how to make the save to previous version workfor libraries, but I can easily do it with individual VIs. For libraries, it creates a new directory, and puts in all of the files and then asks me about saving the lib files as something else. This is where I think I get it wrong. I tried it again today and got the same results.
I greatly appreciate the Help
Brian

Connect vi to test stand

hai guys,
im 1st time using test stand. i duplicate the test stand from a different pc and place all the subvi in the sane location. when i open the sequence file i cannot call bak the vi. how to set the path in test stand to reconnect to the vi .
thanks,
shamaran

Hi,
When you say "duplicate", how did you achieve this?
What error messages (if any) are you getting?
Regards
Ray Farmer

Test stand design for high speed brushless dc servo motor efficiency testing

We are in the process of designing two test stands around the brushless dc servo motor in the attached specifications. The first we would like to operate using Labview and a PXI-7352 controller. The second will be a real time configuration. The motor will need to run in the 25-50,000 RPM range. We want to bring the hall sensors back to the controller and do PID and other control there. The sinusoidal commutation from the controller would then go to an as yet unselected servo amplifier. When the motor is under test we want to be able to measure accurately the power that is being used by the motor - not the motor and controller / amplifier.
Can the PXI-7353 handle this motor speed range?
Will Labview and the PID toolkit be sufficient software to program the first test stand?
Any example VI's available for this approach (I could not locate any)?
What is the appropriate controller for a real time system?
What is the best way to instrument the motor to determine power required at a given test point?
Any suggestion on a servo amplifier?
Thanks in advance,
David
Attachments:
B0912-050 Brushless Motor.pdf ‏91 KB

Mr. Zaatari,
As you will note, there are six questions posted above. As you also know, I have been waiting for your response for 5 days and decided to use this alternate method in hope of getting my questions answered. As you further know you have not answered these questions. It is a shame that you will not post your "answers" here so that the rest of this wonderful NI community might have the benefit of your knowledge as well.
I will respond further to you by email.
David

Electrical start in test stand

Hi all - I wish to incorporate methods of electrically starting test stand in the future . Has allowance been made when waiting for the normal start keyboard keys in test stand to poll for another start signal eg using a callback routine etc.
can anyone point me in the right direction?
thanks dht

Hi,
the principal is not in TestStand. You would code this either into your operator interface, or the process model you're using before "mainsequence" is called, or the client sequence.
The "polling" you're referring to, I assume, is waiting for say F5 to run TestUUTs. This is built into the operator interface, or the sequence editor. If you wanted to add the functionality to monitor a digital line, or something similar, then add that into the operator interface itself. (You can't add it into the sequence editor directly, since you don't have the source code to modify!)
Hope that helps
Sacha Emery
National Instruments (UK)
// it takes almost no time to rate an answer

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

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~

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

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

Uccx 9.0 expected wait time returns a -1 value

Guys I am trying to use the expected wait time feature in UCCX, however the value returned is -1 each time this step is executed. All the other feature such as average wait time etc all works, its just the expected wait time that doesnt. Any ideas please?

During your tests, the call activating the script you are debugging is actually in queue and with a real wait time?
I could find any related bug, can you check this links:
Link1 -- Link2
I will try to find additional information.
Rolando Valenzuela

Increase in wait time of synchronous interface

I am working on HTTP to proxy synchronous interface on PI 7.3
PI uses communication channel with SOAP receiver adapter over XI protocol
Now I am facing below error in the interface while testing after 3minutes-
com.sap.engine.interfaces.messaging.api.exception.MessageExpiredException: Message (INBOUND)expired
Can anyone please tell me how can I increase wait time in the channel.
I have tried adding the parameter name 'XMBWS.Timeout' and parameter value '30000' to increase wait time to 5minutes. But it didnot work.

Shwetha,
Set property of Service "XPI Adapter:
XI" within SAP NetWeaver Administrator -->xiadapter.inbound.timeout.default ---180000ms--(3 min)
Executing the below mentioned steps
1.(PI 7.3)
Goto NWA(PI 7.3)-->configuration-->Infrastructure-->Java System Properties-->goto Services tab-->find xiadapter--> u can increase value inbound.timeout.default
see the below screenshot :
2.
PI 7.0 & 7.1x
Please check point no 2.2.7 of the below doc:
http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/c059d583-a551-2c10-e095-eb5d95e03747?QuickLink=index&overridelayout=true&44478681512917
Mutti

Test Stand and MAX Settings

I am using test stand and Labview 7.1. I used Express VIs to setup my RS232 communications in numerous VIs that I call from test stand for different types of tests. I have the same product, but with different baud rates. Is there a way in test stand to change the baud rate settings in MAX for Com1? I tried to create a Labview program to do it, but once a sequence runs that has the Express VI I/O Control it must start a new VISA session and I loose what was set up and it reverts back to the MAX settings for Com1. The only time The VISA setup vi I created appears to work is when I converted an Express VI (or opened the Express VI's front panel). And messed with the code.

Hey,
I would suggest using the VISA Configure Serial Port to configure the port and then calling the Express VI using the VISA Resource Name Out from the configure VI.
Regard,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~
Attachments:
setbaudrate.vi ‏36 KB

I am trying to debug HTBasic code modules while using Test Stand, how do I refresh the subs that have been loaded in memory?

I am writing an application for Test Stand, we are using modules previously written in HTBasic. Whenever I make a change to the code and try to re-run the program, it just runs the old version of the code. The only way to refresh the code is to close Test Stand down and restart it. Is there a way to flush the memory of modules?

Hi,
I haven't used HTBasic with TestStand 2.0.x, but I'm assuming that you have the steps in the sequence set to unload when sequence file is closed (look under the step properties -> run options tab).
If you're still prototypeing, use the File->Unload all modules option. Have a look at page 4-3 in the user manual - it refers to .DLLs, but I'm assuming the HTBasic falls into the same methodology.
Altering the run options from it's default will affect the memory useage and speed of execution of the test sequence. Have a look at page 5-22 (page 158 in the .pdf) in the TestStand user manual - basically, if a code module is loaded into memory already, when the step gets to execute, the loading overhead is already done. If it stays in memory after this, then it's avail
able for next time (quicker second run 'cos it doesn't need to load again. However, the balanceing factor is the sequence is useing more memory at a time, by haveing the module ready.
My usual setting is to use Load dynamically, and Unload after sequence executes. I use this is only during development however, as this is not the most speed friendly, but a compromise so that if I don't call a step I don't load it, but if I do use a step, I'm sure it's free again when I need to modify the .dll modules I create. If you have a look on page 5-7 (143) of the user manual you can set the sequence file to effectively over-ride each step's load and unload settings - useful if you want to revert back again later. If you use this, you'll see that the top two run options for the step are greyed out, but if you set it back with the sequence file options, they do revert back to their original settings.
Hope that helps (and works!!)
S.
// it takes almost no time to rate an answer

Wait time in Test Stand

Similar Messages

Maybe you are looking for