Event structures in older versions of labview?

Can anyone tell me how to create a workaround for a 'value change' event structure in an older version of labview?  I have a student  version of LabVIEW 6i and need to create a queued buffer from each value change.  Thank you.

James.Morris wrote:
Ah, you're only one release away from the event structure. That's too bad.
You're going to have to implement a Polling loop that continuously checks the user inputs. Make sure you add a Wait function to the loop (~100ms) because that will act as your chance for the user to make changes. You can use shift register(s) to keep the previous loop's values and compare to get a bunch of Value Change booleans. If you want a specific case for the specific events, then you can group all of your Value Changes in to an array and act upon the ones that are True via a Case Structure.
The Event Structure only pulls a single event per loop and has a queue of events to handle for following loops. You might encounter multiple value changes in a single loop if the user clicks fast enough, or you trigger value changes. To avoid losing the trailing events, you should probably have a For loop within the Polling loop that handles all True values. Either that, or have a consumer loop that handles all of your events.
James, I swear I'm not picking on you today
You can set the maximum number of events alowed in the event queue per event in the edit event dialog box.  Check box and int fields in the lower right side.
6.i didn't have a "Value (Signaling)" property- (a subject of some CLAD exam questions not that you suggested it)
Student editions could not use 6.i events.  From 7.0 or 7.1 through 2011 Student Edition could use but not edit event structures. 2012 and on Event Structures are available in "All Versions" of LabVIEW- at the time.  I haven't looked into the newer license options.
On to licensing options. (Not a lawyer! consult your Legal Dept!)
If you are not doing work towards earning a educational certificate you should not be using Student Edition.  And, in some cases (Like working on a student project with commercial investment) not even then!
The Home Edition is also a new option.  It is intended to enable fast "Proof of Concept" development or development for your sole non-comercial use.
LabVIEW Full and Professional are for comercial use and have a "Home Use License Agreement" clause attached. If your company owns a LabVIEW License you CAN install a copy on a "Home PC" for the limited use of aiding your employer (who paid for the license) such things would arguably enclude "Training"
NI is not totally opposed to negotiating "Exceptional" agreements for mutually beneficial reasons.  Youl'd better bring a justification better than "I can't afford it"  Go find some investors and buy a license in that case.  And Yes, until the moderators take this down, I did at one time have a LabVIEW license for exclusively engaging the LabVIEW Community (Forums and NI Sponsored events use only- LAVA was not encluded)  I'm not sure if such a deal could be negotiated in the future.  In Fact, The Home Edition would have been less costly.
 

Similar Messages

  • Can we use latest version of Add-Ons and Toolkits with older version of LabVIEW core?

    Hi every body
    I'm new to LabVIEW
    I have a question .
    Can we use (indeed install) latest version of Add-Ons and Toolkits(for example 2009 or 8.6.1 version) with older version of LabVIEW core(for example LabVIEW 8.6)?
    No problem ?!
    I have LabVIEW 8.6(Evalution) and I want istall Real Time Module 2009.
    Message Edited by mostafi on 10-31-2009 02:49 AM
    Solved!
    Go to Solution.

    I think perhaps 8.6 and 8.6.1 is compatible. But I am 100% sure that 2009 and 8.6.(1) is not downwards compatible
    Besides which, my opinion is that Express VIs Carthage must be destroyed deleted
    (Sorry no Labview "brag list" so far)

  • Removing older versions of LabVIEW

    I have taken over a development machine and updated it to 8.6.1. Can I safely remove all older versions of LabVIEW? (8.2 and 8.5) These older versions seem to be giving me problems with the front pannel on older VIs when I use the 8.6. Thanks.
    Solved!
    Go to Solution.

    testech68 wrote:
    These older versions seem to be giving me problems with the front pannel on older VIs when I use the 8.6.
    What kind of problems? If you have problems opening old VIs in 8.6, you might want to keep using the old version until the issue is identified and solved.
    (Once you are happy with 8.6, you can uninstall the old versions but it does not hurt to keep them around. For example if you have a very old VI, you might not be able to open it directly in 8.6) 
    LabVIEW Champion . Do more with less code and in less time .

  • How do you uninstall older versions of labview

    How do you uninstall older versions of labview and all their components, registries etc?
    Solved!
    Go to Solution.

    If you're looking to get a more through uninstall, then Revo Uninstaller is a good way to go. That will run the regular NI uninstallers and then search for leftover registry entries and files. You can also use MSI Blast.

  • Older version of LabView available?

    I would like to put together an "antique" data aquisition system utilizing
    an older DAQ board and an IBM AT machine that I have kicking around. It's
    just sort of a hobby thing rather than a serious instrumentation project.
    I have the board (NI Lab-PC-1200) and the computer (IBM AT) and was hoping
    to find a version of LabView that would run under MS-DOS 6.0 and I guess I
    would be looking for some drivers too.
    I currently have LabView 6.0 for use with some 21st century equipment, but
    it will only run under windows. When I called up NI, my local sales guy felt
    that my current license would probably allow me the "right" to use the older
    version, but he wasn't sure that locating the actual software would still be
    possible.
    Does anyone o
    ut there have some old discs they would be willing to sell?
    LabView is currently sold with NI-DAQ on the same disc. Would I need to find
    LabView + NI-DAQ+Lab-PC-1200 drivers and load them all separately?
    In the event that I can't find any of this, I suppose that it would be
    possible to do register level programming using C. Does anyone have any old
    code that they would like to share?
    Jon Juhlin
    [email protected]

    LabVIEW has never had a DOS version. You'll have to use something like Quickbasic or the old LabWindows for DOS. Before you spend a lot of time, make sure that the old NI-DAQ for DOS supports the Lab-PC-1200.

  • Is it possible to open a VI using an older version of LabVIEW, and if so how?

    As stated in the title.  I have installed all the run-times from lv6 to lv8.6, but cannot open any VIs that have been compiled in a more recent version of LabVIEW.  We run (on different computers) lv5, lv6.1, and lv8.5.  Upgrading some of the older machines is not possible since they cannot handle the required OS.
    Is there any way to open a VI created/compiled in a higher version of LabVIEW?  This is proving to be a major sticking point with us and our ability to transfer VIs between computers.
    James
    Never say "Oops." Always say "Ah, interesting!"

    Hi James,
    I was able to use VI server to invoke LV 6.1 VI's using LV 7.0 without issue.
    After discovering this and mentioning it in a post somewhere, Rolf Kalbermatter indicated that was expected. and I should not be suprised.
    So....
    Vi Server may help you.
    James Mamakos wrote:
    Is there a separate place for me to post VIs to be converted?  What's a ballpark figure for the maximum file size i could put on to be converted?
    Do you know if the LabVIEW developers can/will create a way to overcome this problem rather than having to convert a VI through all the intermediate versions?
    To the best of knowledge NO.
    For each versino of LV there isw code included that runs behind the scenes when you open a VI from an earleir version which replaces old functions with the new versions. This is called Mutation code. To accomplish its task it has to know everything that changed between version X and Y. Since it is possible to baby step the versions up and the number of user that jump multiple major versions is small, I don't think any effort will go into that work.
    THe largest attachment I have managed to upload was 3 or 4 Meg.
    Just trying to help,
    Ben
    Message Edited by Ben on 04-28-2009 08:58 AM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

  • Installing older versions of labview after newer versions.

    I Just installed LV 8.5 (dev suite) on clean machine.
    Notice that 8.5 will not read LV 5.0 VIs.
    I Would therefore like to install LV 7.0 (dev suite) (over the 8.5 installation).
    Any known issues?

    Moreover, you may encounter problems with the run-time engine when you build the EXE of LV7.0 code & try to run it in the same PC. It may/will say that the application requires an old run-time engine to be installed to get it running.
    Always it is better to install from an older version to a latest version.
    - Partha
    LabVIEW - Wires that catch bugs!

  • Identifying and Converting from an older version of LabVIEW

    I have an old .vi program that I am trying to access and run now. I don't know what version of LabView it was written in but I do know it came off of a Windows 95 computer.
    Any Suggestions?
    Will Huntley
    Solved!
    Go to Solution.

    You said "trying to". Does that mean you've been unsuccessful? On what OS are you trying to run it?
    When you open an old VI in a newer version of LabVIEW, if the VI isn't too old, then it will open. If you close the VI you'll get a dialog asking you to save it. The "explain changes" will tell you the version of LabVIEW used to write the VI.
    If you cannot open the VI because it's too old, and your LabVIEW is too new (e.g., opening a LabVIEW 5.x VI with LV2011), then you can post a request in the Version Conversion board. If the code is really old (e.g., LabVIEW 3.x or earlier), chances are you will not be able to get it upconverted since versions that old require a special toolkit from NI that is not publicly available.
    EDIT: Duplicate answer. Was creating my response while Dennis posted his.

  • Converting from an older version of LabView

    I have VIs written in Labview 3.0 that I would like to convert to 6.1. Does anyone know of any software that will do this? Thanks!
    Manny

    NI give for free a conversion toolkit. Visit ni.com
    "JT" a écrit dans le message de news:
    [email protected]..
    > mstockma wrote in news:506500000008000000EF000100-
    > [email protected]:
    >
    > > I have VIs written in Labview 3.0 that I would like to convert to 6.1.
    > > Does anyone know of any software that will do this? Thanks!
    > > Manny
    > >
    >
    > Have you tried opening the vi's in lv6.1? I think the conversion is
    > automatic.
    >
    > JT

  • No more than 2 event structure?

    I don't anderstand how can I do my programm because I read that we must not use 2 events structures in one loop. But concerning my programms for instance I have to fill arrays only when I press each appropriate "Ok" button (for instance for 5 case I have to press 5 different OK button ) and so on (when I press OK number 6 the program write to excel program.. when I press OK number 7.. )
    How can I do it? I need to create 7 events structures for 7 actions?
    labview 7.0

    When they say not to use two event structures in one loop they are refering to the number of actual "event structures" that are dropped on to the diagram, not the number of events that one structure can handle. You could have "an event" configured for each of your "ok" buttons, and then have those events, when triggered, select a different case of a case structure, possibly on the "timeout" event. If you built it like that, make sure to have a timeout value wired to the upper left corner, or it will default to -1 (never timeout).
    Here is a very simple example of one way to implement it.
    Putnam
    Certified LabVIEW Developer
    Senior Test Engineer
    Currently using LV 6.1-LabVIEW 2012, RT8.5
    LabVIEW Champion
    Attachments:
    simple event.vi ‏36 KB

  • What is the last version of labview to support classic FieldPoint?

    what's the last version of labview to support classic FieldPoint?
    Solved!
    Go to Solution.

    In general, yes.  Others with more experience than I do might be able to help.
    I think there is a chance you can get some older versions of LabVIEW to work on Win7.  There are occasional message threads where people have asked about a particular version and others said they have been able to get them to work.  Just that official support for older versions of LabVIEW for a Win7 OS has ended.

  • Expired SSP can I download older version?

    Hello,
    It was not clear on the ni.com, so I hope I can ask this here:
    I have an expired SSP (03/21/2014 expiration date) for LabView Full version. May I download older version (like LabView 2012) of Labview and activate it with the given serial number (I will need to reinstall PC, and I do not have CD disk anymore)? I see this product under "My Products" site, but when I click on "download old version", I do not see LabView as downloadable content (only some modules, like softmotion, etc..).
    Do I have the right to download old LabView, which I have paid for, and if so, how?
    thanks for info!
    Solved!
    Go to Solution.

    Hi Blokk,
    you can use all LAbVIEW version you have paid for. So download any older version and use it…
    Googling for "labview 2012 downlad" results in good links to an official NI download website!
    When you're unsure about any licensing details you can always call your local NI sales department.
    Best regards,
    GerdW
    CLAD, using 2009SP1 + LV2011SP1 + LV2014SP1 on WinXP+Win7+cRIO
    Kudos are welcome

  • Save as previous version causes events to disappear in event structure

    I am using 2009 and I am trying to save a VI as previous version...saved it in 8.6, 8.5,8.2 and 8.0.
    I mass compiled the Main VI in 8.6 and tried to open it.  I get about 30 errors one for each event case and the event structure has no events added. 
     "Event Data Node:Contains unwired or bad terminal"
    I am attaching a zip file containing my 8.6 source code which I down converted from LabVIEW 2009.  I am trying to open it in 8.6
    Is this a bug or am I doing something wrong?
    Brian
    Attachments:
    8.6.zip ‏556 KB

    Hey Brian,
    This was reported to R&D (# 194525) for further investigation. A possible workaround for this issue is to save the VI to LabVIEW 8.6 and then save it to the various versions you wish to save the VI to. Also, another workaround is to manually re-enter the event specifiers to your cases.
    When I saved the VI from LabVIEW 2009 to 8.2, the only thing that seemed to be out of place was the event specifiers. You can re-configure these by right-clicking on the event structure and selecting "Edit Events Handled by This Case...". Also, when I first saved the VI to LabVIEW 8.6 and then to LabVIEW 8.2, everything seemed to be in order.
    Thanks for your feedback. Let me know if I can clarify any of my proposed workarounds.
    Hope this helps.
    -Ben
    WaterlooLabs

  • Event Structure Components in Eval Version?

    Does the Labview Eval Version include the Event Structure Components? If so, where are they located? If not, that is very lame. It is very difficult the experiment with functionality without them.

    You get everything you possibly want with the evaluation version.  As others have said, it's basically the professional version.
    In addition, you can evaluate any toolkits and modules. (not sure if there are minor exceptions?)
    Once you purchase a license, they license determines what you are allowed to use. The DVD is the same for all versions.
    AFAIK, you can evaluate almost anything without jumping through any hoops. Even if you have an existing activated LabVIEW installation, you can later evaluate a toolkit or module with it.
    LabVIEW Champion . Do more with less code and in less time .

  • Simulate event structure in LabVIEW base?

    I have a LabVIEW base version (v8.6) which does not have the event structure. I found it was quite inconvenient to monitor the status of several controls (the action after click a control depends on the status of other control(s)). Especially if I want to add another function (control), the effort increase exponentially with the existing number of controls
    I got an idea of simulate the event structure using 'Shift Register'. First, I will bundle all the values of controls into a cluster. Then I will put the cluster in a while loop, and compare the value of the cluster with its previous value (xor the shift register). If the compare result is false (none of the control is changed), the program goes to next iteration. If the XOR result is true (one of the control was changed), then the program goes into event handling code (it will pass which control has changed, and the whole cluster). So for each control change, we can write a independent code to process the event. After processed the event, the event was cleared.
    The following is a section of my ugly code currently used to monitor several controls. And I am thinking of rewrite it using above idea so that there will be less likely a hiden bug.
    Any comments of suggestions?
    Message Edited by RyanWu on 10-23-2009 10:16 AM
    Solved!
    Go to Solution.
    Attachments:
    UglyLabVIEWCode.png ‏18 KB

    Ben wrote:
    Altough this is an interseting academic question, we really can't duplicate the efficiency of the Event structure so springing for an upgrade is highly recomeneded.
    But I am not here to sell LV but rather help LV developers so...
    Start by developing an Action Engine with the following actions.
    1) Init -caches control ref for all controls and indicators for which you need an event. Optionally rest them and cache their state.
    2) Check - Will compare the current state with the prvious state and any changes get pushed onto a stack in the AE and if there are elements in the stack (due a change detected now or one left over form the last check) and returns a type-def'd enum describing what changed. Multiple changes should be on the stack for next time.
    3) Get New - will return the new value of the value requested via an Enum.
    In you top level VI use the AE to Init before you run and then use an "Check" method to se if anything changed. If it flags a change (boolean output of AE) then the Enum is used to select the proper case of a case structure. Inside the psuedo-Event case, you can use teh AE with the "Get New" action and pass the enum to choose which value to get.
    It is hardly an Event Structure but it should come close.
    Ben
    But after looking at Knickerbocker's* post we can go farther.
    Put the above code in a sub-VI that feeds a queue. Then you can monitor the queue for updates just like in an event structure AN you can queue up all of the changes at once and can ingore my mention of caching the change methods in the AE. Just let the queue handle the stack.
    Ben
    *Kudos for inspiration!
    Message Edited by Ben on 10-23-2009 10:54 AM
    Ben Rayner
    I am currently active on.. MainStream Preppers
    Rayner's Ridge is under construction

Maybe you are looking for