Is it possible to Create New Test Sequence Group from already created Individual test sequences with TestStand Debug Deployment License ?

[Guru0001]

Suppose I buy the TestStand Development license (for Test Sequence Editor) and create say 100 individual test sequence files. Now I buy the Debug Deployment license for TestStand and deploy it in my customer's PC who will be using the created test sequences for his Production testing.

Now in the customer's PC where only the debug deployment license only is available, will he able to create a new test sequence file by selecting N number test sequences from the listed 100 individual test sequences file and store the newly created test sequence file ?

Will be able to execute and debug the newly created test sequence file from that PC itself ?

If not possible, will he require Test Sequence Editor and full development license in this case ?

[RayFarmer]

Hi,

I believe you will require the full development license if you are going to create test sequence. 

You dont need to deploy the SeqEditor on your target system, if your Test Sequences are created dynamically.

Regards

Ray Farmer

[DWeiland]

Hi Guru,

    Ray is correct. Any time you are going to create new sequence files, you need to have the TestStand Development License. The Debug Deployment License only allows you to debug existing sequences that have been deployed to that machine.

Thanks, let us know if you have any more questions.

Dan Weiland
Applications Engineer
National Instruments

[Guru0001]

Hi Dan,

Thanks for your clarification.

Suppose I get the TestStand development license and install in the Customer PC, will it be possible to create new test sequences from the operator interface itself ? i.e. Customer wants to have only one software (Operator Interface) in which he can create, edit and debug the test sequences. He does not need the TestStand development environment for the Customer's PC, which is dedicated for Production testing.

In this case, since it going to deployed in Customer's PC for automated testing, can you clarify what you meant is the full development license to be purchased for the customer's PC as well ? Customer will not require the entire TestStand development environment in his Production testing PC.  I dont really understand why a full development TestStand license is required in the Production Testing PC ?

Thanks

Guru

[RayFarmer]

Hi,

With the default operator interfaces provided with TestStand you cannot create sequence files. You can only do this using the SeqEditor.

You will have to provide that functionality yourself by modifying the default operator interface. You will find all the source code for the operator interface in the \Teststand\OperatorInterfaces folder.

Alternative you could provide a create mechanism via means of a SequenceFile. There is an example of this in the TestStand\Examples\SequenceBuilderTool folder.

Hope this helps in any way.

Regards

Ray Farmer

[DWeiland]

Hi Guru,

The idea is that you would develop your application on one machine that has the Development license, and then on the test station, or Production PC,  you would have either the Base Deployment License, allowing you to run the sequence created on the development machine, or the Debug Deployment License, allowing you to modify and run the sequence created on the development machine.

Many times sequences are developed for not one but multiple test stations, so National Instruments provides the Deployment licenses to allow customers to use sequences on their Production PCs without requiring them to purchase a Development License for every test station they will be using their sequences on.

The Operator Interface is simply an executable that allows you to run the sequences created on the Development machine with the Sequence Editor. This allows you to use your created sequences on the test station without actually needing the Sequence Editor installed. The Operator Interface is not really meant to develop sequences.

However, as Ray mentioned, all of the code for our Operator Interfaces is included in your TestStand installation. It IS possible to modify the Operator Interface to essentially perform the function of a Sequence Editor, which could then be used on a machine with the Development License to create sequence files, however since the Sequence Editor performs all of the functionality of the Operator Interface as well as creating sequences, it may not be worth the extra effort to modify the OI to do something the Sequence Editor can already do.

I hope this clarification helps Guru, let us know if you have any more questions.

Dan Weiland
Applications Engineer
National Instruments

[Guru0001]

Hi Ray & Dan,

Thanks for your detailed clarification. Now it is clear for me regarding the usage of TestStand Operator Interface and the Sequence Editor.

I have heard of people using TestStand in Automotive & Aerospace equipments. I wanted to understand if TestStand could be used for automated testing of medical equipments during production. Can you give me some inputs on your experience, types of domains in which TestStand is used for production testing ?

I understand TestStand Ver. 3.5 is recently released. Any inputs what are the highlight features when compared to ver 3.1 ?

I understand that the menus in Operator interface is customisable. Is it possible to customise menus in the Sequence editor ?

Regards

Guru

[Santiago D]

Hi Guru,

In response to your question about the use of TestStand for the testing of medical equipment, there are a number of companies that are currently using TestStand in medical field.  Most of these applications involve testing medical equipment.  In some of these applications TestStand has actually facilitated the attainment of FDA 21 CFR 11 certification.

We are currently highlighting how Sanmina-SCI built an FDA-approved production tester for testing and calibrating medical devices that measure blood glucose levels.  You can find more information on the application at the following link.

Sanmina-SCI Selects NI Modular Instruments, PXI and TestStand to Build FDA-Approved Medical Device Test System [http://digital.ni.com/worldwide/bwcontent.nsf/web/all/9C9D8E07A8C5278F86257098004ED818]

Regards,

Santiago D

[DWeiland]

In answer to your other questions Guru,

You can customize the "Tools" menu in the Sequence editor by simply going to "Tools >> Customize".
You can also add "Edit" substeps to and Step Type by accessing the Step Type Properties through the Type Palette. Using this method you can specify a code module to run when a user right clicks on a step and selects your newly created "Edit" substep.

As far as TestStand 3.5 is concerned, you can see slide show describing the new features on our website.

Just go to www.ni.com/TestStand and click on the "What's New" icon, or you can access the slide show directly here:

http://www.ni.com/teststand/gallery/1.htm

Have a good one Guru!

Dan Weiland

[Guru0001]

Hi Dan & Santiego,

Thanks for your detailed clarification.

I wanted to have the TestStand operator interface in production Test PC to have GUI designed for Touch screen interface during the automated testing. It is planned to have any one of the Windows OS in the Prouduction Test PC. (Win 2K or Win XP, etc)

I understand from one of the earlier message clarification that it is possible to use the selected TestStand Active API from the customised touch screen GUI and perform automated testing, if the PC uses Windows OS like Win 2K or Win XP.

1) Has any one developed an ATE software with TestStand having Touch screen on PC running Windows OS ?

2) Considering the above test PC platform having the TestStand Engine, which Windows OS (Win 2K or WinXP) is best suited for ATE applications running production testing ? (considering good performance and best one to integrate with TestStand Engine) ?

Thanks in advance,

Regards

Guru