Save sub-vi's (possibly closed) front panel image to a file

Hello,
I would like to dump a file of a sub-vi's front panel when that sub-vi completes execution. I was thinking of using the "Front Panel:Get Image Method", however the target sub vi's front panel might not be opened. I am looking through the help file, and it says
"If you do not want to display the front panel but want the image to reflect value changes, create a Property Node from any front panel terminal on the block diagram of the VI for which you want to create a front panel image."
I'm not quite sure I understand what that means. Can anyone provide an example?
I am running LV 8.2 for the record.
Thanks,
-Ted

Hi Ted,
"If you do not
want to display the front panel but want the image to reflect value
changes, create a Property Node from any front panel terminal on the
block diagram of the VI for which you want to create a front panel
image."
What that means is to create a property node for something (anything) in your Sub-VI.
I have attached an example for you with a dummy property node. And the front panel of the Sub-VI gets updated on the Main-VI. Try removing the property node in the Sub-VI and you will notice that even though the values are correct in the main-vi, the image of the sub-vi doesn't get updated.
Hope this helps!
Warm regards,
Karunya R
National Instruments
Applications Engineer
Attachments:
MainVI.vi ‏15 KB
SubVI.vi ‏10 KB

Similar Messages

How can I save an EXE front panel image to a file?

The methods to save a VI front panel image to a file don't work on executable applications. How can I save an EXE front panel image to a file? (LabVIEW 6.1)

Hi,
i wrote some vi that save FP to image and created exe and it works fine. How do you save FP to image in VI?
If you use VI server method "Get Panel Image" and use "Write JPG file" ( or BPM) it works fine.
Attachments:
fp.zip ‏40 KB

Problem with Append Front Panel Image To Report.vi

I'm using LV 7.0 with the MicroSoft Report Generation toolkit installed. Under the Report Generation palette there exists an Append Front Panel Image To Report vi. Also on the same palette there is an Easy Print VI Panel or Documentation.vi which uses another Append Front Panel Image To Report vi located under the VI Documentation subpalette. Here is the problem; I have serval vi's that use Append Front Panel Image To Report.vi from the Report Generation palette and I have a couple of vi's that use the Easy Print VI Panel or Documentation.vi which is linked to the Append Front Panel Image To Report.vi located under the VI Documentation subpalette. Clear as mud!
This creates a conflict of intrest. In a nut shell th
ere are two vi's with the same name in different locations doing different things. I have a program with subvi's that need to call each respective Append Front Panel Image To Report.vi and that just is not working.
Is this a known issue with LV7.0 that has already been addressed and/or resloved?
Thanks.

ATC Herman,
Based on the picture you posted and what you are describing, it looks like you might have an incomplete install. What version of the toolkit do you have? Was it first installed on an earlier version of LabVIEW, or did you install it first on 7.0? Your VI Documentation Palette appears the same as if you hadn�t installed the toolkit. I�ve attached a screenshot of what it should look like. The VI in question is a polymorphic VI, which may be causing some of the confusion. If you right-click on it and select �Open Polymorphic VI�, it will show you what options you have, depending on the input. I opened both test and test1, and they appeared the same for me. I was able to have them both on the block diagram. The path to bo
th of them was C:\Program Files\National Instruments\LabVIEW 7.0\vi.lib\printing\ReportDocExtensions.llb\Append Front Panel Image to Report.vi. The .llb ReportDocExtensions has the polymorphic VI, as well as copies of each of the possible instantiations. Make sure you have these VI�s in the .llb in that directory.
There is a KB on having the toolkit on multiple versions of LabVIEW and what files you need. Make sure you have all the files listed.
Please let me know if you are able to get to the bottom of the issue with the above information.
Thanks, and have a happy day!
Robert M
Applications Engineer
National Instruments
Robert Mortensen
Software Engineer
National Instruments
Attachments:
Report_Palettes.JPG ‏57 KB

Append front panel image to report

I am using Labview V6.1 on a Win2000 PC 2.4 Ghz, 512MB RAM.
I am trying to use the append front panel image to report VI to append a VI panel image to a report. I am using notifiers to synch the execution of the VI with the desired front panel an the report generation process. I keep getting an error fron the Append VI that is a 1004 which is VI not in memory. How do I keep a vi in memory? I thought it would stay in memory as it is waiting for a notification from my report section for completion before closing. The notification stuff seems to work properly. Any ideas?

Here is a VI that demonstrates the problem I am having. The other VI is the VI I am trying to append to the report.
Let me know your thoughts. I will be away from this forum starting 8-27 til 9-1.
Let me know your thoughts.
put these files in a c:\P368 folder. or edit my VIs
Attachments:
testing.vi ‏81 KB
build_site_data_str.vi ‏45 KB

TDMS Low level file functions and Saving Front Panel image

Am using TDMS low level file functions to save while also plotting data in my data acquisition programme. However, I also want to programmatically be saving the front panel image on every run of my data acquisition. I have coded all other aspects, except the behavior of functionality of saving the front panel image on every successive runs of the application. Unfortunately, I just have no idea on how to code this aspect on LabVIEW, and all effort to search for example codes on so far have not been successful.
I would appreciate any useful hints or steps from anyone for me to follow, in order to accomplish this behavior, and that is being able to programmatically save my front panel images while using TDMS low level file functions in my File IO system of my application.
Thanks in advance.

Tebefia wrote:
Am using TDMS low level file functions to save while also plotting data in my data acquisition programme. However, I also want to programmatically be saving the front panel image on every run of my data acquisition. I have coded all other aspects, except the behavior of functionality of saving the front panel image on every successive runs of the application. Unfortunately, I just have no idea on how to code this aspect on LabVIEW, and all effort to search for example codes on so far have not been successful.
I would appreciate any useful hints or steps from anyone for me to follow, in order to accomplish this behavior, and that is being able to programmatically save my front panel images while using TDMS low level file functions in my File IO system of my application.
Thanks in advance.
Did you see this link?
CLA, LabVIEW Versions 2010-2013

Get front panel image

I want to print the front panel image with a specific resolution independent
of the actual size of the front panel.
I had the following idea: I use a prperty node with "get front panel image"
feed an intensity graph in a sub-VI with the information and print the panel
of the sub-VI. The intesity graph of the sub-VI has always the resolution I
need for the printer.
This works fine. The peoblem I have is that I can not use the property node
with 24 image depth. For the colour table (I need it for the graph) I always
receive an array with the size of 256 as I receive it with 8 image depth.
With 24 image depth I should receive a much longer colour table.
Maybe somebody has another idea to print the front panel with always the
exact res
olution. Independent of the panel size - always the exact similar
picture on the paper.
Max
-> [email protected] / [email protected] <-
-> Max Weiß * Eulenweg 2 * 76356 Weingarten * Germany <-
-> Fax/Voicebox: 01212 / 5 - 10570879 * Tel: +49 162 9114507 * DB 8 MWE <-

I've played with this some myself. Apparently, LabVIEW can only use up to a 8 bit depth or 256 colors for this function. Most of the time, that is sufficient for printing images which are usually in grey scale anyway. You might also want to play around with some of the Print Methods using invoke nodes. You can print to an html doc and specify whether you want a JPG or PNG and the color depth for the image. You might be able to take advantage of this to work around odd printing problems.

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

Append front panel image crashes in 7.0

I'm trying to use append front panel image.vi in
Labview 7.0 and when called Labview crashes in the
standard report case calling invoke node for IReportData > AppendPictureFromFile. Labview just
quits. What's weird is it appears to work on a
system w/ a local printer but not one w/ a network
priner. Any ideas?

try to generate an HTML report first, and then print that. Some printers are worse than other at printing (what looks like) a simple object.
Otherwise, I would do some basic trouble shooting, like can you print a simpler front panel image (say two numerics) to the printer. Next, I would try to print to a different networked printer.

New report page and append front panel image

Hi,
I am trying to create a report using the Report Generation toolkit in LabView 6.1 which gets printed to PDFCreator.
I have 4 front panel images that I am appending to the report, and I would like each image to be on its own page. I am trying to accomplish this using the New Report Page vi, but it doesn't appear as though it is putting any page breaks in the report, and no errors are being generated. Do the page breaks that this vi puts in only apply to text? What is another method that can accomplish putting each image on its own page? Simply creating and printing 4 reports will not work, since I need the 4 images to be in the same PDF file, and PDFCreator does not support appending to PDF files instead of overwriting.
Thanks,
Ian

Hi Ian,
According to the Help for "New Report Page.vi" you can append either text or another file to the new page. Are you creating a standard report?
Jennifer R.
National Instruments
Applications Engineer

Save a front panel image problem

Hi, i'm trying to save at run-time an image of my front panel, and the little code with the Invoke Node (FP.GetImage) works well but there is a problem, i have a background image for my front panel and this image don't show up in the image saved so i have an image with controls and graphs but a blank background. Is there some way to obtain an image of my ENTIRE front panel? Thanks

Hi,
Here's how I got ride of tghis issue, I use Windows "printscreen" function by simulating a keyboard stroke and then I get the data from clipboard (crop it it necessary) and save the image.
What I like about it is that the "crop" makes it easy to get just what I want when there's more than one monitor.
What I don't like is that it's a windows only solution.
Hope it helps
When my feet touch the ground each morning the devil thinks "bloody hell... He's up again!"

How can I save front panel images each time a loop iterates

So I've been working on some optical codes in LabVIEW for a while, I've read a lot of these similar questions but I can't seem to apply them directly to my situation in all cases.
I essentially have a code that shows an intensity graph that is continually modified in a for loop, I want to save a picture of that intensity graph each loop without having to manually label them. Is there something similar to the get image node that can do this. I've looked through the image acquisition in the vision VIs but only see references to hardware like cameras.
Attached is a simplified version of a changing intensity graph. With the get image I have to establish the names of 10 images and the path there before it will run and save like I want it to.
A million thanks to anyone who can help
Solved!
Go to Solution.
Attachments:
Sample image save.vi ‏19 KB

That worked wonderfully and is exactly what I need for the phase diagrams Im working with. I have a new and similar issue, I do have a camera showing us our laser source in a CCD image within my code. I was hoping to get a picture of that each iteration and hoped the solution you provided would work for both but the CCD jpgs are just black. I'm assuming I may have to use a different acquiring technique with that but dont know the best way to go.
Any help there? I cant really post a VI since the camera stuff wouldnt work but heres a screen shot of the front panel and the CCD image that id like to capture.
Attachments:
2.JPG ‏400 KB

Closing front panel of subvi

I have a main vi that opens many subvi with their front panel (they pop up as a normal windows not like modal). I need to close a subvi by pressing a button on it but I can't find any way.
Thank you everyone,
Massimo Ponte.

You can use vi.lib\UTILITY\VICTL.LLB\Close Panel.vi. Just pass it the name of the VI whose panel you want to close.
Sylke had a similar problem here.

Question on closing Front Panel references

I'm manipulating controls on the Front Panel of my VI. In doing this, I open a slew of references (to the VI, to the Front Panel, to its Panes, and to the objects on the Front Panel). Normally, before exiting the VI, I carefully close them (in LIFO order, of course), but a question has arisen:
I want to "export" a series of references to Boolean controls for use in succeeding VIs. No problem, while enumerating the controls (see above), I simply identify the Boolean references and build them into an array that I pass out. First question -- does anything "go wrong" if I also do a "Close Ref" in the main loop (after adding the reference to the array, of course)? [At present, I'm only doing a Close Ref on the non-Booleans]. Logic says this should be OK, as the Close Ref is mainly doing "garbage collection", and I've done a "copy" operation in building my array, but to a persistent structure.
Second question -- in my "cleanup" routine, I noticed I was "double-disposing" of the references, that is, I did a Close Ref on my array of Boolean References, but also was enumerating the entire Front Panel (as I did when I opened it) and disposing of the references that it found. Again, this should be no problem, but (in principle) I'm doing a Close Ref on two references to the Boolean control. It occurs to me that this is not really logical either -- I should be able to simply "abandon" the array of references -- although it takes up memory that can be "reclaimed" for other uses, the fact that it is an array of RefNums is a "so what" -- the contents of the array could have been a numeric or other "solid" data type.
Does this make sense? To summarize, what I'm trying to do is to "extract" some RefNums to Front Panel objects for later use. In the "extraction" process, I must open (and create references to) multiple objects, including RefNums to my "objects of interest". What I think I can (and should) do, once I've copied the RefNums I need, is to dispose (Close Ref) all of the RefNums that I opened during the extraction routine, and do something equivalent when I do the subsequent "cleanup" (which undoes any modifications I made as part of the extraction).
Comments welcome.
Bob Schor

I usually store the ref. at the beginning of my program, in Functional Globals, and i close them when the program does not need them any more.
I think this is the right approach. And it is simple

Printing front panel images of subvis from executables

I have a top level vi which calls a subvi which has all the plots I want to print in a report. This works as a vi as I can reference the subvi that I want to print the image of. When I make it an executable it no longer works, and even if I change the reference to request the image of the toplevel vi, so that there is a clearly viable (.exe) reference to print, it does not work. I can use file print window, but this does not give me the report. only the image. Any advice gratefully received
Solved!
Go to Solution.

We need to see your code to be sure, but I'm guessing you are getting the VI reference using the path to the VI. Well when an EXE is made the path to the VI will not be the same. You should use a Static VI reference to get a reference to the VI, and then the location on disk doesn't matter.
Here is a quick example I did a while ago using replacing VITs in a similar way.
http://forums.ni.com/t5/LabVIEW/building-an-executable-with-vits-with-Labview-2011/m-p/2384984#M7404...
Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
If 10 out of 10 experts in any field say something is bad, you should probably take their opinion seriously.

Close top vi front panel while sub vi front panel run

Hello,
I'm writing wiring a program and have several (several several several .. ) VI which launches Sub-VI with their front panel.
During there Sub VI, the Front Panel of the Top-VI get bored behind...
Is it possible to Hide this Front Panel while the sub-VI is running.
Thanks
Solved!
Go to Solution.

Sorry for this post, i didn't read every replies of the folowing topic :
http://forums.ni.com/t5/LabVIEW/closing-front-panel/m-p/300115
The VI of falkpl :HideFPvi.vi 24 KB is a very good method for my VI.
Sorry again, hope this'll help someone

Save sub-vi's (possibly closed) front panel image to a file

Similar Messages

Maybe you are looking for