Front Panel values lost upon save

I am just taking my first steps with Labview. I have created a couple of VIs and have managed to get I2C communication happening through a third party DAQ box. The problem I am having is fairly simple, I am trying to save VIs but they are not retaining the values I have entered in the Front Panel.
I have a top level VI and a couple of subVIs that contain lower level functionality for sending I2C messages. The top level VI has a couple of value controls that let me enter device addresses, etc. It also has groups of toggle switches that I am using to set bits that I later combine into bytes of data that I can send.
But whenever I save a VI the front panel settings are defaulting to some other value. I dont understand it, I just want the value box to hold the number I entered. And more importantly in this case I need the array of toggle switches to stay where I set them so when I run it again the same bytes are transmitted. But each time I open the VI, the toggle switches are all greyed out and set to 0.
Is this normal? How do I get controls to retain there values? Is there a design reason they do not?
Thanks for any advice.
Solved!
Go to Solution.

You may also consider initializing these values from a file. There are lots of posts which go into details about how you can do this. This is a much more flexible and maintainable approach then relying on the default value of a control.
Mark Yedinak
"Does anyone know where the love of God goes when the waves turn the minutes to hours?"
Wreck of the Edmund Fitzgerald - Gordon Lightfoot

Similar Messages

  • How do I store front panel values on LabVIEW RT

    I have a program that auto launches on a PXI. Is there any way to store the front panel values, so that the program starts up again with the last values that were used? The ini file method will not work because I am using LabVIEW RT.
    Regards,
    S G
    Certified LabVIEW Architect, Certified TestStand Developer, Certified Professional Instructor

    The best way to initialize inputs in RT is to use constants, or use the Communication Wizard in LabVIEW 7.0 to create a VI that initializes communication to the code running on the RT target. This becomes your user interface. One final suggestion is to use the Operate>>Make Current Values Default feature that is available in RT also.

  • Extended Rights Lost Upon Save

    I have form fields in a PDF document and have done this for years. The Extended Rights are enabled so that users can type in the fields. I just had a report that on Day 1, the users were able to type in the fields and save at day end. On Day 2, users were no longer able to type in the fields. It seems like the extended feature is dropping overnight. Multiple users reported the same problem. Has anyone seen this before and found a resolution?
    To add a twist: The users said that if they closed the PDF window and were prompted to save by Adobe, they clicked Yes and the next day they lost the ability to type in the form fields. However, if they went to File and Save before trying to close the window, they said they were able to type in the fields the next day as expected. Very weird! I was not able to verify what was occuring because I am just being told about this two weeks after the document was used in a training class . . . .

    You may also consider initializing these values from a file. There are lots of posts which go into details about how you can do this. This is a much more flexible and maintainable approach then relying on the default value of a control.
    Mark Yedinak
    "Does anyone know where the love of God goes when the waves turn the minutes to hours?"
    Wreck of the Edmund Fitzgerald - Gordon Lightfoot

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

  • JSP form values lost upon servlet request (RequestDispatcher)

    Hello,
    I have a query screen (jsp) that calls a servlet and gets results. However, although the results or errors display just fine (I do a setAttribute for them), I lose the initial values in the query form (values that the user input - which are stored in the request object). Shouldn't those values be maintained and displayed, since I'm using the RequestDispatcher and thus, I should have the same request object? Thank you, C Turner
    *****My JSP (the related code)*****
    <jsp:useBean id="form" class="com.foo.ActivityBean" scope="session">
    <jsp:setProperty name="form" property="*"
    </jsp:useBean>
    <HTML>
    <BODY>
    <FORM ACTION="ActivityFormHandler" METHOD="POST">
    <P><B>From Date</B>
    <INPUT TYPE="TEXT" NAME="fromDate" SIZE="9" VALUE="<jsp:getProperty name="form" property="fromDate"/>">
    <P><B>To Date</B>
    <INPUT TYPE="TEXT" NAME="fromDate" SIZE="9" VALUE="<jsp:getProperty name="form" property="toDate"/>">
    *****Java from my HttpServlet, ActivityFormHandler (acting as a formhandler)*****
    if (errors.size() == 0) {
    ActivityBean myActivityBean = new ActivityBean();
    myActivityBean.setBeanQueryValues(acctNumber, department, fromDate, toDate);
    Vector resultsVector = null;
    try {
    resultsVector = myActivityBean.executeQuery();
    } catch (CreateException ce) {
    errors.add("There was a problem retrieving the requested data from the database.");
    request.setAttribute("results", resultsVector);
    } else {
    //Data is not okay.
    String[] errorArray = (String[])errors.toArray(new String[errors.size()]);
    request.setAttribute("errors", errorArray);
    RequestDispatcher rd;
    rd = getServletContext().getRequestDispatcher("/public_html/ActivityQuery.jsp");
    //rd.forward(request, response);
    rd.include(request, response);

    For those interested in my question, here's what I figured out.
    Instead of:
    <INPUT TYPE="TEXT" NAME="fromDate" SIZE="9" VALUE="<jsp:getProperty name="form" property="fromDate"/>">
    Use:
    <INPUT TYPE="TEXT" NAME="fromDate" SIZE="9" VALUE="<%out.print(request.getParameter("fromDate"));%>">
    This allows the input field to persist the query value instead of blanking it out when the results are displayed. -ct

  • Main VI Menu event calling a subVI front panel

    Hi all,
    I have a subVI whose front panel is loaded upon calling by a main VI.
    I call the subVI using a User-menu event.
    the subvi-properties are set to allow close window and i am not handling a 'panel close' event.
    The problem is....
    when i run the main VI and click on the menu that loads the subVI front panel, subVI window opens, and if i click on the window-close, the main VI hangs.
    i understand that the control remains with the subVI only and never returned to main VI after i close subVI panel.
    but is it the only way to handle the 'panel close event' or any other way out to solve this?

    Try running the VI with highlight execution turned on, and see if anything unexpected is happening, or you could post your vi and let us take a nosey
    Message Edited by yenknip on 09-12-2008 04:30 PM
    - Cheers, Ed

  • Q:How to trim a VI's front panel at runtime?

    The occupied front panel space can be obtained by calling
    "GetPanelImage" via an invoke node. The resulting cluster "bounds"
    describes the union of all front panel objects. The front panel can then
    be resized to fit these bounds. The content of the front panel can be
    repositioned by manipulating "FrontPanelWindow.Origin". This "...Origin"
    points with an _unknown_ _offset_ (which varies with the FP´s layout) to
    the upper left corner of the front panel content.
    How to exactly calculate the origin from other front panel values?
    Thanks,
    TC

    You can use a VI Server to position the front panel of your subVI. Look at the Ghost in the Machine.vi example that ships with LabView.
    To see where to position the subVI, you need to know the position of the calling VI or of something on it. You could use a property node of the Get Details button.
    1. On the front panel on Panel.vi, right-click on Get Details and select Create >> Property Node
    2. Right-click on the Property Node and select Properties >> Position >> Left.
    3. Point to the bottom edge of the property node and pull it down to add another element. That element should default to Top.
    That will give you the coordinates of the Get Details button. Now use a VI server (based on Ghost in the Machine.vi) to place the subVI front panel the desired distance
    from the Get Details button.

  • How to display PSA screen capture on Front Panel

    Any one know how to display screen capture of PSA series specturm analyzer on front panel. I can save the JPEG file in the C drive, but I can't display on the front pannel. Please see my labview code.
    Solved!
    Go to Solution.
    Attachments:
    Capture screen E4446A.vi ‏21 KB
    reading and writing binary number.vi ‏22 KB
    yumg.jpg ‏20 KB

    Do you actually need to save the front panel image?  Or do you want to save a graph of the signal (spectrum) that you acquired?  If the latter will do the trick, you can simply read the waveform over GPIB (or whichever means you control the analyzer) into an array that is plotted to a waveform graph in LabVIEW.  You then save the image of the waveform graph as an image.
    Since you have all the data, you can even save the data which can be viewed later (and not only by LabVIEW).

  • Why does the Font color change on my front panel?

    I'm using the Font Dialogue to change the color of highlighted text on my front panel. After I save and reopen my app some of the Text will revert back to their original color (Black). Is this a bug in or am I missing something?

    I assume that you want all control labels with white text. If I change the black ones to white and save the VI, the white text color is retained. 
    LabVIEW Champion . Do more with less code and in less time .
    Attachments:
    Control Console.vi ‏90 KB

  • Hide front panel when opened

    I have a VI running as a back ground task (VI_A) to the main VI (VI_B). VI_B starts VI_A and the idea is that VI_A will be minimised on startup. There is a button on VI_B to restore the window and a button on VI_A to hide the window and return to VI_B.
    This is all working OK, I open VI_A front panel when called, VI_B minimises VI_A straight away etc, I am using the WINUTIL.LLB functions to perform this. The problem I have is VI_A front panel is visible upon start up for a couple of seconds (there is no real delay in my execution to minimise). I have tried setting VI_A to be at teh back within VI_A but still it appears at the front for a couple of seconds.
    Does anyone have any suggestions as to why this is occuring.
    Cheers,
    Wayne

    One thing that you could do is to change the Windows Appearance property to NOT open front panel when called. You can then have your main VI (VI_B) open the panel for VI_A as before, but it will not start with the panel open. If you are creating an executable, go to the VI Settings tab page and click on the line with VI_A and then Edit Settings. Turn OFF the Remove Panel property. This should work for you (I've done similar already anyway).
    Rob

  • Front panel USB connection to MB 990fxagd80v2

    Hi Gents, new member here with some issues on me last build. I assemble my families computers , about one every 5 years. Other than that I am not hot in computers. So when I get into a build I have some homework and studying to do, and some glitches. At this moment my newest machine is up and running Win 7 with a few loss ends. My case is an USB 2.0 era with 2 ports in the front bottom behind a little door. Each USB cable has 3 wires ending in a flat 3 pin female plug. The motherboard has 2 USB male ports, 9 pins each, one coded blue the other red each one has an alignment notch. This MB came with a sack of M-connectors to be an easy transition between the front panel plugs and the Motherboard, so, 2 of the M-connectors are red and blue, and have alignment lugs that appear to be made for the USB ports on the MB. The problem is they do not fit. While I am gentle and careful I don't believe they fit. I have other front panel issues I'll save for another time. My Gazelle case seems to use different nomenclature than the motherboard. But the USBs are the issue now, anyone have some light on this subject? I would also like to convert one of the front USBs to 3.0.

    "Each USB cable has 3 wires ending in a flat 3 pin female plug."
     That can't be right as USB are 4 wire, red, white, green, black. Connectors are 5 or 10 pin plugs with no connection on the 5th pin not used on both types & 9 being the key on the 10 pin plug.
    "I'm not sure is I have a variation from the standard MB or what..."
     Any connectors, MB headers are standard throughout the industry therefore they will be the same from all manufacturers.
    "or is the connection does not use m-connectors"
     You should not need m-connector for USB anyway. m-connector was introduced mainly for front panel connections that had individual wires for each LED, switches and such. The set in the pic I show is from old P35 MB.
     Can you post a photo(s) of the case connectors you have?
     See here how to add photo's: https://forum-en.msi.com/index.php?topic=90789.0
     Personally I use Photobucket to host my pics.
     M-connectors for USB should be clearly marked as such if the MB even came with any for USB. Over the years they have eliminated some and I think the ones for USB were eliminated.
     USB plug:

  • Auto save and auto recover of front panel controls/indicators values

    i just want that when i exit from the VI's front panel all controls and indicators current values get saved automatically and when i get back into this vi,those values get recovered automatically.
    Like if i incremented numeric control value from 1 to 5 , when i exit from the vi the value 5 get saved automatically and when i get back into the vi ,it shows the recovered value 5 to me automatically.
    best regards

    I'm Back
    I was mistaken when I said the you could select to save either the controls or indicators or both in the Open G Vi's, They are hard wired for both. I made minor changes to these VI's for my app.,  because I only needed the controls to be saved. The example I am providing uses the Modified VI's, but I've also included the originals.
    Modified
    Read Panel from INI.vi
    Write Panel to INI.vi
    Originals
    Read Panel from INI.vi
    Read Panel from INI__ogtk.vi
    The ability to select either or both could easily be implimented into these Vi's using a case selector and an enum wired as an input
    Controls only
    Indicators Only
    Both
    Incase you don't have the OpenG toolkit I've provided the necessary files for this example to function
    Extract the zip file to your User.lib directory then open Usage.vi
    Hope this helps you
    Georges Janveau
    Attachments:
    Config File Usage.zip ‏861 KB

  • Saving the Control Values on a Front Panel

    I am creating a VI in which I have approximately 10 front panel controls that can be changed by a user. Instead of entering the same values over an over again, I would like to provide the user the option to save a set of control values that can then be loaded the next time around via a drop-down box. Before I began I just wanted to see if anyone had done anything similar. I was stumped as to how to approach it. Any suggestions?
    Matt

    Matt,
    You can also use a datalog file. LabVIEW can write and read clusters to a file, and as long as the cluster don't change you should be fine.
    Basically your code would grab the value of each control, bundle it into a cluster and save that cluster to a file. For reading, you read your cluster from the file and get each individual value to drop it in the right control.
    I'm sure there are some shipping examples on this too.
    I hope this helps.
    Regards,
    Juan Carlos
    N.I.

  • How to Save & reload front panel position

    I would like to save the front panel position into an ini file or registry, so that the next time the program is used, it comes up where the user left it.
    With the Invode Method: Front Panel.Run-Time postition.Get positon  
    I can get all the position data I want:
    left-top
    state
    monitor
    However...  How do I set the same information at startup?   
    There's no  Front Panel.Run-Time Position.Set position. as far as I can see...
    To set position, state and monitor values, it seems I need to first call  FP.Open for the state, then FP.Run-Time Position.Centered to select the monitor, and then FP.Run-Time Position.Custom to set the position....   
    That looks weird and complicated...    Am I missing something here?   Is there a more elegant approach?

    NI explains the difference between Property nodes and Invoke nodes as this.
    Property nodes access the properties of an object and allow you to read/write those properties.
    Invoke nodes perform actions on an application or VI allowing you to get and sometimes set attributes of those actions.
    Sometimes there is some overlap between Properties and Methods as you noticed with the "Get Position" method and the "Panel.Position" property. But most of the Methods do not have a similar Property. For instance, there is a Method you can use on a front panel item called "Get Image". This will return image data about the item that will let you save the items current visual appearance to a graphics file. (.bmp, .png, .jpg) There is no equivalent property to do this.
    So it really depends on what you are trying to do as to which one you end up using.
    Ed
    Ed Dickens - Certified LabVIEW Architect - DISTek Integration, Inc. - NI Certified Alliance Partner
    Using the Abort button to stop your VI is like using a tree to stop your car. It works, but there may be consequences.

  • Front panel entry data save

    Dear All:
                   I modified the data like the sampling rate from 1000Hz to 100Hz in front panel and save the vi with normal "save" function . It defulted to be 1000Hz when the vi was restarted. What is the proper way to save the entry data in the front panel? Comments will be greatly appreciated!
    zibin

    Hi zibin,
    If you're only concerned about that particular control, you can right-click on it and choose "Make Current Value Default" before saving your VI.  If you want to preserve every value on your front panel, go to the Edit menu and choose "Make Current Values Default" before saving your VI.  With both of these methods, the "new" default value is the one that will be displayed the next time you open the VI.
    Hope this helps,
    -D
    Darren Nattinger, CLA
    LabVIEW Artisan and Nugget Penman

Maybe you are looking for