labview 2016 + windows 10 slow down

[ana+]

Hello:

I have designed an application I use in my classes: two projects, each of them with just one .vi, that share information via shared variables using the DSC module; the values of one of the variables are read from an Arduino using the Arduino blocks provided by LabVIEW and Lifa BASE.

On previous years the application worked on Windows 7 and LabVIEW 2009 and 2015. This year we have new computers and we have updated our software to LabVIEW 2016 and Windows 10. The result is that the applications has slowed down so much that it becomes useless. It takes several minutes to before the .vi runs after launching them, and it takes much more time (15-20 minutes) if you try to stop them.

Is there anything I could do to solve this issue? Thanks a lot in advance for your help.

Kind regards,

Ana+

[RavensFan]

Are these .vi's running in the development environment, or an executable you have built with the application builder?

If they are VI's, have you done a full save of the all the files after opening in LV 16?  (My thought here is that if you are opening files saved in LV9 withing the LV 16 environment, LabVIEW needs to recompile everything in the background before running.  But it wouldn't explain a long shutdown.)

Attaching your project as zipped up .vi files would allow us to see if there is anything unusual in there that could explain the slow downs.

[RTSLVU]

LIFA has long since been deprecated and replaced with LINX 

Not that that alone explains what you are seeing.

[ana+]

Hello,

Thanks you all for your answers. Finally the problem has been solved:

- I use two projects with several shared variables that interchange information between the projects. Both projects run inside the LabVIEW environment.

- As you commented, the LIFA library was not the problem, and still works fine with LabVIEW2106.

- It seems that the problem was caused because both projects were created in 2009 versions and then loaded (apparently without errors) in the 2016 version. Especifically, it seems that the problem arises with the historical trend block of the DSC module. This block requires a database in order to retrieve from it the shared variables to be displayed, and it seems that it did not load that database properly. I have deleted the historical trend I had in my project, I have added a new one, and then I have selected the 2009 database when picking the shared variables to be plotted. And now it works 🙂

Again, thank you all for the interest and the help. Kind regards,

Ana+

[billko]

---

@ana+ wrote:

Hello,

Thanks you all for your answers. Finally the problem has been solved:

- I use two projects with several shared variables that interchange information between the projects. Both projects run inside the LabVIEW environment.

- As you commented, the LIFA library was not the problem, and still works fine with LabVIEW2106.

- It seems that the problem was caused because both projects were created in 2009 versions and then loaded (apparently without errors) in the 2016 version. Especifically, it seems that the problem arises with the historical trend block of the DSC module. This block requires a database in order to retrieve from it the shared variables to be displayed, and it seems that it did not load that database properly. I have deleted the historical trend I had in my project, I have added a new one, and then I have selected the 2009 database when picking the shared variables to be plotted. And now it works 🙂

Again, thank you all for the interest and the help. Kind regards,

Ana+

---

Good to know LabVIEW will be around for nearly another ninety years.  😉

[ana+]

It would be better to know that *we* will be around here another 90 ninety years 😉

[billko]

Or the planet, even.