How to edit UserInterface that only Limit-tests are shown

[OnlyOne]

Hello,
i just tested the Simple-UserInterface in TS4.0 for Labview.
While running a sequence all steps are shown in a list.
What i want to do is:
How can i modify the USerInterface that not all steps are shown but only the tests that i specify. For example all steps with a special property.
Is this possible?
Thanks for your help

[AmirG]

Hello,
Unfortunately, this is not possible. There may be other things that I could do depending on what are you going to do. Could you please explain what do you want to achieve by hiding steps as it executes?  Is it purely cosmetic?

Thanks and with kind regards,
AmirG



Message Edited by AmirG on 05-02-2008 09:41 AM

[OnlyOne]

Hello AmirG,
currently the UserInterface shows everything but i want to change ist so that it is easier to use for the opertaor at the end.
The operator dont needs to see comments or sequences only for example a numeric-limit test "Measure Voltage at Pin xy".
Then it would be nice to have 4 columns with Name, Result, LowerLimit,UpperLimit,Measuremt.
It is not for cosmetic but for makeing it easier to understand/read what is shown there.
Do you have any idea how to do this?

BR


Message Edited by OnlyOne on 05-05-2008 07:44 AM

[dug9000]

Currently the sequence view control (the one that shows the steps that are executing) shows the actual contents of the sequence, not just the steps that have executed. Thus I see two possibilities to get the behavior you want.

1) Make your top level sequence be the simple one that you want your operator to see and make it be mostly sequence calls where you turn off tracing for the sequence into which they call (tracing into a subsequence is a step setting under run options for sequence calls). That way you can hide most of the details inside of your subsequences.

2) Don't use the sequenceview control, create your own UI control (e.g. a listview) instead and handle the trace UIMessages yourself and filter out what you want to show by looking at the step in RunState.PreviousStep whenever RunState.PreviousStepIndex >= 0. If you handle the trace UIMessage yourself your can set the cancel parameter to the UIMessageCallback event to true to keep the teststand ui controls from doing anything with that event which will improve performance.

Hope this helps,
-Doug

[OnlyOne]

Hello dug9000,
number 2 looks good, but can you give me an example how to do this?
Thx a lot

[AmirG]

Hello,
I have a couple of ideas for you.  First of all, are you viewing your report from the user interface as well?  You may want to consider modifying what step results are added to the report, so that the operator will only see the relevant results.  You can do this by viewing the Properties of a step, navigating to the "Run Options" category, and disabling the "Record Result" checkbox.

You can also use UI messages to pass data back to your user interface from your TestStand sequence, if you want these specific results to be displayed in a different section of your user interface.  This would require adding some indicators to your user interface that will display your desired results, then passing the relevant data back in UI messages to the user interface.  From your user interface, you can then update your customized indicators with the data passed back from the UI messages.

Here are some links for further reading related to result recording and UI messages.

Result Recording:

What are the Different Levels For Which I Can Disable Result Recording?

UI Messages:

Using Default and Custom UIMessages

Using Non-TestStand UI Controls in a User Interface

User Interface Messages (UIMessages)

I hope that helps.  BR
AmirG

[Josh_W]

OnlyOne,

Here is an example of this behavior.  I modified the Simple User Interface for TestStand 4.0.1f1 to get part of the behavior you desired.  It is saved with LabVIEW 8.5.1, so if you need it saved for a previous version, let me know.

What I did was instead of the default execution view, I used a multi-column listbox.  Then I registered a callback for the Application Manager's UIMessage event.  In this callback, I am handling the trace message and retrieving each step's information after it has executed.  I am also clearing the Listbox whenever a new execution starts, and just before the ProcessModel calls the MainSequence.

See the comments in Simple UI - UIMessage Callback.vi for more detail.  The comments assume that you have a fair knowledge of the TestStand API, so if any of the API calls are unfamiliar, see the TestStand 4.0 Help.

[OnlyOne]

Hello Josh,
thanks for your example.
This is exactly what i was looking for.

[IVI]

Can any one of you please help me with the same source in C#, I am not able to interpret the labview code.

this would be great help!!!

Thanks

Bharathi