I am trying to understand how UI controls work in code modules called by TestStand steps. I can pass a reference to an Application Manager (perhaps the application manager?) to my code module using RunState.engine.GetInternalOption(InternalOption_ApplicationManager). Does the sequence editor have an application manager? Or the engine? Is this the same as the Application Manager control I put on the front panel of the code module? What about SequenceViewManagers and ExecutionViewManagers? Can I create those in my code modules to display sequences or executions? Or can I somehow get those from the sequence editor/engine, or from the Application Manager? I know that I just asked a lot of questions, but I guess what I am looking for is some general guidelines for using the manager controls in code modules. This all came about by an attempt to display an Execution View Manager control in my code module. Feel free to ignore the following description of my various attempts to get this to work. This exercise helped me understand the managers a little bit more, but I'm still a little confused. Suppose I want to create a custom step type for debugging to display the variables for the current sequence context on the front panel of a code module VI. (LabVIEW 8.6, TestStand 4.1.) In my code module, I call ExecutionViewMgr.ConnectVariables to connect to a VariableView control. Where do I get my ExecutionView Mangager from? I tried two methods: 1) create an ExecutionViewManager control; set the manager's current execution using ExecutionViewMgr.Execution (pass RunState.Execution from TestStand to the code module). It seems like this should work, but when I run my sequence from the sequence editor, the ExecutionViewMgr.Execution property node returns error -17500. When I run from a LabVIEW Operator Interface (using the LabVIEW environment, not the exe), I don't get an error. But I must connect a list control using ExecutionViewMgr.ConnectExecutionList, and select the execution from the list when the code module is running. Then I can see the variables when I select the execution in the list. However, the execution display on the OI goes blank. I can see either the variables on my code module or the execution on my OI, but not both simultaneously. It appears that an execution cannot be attached to more than one manager at once (I guess that's reasonable).2) pass the result of RunState.engine.GetInternalOption(InternalOption_ApplicationManager) to the code module; set the manager's current execution using ApplicationMgr.GetExecutionViewMgr() (pass RunState.Execution from TestStand to the code module, then as a parameter to GetExecutionViewMgr() ). In this case, I would expect that there is no ExecutionView Manager associated with the execution when running from the sequence editor. But the ApplicationMgr.GetExecutionViewMgr() function returns a non-Null reference. ExecutionViewMgr.ConnectVariables() causes an error dialog to be displayed (from the function itself, not from TestStand), although it doesn't actually output an error (and the VariableView control remains blank). The error is "Unable to connect Variables View control." (See attachment.) When I run from my LabVIEW OI, it works perfectly--I see the variables on my code module's UI, and the execution appears on the OI simultaneously. I guess this makes sense since the TestStand engine is returning the Execution manager that was already created by the OI.

NI TestStand

Author

Scott, thanks for that information. This has been very helpful. I don't suppose you have any examples of either of the two schemes?

Message 11 of 12

(1,133 Views)

jsiegel -

I am not aware of any KBs that we have available to demostrate these suggestions.

Scott Richardson
https://testeract.com

Message 12 of 12

(1,102 Views)

What do you need our team of experts to assist you with?

How can we help?

Please enter your information below and we'll be intouch soon.

This field is required

Preferred communication method

Email Phone call

What do you need our team of experts to assist you with?