Save and recall front panel configurat​ion on FPGA

First of all, I am a first time user of Labview.  The application is with an FPGA on a NI-9146 board.
My question is, I would like to save the front panel settings when I exit the application, then recall them the next time the application is started. 
Seems to be a few ways to do this but are not supported with the FPGA module. 
The application is fairly straight forward timing and the Windows host PC will provide a GUI to the operator.
Solved!
Go to Solution.

Someone may correct me if I'm wrong, but this task is more tedious then it needs to be.
The normal way of doing this on the FPGA is to plop down a FPGA read function for every control on the FPGA front panel, then write them to a file.  Probably using an OpenG function, but really something like the binary write would work if you don't expect to add/remove items.  Then when the application starts you need to reverse the process ploping down a FPGA write function for every control.
Now there is a slighly easier way that in theory works in a limited use case.  The FPGA VI when running is just like a normal VI and you can get a reference to it.  Here you could run the OpenG Write Panel to INI, and Read Panel from INI.  These are two canned functions that save tons of time.  Now the reason this might not work for most FPGA developers is because in the end, the goal is to not see the FPGA VI and instead only run the bit file and call into the FPGA using the hooks NI provides.  It sounds like you are going to have the VI shown anyway so this method may actually work for you.
It does kinda suck and I think it would be nice if NI had a way to read and write all FPGA front panel controls at once for things like this.
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

  • 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

  • Anyone advise me on how to save and recall the satate information of a cluster of combo boxes?

    I have a set of combo boxes saving a devices state information. I would like to save and recall all the selections. I know there are properties to access the selected items, but searching about, I'm not sure the technique to do this. I would like to save/recall in XML format. I made an attempt and it saved the combo box data, but not the selections. Thanks for any help.
    Solved!
    Go to Solution.
    Attachments:
    TestStateXmlSave.vi ‏22 KB

    I'm not sure what you mean by a bool of array.  There are no booleans in your program from what I can see.  If I understand you correctly, your trying to read the individual elements of your cluster control, is this right?  You can do this using Property nodes.  This is just and example.  Let me know if I'm off base. 
    Use a For loop to process your elements that you want to save.  I would consider using an Event structure for your main VI.  This will do what you are trying to do here, and it will be more compact, cleaner, and more scalable.
    Reese, (former CLAD, future CLD)
    Some people call me the Space Cowboy!
    Some call me the gangster of love.
    Some people call me MoReese!
    ...I'm right here baby, right here, right here, right here at home

  • On demand Save and Recall Control Values, Elegant solution

    I have a developed a sub-VI that will gather ALL of the information (metadata) for each Control save it to a file to be retrieved later.  This is very useful to recall user-specific layouts after a power outtage, for transfer to another machine etc...  Could be easily modified to recall a default setting file as well.  NOTE: cannot save or recall Boolean Latch data.
    Hope this is handy.  Let me know what you think...
    Thanks
    Dan
    Attachments:
    save and recall settings.vi ‏25 KB

    The LabVIEW Idea exchange is to propose and vote for ideas to be implemented in future LabVIEW versions. Are you expecting NI to implement something similar in the future? If you are just showcasing a programming example, the LabVIEW forum might be a better place. Please clarify.
    LabVIEW Champion . Do more with less code and in less time .

  • Recalling front panel

    I know it is possible to show a VI's front panel when it is called by selecting "show front panel when called" in the VI Properties.  If you were to close this vi or stop it, you could once again view its front panel when it was called again.  Now with that said...   Is it possible to call a VI's front panel many times if you don't close it or stop it?

    Are you asking about showing multiple instances of the same front panel at once, or just the ability to open and close a front panel while the VI is running.  If it's the latter, you can use the VI Server to do so.  Get a reference to the VI using the Open VI Reference primitive, then wire that into a property node and select Front Panel Windowpen.  If you set that to true, the FP will be visible, if it is false, the FP is hidden.
    If you are trying to show multiple instances of the front panel, that's more difficult, but also possible.  If you want to do that, you will have to clone the VI in question or use a VI Template instead of a normal VI.  What you do from there depends on why you want multiple instances -- is it for showing historical data, or for showing multiple versions of the same data? 

  • X-Fi Titanium PCI-E and the front panel from my case

    The plug from my frontpanel fit onto the soundcard, but when I plug in a headset I can't hear anything. I can hear sound on the left side of my headset when I plug it in only half the way.
    My Case: Tronje H-650B
    What makes me thinking is the fact that I can hear sound, but only on the left side of my headset and only when the plug is only the half way in.
    Hope you can help me to solve the problem.
    Greetings.

    Re: X-Fi Titanium PCI-E and the front panel from my casev I tried hooking up the HD Audio front connecto of my Lian-Li A05 to the X-Fi Titanium. However, the headset is not detected (neither in nor out). Looking at the pinout I noticed that my connector has the correct pins for the signal, but lacks the following wires (completely missing):
    <div class="pCellBody">4 PRESENCE#? Acti've low signal that signals BIOS that an Intel HD Audio dongle is connected to the analog header. PRESENCE# = 0 when an Intel HD Audio dongle is connected<div class="pCellBody">7 SENSE_SEND? Jack detection sense line from the Intel HD Audio CODEC jack detection resistor network
    I take it these are required to make the card detect the devices. Is there a way to circumvent this?
    Also, the manual gives a confusing description:
    "Intel HD Front Panel Audio standard only.
    Not compatible with AC97 or Intel-compatible HD Front Panel Audio"
    So it is compliant with Intel, but also not compatible with Intel? Or is there a difference between "Intel" and "Intel-compatible"? This makes no sense...

  • Save Part of Front Panel as picture - sharing VI and asking for advices

    Hi,
    I use LabVIEW 8.2.1. (DSC&RT),
    It is common (at my work) that we want to save some parts of the Front Panel and to add it to the LogBook.
    we usually do PrintScreen and then cut the picture to the boundaries we want using 'Paint'.
    I have created a simple procedure that makes it easier and the user can now select the boundaries of the picture at the Front Panel.
    You can see the 2 VI's attached, (try2.vi is a sub vi of try.vi)
    Open 'try.vi' and press 'select boundaries' button and drag the boudaries with your mouse,
    after you have selected the boudaries, press 'save picture' button.
    I hope there are no bugs.
    Originally I have wanted to use drag and drop, but i didn't really understand what is going on behind the scenes
    when I used it.
    For example - look at the example (at NI Example Finder at LabVIEW) 'Drag and Drop - Multiple Data Types to Start Drag.vi'
    (C:\Program Files\National Instruments\LabVIEW 8.2\examples\general\dragdrop\Drag and Drop - Multiple Data Types to Start Drag.vi)
    (or via typing 'drop' in at the NI Example Finder search)
    1. I don't understand how the 'Drag and Drop Data' (located at the Application Control Palette)
    2. I don't understand the inside terminals of the Event Structure of 'Drag Enter' and 'Drop' -
        for example - 'available data names' and 'accepted?'
       where can I get information help written about any of the Event Structure inside terminals?
       (it does not appear in the Context Help when I enter with the mouse)
    3. Do you have any comments on the VI  I did ?
    4.I am planning to use this VI as a part of Log-In data to a follow-up LogBook Using Mysql as Database and NI sql connectivity toolkit,
       so users will be able to insert information to the LogBook from the Front Panel, and attach pictures of the Front Panel.
      Did anyone here has performed anything similar ?
    If you send me corrections of someting or any other NI item, please send it in a version that I can see it (I use Labview 8.2.1 DSC&RT)
    Sincerely Yours,
    Amitai Abramson.
    Attachments:
    try.vi ‏67 KB
    try2.vi ‏23 KB

    There are examples that come with the database connectivity toolkit so you are going to have to be more specific about your question. Whether you call it a logbook or something else, it's still a database and a database write is a pretty generic opertation. If you need help in the design of the database, then you should say that is what you need.
    The event data is going to change depending on the event and the type of control. Again, do you have a specific question?

  • LV 8.0.1 'NOT RESPONDING' and/or 'split' and unusable front panel while scrolling

    Hello,
    Is anyone aware of any display or front-panel glitches and bugs with LV 8.0.1?  I have been using LV for years, but I have never seen the front panel tear itself (literally) in sections while I use the standard scoll bars at the edges of teh screen, then become completely unusable and go into [NOT RESPONDING] mode (???). In other words, my front panel displays have always moved as one continuous piece when scrolling.  During these recent episodes, I would use the scroll bars and parts of my front panel displays would not move while the other section(s) tore away and scrolled as I commanded.  When this happens, my entire PC would slow down, the CPU usage would rise and a approach 100%, and the VI was unusable.  I have been writing a particular VI for several months, starting in LV 6.1, then LV 8.0 PRO-DEV, and recently upgraded to the LV 8.0.1 'maintenance' release.  The problem that  I describe here began to occur within two weeks of the maintenance upgrade.  The problem seemed to be propagating to my back-up version after I opened each VI in unsuccessful attempts to find a VI that did not appear corrupted.  It seemed as if any VI that I opened was going to be plagued by the bug that I described above and I thought that I was going to lose months of expensive work and my job!!!!.  In a last ditch effort ( and a stroke of pure genius) I started saving some of these coorupt version as 'PREVIOUS' in LV7.1 format.  This seems to have turned the situation around, for now, and saved my VIs from becoming corrupted and completely unusable. 
    Please let me know if anyone else has seen this.  Also, please let me know how to avoid this, in the future.  Does this indicate corruption of my LV 8.0.1 PRO-DEV environment or the VI files (or both)?  Does NI have tools to correct these corruptions?
    Thank you.

    Thank you. I can only point to the following events/ techniques that were somewhat different from my previous experiences/ techniques:
    1) Performed 'SAVE AS... ' new file name to these files over several months and several times a day using similar filenames with only one number character different between them
    2) Logging long data files to the root C: drive and closing in on less < 5GB HDD remaining (could this be overwriting soem temp files that LV uses to manag graphics???)
    3) After saving to LV 7.1 and re-opening with LV 8.0, I get a message that is new to me that explained something about wiring a Boolean constant to a case structure and how LV 7.1 or previous used this to keep a sub-vi in memory (???).  Unfortunately for me, I did not capture the exact syntax of this message and I do not wish to intentionally repeat this graphical feature.
    4) I copied a small block of code that contained a 'cloned' sub-vi from one block diagram to the a similar VI that , shortly afterward, exhibited the front-panle 'tearing' feature.  This is something that I usually do not do, and, again, is one of the only new actions from anything that I have done in LV for the past several years.
    5) After the message described in (3), above, the rescued LV 7.1 version had moved a handful of the most recently added indicators to a very remote location, about 30 seconds of edge-scrolling time, to the left of my front panel graphics.  I perfromed a 'drag' operation by selecting these and bumping them to the right edge of the screen for about 30 seconds to get them back to the vicinity of my front-panel graphics.  I have never experienced a VI that shifted inidcators so far off the edge of the screen.
    These are the only ' unique' events that I can recall before the 'tear; effect.
    Thank you.

  • 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

  • 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

  • Using Shared Variables and Initialize Front Panel Binding (to PSP)

    Hi,
    I use LV DSC RT 8.2.1
    I have a Vacuum System That includes signals from - Pumps failure, Valves status, Vacuum gauge, start Pump ...
    Each signal is read by a FieldPoint. 
    All the relevant FieldPoint Channels are read by the Server (a computer in the Ethernet Network) and published to the network in the form of Shared Variables.
    I have a client VI that is reading the Shared Variables published by the Server using Front Panel Binding.
    Problem : 
    Some of the Bindings are in the mode 'Write &Read' and that causes some initialization problems.
    For example - Valve #1 is Open, and then a User start running the Client VI, (the Valve #1 Status mode is 'Write & Read")
                           if in the VI the status of Valve #1 is closed (before running it) then the Valve status is changing to Closed.
    I want the Client VI to first read the Physical status of the instrument and then to change the Value if the User changes it.
    But that's seems to be a problem when using Front Panel Binding... (is it?)
    I know I can Deploy a lvlib in the Client Side and Item Bind to the Shared Variables or Use DataSocket.
    (Is DataSocket is a Reliable method when connecting to Shared Variables? What are the disadvantages when using DataSocket?) 
    What is recommended by those of you that are experienced or by NI ?
    Sincerely Yours,
    Amitai Abramson.

    Amitai Abramson,
    Hello and thanks for using the NI Forums.
    I'm glad that you've read the Using the LabVIEW Shared Variable Tutorial on our website. Check out these other resources:
    Network Variable Technical Overview
    Troubleshooting Network-Published Shared Variables
    Why Do I See Unexpected Value Change Events for Shared Variables Using LabVIEW DSC?
    All You Need to Know About Shared Variables
    Creating a Value Change Event for Shared Variables
    Alternative Method for Using Shared Variables Between Systems in LabVIEW 8.x
    What Is The Difference Between Using Shared Variables And DataSocket VIs To Access OPC Tags?
    The issue that you are seeing by having "Write & Read" bound items on both the server and client side is essentially a race condition, you don't know which one is being read/written at what time. To resolve this issue I would take a look at some of the documents below.
    Using a Local, Global, or Shared Variable in Parallel Loops Can Cause Race Conditions
    Using Local and Global Variables Carefully
    Tutorial: Local Variable, Global Variable, and Race Conditions
    Locking a Shared Resource or Variable in LabVIEW Using Semaphores
    You mentioned not wanting to have two sets of shared variables (one on each side), but this is a great method to resovle this issue, that, or you can develope some sort of hand shaking to prevent these race conditions.
    I would suggest that in the future when using these forums you try to ask only one question per thread and make it more concise. It's hard to tackle multiple questions and such broad questions as "I want to know all the ways that I can connect to Shared Variables, and I want to know the advantages and disadvantages." I suggest this because we want you to get your questions answered and more concise questions will result in quicker and better answers. 
    Message Edited by Ben S on 10-01-2009 06:05 PM
    Ben Sisney
    FlexRIO V&V Engineer
    National Instruments

  • 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

  • [General Question] redrawing and updating front panel objects

    Hello,
    I have several questions on this topic.
    1)  Is there a difference between redrawing and updating the front panel? (I assume so, but when a control is updated it will be redrawn at the same time, right?)
    2)  Is redrawing = rendering? In the case of decorations I think they need only to be rendered once (if fix/static) and stay in memory so that it is available for the gfx-card...
    3)  Are decorations redrawn or updated by LabView with every loop?
    4) Is there a way to prevent LabView from redrawing and/or updating front panel objects (like controls, indicators and decorations)?
        When I put indicators into case-structures they are only updated when the case in which they are placed is executed but they will be obviously still redrawn.
        In another case when I disable visibility of those indicators they will not be redrawn anymore but be updated in the background.
        So when I put these indicators into a case-structure and combine it with toggling the visibility I could stop LabView from updating and redrawing them.
        Is this correct?
        Is there another way to prevent LabView from redrawing single objects? (at best leave them somehow visible)
    Many thanks in advance!

    Nocturn wrote:
    Hello,
    I have several questions on this topic.
    1)  Is there a difference between redrawing and updating the front panel? (I assume so, but when a control is updated it will be redrawn at the same time, right?)
    2)  Is redrawing = rendering? In the case of decorations I think they need only to be rendered once (if fix/static) and stay in memory so that it is available for the gfx-card...
    3)  Are decorations redrawn or updated by LabView with every loop?
    4) Is there a way to prevent LabView from redrawing and/or updating front panel objects (like controls, indicators and decorations)?
        When I put indicators into case-structures they are only updated when the case in which they are placed is executed but they will be obviously still redrawn.
        In another case when I disable visibility of those indicators they will not be redrawn anymore but be updated in the background.
        So when I put these indicators into a case-structure and combine it with toggling the visibility I could stop LabView from updating and redrawing them.
        Is this correct?
        Is there another way to prevent LabView from redrawing single objects? (at best leave them somehow visible)
    Many thanks in advance!
    redraw vs update
    Yes threr is a difference. A control is redrawn when LV decides to update the GUI. Look into "syncronous" setting for controls that forces update when value changed. These tags and thesse tags may help out abit.
    Q2
    Not sure about equality but decoartion may need redrawn if there is overlap of chanable objects.
    Q3
    i have observed decorations that failed to update on occation so I suspect they are only update when required.
    Q4
    LV will update the value for a hidden control but will not update its image. Same if the object is ona hidden tab page.
    No wawy that I know of to prevent an update of a single object with out going to extremes. The Front pnale property "DeferFPupdate" will inhibit FP updates while true and allow then when set false. I use this when doing a lot fast GUI updates so allow the changes to accumulate and be apllied only once.
    Ben
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • LabVIEW Real-Time and Remote Front Panel MemoryManager.cpp line 437 error

    Hi all,
    I'm using a smartcamera (NI 1742) with LabVIEW Real-Time 8.6.
    When I look at the Front Panel with the web browser and I close the browser or I Stop the executable, I always get this error: MemoryManager.cpp line 437. I've checked if someone else had this error, but I guess I'm the only person who got this error. I saw someone who had the MemoryManager.cpp line 406, but mine isn't on this line.
    The application works well, but when I got the error, I need to reboot the smartcam to get it works. In my application, I use the Modbus library and I read/write binary file in the hard disk of the smartcam....
    Anyone knows the solution?
    Thank you very much
    Stephanie

    Hi again,
    Still didn't find the problem on my side. Here's a picture of my code. If I put the code surrended in red at place (1), I don't get the error, but if I put the code at place (2), I get the error. Why oh why....?
    I get the error when I close the browser or click Back button of the browser or Stop the application with the red dot or stop the application with the Quit button on my front panel.
    This morning I found a post on this forum about getting an error using Property node and Remote panel (http://forums.ni.com/ni/board/message?board.id=170&message.id=252705). I did what they suggest: wire the property output to an indicator and it works (disable "Enable automatic error handling dialod" didn't work... I don't know why)... until I put extra code in my VI. 
    I really need help please!
    Thank you
    Stephanie
    Attachments:
    MemoryManager line 437 error.JPG ‏228 KB

  • X-fi soundcard and audigy front panel compatibil

    Hi,
    Does anywone know whether one can use an old audigy front panel from the platinum edition together with the new x-fi soundcard?
    thx,
    Jo

    Yes it does. A Creative Moderator on this site said it's compatible.....
    I also tried it and it worked flawlessly ! I have both X-FI and Audigy ZS Platinum Versions.
    <IMG height= alt="" src="http://forums.creative.com/i/p.gif" width= border=0>Re: X-Fi compatible with Audigy2 front panel?<A target=_blank><FONT color=#333333>Options[/url] <IMG alt=Options src="http://forums.creative.com/creativelabs/i/button_options.gif" border=0> <IMG alt="" src="http://forums.creative.com/i/rank_icons/admin.gif" border=0><SPAN>Catherina-CL<SPAN>AdministratorPosts: 3452Registered: 0--2004 <IMG height=8 alt="" src="http://forums.creative.com/i/p.gif" width=50 border=0><IMG height=36 alt=Catherina-CL src="http://forums.creative.com/creativelabs/i/icons/Moderator__Moderator/FM-orange.gif" width=36 border=2>
    <SPAN>Viewed 39 times
    <IMG height= alt="" src="http://forums.creative.com/i/p.gif" width= border=0>
    They should be compatible, but it wouldn't be officially supported. Should work the same as the other dri've though.
    Cat
    <B>Forum AdministratorCreative Labs</B><IMG src="http://images.americas.creative.com/images/local//signature/GET_CREATIVE_00.jpg">

Maybe you are looking for