11-28-2013 10:59 AM
The attached VI can be used to demonstrate that the order that events are handled by the event structure is not deterministic. (i.e. it can't be deducted from the order in which they are generated). Placing the user event generation at different locations in the sequence renders unexpected results. In LabVIEW 2013 however the behaviour is deterministic (i.e. it follows the logic that I always apply, events are handled in the order that they are generated.
My question:
Can anybody confirm this in LV 2012 (wrong behaviour, IMO) and LV 2013 (expected behaviour, IMO)?
We need to make a choice to move a large project to LV 2013 asap or postphone it a little.
Many thanks for people that try.
VI is saved in LV 2012.
Solved! Go to Solution.
11-28-2013 11:17 AM
The given VI works as expected in LabVIEW 2012 and 2013. Do you have a sequence order that does not give the expected result?
Attached is a slightly more comfortable testing version.
11-28-2013 12:56 PM
11-29-2013 04:32 AM
Hi,
I tested with you modified version and it still doesn't work as expected, as expected. But I have some test results that I can share now. In the attached zip file you can find 4 images: "LV12_N1_UE_N2_wrong.png", "LV12_UE_N1_N2_wrong.png", "LV13_N1_UE_N2_OK.png" and "LV13_UE_N1_N2_OK.png".
LV12.0.1f5 ad LV13.0f2.
LV12_N1_UE_N2_wrong.png: expected order of event handling -> "LV13_N1_UE_N2_OK.png".
LV12_UE_N1_N2_wrong.png: expected order of event handling -> "LV13_UE_N1_N2_OK.png".
LV12_UE_N1_N2_wrong.png: Results between single run and continuous run differ, single runs seems OK.
IMO it looks like a race-condition between control events and user events.
11-29-2013 07:44 AM - edited 11-29-2013 07:48 AM
Hello Mr. Buurman,
I'm not able to reproduce this on a LabVIEW 12.0.1f5 pc.
That's really unusual and I haven't seen that before.
Do you have any other PC at your disposal where you can reproduce this behavior?
Can you share a MAX Report with me?
General question: Can anyone else on the forum reproduce this?
11-29-2013 07:49 AM
Here's my screen capture:
11-29-2013 07:56 AM
I can't look at the code, but based on the description it sounds like what was discussed in this thread - http://lavag.org/topic/9986-out-of-order-events-is-not-a-bug-sort-of/
The good news is that the changes made to events in 2013 also included the fix for this issue, so I would say that you should upgrade (or use one of the workarounds described in that thread).
11-29-2013 08:02 AM
Thank you for posting this link, it explains the behaviour I see and validates my own conclusions. At least it is now a known problem with work-arounds.
12-02-2013 03:11 AM
What Tst said.
I have also seen this problem in the past (and had trouble convincing others the problem was real) and the changes in LV 2013 are a very welcome fix to this annoying behaviour.
Shane.
12-03-2013 07:14 AM
Thanks to everyone for the feedback!
I had not yet experienced this myself, so thanks for making me aware of it!