LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Can you REVERT multiple VI's to an older version?

I have LV 2018 on PC1 and LV 2017 on PC2 and would like to revert all of the 2018 VI's to 2017.  Is it possible to do this on multiple files?

 

The real issue is the licensing, both machines are mine and I will only use one at a time.  I can't upgrade the 2017 machine to 2018 so I'm looking to revert.  Any help would be greatly appreciated.

0 Kudos
Message 1 of 8
(1,854 Views)

Have you tried saving for previous version from the project window (assuming all VIs are part of the same project)?

Lucian
CLA
0 Kudos
Message 2 of 8
(1,844 Views)

You can Save For Previous Version... a whole project. All vi's will be saved to a directory (possibly with subdirectories) of your choice.

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 3 of 8
(1,838 Views)

yes i can do that, but i have 100's of projects.  Hoping there is a way to revert a group of projects at once.  

 

OR

 

If I could share my license to multiple machines that would work too, doesn't seem like an option with the way NI does licensing though.  I'm a little confused on the licensing though so if there is a way to just upgrade the 2017 to 2018 let me know.  The LV S/N is the same for both machines but i can't get the 2018 version on the 2017 machine...confused.

0 Kudos
Message 4 of 8
(1,828 Views)

@coolhandLV7 wrote:

yes i can do that, but i have 100's of projects.  Hoping there is a way to revert a group of projects at once.  

 

OR

 

If I could share my license to multiple machines that would work too, doesn't seem like an option with the way NI does licensing though.  I'm a little confused on the licensing though so if there is a way to just upgrade the 2017 to 2018 let me know.  The LV S/N is the same for both machines but i can't get the 2018 version on the 2017 machine...confused.


Why do you need to install the LabVIEW development environment on multiple machines? You should be building executables and deploying them, as there is no license required to run a LabVIEW executable. In fact you (your company) can even sell your executables.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 5 of 8
(1,815 Views)

because i need to develop in different locations.  Ideally i'd "Check out" the license and do my work, i don't think it's possible though.  This is one of the main reason my company is dropping LV altogether, there are a few of us left though.

0 Kudos
Message 6 of 8
(1,812 Views)

This snippet may help you, if you are able to get a list of your projects some way.

However, depending on the project, the backsave may not work fully automatic, for example if there are password protected vi's.

I did not test much, so there may be other drawbacks. I got one project converted with no problems though.

 

save-for-previous.png

 

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
0 Kudos
Message 7 of 8
(1,790 Views)

@coolhandLV7 wrote:

because i need to develop in different locations.  Ideally i'd "Check out" the license and do my work, i don't think it's possible though.  This is one of the main reason my company is dropping LV altogether, there are a few of us left though.


I support several ATE systems and various test applications in our lab.

 

I have the LabVIEW development environment on a laptop so I can take it out into the lab to develop or troubleshoot test systems.

 

Then build an executable and leave that on the test station computer.

========================
=== Engineer Ambiguously ===
========================
0 Kudos
Message 8 of 8
(1,776 Views)