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

Similar Messages

Bug? Right-click on Front Panel causes selection rectangle!

Originally posted on LAVA: http://lavag.org/topic/12097-right-click-on-front-panel-causes-selection-rectangle/. This post contains an updated description of the problem.
Anytime I right-click on a control on the FP, and dismiss the context menu, I get a selection rectangle. If I don't catch it, moving outside the bounds of the FP will cause the FP to scroll to continue my unwanted "selection". So far this has been repeatable every time.
I noticed that the problem doesn't occur on the Controls pallette, only the context menu for controls. Also, if I mouse over the context menu before dismissing it, the problem doesn't occur. If I select an item from the context menu (which also dismisses it), the problem doesn't occur.
I am running LabVIEW 8.6.1f1 on Windows XP Home SP3.
-Ian
Solved!
Go to Solution.

I once worked in a lab which contained a transformer with its incessant 120 Hz hum. Just when I could tune it out someone would say "What's that hum?" and then it would annoy me again. Similar story in a different lab which had a cooling water drain. Just when I get used to the sound, someone would bring it up.
This behavior has p#$#ed me of on numerous occasions and I am mostly used to it by now. At home I use a track ball mouse which covers a lot of real estate in a hurry so of course I am often scrolling a FP into never-never land. Now you bring it up and I am having flashbacks... (Thanks really, it is time to get this fixed)
I have learned to spot the little circle in the crosshair cursor. When it is missing, you are in selection mode.

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

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

Node-webkit Helper causing system hangs

I'm using the intel XDK developer tool and having frequent system hangs when node-webkit Helper is accessed. The CPU use in monitor is ofter in excess of 100%. I've seen other people having problems with node-webkit Helper on OSX with different apps. Does anyone know of a solution for this?

There are two fairly common reasons why an update doesn't work properly:
1. Use of a Delta updater instead of the Combo Updater. The latter seems to cause fewer problems or, rather, may "fix" some problems that the Delta updater misses.
2. The user needed to repair the hard drive and permissions prior to installing the update. This is the most common problem. Installing an update on a system that is corrupted or where permissions are invalid will usually cause the resulting updated system to malfunction.
In some cases there are actual system files that have become corrupted and cause an update to malfunction. If this be the case usually it's necessary to do an Archive and Install to replace the old system (hard drive should be repaired prior to doing the Archive and Install.)
Among troubleshooting efforts to try are: (1) boot into safe mode to see if the problem is solved. Safe mode disables third-party startupitems, contextualmenuitems, and extensions; (2) create a new user account and log into the new account; A new user account has no login items or old preference files. If these are corrupted the system will work properly in the new account; (3) Use a utility such as TinkerTool System to clear user cache files, font files, and log files. If these become corrupted they will cause the system to malfunction.
Install the freeware utility AppleJack (www.versiontracker.com) on each of your Macs. In the event of severe problems you can boot the computer into single-user mode and run AppleJack to fix many items that cause problems. AppleJack is only run from the commandline in single-user mode.

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]

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

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

Readjusting front panel window.

Double clicking on terminals in the block diagram switches to their counterparts on the front panel. Frequently this leads to an unwanted shift of the front panel, in particular if objects (such as error clusters, ...) are placed outside the visible region of the front panel. Readjustment usually requires several scrollbar actions. I wonder if there exists a simple method to readjust the front panel coordinate system with respect to the top left corner of the front panel using a simple click action.
I am presently using a workaround which does the job if the misplacement is top-left (see attachment).
Reimar Spohr
Attachments:
Readjusting front panel window.png ‏11 KB

I am suggesting a modified version according to -lvABC to be dropped into a calling VI.
Reimar Spohr
Attachments:
Move Calling VI Front Panel to Origin.vi ‏25 KB
Move Calling VI Front Panel to Origin.png ‏43 KB

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.

890fxa-gd70 front panel sound

hi, i want to ask if 890fxa-gd70 supports ac97 front panel audio?..
i know the board has hdaudio but my case only has ac97 connection..
i want to know if i can safely plug my ac97 front panel audio to the board..
if not supported how can i use my ac97 front panel audio to my 890fxa-gd70..
will i need to buy a new hdaudio wire or can i just rearrange the pins in my ac97 to make it work..
thanks..

hmm.. does that mean it is safe to plug my ac97 front panel to my mobo?..
btw i saw this on the net:
AC'97 front panel audio does not work with onboard HD Audio
The onboard front panel audio connector provides microphone in and line out signals for the front panel. Many chassis manufacturers offer chassis with front panel audio ports and cabling. Those front panel solutions may support either AC’97 audio or High Definition (HD) audio.
The onboard audio headers on Intel Desktop Boards with the Intel® 945 chipset and later support HD audio.
Compatibility:
HD front panel audio solutions should be plugged into HD onboard headers.
AC’97 front panel audio solutions should be plugged into AC’97 onboard headers.
Some AC’97 front panel audio solutions (but not all) may work with HD onboard headers.
If you want connect an AC’97 front panel audio system to HD onboard headers, try these steps:
Connect Mic_IN (MIC) to MIC2_L.
Connect Audio_R (RIN) to OUT2_R
Connect Audio_L (LIN) to OUT2_L.
MIC_RET and OUT_RET are for HD audio only; you don't need to connect them for AC'97 audio.
Intel does not validate AC’97 front panel audio solutions with boards using HD audio. If the steps above do not work, you will need to use an HD front panel audio solution for full compatibility with Intel Desktop Boards using Intel 945 chipsets and later.
but i dont know what pin# are:
Mic_IN (MIC) : MIC2_L.
Audio_R (RIN) : OUT2_R
Audio_L (LIN) : OUT2_L.
MIC_RET and OUT_RET
i looked at the link you gave me but i cant see any of the listed names there..

Selecting front panel properties after runing causes crash

After I run my program (which uses several call library function nodes to access numerous dll files) and then try to alter the properties of a front panel control labview crashes. Sometimes it simply locks up, other times it displays a recoverable error message, and finally sometimes it displays a hard error message from which I cannot recover and only send an "error report." While the errors are annoying I really want to know why changing the properties causes them which may lead me to other problems in my code. Thanks for any thoughts you can provide.
-Dave

NIDave wrote:
> Thanks for the reply Jeremy, I try to change them manually after the
> program stops. I use a property node to alter other controls but not
> the one I discovered the problem on. I am suspecting a memory leak
> within the dll or some problem with the way I am passing strings and
> arrays in and out of my call library function nodes. (I initialize
> the strings and arrays before the function is called, so I am leaning
> toward an issue in the C code.
Well here you go. Calling a DLL and then getting (delayed) crashes in
LabVIEW absolutely always means that the DLL is trashing some memory it
shouldn't. This either happens by passing wrong data (DLL expects by
reference and you pass by value) or arrays and string not initialized or
not intialized to be large enough. Last but not least the DLL of course
can just simply be buggy and do stupid things.
So you will have to verify somehow that the DLL works correct outside of
LabVIEW. If you have verified that, then you need to check all
parameters of all function calls into the DLL to be correct and also
large enough for the DLL.
Especially make sure that for strings you allocate 1 more byte than the
longest string the DLL may want to write into, and for arrays that you
allocate the right number of elements of the right type. Sometimes the
documents state that the array must be at least 100 elements long but if
this is an integer then that amounts actually to 400 bytes.
> Also another oddity, when I first open labview and run the code it
> works great, however if I try to close the VI but not labview then
> run it again it fails. I think that labview is not dropping the dll.
> Is there a way to force it to release the dll?
Not really. A DLL should not depend on being unloaded to be callable
again. But the error you describe could be because of several reasons.
Basically make sure you call any existing Close or similar function at
the end as well as initialization function in the beginning. Also the
error could be related to the DLL trashing memory somewhere. So try to
get the DLL to work properly without any bad effects after having it run
once including no crash when unloading the VI, closing any front panel,
doing some LabVIEW edit functions or last but not least closing LabVIEW.
Rolf Kalbermatter
Rolf Kalbermatter
CIT Engineering Netherlands
a division of Test & Measurement Solutions

How Do I Close a Front Panel

It's Late in the day and I am a bit dozey from debugging.
I have a VI that conditionaly displays it's front panel.
It processes a file and if it finds any errors, it opens it's front panel to allow the user to correct them.
When finished, it (should) close the panel and return to the main function
I open it using Fopen invoke node but am having trouble closing it afterwards.
FClose invoke node doesn't seem to close it and FOpen Activate=false throws an error.
Can anyone tell me the the right invoke/property node to use.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
Attachments:
Panel open.PNG ‏6 KB
Panel close.PNG ‏6 KB

Tried that, Didn't work for me.
I did find a workaround where I hid the panel.
Not comfortable with it, as I don't know what happens with memory etc.
The VI is a state machine with memory elements.
iTm - Senior Systems Engineer
uses: LABVIEW 2012 SP1 x86 on Windows 7 x64. cFP, cRIO, PXI-RT
Attachments:
not close.PNG ‏5 KB
workaround.PNG ‏6 KB

Close Front Panel Causes System Hang.

Similar Messages

Maybe you are looking for