Don`t close front panel in a loop

   I'm doing a numerical limit step that calls a labview module and show the measurement in the front panel.
   My problem is that I want to do the same mesaurement using the loop options, and every time the loop executes, my front panel is open and closed.
   The right behavior is opent the front panel the first iteration, do and show the measurements during the loop, and close the front panel in the last.
Really I can`t find any option to do this in only one step.

see at this link for response
http://forums.ni.com/ni/board/message?board.id=330&message.id=11573#M11573
Regards
Ray Farmer

Similar Messages

Close Front Panel Causes System Hang.

I have an application where there are several front panels that I would like to have open at once, but where when they stop they would close. I was using the scripting function fp.close - but as the application has got more complicated this seems to work less and less well. Basically when i hit close, the system hangs for a few seconds, then the time critical stuff i have tends to timeout and then crash, and everything goes funny for a while.
My (uneducated) guess is that when it closes a front panel it drops loads of stuff straight out of memory - in an uncontrolled way.
After going for a cup of coffee it usually sorts itself out. But clearly this isn't a sustainable solution for my application or my kidneys.
Am I doing something wrong? - Is there something i should do to allow the Vi to finish before i try to close it? Should i be releasing references or somethign to make things better. I thought about running the close vi sub as a new thread - but not sure if this would actually do anything different.
Attached - the subroutine that i pass a vi ref to.
Attachments:
RunningVis_CloseSubVi.vi ‏17 KB

There's nothing in the attached VI that would necessarily cause your problem. I would, however, suggest that you feed your reference through the nodes in proper flow control method rather than branching off like you've done.
When a VI fails to close quickly, I have most often found it's due to open references which aren't explicitly closed. File references, VI references, multiple calls in a loop acquiring the same reference over and over without releasing it, .NET calls not being closed - that kind of thing.
Richard

Open and Close Front Panel of SubVI

Hi all,
Running LabVIEW 2011 on Windows 7 x64. I am trying to get a subVI front panel to open from my main FP with the press of a button and then close with a button press in the subVI. Here is the piece from my main FP that calls the VI and opens the FP
Plots is defined in another loop and all of the loops are in a flat sequence. I did it this way because I want it to start with the first press and not stop my main loop from running. I have moved the item in the left loop around a lot so I'm not sure if I can run that in the same loop as the event or not. Either way opening the VI seems to work fine.
The problem shows up when trying to close the subVI for the SECOND time. The code is here:
As I said, the first time I open and close the VI everything works as I expect it should. I am then able to open it again but now the "blank button" doesn't function and I can't close the window or even open the block diagram to probe anything. I have been trying to figure this out for awhile, any insite would be greatly appreciated!
Thanks
Solved!
Go to Solution.

Its good that you found the bug.
This code may serve as a way for you to compare notes.
Ben
Ben Rayner
I am currently active on.. MainStream Preppers
Rayner's Ridge is under construction

Close Front Panel

Is there a way to close the VI front panel from inside the VI? I can
trigger an exit of LabVIEW itself, but can't find an event to close
the front panel.
Thanks.

First off if you are going to build this into an exe then don't worry about it. but if want to close the vi programmatically then here is an example.
Hope this helps you out
Joe
Joe.
"NOTHING IS EVER EASY"
Attachments:
Untitled.vi ‏20 KB

Close front panel but leave open block diagram

Is there a way to do this? I would like to have my block diagrams of a few subvi's open but front panels closed so my task bar isn't so cluttered. It's not a big deal, I was just curious
CLA, LabVIEW Versions 2010-2013

Chris_VH wrote:
No current way unfortunately.
A colleague and I actually just put in a product suggestion for this yesterday.
So if they fix this do I give you or them credit for the solution?
CLA, LabVIEW Versions 2010-2013

Open and close front panel

Hi,
I wish to have a VI that works as a main menu from which you start new
VI's depending on your choice. When the new VI start I want the main
menu to hide it's front panel temporarily until it the second VI
returns.
Anyone has a solution to this?
/Nimrod
Sent via Deja.com http://www.deja.com/
Before you buy.

[email protected] wrote:
When the new VI start I want the main menu to hide it's front panel temporarily
until it the second VI returns.
If you are using LabVIEW 5.1, you can use the VI server attributes to hide
the VI by moving it off of the desktop. I will send you a sample in private
mail.
The attribute (property) you need to use is Front Panel Window -> Window
Bounds.
Set it to something that is larger than your window size, like 2000, 2000,
2200, 2200.
I hope that this helps,
Bob Young
Bob Young - Test Engineer - Lapsed Certified LabVIEW Developer
DISTek Integration, Inc. - NI Alliance Member
mailto:[email protected]

Printed front panel graphics quality (Print Panel to Printer method vs. Append Front Panel Image to Report.vi)

LV 6.02 (or 6.1)
NT 4.0
I have a vi that the front panel includes all the information I need to print except that it is on different pages of a tab control to conserve screen space. I was attempting to programatically cycle the value of the tab control in a For loop and invoke the Print Panel to Printer method to print 7 pages of the front panel, each with a different tab page selected. The printouts were excellent quality but beginning with the second consecutive Print Panel to Printer method the on screen front panel image of the VI being printed would become jumbled (sometimes, by the time 7 printings were done, the entire front panel image would disappe
ar and a bitmap of the desktop or underlying windows would be visible in the VI's panel frame) yet the subsequent Print Panel to Printer methods continued to print the panel as they should appear. The visible front panel graphics would never return to normal and the only solution was to close the vi (in the dev system) or exe (compiled) and re-launch. I tried a lot of things (like hiding the panel to print before printing and showing it after printing) with no luck. It appears that two or more of these consecutive invoke methods caused the problem regardless of whether the tabs were cycling, or even if there was no tab control and much fewer controls on the panel to be printed than normal. I also had the same problem with LV 6.1.
Finally, I was forced to switch to the report generation toolkit vi's, I cycle through the tab pages and use the Append Front Panel Image to Report.vi to append each image to the report. This is faster and control returns to my program quicker but I a
m unhappy with the printed quality of the graphics of the front panels. They are not as high of resolution as those generated via the Print Panel to Printer method.
Any suggestions?

You might try changing the way the VI is printed by going to tools >> options >> printing. Try the postscript and bitmap settings.
Jeremy

Question about subvi front panel

I want to call a subvi in the main program and do like
this:
1. When the main program calls the subvi, the subvi shows its front
panel and executes.
2. After the subvi finishes, it can close the front panel.
Now, I meet a problem: I can popup the subvi node setup dialog to enable
"show front panel when called", which implements the first one, but I
can not close the front panel until originally closed(main
program stops). How can I close the subvi's front panel(after it
finishes running) even when the main program is still running?
Thanks in advances.
Sent via Deja.com http://www.deja.com/
Before you buy.

In article <[email protected]>,
"Remco Breen" wrote:
>
> [email protected] wrote in message <[email protected]>...
> >In article <[email protected]>,
> >"Kevin B. Kent" wrote:
> >> [email protected] wrote:
> >>
> >> > Now, I meet a problem: I can popup the subvi node setup dialog to
> >enable
> >> > "show front panel when called", which implements the first one,
but
> >I
> >> > can not close the front panel until originally closed(main
> >> > program stops). How can I close the subvi's front panel(after it
> >> > finishes running) even when the main program is still running?
> >
> >
> >
> >
> >> Select the "close front panel if originally closed" option.
> >> in addition to the "Show front panel when called"
> >>
> >> Kevin Kent
> >
> >
> >I have tried this, in this way, the subvi's front panel is closed
only
> >after the main program stops. In fact, what I want is to close the
> >subvi's front panel even the main program is still running.
> >
> >
> >zhljh
> >
> >
> >Sent via Deja.com http://www.deja.com/
> >Before you buy.
>
> Another option would be to open a VI reference (found under
"application
> control") and tie that to a property node and select the property
"front
> panel.open". Change it to a control and attach a boolean false to it
when
> you like to close.
>
> RB.
>
I think a more elegant way of closing the SUB VI is to start off the way
that Remco states regarding opening a VI reference. Only in the Sub VI,
you should program a Terminate control (such as an Abort button to exit
from a While loop... or something similar) and via the VI reference,
select the 'Set Control Value' method to gracefully stop the Sub VI
execution. Of course the Sub VI will have to set the close if originally
closed attrib set.
There is a great source of example LabVIEW apps at:
http://digital.ni.com/explprog.nsf/web%2Fswgrp?OpenView&Start=1&Count=50
0&Expand=3.7#3.7
In particular, see "Stopping a Running SubVI from the Main VI Using VI
Server" example. It demostrates this techniques better than I can
explain it. Hope this help.
Rick
Sent via Deja.com http://www.deja.com/
Before you buy.

Front panel remains after terminating lavbiew application

I have created an application from a LabView VI. I'm launching the application from LabWindows. I'm monitoring for the application to terminate. However, when I terminate the LabVeiw application, the LabView front panel is displayed and the LabWindows application terminated function doesn't see it as terminated until I close the front panel. Why is the VI front panel being displayed when the application is terminated. I have the program to run in dialog center screen. Once the application terminates, the dialog disappears and the LV front panel appears.

I like to put the Close invoke node inside of a Conditional Disable Structure. This way the front panel only closes when you are running an EXE and not when you are playing with the code.
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
Attachments:
Close Front Panel.png ‏10 KB

Can not open front panel sub VI when running an application VI.

When I create an application of my program a problem occurs. When I select options (press a button or so) from the main front panel that should result in a popup menu (sub VI cal) LabVIEW indicates that something is happening but the front panel does not open. The mouse indicator changes to the time glass so LabVIEW is doing something but the window of the sub VI does not open.
The problem has the same characteristics on several places. There are some sub VI front panels that opens but I ca not find the reason for why these open and not other.

Hi
there are three ways trhough which you can force a subVI to show its front panel
1. open the perticular SUB VI
click File->VI properties select window appearence catagory.
click customize button and select "Show Front Panel when called" and "close afterwads if originally closed" check boxes
save the VI
whenever you use this Sub VI every time it will pop up front panel
2. dont perform the changes suggested in option 1. place the instance of subVI in your main application and if you want that instance to popup a front panel then right click on subVI and Select "SubVI Node Setup" again select "Show Front Panel when called" and "close afterwads if originally closed" check boxes
with this option only certain instances of SUB VI will cause pop up to occur
3. this is the most flexible option. use invoke node to show front panel. in invoke node select show front panel method to popup the VI and use close front panel method to close the pop up window.
Tushar Jambhekar
[email protected]
Jambhekar Automation Solutions
LabVIEW Consultancy, LabVIEW Training
Rent a LabVIEW Developer, My Blog

VI front panel won't close when it's done executing, when this vi was called by reference.

I've created a simple vi set to demonstrate the issue I'm having. I'm dynamically launching sub vi's from a main application. Simply put the main application is my test exec and the subvi's I'm calling dynamically are different tests. In the example I'm posting here the test vi is called Electrical Test 1.vi. I've configured this Electrical Test 1.vi to show front panel when called and close afterwards if originally closed. Problem is it won't close the front.
Other things to keep in mind
I want to be able to launch the test vi and not wait till it's done.
I'm using LabVIEW 2012 SP1.
Solved!
Go to Solution.
Attachments:
vi_launcher - v5.zip ‏73 KB

Basically the close after call only matters if the VI is called as a subVI (just like if you open a VI yourself and run it, it doesn't close when it is done). The two ways around this are to either have your top lvl app close the VI when it is done, this is explained here:
http://digital.ni.com/public.nsf/allkb/987B2026B41BD39786256CF800032E8C
or to have your VI close itself when it is done. Use a This VI reference and the Front Panel:Close invoke node.
Hope this helps.

Open and close a vi front panel dynamically

I created a main vi panel that display all the signal names. I like the main vi to open a new plot screen when I double click on the signal name. I was able to do that using invoke node. But I when I close the plot screen by clicking on the Window "Close" button, the main vi was not able to open a new one again. So I disabled the Window "Close" button and only use the "Stop" button coded in while loop in the blockdigram of the plot screen. It worked, but the plot screen is still open and changed to editing mode. Is there an easy way to close the plot screen by only one click. Another question is that how does the main vi can open multiple plot screens. Thanks for your advice.

I think I know what happens:
If you close the front panel of a sub-vi, the code is still running, so the VI doesn't terminate and somehow you can't address it (it don't know how you communicate with your sub-vi).
So in your sub-vi you should monitor the panel-close event, and finish the code of the VI and finish the 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!

An alert messarge i don't underdant: insane object at BDHP + 83ACC in "VI name's":{graphics} (0x80):Front Panel Terminal (Term)

Hello!
I don't know why in just yesterday appear in one of my VI an alert message or error message when i want to close oer save the VI.
The message is like the following one:
Insane object at BDHP + 93ACC in "Vi name's": {graphics} (0x80}: Front Panel Terminal (Term)
I don't know why now it appears this message because i have no modify the Vi.
I want to ask you why it appears this message and the most important......how can i solve it?
Thank you very much
Larson

Hi!!! I copy and paste from an NI engineer post asking about what is the "insane object" problem:
This message means that an object in LabVIEW such as a wire or a loop tunnel does not pass an internal test known as a sanity check. If the errors are serious enough, LabVIEW exits because something has become very corrupted. Sanity checks occur before each save, to ensure that corrupted VIs are not written over good VIs. They also happen as part of the compile process. Thus, sanity checks happen frequently. Many insanities are actually fixed (made sane) after the dialog box appears and will not appear again, so the first thing you should do after receiving an insane object error is to try to make a backup copy of the VI, run it, and perform some additional editing to see if the problem was resolved automatically.
VI corruptions do not happen often. They can happen because of disk corruption, but this will often lead to a file that can no longer be loaded. Corruptions can also happen because the programmer did something that corrupts a LabVIEW data type, perhaps as the result of a call to external code. The following are examples of insane object errors:
Insane Object at BDHP+4D50 in 'sksks.vi': (graphics) (0x80):wire segment (WIRE)
Insane Object at BDHP+5CA0 in "CAPL3.vi": (graphics) (0x80):loop tunnel (DCO)
In the first example above, the error message itself gives information about which object is insane. BDHP means the offending object exists on the block diagram heap, as opposed to the FPHP for front panel heap. The +4D50 is the hex offset in the heap where the object is located. The "Wire Segment" text indicates that the object is a wire object. The "graphics" text indicates that the insanity is graphics-related, which means it is not serious and will most likely be repaired automatically.
The second message above is similar, but refers to a loop tunnel (i.e., the tunnel formed where a wire crosses the edge of a loop) rather than a wire.
Solution: If you receive an insane object message, it is best to delete and recreate the most recently created objects on either the front panel or block diagram, depending on whether the error message contains "FPHP" or "BDHP". Make use of the text in the error message in deciding which objects to rebuild. In the case of the second message above, it would be best to delete and recreate the most recently created loop tunnels.
Another workaround that works best if the VI is small is to select the entire diagram and copy it to a new VI. After saving the new VI, there is a good chance the insane object error will no longer appear. If the VI is too large to cut and paste to a new VI and another computer with an identical version of LabVIEW is available, you can copy the VI to disk (or to your network if that is available) and open it on the second machine. If the insane object errors do not appear, save the VI (on the second machine) and transfer it back to the original PC (by disk or by network). The new, uncorrupted version of the VI should now run without generating the insane object error.
Hope that helps you,
Jaime
Regards,
Jaime Cabrera
NI Applications Engineering Spain

How can I close all open subVI front panels, without closing my top level VI front panel when all VIs are built into executables?

I'm using the code shown in the sample VI discussed here: http://digital.ni.com/public.nsf/allkb/353A696A3F393D9B86256E8B007A2912
to close all open VIs except my top level VI. My top level VI is actually a separate executable and the sub-VIs are their own executables. All reside under the same project. It works very well if I'm running in LabView but will not work when I build them. I added all the sub-VIs to the Always Include box in my top level VIs properties which did nothing. I also tried adding them to the Startup VIs box. This allowed me to close them all programmatically from the top level VI but it also open all the VIs at once (which was expected and not desired). I think the problem is the executables are not able to see outside their own memory space so the top-level VI never finds any other open front panels to close. Is this correct? Is there another way to go about doing this?
Thanks!

Where do I begin…..
I’m using a “server” to control 4 “client” PCs. My server opens references to 4 VIs on each client then executes them sequentially. So on a normal day, the server will run everything itself and I will have no contact with the clients. But on a several occasions, I’ve needed the ability to walk up to one of the clients and run just one of the 4 VIs.
We are updating from LabView 6.1 to 8.5 and we want to run executables rather than VIs for various reasons. I have a new VI running on the client PCs who’s only function is to initialize the shared variables and open/close the VIs. I initially thought of making the remaining 4 VIs sub-VIs but I will loose the ability to run them individually. I think I would also have to rewrite the VI running on the server since the 4 references it originally opened do not exist. I don’t think you can open a reference to a sub-VI on another PC. Can you???
As you can see, this is a huge mess. I’m still pretty new with LabView so any help you can provide would be great.

How can I close a remote front panel by closing only the browser window?

I control a remote front panel in a browser (from the client PC). If I don't use the 'close' - button in my program to end the remote front panel, but instead of this the 'x' of the browser window (in the right bottom corner), my program won't be close, it continues on the server. Do you know how to end a VI by closing only the browser windows?
Thanks for any help!
wolfe

I found the examples. Thanks.
But I could not find a solution yet. Now I know how to end a VI by clicking on the x of the VIwindow.
My problem is, to end a VI by clicking on the x of the BROWSER window after I loaded and controlled a remote panel VI in a browser (e.g. IE).
If you have any ideas ... I'd be happy.
Thanks for your help.

Don`t close front panel in a loop

Similar Messages

Maybe you are looking for