Creating plug-in code modules in Labview 8.2 project explorer

[James T @ UWA]

I use a series of master applications that can run user-selected plug-in modules created as LLBs. 

To create the LLBs in LabView 6.1 and 7.1, I saved a top level VI as an application distribution into a LLB using the "save with options" under the file menu.  This saved the top level VI and its entire hierachy of sub-VIs into the LLB.  The top level VI could be then invoked from the master application with a "Call By Reference" node.

The "Save with Options" has disappeared from the file menu in LabVIEW 8.2 (we have skipped a version).  It is not clear to me how to do this in LabVIEW 8.2.  I am confused between lvlib and llb, and cannot seem to create the LLB in the way I used to.  Advice welcome. 

James Trevelyan, University of WA Telerobot (http://telerobot.mech.uwa.edu.au)

[mikeporter]

Yes, this is one of the many places in V8.x where NI has decided to fix things that weren't broken - but you can still do what you want.

1. Open the top-level VI and select Save As... from the File menu.
2. In the confusing new dialog box that opens, select the botton radio button (Duplicate hierarchy to new location), and clich the Continue... button.
3. In the file save dialog box, navigate to the directory where you want to place the new LLB.
4. Enter the name for the library in the File Name field, and click the New LLB button.

The VI that you started the save from will automatically be created in the library as the "Top-level" VI.

Mike...

[TCPlomp]

---

@mikeporter wrote:
Yes, this is one of the many places in V8.x where NI has decided to fix things that weren't broken - but you can still do what you want.

---

Mike I think you are overreacting here..

But on topic, there is a better way.
Using the project (You are gonna use it someday), create a new build of the type 'source distribution'. Here you have many options, one of them is to save the destination as an LLB.
The beauty of this is when you want to do this again in some months, you don't have to think about it, just select build of that source distribution.

The problem of the old method was that there were too many options in one dialog, and this is a more in line with the view that a source distribution is a special build type.

Ton

[James T @ UWA]

Mike's solution seems to work fine and is simple in comparison to yours, Ton.  However, I'd like to be able to follow both.  I tried the project window, but the results were to say the least a mystery. (Attached summary, error messages and screen shots).

I have a folder C:\Jobs\mech\experiment\exps\iron rev4\  in which the source code top level VI "iron client master.vi" resides with its dependencies either in the same folder or subfolders.  One of the subfolders is "build" where I wanted the LLB to appear.

The build module seems to expect a "lvlib" module that doesn't exist.  When I create it, there is no change to the error messages.  Maybe if you could point me to some coherent documentation, something more comprehensive and clearly explained than the cryptic help files that mean everything when you know what it is talking about, it might help.

Thanks to both for your prompt responses.

James T

[TCPlomp]

Strange, I've never seen the searching for a never existed lvlib.
I noted that your llb is not placed in the build directory but that shouldn't be a problem.
What did you specify as 'Additional Exclusions' and 'Source File settings'?

Hope I can help you!

Ton

PS be aware your email address was shown in the PDF

Message Edited by TonP on 06-11-2007 08:00 AM