Test status from operator interface

Hi,
I am using C# operator interface to execute a test stand sequence.I need to change test status LED colurs for each step as follows.
Grey- Step not started
Yellow- Step under progress
Green-Step sucessfully completed
Red- Step fail
How can I implement this?
Can I read local variables  in test stand from operator interface and update status LEDs? Which API to be used for this?
Kindly suggest..
Regards
SajK

Hi SajK,
Are you referring to the LEDs in the List Bar on the left hand side of the OI that is associated with a particular sequence?
If so, the functionality you want to modify is controlled by the
ExecutionViewMgr, and is read only. In order to change the way in which
those icons are determined / displayed, you would need to disconnect
the ExecutionViewMgr from the Listbar. However in doing this, you'd
also be losing the automated functionality such as the display
messages, displaying multiple executions at the same time, etc. In
essence, you would have to re-invent a lot of features that the
ExecutionViewMgr takes care of for that List bar.
An easier, although slightly more work-around-ish option, is to simply
change the icon files that TestStand is using for the various states.
All of these icon files can be found here:
C:\Program Files\National Instruments\TestStand 3.x\Components\NI\Icons\NI_UIControls
You could simply change, for example, "ExecFailed.ico" to a solid red led, and TestStand would grab that on execution.
That would be the easiest way.
Hope this helps SajK, have a good one.
Dan Weiland
Applications Engineer
National Instruments
www.ni.com/support
Dan Weiland

Similar Messages

  • How to view Work process status from Operating System level???

    Hi,
    How can I check work process status from Operating System in Unix. For example : In Windows, I can see the work process status from SAP MMC in WP Table.
    How can I view from Unix?
    Appreciate your feedback. Thanks.

    Hi,
    You can terminate. Please look into the menu given by DPMON carefully. You can kill the process using the k option.
    Otherwise you can also kill the process kill -9 <PID of the process>.
    Please do not terminate update and ENQ work process. This may lead to data loss. If the condition can not be control by killing some processes and again all the WPs are occupied. I recommend SAP system restart.
    Restart will ensure that all necessary roll backs happen and no data loss.
    With Regards,
    Saurabh

  • Launch TS sequence with operator interface

    create shortcut for launching a TS sequence with operator inteface.
    Right now, with Windows98,
    1. I doubleclick the test stand Labview Operator interface on the windows desktop.
    2. Click on File menu
    3. click /Select the sequence (at the bottom of File menu to launch the sequence in the Operator Interface.
    How do I create a shortcut to do these three steps?
    Double-click an icon on the desktop, launch the Operator interface and the sequence.

    Hi,
    I guess what you want to do is launch the OI and load a test sequence from the command line.
    Unfortunately you cannot do this with the LabVIEW Operator Interface as labview apps does not except the command line parameters.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • Problems in Operator Interface for LabVIEW

    Hi Ray,
    I am using LabVIEW 7.0 and TestStand 2.0 version. I am using the default operator interface for labVIEW provided in the TestStand and i am using custom step types in my sequence file.
    This sequence calls a VI, which transmits strings that i specify from the serial port to the NI-7831 RIO Fpga Card for differnt baud rates. The same sequence is working fine when called from Sequence Editor but it is not working when it is called from Operator Interface for LAbVIEW. It justs either fails the test or skips them. Please tell me if there is any solution for it. I have attached the sequence file and the vi that i am calling from my sequence file.

    Hi,
    You forgot to attach your sequencefile and VI, but never mind.
    I think the problem maybe that because you are using the default Operator Interface.
    If it still the one in the NI folder, then you will have to re build the testexec.exe application using your LabVIEW 7.0 Application Builder. The default exe file has been built using LabVIEW 5.1.1
    Before you start, copy the LV folder from OperatorInterfaces\NI\ to OperatorInterfaces\User.
    Load the testexec.bld file in your Application Builder and rebuild testexec.exe.
    Launch your new testexec.exe from the User\lV folder and retry your test sequencefile.
    Hopefully that should cure your problem.
    Regards
    Ray Farmer
    Regards
    Ray Farmer

  • How can I test the log in state from in side the Operator Interface code.

    From inside LabVIEW Full OI, I want to test if the operator logged in after the IApplicationMgr Start.
    Right after the IApplicationMgr ‘Start’ I have a loop that tests the IApplicationMgr ‘LoginLogoutRunning’ state and waits until the LoginLogout call back is done.
    I want to exit if the program if operator canceled the login and did not log in.
    I have tried “GetEngine” ref. From there get the “CurrentUser” ref but seems not to contain any information about the Current User.
    How can I test from my Operator Interface code logged in state of the application?
    Thanks
    Jim D.

    Try Engine.CurrentUserHasPrivilege
    For the string parameter 'privilegeName' enter Priv_UserLoggedIn or the string value "*".
    "Priv_UserLoggedIn–(Value: "*") Use this value with the Engine.CurrentUserHasPrivilege method to determine whether a user is logged in."
    Option 2: You could also setup a callback on application manager for UserChanged Event.  If the User is null then the login was canceled.  (see a copy of the help further down)
    From the teststand help for Engine.CurrentUserHasPrivilege method below...
    CurrentUserHasPrivilege Method
    Syntax
    Engine.CurrentUserHasPrivilege ( privilegeName)
    Return Value
    Boolean
    True if the current user has the privilege.
    Purpose
    Confirms whether the current user or any user group that the user is a member of has a specific privilege.
    Remarks
    Returns True when the privilege property is True, when the privilege property of any group that contains the privilege is True, or when privilege checking is disabled, StationOptions.EnableUserPrivilegeChecking is False. If privilege checking is disabled but StationOptions.RequireUserLogin is True, this function returns True only if there is a user currently logged on.
    Parameters
    privilegeName As String
    [In] Specifies the name of the privilege to check. You can specify the name of any privilege property. You can specify the full privilege path in the user privileges property tree, for example, Debug.RunSelectedSteps, or you can specify the base privilege name, RunSelectedSteps. If you specify only the base privilege name and more than one instance of the base privilege name exists, then the method returns the value of the first base privilege it finds with that name. Refer to UserPrivileges for more information.
    Teststand callback for UserChanged Event...
    UserChanged Event
    Syntax
    ControlName_UserChanged ( user)
    Applies To
    ApplicationMgr
    Purpose
    Occurs when the current user logged in changes.
    Remarks
    Use this event to update the parts of your user interface that depend on user permissions when the current user logged in changes.
    Parameters
    user As User
    [In] Current user. If this parameter is NULL, there is no user logged in.

  • How can I view TestStands Operator Interface front panel, from a VI, while a test is taking place.

    I need to view the sequences and steps that are displayed during a test session while running TestStand. Except I would like to view this in a LabVIEW front panel

    JD,
    I'm not sure if you're asking to be able to view the actual code module's front panel (ie. VI front panel) while it's executing, or if you just want to see the steps and overall sequence in a VI front panel. If the latter is true then you can use the simple LabVIEW operator interface that ships with TestStand, as Dennis mentioned in his answer. This would indeed be a great place to start if you want to add any further functionality to the operator interface. If the former is true and you want to see the actual VI front panels of the steps as they execute, you can check that box "Show VI Front Panel" from the "Specify Module" window in TestStand.

  • How can I get RTE information in operator interface (LV) from TS API?

    Hi!
    I have operator interface in Labview and use TS API to run tests.
    I would like to eliminate RTE dialog and to show error messages directly in front panel control.
    I have created callback for TS Application Manager BreakOnRTE event.
    It works good and I can lock dialog apearance.
    But if I try to get ErrorObject from event parameter (execution) is is empty (has no error information).
    But this parameter is real execution which contains step with RTE.
    When I allow the dialog appearance in this callback, it contains RTE information.
    Where can I get error information from this callback or get it any another way?
    Thanks in advance for any assistance.
    Solved!
    Go to Solution.

    I have found the way to get RTE from callback BreakOnRunTimeError of ApplicationMgr.
    This way is:
     Execution->GetThread[0]->GetSequenceContext[0]->GetRuntimeErrorMessageEx().
    It was not clear for me: all Error fields in step and Sequence are not filled yet on callback time.
    Only the context method can return error message.
    The question is closed.

  • How to change the status of test cases in Test Plan from Design to Ready using Excel VBA

    HI,
    How to change the status of test cases in Test Plan from Design to Ready using Excel VBA

    Thanks Florin,
    Your piece of code has worked alot, and it was very helpful in changing the Status of the Workitem to "READY" for all the Users fo the workitem.
    Points have been rewarded for your help.
    Process: We have acheived this using the "Work Item Exits", Usng "AFTER_EXECUTION" Method.
    Note: The Exit will be executed if "exit_cancelled"  statement is present/used in the work item method. if not it is not taking to the exit code. I'm unable to find the reason for it. Florin can u please explain this point.
    Please check the link for adding the code in Work Item Exits.
    http://wiki.sdn.sap.com/wiki/display/ABAP/ProgramExitsIn+Workflow
    Please find the Code:
    method IF_SWF_IFS_WORKITEM_EXIT~EVENT_RAISED.
    Get the context of the workitem
      me->wi_context = im_workitem_context.
    After execution of the workitem call the method AFTER_EXECUTION
      if im_event_name eq swrco_event_after_execution.
        me->after_execution( ).
      endif.
    endmethod.
    METHOD AFTER_EXECUTION.
    This method acts as the Event Handler for SWRCO_EVENT_AFTER_EXECUTION
      DATA: LCL_L_WID TYPE SWW_WIID,
            L_STATUS TYPE SWR_WISTAT-STATUS,
            L_NEW_STATUS  TYPE SWR_WISTAT,
            L_SWR_MESSAG  TYPE STANDARD TABLE OF SWR_MESSAG,
            L_SWR_MSTRUC  TYPE STANDARD TABLE OF SWR_MSTRUC.
    Get work item
      CALL METHOD WI_CONTEXT->GET_WORKITEM_ID
        RECEIVING
          RE_WORKITEM = LCL_L_WID.
      L_STATUS = 'READY'.
      CALL FUNCTION 'SAP_WAPI_SET_WORKITEM_STATUS'
        EXPORTING
          WORKITEM_ID    = LCL_L_WID
          STATUS         = L_STATUS
          USER           = SY-UNAME
          LANGUAGE       = SY-LANGU
          DO_COMMIT      = 'X'
        IMPORTING
          NEW_STATUS     = L_NEW_STATUS
         RETURN_CODE    = SY-SUBRC
        TABLES
          MESSAGE_LINES  = L_SWR_MESSAG
          MESSAGE_STRUCT = L_SWR_MSTRUC.
      IF SY-SUBRC EQ 0.
      ENDIF.
    ENDMETHOD.
    Thank You Once Again,
    Ajay Kumar Chippa

  • How to disable the run-time popup menu in the sequence display on TestStand Operator Interface, that allow the use to skip the test?

    How to disable the run-time popup menu in the sequence display on TestStand Operator Interface, that allow the use to skip the test?

    Hello,
                  Regarding the skip/force pass/force fail options, when I set the ControlExecFlow to True in Teststand 3.1 and 3.5, in the Sequence Editor the menu options for skip/force pass/force fail are not active for Technician but, when I launch the Operator Interface logged with Technician the options are active. The problem is that if the technician sets one step to one of these options, and change the user to Operator, the test step remains skip/force pass.
                  Is there any possibility without modifying the Operator Interface (at programming level), to reload default values of the steps when changing the user to Operator?
    Thank you,
    Best regards,
    paio

  • Operating level snapshot to prepare a test setup from a production database

    Hi ,
    Can any one explain the detaild process about Operating level snapshot to prepare a test setup from a production database
    Thank You

    Hi;
    Can any one explain the detaild process about Operating level snapshot to prepare a test setup from a production databaseMainly; We are using IBM disk and our disk team take snapshot of disk and we can work on those snapshot than storage team again revert back system orginal state.
    As you can see its performed by storage team contact wiht your vendor.
    If you dont have storage team than I suggest see my below post:
    http://heliosguneserol.wordpress.com/2011/12/08/11g-snapshot-standby-for-real-time-testing/
    Regard
    Helios

  • Send UI meassages from teststand sequence to Simple CVI Operator Interface with Asynchronous Timer

    Hello,
    Is it possible and how is it possible to send UI meassages from a teststand sequence to the Simple CVI Operator Interface with Asynchronous Timer which could be downloaded from NI Hompage. I use this problems because it is more stable than the standard OIs
    regards samuel

    This post could help:
    http://forums.ni.com/ni/board/message?board.id=330&message.id=7567
    Regards.

  • How to force SequenceFi​leUnload callback to run from within operator interface

    I need to force SequenceFileUnload callback to run from within operator interface arbitrary, with possibility to control execution flow.
    I.e. discarding object handle of execution object, which has client sequence file, which has SequenceFileUnload callback, causes it(SequenceFileUnload callback) to run. Unfortunately, after discarding execution object handle, it can be used to control execution flow(pausing, aborting, terminating).

    Thanks for the clarification. Here are the answers to your 3 questions:
    1) You can programmatically run any sequence (including callbacks) by using the TestStand API Engine.NewExecution() method.
    2) The Execution API object has several control methods for breaking, aborting, terminating, restarting, etc... All you need to do is obtain a reference to the Execution you want to perform one of these actions on and call the appropriate method on the reference. If you start the SequenceFileUnload callback with the Engine.NewExecution method, this returns a reference to the Execution object that you can call these methods on. If you don't use the NewExecution method, you can do a check in your UIMsg event handler for the StartExecution UIMsg event
    for an execution starting that is running the SequenceFileUnload callback, and simply manipulate the Execution reference the UIMsg contains as you see fit.
    3) To disable the SequenceFileUnload callback for a sequence file that is currently loaded. You can set the SequenceFile API object property "UnloadCallbackEnabled" to FALSE, and the callback will not execute for that file when it is unloaded unless you go back and reset the property to true before unloading. Note this property is reset each time you load the file.
    For more information on the TestStand API objects, methods, and properties discussed in this post, refer to the TestStand Programmer Help accessed through the Sequence Editor's Help >> TestStand Programmer Help menu selection.
    Jason F.
    Applications Engineer
    National Instruments
    www.ni.com/ask

  • Remove step icons from CVI Operator Interface to improve execution performance

    The CVI Operator Interface updates the icons for each step (lower right) when tracing is enabled. Can these be stopped but the steps still visable and would this improve execution performance.

    Hi Dave,
    I take it you are using the old style Teststand Operator Interface.
    The only way would be to modify the code in the exedisp.c, in UpdateOnStepChange() function. Just comment out the SetCtrlBitmap() function there are two calls in this function.
    As to whether it is going to make a noticable different in performance, well that depends on the spec of the controller (PC), graphics card etc. you are using. But you probably wouldn't notice any diference.
    Before you make any changes, copy the sub-folders from the NI folder to the User folder and work from the User folder.
    Regards
    Ray FarmerMessage Edited by Ray Farmer on 05-07-2005 06:29 PM
    Regards
    Ray Farmer

  • Work status from the BPC for Excel interface

    Hello everyone !
    I got an issue on version 7.0M of BPC with WorkStatus. When i try to access to the work status from BPC the page won't load but i can access to it by the Web. Do you have any clue about that ? 
    It it the BPC server configuration ? The web site is with ASP2.0 is it an issue ?
    Best regards,
    Damien

    The problem seems to be related to how you configured the BPC application and web server.
    Just check table tblapsetinfo and tblserverinfo from database appserver to see if you have right configuration.
    I mean if you have the same name (FQDN or IP) for both application server and web server.
    Osoft virtual directory must work using .Net 1.1 no t2.0.
    Regards
    Sorin Radulescu

  • I am trying to use the T. S. operator interface I need to add pass fail and error

    Hello:
    I  am using Labview 6.1 and Test Stand 2.0
    I have made some modification to a copy of the T.S. Labview operator interface. How do I get the pass/fail or error from test stand to be pass to LabView so I can tell the operator that the unit pass or fail the test. I do not want to use the Test UUTs. I want this to be very low operator response.
    Message Edited by Toro on 02-28-2006 01:52 PM

    Not sure if this is available in the earlier versions of TestStand, but I think so.
    You could post a UI Message, from your execution entry point in the process model, to your User Interface indicating the pass/fail/error status when a test run is complete.  You will need to handle the UI Message in your Operator Interface.  See TestStand II Customisation course notes for handling UI Messages.
    The data passed in the UI Message can be anything you like, the UI Message handler in the User Interface will have to process the message and update the display as required.
    Hope this helps
    Steve
    Message Edited by SercoSteve on 03-01-2006 10:02 AM
    There are 10 types of people in the world that understand binary, those that do and those that don't.

Maybe you are looking for