NI TestStand Idea Exchange

About NI TestStand Idea Exchange

Do you have a feature idea for how to improve NI TestStand? Submit and vote on ideas now!

  1. Browse by label or search in the TestStand Idea Exchange to see if your idea has previously been submitted. If your idea exists sure to vote for the idea by giving it kudos to indicate your approval!
  2. If your idea has not been submitted click Post New Idea to submit a product idea. Be sure to submit a separate post for each idea. Note: the TestStand Idea Exchange is not the appropriate forum to submit technical support questions.
  3. Watch as the community gives your idea kudos and adds their input.
  4. As NI R&D considers the idea, they will change the idea status.
  5. Give kudos to other ideas that you would like to see implemented!

The TestStand R&D team is committed to reviewing every idea submitted via the TestStand Idea Exchange. However, we cannot guarantee the implementation of any TestStand Idea Exchange submission until further documented.

Top Kudoed Authors
User Kudos Count
1
1
1
cancel
Showing results for 
Search instead for 
Did you mean: 

Sequence adapter available for substeps

When creating custom step types, it is highly recommended to use Post-Step for calling execution module instead of Default Module.

Thus, when instanciating a custom step type, parameters passing is not saved within the sequence but only in the step type definition.

This allows to change parameters passing without having to update all the step types instances.

 

In some big test benches, it is intersesting to have low-level step types and high step types based on low level step types.

High level step types execution modules are sequences using low level step types.

 

Since sequence adapter is not available for Post-Step, we are obliged to call the sequence through Default Module.

Thus it can generate problems when adding parameters in sequence call.

 

I suggess to allow Sequence Call in SubStep creation :

 

SequenceAdapterInPostStep.png

 

Jean-Louis Schricke, MESULOG

TestStand Architect

Jean-Louis SCHRICKE
CTA - Certified TestStand Architect (2008 & 2010 & 2014)
CTD - Certified TestStand Developer (2004 & 2007)
CLD - Certified LabVIEW Developer (2003 & 2005)

5 Comments
Member D.S
Member

Is there any progress from NI regarding this suggestion?

 

Trusted Enthusiast

One thing that can be done in the meantime to get behavior similar to what you are asking for is to use a code module of a different type (e.g. dll, vi, etc.) with code that does the following:

 

1) Call Execution.NewThread() to call the subsequence you wish to call. Pass ThisContext for the sequenceContextParam.

2) Since the sequence is running in a new thread you need to wait for it. Call Thread.WaitForEnd on the thread you created and pass ThisContext for the callingSequenceContext parameter. NOTE, you probably do NOT want to set the stepToStoreResultsIn parameter if the user might also be specifying their own sequence call with your step type because I think only one set of results can get stored on the step. If you are not allowing the user to specify a code module then maybe it would make sense to specify that parameter as long as you only have one subsequence substep.

 

Keep in mind I haven't tried to implement the above, but I'm pretty sure it should work.

 

-Doug

Member

Doug,

 

I am sorry to inform you that you didn't understand the need.

The need is to allow creation of Custom Step Types which module is a sequence call, within a PostStep instead of Default Module.

 

Until now, calling a sequence is possible only with Default Module which implies evolutivity issues when changing sequence parameters (since each instance of the CST stores calling method within the sequence).

 

Jean-Louis Schricke

Jean-Louis SCHRICKE
CTA - Certified TestStand Architect (2008 & 2010 & 2014)
CTD - Certified TestStand Developer (2004 & 2007)
CLD - Certified LabVIEW Developer (2003 & 2005)

Trusted Enthusiast

Jean-Louis,

 

I think you misunderstood my suggestion. I was explaining how you could use a PostStep of a different module type to effectively make a sequence call programmatically so that you wouldn't have to wait for such a feature to be implemented. Basically, you can use one of the other adapters and a code module that knows how to programmatically call sequences to get a similar behavior to what you are asking for.

Member

Ok Doug, understood.

 

It is a good suggestion.

 

But I think that the best solution should be that NI allow sequence call within PostStep...

 

Thanks,

 

Jean-Louis

Jean-Louis SCHRICKE
CTA - Certified TestStand Architect (2008 & 2010 & 2014)
CTD - Certified TestStand Developer (2004 & 2007)
CLD - Certified LabVIEW Developer (2003 & 2005)