LabVIEW user interface event structure "priority"

Do Pane events get processed first and then control events?
I have a VI that checks a value change of button that is latched and it also checks for the mouse down event on the Pane. I noticed that the Pane event gets processed and then the value change of the button. This is not too critical at this point for my project but was curious if this is on purpose.
Attached is a VI that does this.
Attachments:
Pane vs Control Events 2014.vi ‏11 KB

When debugging what event occures in what order, I usually find the Event Inspector Window helpful. It basically tracks the queue that LabVIEW uses and shows the order that events are generated and handled.
http://zone.ni.com/reference/en-XX/help/371361K-01/lvdialog/event_inspectorwindow/
https://decibel.ni.com/content/blogs/Sixclear/2013/11/04/vi-high-51-event-inspector-window-flushing-...
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Similar Messages

How can I give the "user interface thread" higher priority?

We do alot of activex calls to front panels. We need to increase/decrease the priority of the user interface thread to resolve our thread problem. Anyone know how to do this?
Chuck

Hello,
As P.M. was saying, you can adjust the thread priorities
through the VI Properties dialogue.
Another place to modify the multithreading system in LabVIEW is a VI
located at: [LabVIEW Directory]\vi.lib\Utility\sysinfo.llb\threadconfig.vi. However I do not think this will remedy any
problems you are having.
From a Multithreading in LabVIEW tutorial (http://zone.ni.com/devzone/conceptd.nsf/webmain/d2e196c7416f373a862568690074c759)
Priorities in the User Interface and
Single-Threaded Applications
Within the User Interface execution
system, priority levels are handled in the same way for single-threaded and
multithreaded applications.
In single-threaded applications and
in the User Interface execution system of multithreaded applications, the
execution system queue has multiple entry points. The execution system places
higher priority VIs on the queue in front of lower priority VIs.
If a high-priority task is running and the queue contains only lower priority
tasks, the high-priority VI continues to run. For example, if the execution
queue contains two VIs of each priority level, the time-critical VIs share execution time exclusively until both finish.
Then, the high priority VIs share execution
time exclusively until both finish, and so on. However, if the higher priority
VIs call a function that waits, the execution system removes higher priority
VIs from the queue until the wait or I/O completes, assigning other tasks
(possibly with lower priority) to run. When the wait or I/O completes, the
execution system reinserts the pending task on the queue in front of lower
priority tasks. Refer to the Synchronous/Blocking Nodes section for a list of
asynchronous functions that wait.
Also, if a high priority VI calls a lower priority subVI,
that subVI is raised to the same priority level as the caller for the duration
of that call. Consequently, you do not need to modify the priority levels of
the subVIs that a VI calls to raise the priority level of the subVI.
Thus changing the priority of your VI will change the
priority of UI calls for that particular VI.
Again, I caution you because I suspect that if you are having problems
with your application not running correctly, I do not believe that manipulating
the thread priorities will resolve these issues.
Hope this helps,
Travis M
LabVIEW R&D
National Instruments

How to get the value of the global variable of test stand in labview User interface?

Hi.
Can anyone Please share examples and tell me to how access the test stand global variable using labview user interface.
Solved!
Go to Solution.

I'm not surprised that what you are doing doesn't work. The Start Execution UI Message is triggered when the user clicks a button to start an execution. Realize that most executions go through a process model. So you could be looking at the sequence context of the process model and not your client sequence file.
I recommend reading that link I posted above. UI Messages are your best bet but you cannot just piggy back on an existing UI Message like this. They may not be getting sent at the time you need them to be. The only way to ensure you get what you want is to trigger one yourself at the right time.
Regards,
jigg
CTA, CLA
teststandhelp.com
~Will work for kudos and/or BBQ~

Reading the output values after each step executes in LabVIEW User Interface

Hello all,
Development environment: TestStand 2010 SP1 and LabVIEW 2010 SP1
Problem: is there a way to execute the subsequent steps programatically and get the output values from each of them?
I have already extended a little bit a Full OI interface for TestStand to load up any sequence, choose some of the steps and run them step by step (something like option to Run Selected steps). What I am trying to do is to add some actions between each step and do that in User Interface (I can't modify the sequence!), so I am starting the NewExecution with some previously configured InteractiveArgsParam and set an option breakAtFirstStep to True. Afterwards I am just doing something like Step Over when debugging the sequence and this works good, but I didn't fine a way yet to read the output values from the steps...
Then, if I wait until the execution finishes I can read my Results by processing the ResultObject, but this works only after finalizing of the test sequence. Since I wanted to stop after each step, read the values, do some actions and continue to the next step I tried to register an event callback for Trace of Execution View Manager. I can see that after each executed step this event is triggered, but when I try to read a ResultObject returned in Event Data it is not filled with values (ResultList seems to be empty?). Is it a proper behaviour or maybe I am doing the readout in wrong way? (It is the same VI as for reading ResultObjects after sequence finishes and there it works fine for arrays, containers and other data types).
Like I mentioned I can't modify the Test sequences, I can't add a UImessages.
What are my options? Should the trace event returns all output values from each steps or is it just used for status checking? Or maybe there is completely different approach to that matter?
Thanks in advance for any suggestions,
Best Regards.
CLA, CTD, CLED @ Test & Measurements Solutions Poland
Solved!
Go to Solution.

Thanks for your replay, I have tried to build it in my LabView Block Diagramm, es seems like this image.
But the variable GetNumSubProperties ist always 0. Why?
PS: I need only the variable "Step.Result.PassFail" from the last step, do you know, how can I get it? I think, it is maybe easier than read all the "Result".
Attachments:
ReadStepResultInLabview.JPG ‏39 KB

What are the Dynamic Events avaliable in the LabView 6.1 Event Structure?

I recieved LabView 6.1 recently and I am working with the Event Structure, and I'm trying to figure out what Dynamic Events are avaliable in the event structure, and how to access them. If you don't understand what I'm talking about, open a new VI in LabView 6.1 and drop an event structure on the diagram. Add an event and look at the dialog box that appears on the screen, specifically the Event Sources section. The third option in this area of the screen is "grayed out" but reads "Dynamic". I'm curious what these events are, and how I access them. I'm running WinNT 4 SP6.
Thanks,
Chris Davis

I believe this is part of a feature which is not yet present in LabVIEW 6.1, but may be present in a future release.

LabVIEW 2012 while event structure cannot stop

I am trying LabVIEW 2012.
An example of while-loop with Event structure inside cannot be stopped with the boolean stop button. Any thing wrong?
Please see the attached VI.
Thanks.
Solved!
Go to Solution.
Attachments:
Close VI prompt.vi ‏9 KB

Yep, something is wrong. You need to add a event case to detect a value change on the stop button.
The thing is now your event structure keeps waiting for one of the event that it handles, and ight now it only handles the "panel close" event, the "timeout" event is handled too but since you haven't connected anything to the timeout terminal (top left corner of the event structure) the timeout is -1. So when you run the VI the while loop is stuck in the first iteration and waits for a panel close, the stop button will only be taken into account after the even structure catches an event ; I think this is because LabVIEW will execute code linked to the stop terminal of the while loop only after all the rest of the code in it has finished executing.
Hope this helps
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

Accessing TS Watch view window in LabVIEW user interface?

HI All
I am trying to build TS user interface in LabVIEW. I want to give ability to user to debug sequence while running.(ability to put breakpoint and view the value of variables in watch view window).
Can we access TS watch view window in LabVIEW .I did not find any activex control for it.
If not how can you give user ability to debug sequence?
Does anyone have idea about this?

hi
I have tried using that.Call stack gives you option to view current execution from the list of executions.(Call stack in TS basically).
It does not give you watch view interface .
Basically I want user to give option to debug sequence . So on the execution view control he should be able to put breakpoint and then once execution reaches breakpoint , he should be able tov view variables values by adding them in watch view pane.
any ideas how to do this?

How to create Labview User Interface with buttons?

Hello,
I try to create a user interface, where the TestStand sequencies can be selected one by one not only Test UUT, Single run and run Mainsequence (about 20 buttons needed).
I'm playing with the simple UI shipped with TS and can load the sequence file and run automatically a sequence (Main or another).
How can I create and assign buttons to all sequence files in my TS project?
Any help would be appreciated.
Thanks. (TS 4.0, LV 8.0)

I've modified my main VI with the below steps.
I still don't know how to create and assign front panel buttons to the user interface.
Anybody could explain to me how do I need to modify the attached part of my main vi and how to assign buttons.
Thanks.
Attachments:
InteractiveArgs_2.png ‏12 KB

Access to ResultList objects from Labview user interface

Hi!
I would like to have access to TS Locals.ResultList[] objects from user interface (LV) after test report is generated.
According to TS Help in this point I can get sequence context for the process model sequence file which posts UIMsg_ModelState_PostProcessingComplete message.
But objects of my interest are located in context of client sequence file.
Can I get access to Locals.ResultList objects with use provided model file context?
Are there another ways to get wanted data?
I have references to sequence file and execution in this point and tried to use Execution.RunTimeVariables property.
But could not get wanted data with any supposed lookup string from this object.
Thanks in advance for any ideas.
Solved!
Go to Solution.

The general idea is the following:
You have to keep in mind that Locals.ResultList on the model level (callstack) is simply the return value of a sequence call step (MainSequence). Therefore, you will only have this single entry [0].
To get access to the results of the steps inside you MainSequence (and any other sublevel in the callstack), you have to dig into this callstack using this "root-property":
Locals.ResultList[0].TS.SequenceCall.ResultList
hope this helps,
Norbert
[EDIT]: Since i have not stated it: The screenshot displays the UIMessageEvent callback function in a simple oi where the manager control is the Application Manager.
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Additional labview user interface windows?

Hi there,
I am currently writing a control/monitoring program with labview. I am wondering if it is possible to have a button/link in my front panel to open an additional front panel which displays more detailed information of the same program (i.e. history graphs, numerical indicators, etc.).
Thanks,
Daryn

Daryn,
Yes. When you want to display the detailed information, call a subVI which has the desired indicators on its front panel. Under VI properties (Window Appearance >> Customize..), set it to Show front panel when called and Close afterwards if originally closed. These options have been avaiable since the LV 1 or 2 days.
Lynn

VI containing Event Structure will not receive front panel events in LabVIEW Real-Time.

Hi again, I'm working in my first UI (attached VI).
It works when running directly from PC. It doesn't when running from cRIO, there's the message "VI containing Event Structure will not receive front panel events in LabVIEW Real-Time". I've been reading and I found that "Event structures on RT targets do not support events associated with user interface objects, such as VI panels or controls. For example, associating the Value Change event with a control does not work. RT targets support only user events".
Is that the problem? If it is, how can I create Mouse Up, Mouse Enter, Value Change (or other user interface events) user events?
If I run my VI in FPGA mode should it run?
Attachments:
HMI.vi ‏33 KB

Since it looks like you are new to the whole RT and machine control, I recommend giving this a good read: NI LabVIEW for CompactRIO Developer's Guide
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines

Event structure react to programmatic events in Labview 7

I originaly thought, that Labview 7 would have the option to have the event structure react to programmatic changes. That's what I thought "dynamic" support would do. Instead, it doesn't seem to be the case. Is there a way to make an even structure react to a "programmatic event" in Labview 7?

You can do what you want, although your terminology is a little off. You can use the User-Defined Events which are new to LabVIEW 7.0 to create and generate programmatic events. There is a shipping example calling "Programmatically Fire Events." This is an example of User-Defined Evenst.
When you say "dynamic" events, you are probably referring to "dynamically registered" events. This is different. This means that you can register and unregister an event programmatically. Now, this can either be User-Defined events or just the user interface events which are available by default. The LabVIEW Zone currently has an article up by the developer who built these feature
s so I would suggest taking a look at that. It should help get you started on this. They're certainly a very powerful new tool, but also very advanced.
J.R. Allen

How can I tile up the execution window in the Labview Teststand user interface

I am using the Labview User interface provided with the TestStand development environment.
Running the BatchUUT.seq Example using the TestStand Sequence Editor, you will see that the Execution Window will be divided in 4 windows showing the execution status of the 4 UUTs.
Running the same Sequence using the provided Labview User Interfaces (Simple or Full-Featured) will just show one window with the execution status.
Is there a way to tile up the window to display the execution status in the Labview User Interface?

Try something like this:
You wouldn't use random numbers of course, but rely on already opened clones. So you would extend the "Manage Clones" to manage the data for the window position, but set it for each clone in the way the screenshot shows.
hope this helps,
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

Is it better to have one Event Structure with more (10 or 15) cases or several with fewer?

I have several buttons and events on the GUI of my app to monitor. Would it be better to use one Event Structure with several cases (10 or 15) or have a couple and split the cases evenly? None of the cases have much processing to handle, so there is not a time lag issue. I am just worried about overloading the structure. One of the tech support guys mentioned that the event structures are not that hard to get confused.
Has anyone had any problems with Event Structures?

I use event structures very often in my code. I use them just to handle the interface and to run small code. I have had event structures that handled over 50 user interface events and never had a problem. In my personal opinion If there was any code to run I would let the event structure handle the the user interface event that fired a que in another while loop that handled the code.You can find examples on this, if not I will send you one. It is just good programming practice for beginners because it will alow you to build more robust VI's in the future.
Hope this helps
Joe
Joe.
"NOTHING IS EVER EASY"

How to control the tab control using event structure?

Hi,
I am using tab control and event structure in the program.
When i run the application event is not happening for the active page.
When user switches from active page to the other page then event is taking place for all pages
So, how to get the event trigger for the active page when the application is started
For more clarification i am attaching the code "Test Control Tab using Event Structure.vi"
Attachments:
Test Control Tab using Event Structure.vi ‏52 KB

You have a basic misunderstanding of dataflow. Maybe you should start with some tutorials or study some of the examples that ship with LabVIEW.
The event structure belongs inside the while loop, and not vice versa. RIght now, the event structure only runs exactly once and never again.
If the stop is pressed first, the VI will stop. Game over.
If the tab control is changed (from any state to any other state!), the inner loop will spin forever as fast as the CPU allows, either executing one or the other case. It just reads the tab terminal to decide which case to execute. Changing tab never triggers any events. The VI is trapped inside the event until stop is pressed to stop the VI.
you were closer to a reasonable program in the other thread:
http://forums.ni.com/ni/board/message?board.id=170&view=by_date_ascending&message.id=287905
Have you tried execution highlighting? Maybe things would become more clear of you do.
LabVIEW Champion . Do more with less code and in less time .

LabVIEW user interface event structure "priority"

Similar Messages

Maybe you are looking for