LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrading Older LabView version 13.0 Software to 2025 version

Hey there all,

 

I am new to LabVIEW and was wondering how to upgrade older LabVIEW .vi files to be compatible with the newest version of LabVIEW.

 

Background:

 

I am running LabVIEW 2025 Q1 and receive the following message when trying to run software located in this github repository: https://github.com/LibourelLab/BiofloSoftware

 

LabVIEW: (Hex 0x623) You cannot open a packed library saved in a version earlier than the current version of LabVIEW. The file {filename} could not be loaded.

 

However, after closing about 10 of those dialogs, the project finally opens up and I can see some files, but it is having trouble finding all of them. 

 

Question:

Is there a way to open these files and just look how they are laid out so I can try implementing them in the newer 2025 version?

 

Thank you for any help in advance.

 

0 Kudos
Message 1 of 3
(197 Views)

Every LVLIBP file is a "packed library", so you should get that popup once per LVLIBP in the repository that you load.

 

LVLIBP files are built from LVLIB files and their contents, so if you look around, you should see one LVLIB file in there per LVLIBP file that gives you an error.  Just open those up, and see the VIs inside them.

 

If you want to use them all in 2025, you will need to open each LVLIB in turn (probably in its own LVPROJ file), and re-build the LVLIBP file that it generates.  I'm not looking closely at the program structure, but there's a chance that these are built in a hierarchy, as some LVLIBP files will reference other ones.  If so, you will need to be sure to build them in order, with the highest tier of them (no dependencies on any other LVLIBP  files...) built first.

Message 2 of 3
(171 Views)

The application is based on an old version of the Actor Framework. Nowadays it is shipped with LabVIEW. You will first have to build it into a PPL and replace the Actor Framework.lvlibp files. Then rebuild the PluginInterface and replace those PPLs. Afterwards, I think you can rebuild the Plugins.

You will probably still be prompted for some files because their location changed.

 

The example finder has a project how to build the Actor Framework into a PPL:

<examples>\Application Control\Actor Framework As PPL\Actor Framework as Release PPL.lvproj

note you have to change the output name to include a space ("Actor Framework.lvlibp" instead of "ActorFramework.lvlibp")

 

If the project requires more AF files, try this guide:

https://forums.ni.com/t5/Actor-Framework-Discussions/How-to-build-a-PPL-including-Actor-classes-mess...

 

Message 3 of 3
(138 Views)