NI TestStand

cancel
Showing results for 
Search instead for 
Did you mean: 

selectable sequences

Hi Chris,

Sorry for the delay.  I was on vaca.

 

I have TS 4 and LV 8.  Does that help ??  What-ever shipping example that was sent with those versions.

 

Clint

0 Kudos
Message 11 of 17
(2,114 Views)

Chris,

Can you save the example in:

 

TS Engine ver: 4.0.1

Seq Editor ver: 4.0.0.1030

 

Thanks,

Clint

0 Kudos
Message 12 of 17
(2,112 Views)

Hi Clint,

I was on holyday, too. I also was not able to open the file! It seems NOW i have to install
TS4.1 on my maschine.
http://forums.ni.com/ni/board/message?board.id=330&thread.id=20047

Greetings

Juergen

 

 

--Signature--
Sessions NI-Week 2017 2016
Feedback or kudos are welcome
0 Kudos
Message 13 of 17
(2,092 Views)

I am sorry about that.  Attached is the example saved in TestStand version 4.0.1.

 



Message Edited by Chris_G. on 07-01-2008 11:09 AM
Chris_G
Sr Test Engineer
Medtronic, Inc.
0 Kudos
Message 14 of 17
(2,072 Views)

Thanks Chris,

A few questions.

1. In the 1st message popup  you set "step.result.buttonhit" and in select a seq you have "step.result.buttonhit" won't one over write the other ?? Losing info?  One is to select ( in my case)  a troubleshoot /end to end run and the other is to selct which seq to run ( A,B, C).

2.  What does "runstate.sequencefiledata.seq(locals.buttonhit).asproperty...........  "in "SequenceCall" of this example do??

So this will allow me to set a variable in the main seq and pass it to either seq a,b or c bsed on which button in "Mode" is selected and which seq is selected???

 

Thanks,

CE

0 Kudos
Message 15 of 17
(2,054 Views)

Hello Clint Eastwood,

To answer your questions:

(1)    “Step.Result.ButtonHit” is not a variable that we are writing to, but rather it is the result of the user’s click on the Message Popup that we are reading from.  In the first Message Popup it is stored to the variable “Locals.buttonHit”, and in the second Message Popup it is stored to “FileGlobals.nButtonHit”.  Both steps use the Post-Expression to do this.  Nothing is being overwritten.

 

(2)    The Pre-Expression for the “Sequence Call” step:

 

RunState.SequenceFile.Data.Seq[Locals.nButtonHit].AsPropertyObject().SetValNumber ("Parameters.param", 0, Locals.buttonHit )

 

sets the value of “Parameters.param” in the selected sequence (contained in “Locals.nButtonHit”) to whatever the user selected in the first Message Popup (contained in “Locals.buttonHit”).  To understand the method better, I would recommend taking a look at the NI TestStand Help and searching for it.

 

(3)    Yes, this will allow you to set a variable in the Main sequence and pass it to any sub-sequence of it.  Try it out and see for yourself J

Chris_G
Sr Test Engineer
Medtronic, Inc.
0 Kudos
Message 16 of 17
(2,011 Views)

Thanks Chris,

I will try it.  Funding has been cut on this project until Sept so it'll be a while until I can get back to it.

Clint

0 Kudos
Message 17 of 17
(1,996 Views)