LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

No VIs showed after opening llb

Hello,

I have the followig problem. When I open a certain llb it doesn't show the included VIs.

Does anyone know what causes this problem. I'm using LV8.5

 

Thanks Bastian

0 Kudos
Message 1 of 9
(3,464 Views)
Are there any vi's within that library (check the llb file size)!   it happen only for this llb or for all the llb's present in your system?
Message Edited by JK1 on 09-07-2009 05:32 AM
With regards,
JK
(Certified LabVIEW Developer)
Give Kudos for Good Answers, and Mark it a solution if your problem is solved.
0 Kudos
Message 2 of 9
(3,462 Views)

to add to JK1's post,

 

A empty project is 948 bytes in size

 

on disk it is 4.00kb

 

this is in 8.6.1

Message Edited by Harold Timmis on 09-07-2009 06:43 AM
Harold Timmis
htimmis@fit.edu
Orlando,Fl
*Kudos always welcome:)
0 Kudos
Message 3 of 9
(3,454 Views)

The file size is about 5MB. The problem only occurs at this llb. Other llbs still work.

 

0 Kudos
Message 4 of 9
(3,442 Views)
Could it possibly become corrupt when transferring the llb?
Harold Timmis
htimmis@fit.edu
Orlando,Fl
*Kudos always welcome:)
0 Kudos
Message 5 of 9
(3,437 Views)

I don't think so. The file is in a certain directory since two month.

Yesterday I still could open the VIs of that llb. I think the file is damaged.

My last back up was one week ago.

0 Kudos
Message 6 of 9
(3,435 Views)
so the file isn't bad and it is bad.. lol:)
Harold Timmis
htimmis@fit.edu
Orlando,Fl
*Kudos always welcome:)
0 Kudos
Message 7 of 9
(3,430 Views)
After you restore the backup, remove all of the VIs from the llb and STOP using an llb for development. A single corrupt VI can make the whole llb unreadable. An llb is obsolete. They serve no purpose unless you are doing a distribution.
0 Kudos
Message 8 of 9
(3,407 Views)

Hello,

I had the same trouble with an LLB file (in LabVIEW 2013). However, I could reproduce the failure:

I wanted to include the VIs of the LLB in the palette menu, so I set a link to the LLB (in the palette editor).

This worked fine (but of course, all the VIs in the new sub-palette were placed in random manner).

As soon as I modified the new sub-palette (for instance, repositioning of a VI), the LLB was corrupted.

Also other modifications (changing sub-palette name, removal of VIs) leaded to a corrupted LLB. So:

NEVER LINK TO AN LLB FILE TO CREATE A SUB-PALETTE; ALWAYS USE A SEPARATE MNU FILE!

 

I hope, this might help some of you...

 

Cheers!

0 Kudos
Message 9 of 9
(2,549 Views)