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.

Similar Messages

  • Problem printing front panels from LabVIEW 5.1 using a different O.S.

    I have an excecutable that was developed using LabVIEW 5.1 on a Windows NT OS platform. I am attempting to run this executable on a PC using Windows XP. Everything appears to be running just fine until I attempt to run a portion of the program that executes a "print front panel upon execution" function that prints out a table, created from a sub vi running in the code. The print command executes, however, the font sizes that are generated on the hardcopy are not what I had originally intended them to be. Also, sometimes the page breaks are in the wrong place, thus making my printouts quite illegible. I ran the same executable on a workstation running Win2000, using the exact same printer, and everythin
    g printed out just fine. Is NI aware of this issue, and are there any possible solutions for it?

    The versions of labView that NI supports win XP are versions 6.1, 7.0. and 7.1
    You could be seeing an incompatability between version 5.1 and XP
    LabView 5.1.1 officially supports windows 95/98/NT/2000

  • 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

  • Print front panel

    I have been going through messages for a while but just can't seem to find exactly what I'm looking for. I need to print a waveform chart that has two plots that update at about 10Hz. Simple enough, right? Problem is that the report vi's have no way I can see to easily enlarge the image. I tried putting a larger chart in a sub vi that prints after executing but the chart only get part of the data when I run it. Then I tried the invoke get image method but can't find an indicator for the image data. Is there a way to print an enlarged waveform chart image? It would be even better if I can just print a front panel of a subvi with the same data on the waveform chart that appears on my top-level VI.
    PaulG.
    "I enjoy talking to you. Your mind appeals to me. It resembles my own mind except that you happen to be insane." -- George Orwell

    What I have done in these situations is to have a graphs that is sized to printout the size that I want. I then update the graph from the program data, grab an image of the graph using the Get Image method, and save the image as a jpeg file. I can then either printhout this file or include it in a standard report.
    OR you can use Draw Flattened Pixmap.vi to turn it into a form that will go into a picture indicator
    OR you can create a VI with the graph on its front panel that is set to print itself when it finishes executing - or which you print programatically
    Mike...
    Certified Professional Instructor
    Certified LabVIEW Architect
    LabVIEW Champion
    "... after all, He's not a tame lion..."
    Be thinking ahead and mark your dance card for NI Week 2015 now: TS 6139 - Object Oriented First Steps

  • 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

  • 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

  • Reference to control on main front panel fails when subvi front panel is closed?

    Hi All,
    I'm experiencing an odd bug. In my code, I use a subvi to control a piece of hardware. This subvi has controls for all of the functions of my hardware.
    I'm changing the value of one of these controls from my main front panel by running a reference to a knob on my main front panel into the subvi, grabbing the value of the knob with a property node, and then updating the value of the subvi control using a signaling property node.
    This works fine when my subvi front panel is open but fails to work at all when the subvi front panel is closed.
    I'm new to labview , so any help is appreciated.
    Thanks,
    Arpan
    Solved!
    Go to Solution.

    What is your LabVIEW version?
    Front panels that are not shown are typically not updated and might not even be loaded into memory.
    The presence of certain code elements (e.g. property nodes) often forces the front panel to be in memory even if it is not shown, but I haven't studied it in a long time so there might be subtleties. Maybe somebody from NI can give more details.
    If it does not work unles the FP is open, open the front panel minimized to avoid distraction.
    Can you attach some code? Maybe there are better ways to do all this anyway.
    LabVIEW Champion . Do more with less code and in less time .

  • 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.

  • 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

  • Looking for a way to programmatically set the visible portion of the front panel when a subVI opens

    I am looking for a way to programmatically set the visible portion of the front panel when a subVI opens.  Haven't found any posts that relate, but I'm not sure how to ask the right question.  To be clear, I want to write a helper VI to go through a list of subVIs to make sure the background images are all in the same place when their respective subVIs open.  I hate manually playing with scroll bars before I save each of the VIs...  I'm figuring I need to find the top/left location of the background image (know how to do this already) and then set a VI FP property to  these values or some offset, but I can't find the relevant property. FP:run-timeposition:custom looked promissing, but only affects the location of the window, not the area of the front panel the window is displaying.
    Solved!
    Go to Solution.

    Cool.  Getting closer.  The way I implemented your suggestion affects the subVI only if it is open.  I can use this to do what I'm after, perhaps putting the code into each subVI.  Maybe open all subs, run the helper, and save.    Seems like I'm missing the elegant version...
    My proof of concept code:

  • 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

  • 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

  • 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

  • Dynamically opened front panel won't work in executable

    I am dynamically opening the front panel of a VI from the top level VI. After I build an executable, this does not work anymore.
    Any ideas?
    Scientia est potentia!

    See the marked solutions in these threads.
    http://forums.ni.com/ni/board/message?board.id=170&thread.id=402041
    http://forums.ni.com/ni/board/message?board.id=170&message.id=400907&query.id=212194#M400907
    Message Edited by elset191 on 07-23-2009 03:38 PM
    Tim Elsey
    LabVIEW 2010, 2012
    Certified LabVIEW Architect

  • Remote front panel with labview 8.6 executable

    I am trying to create a remote front panel of my application, built in an executable using Labview 8.6. I want to run that application on a target machine (not the one used for developing the project) and view and control the front panel of the VI from a web browser on another computer.
    I have followed these steps: 
    How can I use remote front panels with Labview Executables?
    But when I finally open the web browser and navigate to the URL I obtain that the page cannot be found.
    I have my Labview project created and I have built a web page using Web publishing tool. I have saved it in my Labview 8.6/www directory and added it to the project. I have built my executable including HTML file and copied all the obtained folders to the target PC.
    Then, I have modified the .ini file like in the step 7, but when I arrive to the step 8 I don't know what to do. Which  niwebserver.conf should I modify? The one localized at Labview 8.6 directory of the target machine? Or the one that is created in the directory where I have copied the executable when I run the executable?
    In the DocumentRoot tag  I have to replace the default Labview/www with the location of my HTML file. Should I use quotation marks or no?
    Have you got any ideas of what is happening?
    Thanks!

    Ok, but when I create the executable, in the folder where the application.exe and .ini are there isn't a file called niwebserver.conf. When I run the application a file with this name appear in the directory (the one I include), but it hasn't the section Directives that apply to the default server as in the manual.
    What I have done is to copy the niwebserver.conf file ubicated in the Labview 8.6 of the target machine in the same directory of the executable but it doesn´t work...
    niwebserver.conf
    ServerRoot "."
    ErrorLog "./logs/error.log"
    LogLevel 3
    ServerName default
    DocumentRoot "./../../www"
    Listen 80
    ThreadLimit 10
    TypesConfig mime.types
    DirectoryIndex index.html
    LoadModulePath "./modules" "./LVModules" "./.."
    LoadModule LVAuth lvauthmodule
    LoadModule LVSnapshot lvsnapshotmodule
    LoadModule LVRFP lvrfpmodule
    LoadModule LvExec ws_runtime
    LoadModule dir libdirModule
    LoadModule copy libcopyModule
    AddHandler LVAuthHandler
    AddHandler LVSnapshotHandler .snap
    AddHandler LVRFPHandler
    AddHandler LvExec
    AddHandler dirHandler
    AddHandler copyHandler
    CustomLog "./logs/access.log" "%h %l %u %t \"%r\" %>s %b"
    KeepAlive on
    KeepAliveTimeout 60
    Timeout 60

Maybe you are looking for