Version Conversion

cancel
Showing results for 
Search instead for 
Did you mean: 

convert to 2025

i want it to be at 2025 version 

0 Kudos
Message 1 of 5
(173 Views)

You can open a VI in a later version of LabVIEW. You don't need a conversion. Make sure you have the required modules or toolkits installed, if any.

-------------------------------------------------------
Applications Engineer | TME Systems
https://tmesystems.net/
-------------------------------------------------------
https://github.com/ZhiYang-Ong
0 Kudos
Message 2 of 5
(131 Views)

@ZYOng wrote:

You can open a VI in a later version of LabVIEW. You don't need a conversion. Make sure you have the required modules or toolkits installed, if any.


Mostly correct. Unfortunately, the VI is still stuck in a virus scan and we cannot inspect it, but anything older that LabVIEW 6.0 cannot be opened in a modern LabVIEW version.

 

Good point. This looks like a VI that requires suitable drivers matching the bitness of the VI, so if you get an error it could be due to missing drivers, not a version incompatibility. What is the exact error you get when you try to open it in LabVIEW 2025?

 

Where does the VI come from? That "17." at the start of the filename suggest it might be from a tutorial, course, or even supplementary to a book.

0 Kudos
Message 3 of 5
(121 Views)

The file is currently saved in LabVIEW 2011. LabVIEW 2025 can open this VI with no issues. No conversion necessary.



There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
0 Kudos
Message 4 of 5
(90 Views)

@mahmoud2121 wrote:

i want it to be at 2025 version 


As has been said, you can easily open it using LabVIEW 2025 and if you then save it, it will be in the 2025 version.

 

The VI is just a simulation and does not require any drivers or toolkits. All parts are included in LabVIEW base. It is basically an ugly pile of express VIs wired together with dynamic data running in a greedy loop. At least the simulation should be set to "simulate acquisition timing" instead of "run as fast as possible".

0 Kudos
Message 5 of 5
(78 Views)