Entry point parameters

[Believer]

Could some help me out with Entry Points please?

Specifically I would like to pass a parameter through to the process model [I don't want to use a callback in the client sequence]

It seems that Entry Points can have Parameters, but how do you supply those parameters to it?

For example, below, 'Single Pass' gets the sequence name passed in as a parameter.

Thanks,

Ronnie

[RayFarmer]

Hi,

Not sure want callback you have in mind?

By default MainSequence defined in the Process Model has no parameters defined. Therefore if you need to pass parameters then you have to use a modified Process model.

If you dont want to modify the process model, then you could handle the passing of data from client file to the process model by use of the properties of a local variable.

If you right click on a local variable, there are two properties that allow you to propogate the value to a caller and from a caller.

I am sure there is an example of this on this forum.

try this link

http://forums.ni.com/ni/board/message?board.id=330&message.id=19560&query.id=1791977#M19560

Hope this helps

Regards

Ray Farmer

Message Edited by Ray Farmer on 08-10-2009 07:06 AM

[James_Grey]

The NI models have a single parameter called sequence, which defaults to "MainSequence" if it is not passed. It is usually not passed. However, when an NI UI calls Engine.NewExecution because the user selected Run Selected Steps Using <Entry Point Name>, it passes the name of the sequence that contains the selected steps to the execution (and thus to the process model entry point) so the entry point can know which sequence to run.

Note that the Test UUTs entry point is not an option for Run Selected Steps because it does not enable Sequence Properties>>Allow Interactive Execution of Entry Point.

[Believer]

Thanks Ray & James for your answers.

Ray - yes I do want to alter the process model and have my own customized one.

When I said 'I don't want to use a callback in the client sequence', I envisaged the

scene where the process model calls a callback function with a reference parameter

which the client sequence then populates - and so the parameter gets into the process

model that way. But then that depends on the client sequence implementing it.

You rightly said that the client sequence could just set the parameter (variable)

in the process model [as an expression].

James - thanks for shedding light on how the 'sequence' parameter gets passed.

So I guess this is something that happens behind the scenes with the NU GUI.

If I wanted to add another parameter to 'Single Pass', could it be done? - or

would that involve customizing the GUI (which I can't do).

Thanks guys!

Ronnie

[James_Grey · Accepted solution]

"If I wanted to add another parameter to 'Single Pass', could it be done? - or

would that involve customizing the GUI (which I can't do)."

Yes, it would involve customizing GUI. However, there are lots of other ways to get data to your entry point, including file globals, station globals, and Execution.RunTimeVariables. Of course, you can also share data via code modules without even using a TestStand mechanism.

[Believer]

Ray,

I just read the post you mentioned above:

http://forums.ni.com/ni/board/message?board.id=330&message.id=19560&query.id=1791977#M19560

Yes - thanks - that was really helpful too.

So as is often the case with TestStand, it's not 'can it be done' but 'which method do I choose'...

Ronnie

Message Edited by Believer on 08-10-2009 09:54 AM