How to execute a sequence from cvi code ?

[Kobi_K]

Hello ,

I'm programing a test software using Labwindows CVI 9.0 and TestStand 4.2 .

I'm Using CVI GUI and i want for example to press a button that will lanuch a squence from Teststand .

the SEQ file is already open because i'm launching the GUI from Teststand .

How can i execute a seq from CVI ?

Thank you for your help.... Kobi

[RayFarmer]

Hi,

Why don't you have a look at the simple UI for CVI supplied with TestStand and go from there.

There may even be a simplified UI example on the NI website, I know there are various examples there.

You do not want to be running Teststand SeqEditor to launch CVI GUI to run a test Sequence.

You should be running a CVI UI (which acts like a basic version of the SeqEditor), which starts the TestStand engine and runs your test sequence.

Regards

Ray Farmer

[Kobi_K]

First of all thank you for your comment....

The problem is i'm new in teststand and cvi i'v red all the manuals and tryed to find those examples but no luck..

Can u plz give me a direct link ?

Thank you...

[Callie]

Refer to the Example User Interfaces section in Chapter 9, Creating Custom User Interfaces, of the TestStand Reference Manual (p. 9-1):

Example User Interfaces
The <TestStand>\UserInterfaces directory includes the executable, project, and source code files for each example user interface. The Full-Featured subdirectory contains user interfaces for loading, viewing, editing, saving, executing, and debugging sequence files. The Simple subdirectory contains similar but limited user interfaces with fewer commands and options but no menus. Also, the simple example user interfaces display the steps for executions you run but do not display steps for sequences you load. Both subdirectories contain source code for LabVIEW, LabWindows/CVI, Microsoft Visual Basic .NET, C#, and C++ (MFC).TestStand installs the source code files for the default user interfaces in the <TestStand>\UserInterfaces and <TestStand Public>\UserInterfaces directories. To modify the installed user interfaces or to create new user interfaces, modify the files in the <TestStand Public>\UserInterfaces directory. You can use the read-only source files for the default user interfaces in the <TestStand>\ UserInterfaces directory as a reference. When you modify installed files, rename the files after you modify them if you want to create a separate custom component. You do not have to rename the files after you modify them if you only want to modify the behavior of an existing component. If you do not rename the files and you use the files in a future version of TestStand, changes National Instruments makes to the component might not be compatible with the modified version of the component. Storing new and customized files in the <TestStand Public> directory ensures that new installations of the same version of TestStand do not overwrite the customizations and ensures that uninstalling TestStand does not remove the files you customize.

Note: National Instruments recommends that you track the changes you make to the user interface source code files so you can integrate the changes with any enhancements in future versions of the TestStand User Interfaces.

You might also find the Example Programs topic in the NI TestStand Help useful for other tasks.

[Manooch_H]

Kobi -

Could you please explain the functionality or goal you are trying to achieve? Perhaps an outline of the process/order of operations you envision executing.

I look forward to hearing back from you.