From 04:00 PM CDT – 08:00 PM CDT (09:00 PM UTC – 01:00 AM UTC) Tuesday, April 16, ni.com will undergo system upgrades that may result in temporary service interruption.

We appreciate your patience as we improve our online experience.

LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

How to extract VI's from a .lvlib file so that the do not belong to that library anymore?


@rolfk wrote:

@Ben wrote:

Tools >>> LLB manager?


No that is only for the old LLB files, which was simply a single level archive file.

The newer lvlib files are a very different kind of library, similar to LabVIEW classes but without the OOP part. The only way to remove VIs from an LabVIEW library is to open the lvlib file in LabVIEW and right click on the VI in there and select "Remove from Library" or something to this wording.


It was the part about...

 

"

There are a couple of VI's in this library file which their name contain "-" so that in the library, their names appear with "*" or "?" (e.g, "-IDN-.vi" appears as "*IDN?"). What should I do about that also?

"

 

That had me thinking it was a LLB.

 

Ben

Retired Senior Automation Systems Architect with Data Science Automation LabVIEW Champion Knight of NI and Prepper LinkedIn Profile YouTube Channel
0 Kudos
Message 11 of 13
(530 Views)

Thanks a lot for informing me. Is there any possibility that I can make these .dll's by LabWindows/CVI 2019? National Instruments seemingly has just LabWindows/CVI 2019 Runtime Engine working on both 32-bit and 64-bit platforms, and not the base and full application.

0 Kudos
Message 12 of 13
(518 Views)

No! LabWindows/CVI supports creating both 23-bit and 64-bit binary files since at least version 2015 according to the help file.

Rolf Kalbermatter
My Blog
0 Kudos
Message 13 of 13
(507 Views)