Executing Sequence from LabVIEW

[Flamboyant]

I am not an expert in TestStand. I dont understand what you are telling. If possible could you post an example. That would help more.

[Norbert_B]

The code would look somehow like this:

hope this helps,

Norbert

[Flamboyant]

I need little more help on specifying the parameters. I went through the TestStand help, i could not figure out what to wire to the sequenceFileParam and processModel Param. I have attached my Sequence and LabVIEW. If you could make this work and post it here, it would be of great help.

[Callie]

Refer to the NI TestStand Help topic for Engine.NewExecution:

http://zone.ni.com/reference/en-XX/help/370052J-01/tsapiref/reftopics/engine_newexecution_m/

Thanks,

Callie Jones

NI TestStand Documentation Team

[~jiggawax~]

Flamboyant,

The problem with most CLD and CLAs that try to use TestStand is that they still think LabVIEW should be the top layer of software.  This is not true when you use TestStand.  TestStand IS the top layer of software and should be what you run (NOT LabVIEW).  The layers go like this:

TestStand -> Code Module (LabVIEW) -> Driver -> Hardware

Whereas it seems you want this:

LabVIEW -> TestStand -> ? -> Driver -> Hardware

That being said however, there is a User Interface (that ships with TestStand) built in LabVIEW and should be the top layer when ran on a deployment computer.  So something like this:

User Interface (built in LabVIEW) -> Sequence File/TestStand Engine -> Code Module (LabVIEW step) -> Driver -> Hardware

I understand that every application and need is different and forgive me if I'm out of line.  It just seems that you are new to TestStand and are struggling with some of the basics.  The User Interface (that was written in LabVIEW and ships with TestStand, we pionted them out earlier) contains all of the information you need to run a sequence from LabVIEW.  That's what it does.  That's what it is.  So I recommend looking through that code for a lot of your answers.  It is not as trivial as just calling a few property nodes. 

I DO NOT recommend using the sequence editor on a deployment computer to run your sequences.  It's purpose is for creating, editing and debugging sequences files. And though it is true that you can run sequence files, the sequence editor was not intended for deployment.

I made a video that might be useful: http://www.youtube.com/watch?v=jzZWeRHaXaA  You may have to turn up your computer volume.

[~jiggawax~]

http://zone.ni.com/devzone/cda/tut/p/id/7560

I should also like to point you to this link.

[Flamboyant]

Callie wrote:

Refer to the NI TestStand Help topic for Engine.NewExecution:

http://zone.ni.com/reference/en-XX/help/370052J-01​/tsapiref/reftopics/engine_newexecution_m/

Thanks,

Callie Jones

NI TestStand Documentation Team

---

The link does'nt exist

[Flamboyant]

Refer to the NI TestStand Help topic for Engine.NewExecution:

http://zone.ni.com/reference/en-XX/help/370052J-01​/tsapiref/reftopics/engine_newexecution_m/

Thanks,

Callie Jones

NI TestStand Documentation Team

---

[Flamboyant]

Hi ~jiggawax~,

Is it possible for a single person to be a fullfledged LabVIEW Developer as well as TestStand Developer. The mindset required for each is totally different it seems.

[Callie]

This topic is also available in the installed NI TestStand Help.

1. Launch TestStand.
2. Select Help>>NI TestStand Help.
3. Click the Index tab.
4. Type "NewExecution" and click the NewExecution entry in the index list.
5. Select Engine.NewExecution in the Topics Found dialog box and click the Display button.

Callie Jones

TestStand Documentation Team

[~jiggawax~]

"Is it possible for a single person to be a fullfledged LabVIEW Developer as well as TestStand Developer. The mindset required for each is totally different it seems."

You are correct that the mindset is different.  However, they serve different purposes.  One is a test executive while the other is a programming language.  I always laugh when people try to compare the two.  One of the biggest misconceptions about TestStand is that it replaces LabVIEW.  That is simply not true.  You just have to use LabVIEW differently when you use it with TestStand.

When used with TestStand, LabVIEW is used to write modules.  Whereas when used as a stand alone, LabVIEW is used to write applications (except for the User Interface part of TestStand which can be a LabVIEW application).  In fact you can do everything that TestStand does with LabVIEW.  So why is TestStand even an option?  Because all of the heavy lifting is done for you.  It generates reports, determines pass/fail status, sequences tests, manages users, collects results, writes to databases, has a User Interface, etc....  That way all you have to do is write some modules in LabVIEW to communicate with the instruments or do some complex algorithms and not have to worry about all the other functions.

What do you mean by "fullfledged"?  I have written some pretty intense applications in LabVIEW.  I have also deployed some complex automated systems in TestStand.  Does that make me fullfledged?  I know people who have their CTD and CLD.  I would rather have a CTD and CLD on my team than just a CLA.  I think knowing both is very valuable.

I love these kinds of conversations.  Hopefully I don't come accross as rude or brash.  I am willing to help you with any and all questions regarding TestStand.  It is a hard thing to pickup.