NewExecution sequenceArgsParam

[Madottati]

Hello,

some time ago I faced the same problem. Then I created a local variable in the sequence, where I call this VI from. The local variable is calles "Parameters" and the type is container. This container can contain any kind of data, and it has to match the parameters of the called sequence. I take the property object reference of this, convert to variant and pass it as sequenceArgsParam. The passed parameters will appear in the new started execution.

Madottati

[aSquared]

HI ~jiggawax~, 

Thanks for the many ideas, 

I can use the Global Temps , and I never heard about the * option in the name of the queue before.....

But I think that for my application it will be very elegant if I could send some parameter together with the interactive execution.

I am adding some example so you can understand me more.

Please save the two files attached here-

*open the 1.vi attached.

*View the block diagram, and change the control 'try.seq path' value to the path of the Sequence file try.seq you have saved.

*Run the VI and see that it pops -up a dialog with the value of 66, this is the value of the 'Locals.uuu' in the sequence.

Can I send some value with the interactive execution ? maybe with the SequenceArgsParams ? or with some other way so the interactive execution will use this value ?

Amitai

[johndoe858]

HI,

Am trying to use the NewExecution sequenceArgsParam in the following way:

Have a process model with a modified entry point and a client sequence will different subsequences. A LabVIEW VI will trigger running different sequences (based on different  button press actions). This action has to happen in the following manner:

1. The LabVIEW VI has to call the client sequence using the Process model and the modified entry point. I should be able to pass parameters to the entry point

2. The client sequence will take some action based on some (different set of) parameters passed to it.

Have modified the examples in the TS examples. Attached a zip file containing the same. 

1. Edit mode VI calling sequence.seq

A copy of the sub-sequence Execute With Process Model  from the following file:

C:\Users\Public\Documents\National Instruments\TestStand 2019 (64-bit)\Examples\TestStand API\Executing Sequences Using API\LabVIEW\ Executing Sequences Using API.seq

2. Execute framework sub-sequences with process model.vi

Modified from the original VI in the sub-sequence call from (1) above

3. Test edit mode sequence.seq

This is the target sequence file. Expected to receive two inputs: Edit_mode (Boolean) and SubSequence_name (String) and run the required SubSequence accordingly (only pseudo-code)

You can use the default sequential model path as the process model file to use, and Single Pass as the entry point.

Since the target sequence file is Test edit mode sequence.seq, I assumed that the inputs to IEngine-->NewExecution method specified by “sequenceArgsParam" would apply to the “sequenceFileParam” -> Target sequence file

But it does not seem to the case. They are applied to the SequenceName which in this case is the entry point in the PM (You can change this to Single Pass)

What we want to be able to do is the following:

Using TestStand APIs from LabVIEW, call a target sequence with specified set of parameters, through a specified Process model sequence with a specified entry point and different set of parameters.

Alternately:

Am assuming that the InteractiveArgsParam will emulate Right clicking the step and saying Run selected steps using “Entry point”. Any example that can help me get started on this will also help.         

Thanks