LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Standard Procedure for Editing vi.lib VIs...

Okay, so there are some VI's in the vi.lib>gmath>parser.llb library that I would like to make some changes to, one of the changes being the ability to input numbers in SI notation, I have already found the changes that I need to make, but since this is in the vi.lib I don't just want to go in there and start hacking stuff up. What is the general procedure for changing VI here? Should I copy the parser.llb to my user.lib directory, then change the name of the library to parser_CompanyName.llb and then append my company name to each VI name in the library to avoid any bad linkage? Thanks for any input, all help is greatly appreciated.

0 Kudos
Message 1 of 5
(2,868 Views)

Your on the right track!

 

An easy fix is placing all the VIs in a library (lvlib), this would give the copies a new unique name to prevent bad-cross-links.

 

However if your alterations are only in the user interface I owuld write a wrapper around those VIs with mhy custom code in the wrapper.

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
Message 2 of 5
(2,859 Views)

You may also want to place the new VIs in user.lib so they will be found, much like VIs in vi.lib.

0 Kudos
Message 3 of 5
(2,833 Views)

Hey amaglio,

 

There shouldn't be any issues with your proposed method for customizing the .llb files. It will preserve the standard LabVIEW libraries and give you easy access to your own. Though I will say that TCPlomp's solutions is probably easier to implement. Placing those libraries in an lvlib and then putting that lvlib in your project should make everything easier to keep track of. You are definitely on the right track. Hope that helps!

John B.
Embedded Networks R&D
National Instruments
Certified LabVIEW Developer
0 Kudos
Message 4 of 5
(2,814 Views)

Thanks all for your input, it is greatly appreciated. TCPlomp did have the right idea by just renaming the library, this is the only name I need to change for cross referencing concerns.Thanks Smiley Wink

0 Kudos
Message 5 of 5
(2,811 Views)