LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Application Builder for LV 7.1

I cannot import the information for 'open front panel' on sub-vi's when building the application. In other words, after the application is built, I get a 'Null window' message when trying to run sub-vi's unless I manually tell the application builder which sub-vi's should be 'show front panel when run'.
0 Kudos
Message 1 of 17
(5,161 Views)
I'm new at LabVIEW, but I have developed an application with a button that opens a subVI front panel when pushed, in labVIEW 7.1. In this subVI, I just selected the option "Open front pannel when called", and when I build the application it runs perfectly. I don't knows if this is what you mean... I hope this helps
0 Kudos
Message 2 of 17
(5,157 Views)
what you need to do is open your main application right click on the VI in question and select SubVI node setup check the box for open when called and close afterwards if originally closed. this is one method. The other method is open the subvi in question go to Vi properties/ window appearance/ custom. then select how you want the window to show up to the user and inside there is also the option to open when called and close if originally closed.
try these methods and let us know if they work or not. if they do not work then post your code and let us have a look to see if there may be something else wrong.
PS when you post your code save it for ver. 7.0

Hope this helps you out.

Joe



Joe.
"NOTHING IS EVER EASY"
0 Kudos
Message 3 of 17
(5,157 Views)
Hi Joe. The second option you explain is what I mean, you have explaint it better than I... I didn't know the first option exist. It's necessary to use both methods at a time, or you just use one of them? Is there any recommendation on one or the other?
Thanks!!
Esther
0 Kudos
Message 4 of 17
(5,158 Views)
Yes, I did set up the vi properties to open front panel when called and close afterwards in the source code. I've tried building the application with both the original application and after saving as an 'application distribution' with all wiring diagrams removed. The source code opens and closes the sub vi's but the attributes don't seem to transfer to the application builder. I can re-do the attributes in the application builder but there has to be a way to automatically import them. I wish I had 7.0 for many reasons... not the least of which I need to develop on a Win98 machine... grrrrrr. I was to late in ordering.
0 Kudos
Message 5 of 17
(5,157 Views)
They do not have to be used together.
To explain further lets say you have created a VI to be used as a subvi in a main app. You may want that subvi to be called when you press a button and this vi will always open its front panel. In this instance you would use method two.
Now lets say that you created a subvi that can be used in many different main applications then you would set the window appearance as want it but do not select the option of open when called. Then you can set whether or not the front panel is shown using method 1.
I hope this answers your question.

Joe



Joe.
"NOTHING IS EVER EASY"
0 Kudos
Message 6 of 17
(5,157 Views)
It has been my experience that the LabVIEW Application builder does an excellent job to retain the front panel automatically for any subVI that will ever need to show it while running.

I don't quite understand your syntax, because the application builder does not have an option to set "show front panel when run". A related VI setting is for example: "remove panel". It seems in your case, the panel gets removed.

I suspect there is something unique in the way you interact with your subVI from the top level VI, fooling the application builder into thinking that the front panel is never needed. Does this particular subVI normally run in the background doing some computations and you later force passive visibility of the front panel with a VI reference? Is th
e VI "called by reference node" only?

I would suggest to simply spent some time manually editing the build settings, then save the *.bld file for future use.
0 Kudos
Message 7 of 17
(5,158 Views)
Till date ( and that is three days old ) I have not been able to build a single application that runs on a PC which has no LabVIEW installed.

Scene 1.
Build an .EXE file alone and try running it on another PC. You are asked for the LV7 run time engine. What do I do?

Scene 2.
Build the Installer and create a SetUp file. Copy this folder on a CD-ROM. Try to install this on another PC. Plenty of errors - one such is that no DAQMX sub VIs were copied and the message lists all of them as absent.

Is there any tutorial to create an standalone application using Application Builder ? The 4 page manual that came with the software was, well, not that useful...

can someone tell me whats going on ? And why am I not able to do what I want to do ?


Thanks

Raghunathan
Raghunathan
LabVIEW to Automate Hydraulic Test rigs.
0 Kudos
Message 8 of 17
(5,080 Views)

Hi Raghunathan

To run your exe on another PC you need to have LV runtime installed.
If you don't have it, you can download it from here

I don't think there is a tutorial but there are these application notes. I haven't looked at them but there maybe some clues.
I've found that you need to play with AppBuilder a bit to work out how to use it. The Advanced.. settings under the Installer Settings tab need to be correct to support particular configurations. Notice that there is a Help button on the bottom of each dialog that brings up a bit more detail.

Hope that helps

Neil

0 Kudos
Message 9 of 17
(5,068 Views)
Dear Neil,

Thanks for the clarifications.

But before I download the 20.2MB run time self executable, is there any way I can get it from the LV7 full development CD that I have ? That will be far more easier ain't it? Could you please revert on this ?

I did go through the application note link that you had sent. But they look to be done for much more advanced conditions.

Regards

Raghunathan
Raghunathan
LabVIEW to Automate Hydraulic Test rigs.
0 Kudos
Message 10 of 17
(5,055 Views)