09-07-2017 01:22 PM
Just upgraded my project to LabVIEW 2017 and I am seeing a random problem where messages occasionally fail. I have built a AF based sequencer using LabVIEW 2015 and have used it successfully in many projects. That same codebase running on 2017 on both Win 7 Pro 32 bit OS and Win 10 64 bit OS has issues. I have reverted the code back to 2015 and it is running without issues again. Has anyone else experienced problems under LV2017?
-Don
09-08-2017 01:04 AM
I am chasing down some issues after switching to 2015.
In my case, I do think, that there might be an issue with changed timings leading to unwanted / unforeseen behaviour to to the asynchronous nature of the AF.
09-22-2017 02:58 PM
Hi Don,
What do you mean by messages 'fail'?
We are considering the same thing... currently using 2015, and like to upgrade to 2017, but your post is making me concerned.
Thanks,
John
11-01-2017 02:43 PM
I missed this when it was first posted.
There are no substantive changes to the AF between 2015 and 2017 in the queue behaviors. No one else has reported any issue like this. If you have code that is failing in 2017, can you share it with NI?
01-01-2018 08:52 PM
I am happy to report that I traced the issue to a method I was using to flush an event buffer queue. The issue was not a bug in LV2017.