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

[Abdulla]

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

[Dennis_Knutson]

If you have Check User Privileges turned on and you have the users login with the operator profile, the option is not available. The default technician profile allows this and I think it's very handy for a technician to skip a step when trying to debug a UUT, but you can modify the technician profile to exclude them as well.

[paio]

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

[nickb]

Hi Paio!

I think that the best way to accomplish this would be to edit the FrontEndCallbacks sequence.  Here you could set up a post expression on the logout of the user that closes the sequence.  When the operator opens the sequence back up, the options that the technician has changed should be gone,  because the technician can not save his work by default.  However, if you are allowing your technician to save his work, this solution will not be as effective.  Let me know if you have any further questions!

NickB

[paio]

Hi NickB,

I understand what you mean but I don't manage/know how to set up a post expression that closes the sequence.

Can you please help with that also?

Thank you,

Best regards,

paio

[nickb]

Actually, as I think about it again, if your user logs out before logging in, all of the sequences should close.  If you just go to log in without logging out, as it seems is the case with your situation, you will need to add a step to close open sequences.  This can be accomplished by placing an ActiveX action step after the login step of the FrontEndCallbacks sequence (which can be found at <teststand>\components\ni\callbacks\frontend).  The automation server will be "NI TestStand API 4.0 (or whatever your version)", the object reference will be runstate.thread, the class will be thread, the action will be Call Method, and the method will be PostUIMessage.  The event code will then be UIMsg_CloseWindows, the numericDataParam will be 0, the stringDataParam will be "", and synchronous will be False.  Then go to the properties of the Login step, and edit the Post Action so that  On Condition True, you go to the ActiveX action step you just created.  Let me know if this does not seem to match your needs, or if you have any other questions!

NickB

[paio]

Hi NickB,

 Well that worked very well and it was almost what I needed. What was missing is that I had to add the Engine.TerminateAll also for uncompleted executions.
 Thank you very much for you prompt answers and for your big help.

Thank you,
Best regards,
paio