Using customise operator interface

[asafv]

I'm trying to customise the simple operator interface (Lv) to my needs,

and I'm facing several problems.

* Adding to the test results the numeric result.

* Removing the tracing of the action step .

* I'm running the single pass and have an indication
every time the seq. failes but It's for a short time,
how can I Fixed It until it runs again.

* I can't access the file globas with the operator interface,
maybe there is an example (I used the sequence context).

[KittF]

assaf wrote:
>I'm trying to customise the simple operator interface (Lv) to my needs,>>and
I'm facing several problems.>>* Adding to the test results the numeric result.>>*
Removing the tracing of the action step .>>* I'm running the single pass
and have an indication> every time the seq. failes but It's for a short
time,> how can I Fixed It until it runs again.>>* I can't access the file
globas with the operator interface,> maybe there is an example (I used the
sequence context).>

[anand jain]

Here are answers to you questions:

1. Adding to the test results the numeric result:

In the VI UI Message Handler you will be handling different UI messages.

When you handle the "Trace UI Message" you get a handle to sequence context.

Using this handle you can access the numeric result by using "Step.result.numeric".
This value can then be appended to the string, which is displayed in the
front panel.




2. Removing the tracing of the action step

I am not really sure what do you mean by removing tracing of the action step.

I think you do not want to display the step name if it is an action step.
You have to check for a
the step type and check to see if it is an action step. The steps you will
need to go through
are from a sequenceContext get a handle to the sequence. Using the "sequence"
handle you will need to
get a handle to a given step using the method "GetStep". From that handle
using an method "AsProperty
Object" you can get the "typeName". From that you can decide if that step
is a method and decide
if you want to run the trace step or not.



3. I'm running the single pass and have an indication every time the seq.
failes but It's
for a short time,>


Again I am not sure what you would like to do. You would like to display
a failure dialogue and keep it
till the users clicks on a button as the current operator interface does
or would you like to
just keep a failure window open till the next UUT starts. In the first case
it should just involve using
a loop and switch to display the information. In the second case you will
need to use
vi server to launch a vi and display its front panel and close it when the
next UUT testing starts.
The second procedure is how the current teststand operator interface shows
information and displays it
till another task is done.




4. I can't access the file globas with the operator interface,> maybe there
is an example
(I used the sequence context).

If you have the sequence context you need to use the TestStand get property
value (Number).vi to get
the value of the file global. Your look up string will be "fileGlobals.
name