Hiding front panel with built applications

I've seen and used the techniques to run a VI with a hidden front panel. I have the VI open a reference to itself and it works as expected. However when I build my code into an application, it no longer works. Watching Task Manager I see the application quit when the panel becomes hidden. I've even tried building the window-less.zip example I downloaded from the NI website. It worked in VI form but not in EXE form. Anyone have any suggestions?
Andy Brown
Averna

Andy,
I ran into this problem back in LabVIEW 5.1 when I was developing a game in LabVIEW. I had an introductory screen that allowed the user to run the tutorial or play the game, and upon selection I hid the introductory screen and displayed the panel of the appropriate subVI (tutorial or game). Unfortunately when I built an executable, it would end once I chose to run a subVI, and I later found out that this is because closing the front panel of an executable essentially closes its reference. My workaround was to use LabVIEW 6i and the new tab control to keep all of my front panel operations in the same VI, and programmatically switch between the tabs in order to display different screens (like tutorial, enter info screens, the actual game, etc.)
I hope this
suggestion helps. There may be a way to bypass the problem with closing EXEs once their front panels are gone, but I do not know of one.
Good luck with your application, and have a pleasant day.
Sincerely,
Darren Nattinger
Applications Engineer
National Instruments
Darren Nattinger, CLA
LabVIEW Artisan and Nugget Penman

Similar Messages

  • 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

  • Same object size (front panel) with different screen resolution

    Hi everybody,
    I realised an application, and I try to instal it on various computer. The probleme is that they haven't the same screen resolution, so the front panel is not the same on each computer. It is possible to build an application which have the same front panel with different screen resolution ?
    Kriss.

    Hi Krisss,
    switch off any "adapt to screen resolution" switches in the VI properties...
    You should also define "same front panel" and "same object size"! Do you mean the same pixel size or size in mm or size in percent of screen?
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Saving Image of front panel in an application

    See attached image.
    Using my source code, I can save the image of the front panel with no problem. However, when i build an application and run this, the image of the front panel does not save. Can anyone help?
    Attachments:
    Save Image of Front Panel.JPG ‏19 KB

    This piece of code does the trick, don't mind the wiring.
    André
    Message Edited by andre.buurman@carya on 09-17-2007 05:39 PM
    Regards,
    André
    Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)
    Attachments:
    Top level dir.PNG ‏10 KB

  • Programmatically Open a Remote Front Panel with Panel Open Method

    Hi,
    I am trying to open the front panel of the VI on my cRIO-9024 through a remote computer. Currently, I am able to run the VI with no problems with the RUN VI method; however, when I try to open the front panel, I receive "Error 1043 - This property or method is not supported in this version of LabVIEW" or the Front Panel is simply not visible. My cRIO is configured to allow TCP/IP protocol, The VI is visible, and I have made my project into a source distribution on my cRIO.
    Any help or suggestions regarding this problem would be great. I am very new to LabVIEW.
    I have attached a screenshot of my block diagram and project.
    Thanks,
    Jake 
    Attachments:
    Block_Diagram.PNG ‏12 KB

    Project Img
    Attachments:
    MyProject.png ‏15 KB
    MyProject.png ‏15 KB

  • Opening multiple sub VIs (front panels) in an application

    Hi, 
    I am working on a small process control application. The main VI represents a layout of various equipment (pumps, valves, heat exchangers). Each TYPE of equipment
    can be turned on/off through a particular subVI. The subVI is displayed when the operator clicks on the component.  At the moment only one subVI front panel can be loaded. I would like to have multiple panels open at the same time; this to include multiple instances of a same VI and different subVIs.
    I have tried to set properties in the WindowsApperance dialog box but cannot acheive the desired operation. 
    Any suggestions?
    Thanks

    Trust my personal experience: You do NOT want multiple dialog windows open.  The users will hate you and curse your name if you do.  You really want to use subpanels and limit what the user can do.  Subpanels are a way of inserting a VI's front panel into another VI's front panel.  So you want to have a section of your main front panel that the user can load whatever control subVI they need.
    There are only two ways to tell somebody thanks: Kudos and Marked Solutions
    Unofficial Forum Rules and Guidelines

  • Using a "menu ring" feature on the front panel with event structures

    hello - right now i have many event cases controlled by many "ok buttons". i would like to use a menu ring on the front panel to save space from all those buttons, but i don't see how it will work with all the individual event cases. currently each event is tied to a single button, and the menu ring acts as one thing on the block diagram so i can't tie an event to a choice in the menu. any suggestions? thanks....

    Alternativley, you could use an enum control instead of a menu ring. It will name the cases according to the selection automatically.
    If you want to use a menu ring and strings, you could do something like in this image.
    Message Edited by altenbach on 02-09-2006 01:43 PM
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    RingText.png ‏3 KB

  • Publishing front panels with web server

    Hello,
    I'm working with LabView 7.1 and trying to publish a front panel by means of the web server.
    The problem is that I'm only able to connect to the VI through the internet when both , the host and the remote are networked. 
    When I try with computers outside that network the browser doesn't find the webpage.
    Thank you for your help
    Lian

    You need to know:
    The public IP of your router.
    The private IP of your LabVIEW server.
    The port used by your server.
    First you need to forward the port on your router. Basically, you need to tell the router that incoming NEW connections to a certain port of the public IP of the router should get forwarded your server. (Without forwarding, the router only works for outgoing connections). Once the port is forwarded, clients located on the outside need to connect to the public IP of your router.
    Possible complications:
    Your ISP might block certain incoming ports for security reasons. In this case you can configure a different port for the server.
    With some routers you will not be able to connect to your server (for testing) with a client located on the same LAN via the public IP of the router. Only routers that incorporate a loopback proxy support this. What is the brand and model of your router?
    Good luck!
    LabVIEW Champion . Do more with less code and in less time .

  • Storing front panel values between application runs

    Labview 6.1 built application
    I have built an application in which the operator can change setpoints that transmit through datasocket to a central controller.
    The operator needs to be able to close his PC down, each time he reboots the application reloads with the default levels, this can cause alarm problems etc.
    Is there a way of him entering the values to an area that will save his last values and reload as the datasocket values when the executable is restarted?
    (his/her) no offence.
    Any code or advice, thank you.

    Hi,
    You can use configuration files VI placed in the File I/O section. I use LV7 and It has it, I supose LV6 also has it.
    What you can do is create an ini file with a configuration by default
    and then when program starts you read it and load this values to your
    window. You can load them reading from the ini file when you open the
    window that contains these levels. Finally, in this window you can
    create a button to save the new values that the operator enters for the
    levels. So If the operator need to save new values, he/she will press
    that button and the values will be saved to the ini file and then when
    operator closes his PC, reboots it and restarts the application the
    default values will be the last values the operator has entered and
    saved in the previous execution of the program because each time you
    restart it the values are loaded from the ini file.
    I hope this helps you,
    ToNi.

  • Audio Front Panel with MSI

    1.Product Type: Motherboard MSI G965M MS-7241 with integrated Realtek audio and updated driver for Windows Vista - 6.0.1.5331
    2.BIOS version: AM v. 1.1, 2006-10-23
    3.External VGA Type: NVIDIA GeForce 7600GS
    4.CPU Type: Intel Core Duo 6400
    5.Memory Type: Dual Channel 2GB
    6.Power Supply Type: 400W
    7.Operating System: Windows Vista
    8.Problem Description: Front panel audio connectors 3,5 mm plugs are not operating regardless they are connected to JAUD1 port. Plugging with the headset with microphone doesn't gives any effect - they are unvisible by the system.

    Does the case support HD Audio"Azalia"?
    Have you tried to disable the front panel jack detection under analog connection settings (click on the wrench) in the Realtek HD Manager?
    This thread may or may not help: https://forum-en.msi.com/index.php?topic=105631.0

  • I want to save an image of the front panel, (with data), after every VI run

    When I try to copy the front panel (using a select all), and paist to paint, all the data in the graphs show up as they did after the last run, but the data in the charts dissapear. The chart itself is copied but the data is not. Any ideas on how to solve this?
    Thanks,
    Brian
    Attachments:
    Brians_graph_compilation2.vi ‏1363 KB

    This Knowledgebase also has some information on programatically saving VI images
    http://digital.ni.com/public.nsf/websearch/942DAA35C7B35616862565FE005F713F?OpenDocument
    (KB 197BB7VJ if the link doesn't work).
    Note that you don't have to put the code in the VI you are running in order to save it to a file, so you don't actually have to modify your VI. You can just run a seperate VI that uses the VI name from the first one (I've attached a VI which could either be run standalone or used as a SubVI, as well as an example of using it as a SubVI).
    If you don't want to do it programatically you could just hit the print screen button on your keyboard and then paste it into paint and crop off the extra windows stuff.
    Attachments:
    CreateVIJPEG.vi ‏34 KB
    ImageExample.vi ‏24 KB

  • Lock front panel with has titel bar?

    How can I lock a front panel that has a title bar?
    I do not want that the user
    - close the window --> ok, vi-property
    - resize the Window --> ok, vi-property
    - minimize the window --> ok, vi-property
    but:
               I also want, that the user can't move the window using the titel bar
    I do not want to poll permanently the windows-position.
    Any idea?

    Hello zav,
    via vi->property node you can also set the window size. So switch of
    closing/resizing/minimizing in the vi properties dialog and do the rest
    in a small while loop parallel to your main program (permanently set
    the window size to the size of the screen).
    Attached is a picture of a sub-vi calculating the window position
    regarding to screen size. The output is wired to a property node
    'Frontpanel Window.Window Bounds'. Hope this helps...
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome
    Attachments:
    WindowSize.png ‏4 KB

  • Dsc 8.2.1 cannot find files with built application

    I am building an application using the DSC 8.2.1 with LV 8.2.1.  I am running into the problem where I go to start the .exe and I get asked for varxnode.xnode and a ton of other files.  It feels like I have to copy almost all of my labview development folder over to get all the vis required, which is VERY tedious and will make for a huge .exe.  I am sure I am doing something wrong.
    My program is using Fieldpoint 5.0.1, DSC 8.2.1, and LabVIEW 8.2.1.  In the .exe I have debugging enabled (I get an error that the vi became broken when I try to disable debugging.), Enhanced DSC support (I read that I need this enabled to use the netowrk published shared variables).
    THanks for your thoughts.
    Kenny

    Kenny,
    In order to eliminate the problem, you will probably want to disable enhanced DSC support.  Here is a description of what the Enhanced DSC Run-Time support actually does:
    Enable Enhanced DSC Run-Time support (LabVIEW DSC Module) - Enable this feature if your application uses VI server refnum (green) methods and/or properties to programmatically modify a library file. If your application uses the VI server refnum methods and/or properties to programmatically modify a library file and you do not enable this option, then those methods and properties will return errors when run from the built executable. You do not need to enable this option if your application uses the online (purple) variable refnum properties to manage processes and shared variables. You do not need to enable this option to programmatically deploy or undeploy a library file. Enabling this option will increase the size of the built executable and reduce start-up performance of the built-executable and should be enabled only for applications that use the VI-server refum methods and properties for modifying library files.
    If your program is not programmatically modifying libraries using the VI-server refnum methods, you will probably not need that support.  However, if you are, you will need to install the DSC Run Time System onto the machine.  There is a KB on this topic here:
    http://digital.ni.com/public.nsf/websearch/DD1E23328AF0A303862570A4006F4134?OpenDocument
    I hope that this helps.  Have a great day.
    Regards,
    Message Edited by Coal Man on 05-16-2007 10:19 AM
    Brian Coalson
    Software Engineer
    National Instruments

  • Porblems with built application, using wordsub.llb

    I am trying to compile a Vi that uses the New Report.vi to create a test datasheet. When I run the Vi in development mode, it works ok. When I run it after using the "build application" fucntion, the vi gives an error (Code 7). The description for the error says something about the "open vi reference". I believe the error has something to do with the "word" related vi's that are contained in the wordsub.llb.
    Does anyone know what I am doing wrong?
    Is it something with the build process?

    Are you using LabVIEW 8.0 or later?  If so, the instructions for building an executable are incorrect...they state that you must add _wordsub.llb as a Support File, but you should actually add _wordsub.llb\Word Dynamic VIs.vi as a Dynamic VI when building the executable.  Also, if you are calling any Excel-specific VIs, you would need to add _excelsub.llb\Excel Dynamic VIs.vi as a Dynamic VI as well.
    Try this out and see if it works...we are planning on changing the documentation for the toolkit for the next release to indicate the different steps you need to take for building an executable with Report Generation Toolkit VIs in LabVIEW 8.0 versus previous versions.
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

  • Dual monitors issues with Built application

    I made a vi that uses both monitors.  I set the run time position to the second monitor on one vi and the first monitor on the other vi.  The vi running on the primary monitor calls the second vi on the second monitor vi the Vi Server.  This works great when working in the development environment.
    But when I build the application, the vi that is supposed to be on the second monitor, shows up over the vi on the primary monitor.
    Did I miss a setting in the Application Settings??
    Kenny
    Kenny

    Hello Kenny,
    might be a bug. but the following code offers more options:
    Ton
    Message Edited by TonP on 09-02-2006 04:35 PM
    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!
    Attachments:
    fillscreen.JPG ‏35 KB

Maybe you are looking for