Hi all, I have bunch of subroutines will be needed for all projects developing in the same computer. For long time, I wrap each of those subroutines as a separate subvi and call the subvi when needed. But I just saw someone will build a LLB to contains all those subvi. Will it be the same to build the LLB or separate subvi? So what's the advantage to use LLB? I saw the builtin functions are all wrapped into a LLB. So if I create my LLB, where should I put that LLB so it will be appear on the main palette? The second question I have is what's a Project is for in labview 2013? I have been using labview 7 for long time and I create my project in a folder. But in LV2013, I can creae a project and bind everything in there. So what's the advantage of using a project? Thanks.

There really is no use for an llb anymore. It was primarily used to store VIs with long names - names that were not acceptable in the early days from the transition from DOS. Storing working files in an llb is a bit dicey since a single corrupt VI will render the whole llb unreadable. An llb is not suitable for source code control. The source code control is only able to track the llb and not the individual files. The only time an llb should be used is to distribute released code. Better and what is being used now is the lvlib or the packed library. One of the biggest hassles of older versions of LabVIEW was the inability to load different VIs with the same name. Placed into separate vilibs, you can now do that. The advantage of the project is what you said - binding everything together irrespective of the actual file locations. The project can contain files other than VIs - word and excel files for example. A project is also required to create an exe. The project will contain the build specs for the exe and installer. A project can also contain DAQmx tasks. Even if you don't intend to create an exe, a project is still a handy organizational tool.

LabVIEW

about using LLB, subvi and project

Solved!

No trouble- I live for Kudos! glad to have helped.

"Should be" isn't "Is" -Jay

Message 11 of 11

(302 Views)

LabVIEW

about using LLB, subvi and project

Re: about using LLB, subvi and project