rename LVLIB containing LLB

[James_W]

Please can someone correct me if I am trying to use the LabVIEW file structures incorrectly.

I have built a self contained instrument driver - contained in an LVLIB

It references some code written by the H/W manufacturer that was supplied in an LLB.

Problem:

The whole point of going the LVLIB rout is that when I get a different variant of the H/W which requires different setup parameters or talks on a different protocol speed (but uses the same command set defined but the manufacturer in the LLB) I want  to create a new LVLIB for the new project I'm working on so that my S/W modules match the H/W modules.

When I do this all the LLB references fall apart and require resorting with LLB manager.

If I save the LVLIB as... the save corrupts.

Is there a solution to this - other than remove the code from the LLB?

James

[smercurio_fc · Accepted solution]

You could simply not include the LLB in the lvlib. It seems to me that the lvlib is for your code, rather than a third-party set of code, so technically, the LLB shouldn't really be in the lvlib. You could also simply convert the LLB to a directory, since the LLB is just a fancy container. (I'm not sure if this is what you meant by removing the code from the LLB.)

[James_W]

The "Fancy container" is just that -  a problem.

the reason for including the LLB code in the LVLIB is that if I have driver code for Instr 1 and Instr 2 which are both variants of the same instr using the same LLB code but configured a level above totally differently, then when I add them to a project I don't get conflicts.

If I move around the folder containing the LVLIB driver code the LLB code always goes with it. (a small overhead but one that so rarely happens that the disk overhead is worth the hassle of not resolving project conflicts).

I guess I'll have to take the code out of the LLB.

There isn't a programatic way to do this is there (in case the manufacturer updates the LLB code?)