11-03-2009 04:17 PM
I hope I can explain my problem correctly.
I started a new project and wanted to build an .LLB and have subvi's called under these in the project as this is what I was used to doing minus the project in LV 8.2.1.
The problem is I built my GUI under the LLB but did not put any of the other vi's underneath it. So my project has 1 LLB and several vi's attached to it. The problem is when I tried making an executable it wants a startup vi(which is my LLB) and it will not allow me to put it in the startup vi column so I cannot build an executable.
I tried converting the LLB but got an error and almost lost my whole project because it deleted the LLB and did not convert it. Luckily I had a backup.
How do I make an executable when my front panel is in an LLB format?
11-03-2009 04:34 PM
11-04-2009 12:56 AM
An LLB is not a LabVIEW code-file like a VI, it is more a container file like a .zip file.
I advise you not to develop code in an LLB, just stay in a VI. The problem with developing in an LLB is that if the file structure is corrupt all the code is damaged. Since you only have one file in the LLB I see no reason to maintain the LLB.
However you should be able to select the VI inside the LLB as your startup VI.
Ton
11-04-2009 07:52 AM
11-04-2009 07:53 AM
11-04-2009 08:00 AM
I'm confused as to what you are seeing and wanting. Where do you expect to see VIs 'under' an LLB? Why do you say your user interface is an llb? A user interface is a VI and that VI may be contained inside an llb.
Why don't you post the llb that you created?
p.s. I agree that using llbs is not the right thing to do. It's obsolete technology.
11-04-2009 08:05 AM
Could you post a screenshot of the project with the LLB?
And of the build window?
Ton
11-04-2009 09:01 AM
I solved the problem. Maybe not the best way but, I just copied the block diagram into a new vi. Luckily it saved all my decorations etc except the graphics I had to redo. Saved it as a vi instead of an LLB and all should be good now.
I hope this was just an isolated incident on my part.
Thanks.