While running a test stand sequence, what
I want to do is have a window that displays certain items. During my
sequence I would like to have a window that is updated any time I want
something displayed. Example: I want to tell the user that a voltage
measurement has been taken and its value. So I would tell this window
the step name and the voltage measured so the user can see what is
happening during the test. Or, I want to display the status of the
major subsequences so the user sees the test is running. I would
tell this window the subsequence name and the status. Each time
something is displayed in this window the list should be appended so
the user can scroll back in time to see the status of everything. The
window should stay on top and not be closed until its told either
programatically and/or a button. Also each new UUT should clear the
window. This could be a labview vi or a cvi function or something in
teststand. I tried using a postUImessage method and it works but it is
not very informative or visible. This would be perfect if it would run
in a larger window with a scoll box that gets updated. An example
program or sequence would be great. I will take what ever I can get.
Thanks for all of your help in advance.
Erik
The easiest way to do this would be to create a subVI that shows up everytime you want to view information. You can write information to a file and append to it everytime a test runs.
You can get the information in your Operator Interface(OI) from the sequence context, cast it to a string and append it to the file using regular LabView file I/O functions. You can read data from the file and pass it to the message popup VI in LabVIEW thus showing the information when needed.
I'm no expert but I do something similar to what you want to do. I implement it with a CVI code. I resize the TestStand window and place the CVI window just next to it. During the test, the operator can see various activity like RS232 communication etc... Basically you can put in this window whatever you like. I agree that it is much more inteligent to do it as part as the TS window but since I don't even attempt to dip into its code, I find this solution sutable.
Hello all,
I have the same problem as Rafi. I also used the postuimessage. This is
a nice method and is the one I am currently using until I find
something else. The problem with this is it is not obvious. I want
something that is blatantly obvious to the user. Something that will
hold the user messges until a new UUT test is started. The LV example
seems like a lot of work for something that should be very easy. A Step
type of "Message Popup" would be perfect if it had a scolling window
that could be updated throughout the test.
Thanks for the responses!
Erik