How to get SequenceContext (TS API) from LabVIEW

[CyGa]

Hi!

I embedded TS interace in my LV code and would like to programmatically tune some settings of TS (Report, ...). Usually in TS I use RunState reference to get and set specific properties. It looks like RunState ref is not available through TS API => Am I wrong ?

It also looks like SequenceContext could allow me getting/setting interesting prop. But how to get ThisContext or SequenceText whithin LV ?

[tbob]

The only way that I know to get a Sequence Context into Labview is to call the Labview code from TestStand and pass This Context through the connector pane.

[CyGa]

Hi tbob,

that's what I would if I was using LV in TS... But i'm using TS in LV 

I can't figure out how to get it !

Anyone has an idea ?

[tbob]

You cannot just grab This Context using Labview alone.  The context must be passed from TS to LV through the connector pane in a step.  It's a simple matter.  TS must be running for This Context to be valid.  So why not just pass the context to LV in a step. 

Are you running LV alone and TS is not running?  If TS is running, are you not calling a LV vi from TS?  This is where the context must be passed to LV.

[Dennis_Knutson]

Remarkably similar question here. Is that you with a different login? If not, read that.

Not even sure how sequence context applies to the report options. What options do you want to change that are not available with the current method?

[CyGa]

Hi Dennis,

I only have one login but it seems that another person has the same problem.

You can in the picture enclosed that I call TS Engine from LV. Placing a step in the sequence to get ThisContext and send it back to LV is not something I can do because, in the future, I won't have the control on sequence file contents.

Indeed, having the SequenceContext would allow me to have control on Report options (reference to the post relative to Dennis' post) but also on Execution, Thread, SequenceFile and Engine.

[tbob]

I just re-read the original post.  You cannot have a valid RunState reference if TS is not running.  Similarly you cannot have a valid This Context if TS is not running.  Both are formed only when TS is started.  So you cannot modify TS parameters from LV unless TS is running and it calls the VI in a step.  Why are you wanting to run TS from LV anyway?  This is not the way it was designed to operate.  You can change TS parameters with a VI easily if you call that VI from TS.  So make that VI call your very first step, or put the VI call in the Process Model or in a callback sequence.

[tbob]

---

@zyl7 wrote:

Hi Dennis,

Placing a step in the sequence to get ThisContext and send it back to LV is not something I can do because, in the future, I won't have the control on sequence file contents.

---

Don't put the step in a sequence file.  Put it in the process model or a callback.  Send the modified process model to your customer.  Then he can use whatever sequence file he wants.  As long as he doesn't modify the process model, and he should never do this, then you will be OK.

[CyGa]

The purpose to control TS from LV is that my customer has one unique interface for maintenance (done with LV code) and product test phase (done with TS). The sequences can be made by directly by customers so I can't force them to add specific LV steps in their TS code. Modifying the process model could be an idea...

I do not want to have SequenceContext before TS is running, I can start an execution and get ThisContext after...

[CyGa]

In that case, the LV step would have to store ThisContext in a TS variable and then I would have to read that memory from my main LV code... Am I right ?