LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

LV 2009 project LLB as startup vi in .exe build?

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?

0 Kudos
Message 1 of 8
(3,289 Views)
Attached (hopefully) is an image of my Project and I hope this clears it up a bit.
0 Kudos
Message 2 of 8
(3,283 Views)

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

 

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 3 of 8
(3,268 Views)
There is not a limitation that a VI in an LLB cannot be a startup VI of an application. If the arrow on the source files page of the application builder is not enabled, it is possible that there is a problem with the VI itself. Typically this is due to the VI being broken. I would suggest you try another VI from an LLB and see if you can add that as a startup VI.
George M
National Instruments
0 Kudos
Message 4 of 8
(3,251 Views)
The problem is there are no vi's under the LLB! So I cannot choose any as the startup vi.  Why would LV let me do this in the first place?  I need to find a way to correct it as my user interface is the LLB and I need to make an .exe.
0 Kudos
Message 5 of 8
(3,250 Views)

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.

0 Kudos
Message 6 of 8
(3,247 Views)

Could you post a screenshot of the project with the LLB?

And of the build window?

 

Ton

Free Code Capture Tool! Version 2.1.3 with comments, web-upload, back-save and snippets!
Nederlandse LabVIEW user groep www.lvug.nl
My LabVIEW Ideas

LabVIEW, programming like it should be!
0 Kudos
Message 7 of 8
(3,243 Views)

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.

0 Kudos
Message 8 of 8
(3,228 Views)