LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

OpenG librarys Bug in LabView 2024

Solved!
Go to solution

I tried to install the OpenG libraries using VIPM, but after installation, all VIs are set to version 20.0 (in VI properties). When I mass compile them, they upgrade to version 24.0. However, after restarting LabVIEW, the version reverts to 20.0. I have tried selecting and deselecting "Separate compiled code from source," but it does not work. I want to upgrade all OpenG libraries to version 24.0 so that my project works correctly. Can anyone help me find a solution? Thanks.

0 Kudos
Message 1 of 14
(714 Views)

@Hatimelaiha wrote:

I tried to install the OpenG libraries using VIPM, but after installation, all VIs are set to version 20.0 (in VI properties). When I mass compile them, they upgrade to version 24.0. However, after restarting LabVIEW, the version reverts to 20.0. I have tried selecting and deselecting "Separate compiled code from source," but it does not work. I want to upgrade all OpenG libraries to version 24.0 so that my project works correctly. Can anyone help me find a solution? Thanks.


Your project should work regardless of whether you mass compile or not.  In fact, mass compiling them to LV 2024 will make them incompatible with anything before that version.

 

So what about your project doesn't "work correctly"?  Before we ask "how" to do something, it is usually more important to ask "why".

Bill
CLD
(Mid-Level minion.)
My support system ensures that I don't look totally incompetent.
Proud to say that I've progressed beyond knowing just enough to be dangerous. I now know enough to know that I have no clue about anything at all.
Humble author of the CLAD Nugget.
0 Kudos
Message 2 of 14
(689 Views)

Thnaks for your response. But my project does not work if one of the Library VIs are saved in version 20.0. I get this error in Teststand in project and VIs that use openG library (specially openG variant): "LabView Project 24.0 could not be converted to runtime 24.1 " and "VI could not load in LabView runtime 24.1". when i masscompile the Libs my project works fine. But like i just said the OpenG libs keep returning to previous version

0 Kudos
Message 3 of 14
(683 Views)

As Info: my project was working in LabView 2019. This Error happen after updating LabView to 2024. And this Errors is happening only in VIs using openG variant when the openG_variant.llb is in version 20.0

0 Kudos
Message 4 of 14
(659 Views)

Are the files write protected? 

G# - Award winning reference based OOP for LV, for free! - Qestit VIPM GitHub

Qestit Systems
Certified-LabVIEW-Developer
0 Kudos
Message 5 of 14
(653 Views)

No, they are not write protected. But when i open "openg_variant.llb" the VI version revert automatically to version 20.0 and when i want to close it it ask me to save it in 24.0. After save it if i open again the version is 20.0 

0 Kudos
Message 6 of 14
(644 Views)

Any chance you're saving them to a OneDrive/Google Drive/etc location and it's getting overwritten by something?

0 Kudos
Message 7 of 14
(633 Views)

No, All my Libs are saved under "C:\Program Files\National Instruments\LabVIEW 2024"

0 Kudos
Message 8 of 14
(589 Views)

@Hatimelaiha wrote:

No, All my Libs are saved under "C:\Program Files\National Instruments\LabVIEW 2024"


Maybe a user access control issue. Does your user account have the right to change, create or delete files under "C:\Program Files\National Instruments\LabVIEW 2024"?

0 Kudos
Message 9 of 14
(581 Views)

yes, i have the right to change

0 Kudos
Message 10 of 14
(574 Views)