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 .

Similar Messages

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.

I can't add an event to an event structure. Option not visible in the menu. Fix?

I didn't have the event structures on my pallette to begin with (LabVIEW 6.1), so I added them by downloading the struct.mnu file on the website. Now they show up in the pallette, but are not usable because I can't add events. Any help would be much appreciated.

You're correct, if you have the Full version, you should be able to create and edit the Event Structure. The Base version is the only one that is limited.
I would try the reinstall and see if that takes care of it. Something must have gotten corrupted.
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.

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 Question

Hopefully I can explain this okay....
I'm using an event structure to control several features in my program and all have worked great. All of the events in my program are handled via boolean buttons with value changed option. I have a numeric control in my program that controls integration time. This changes when the user clicks the up or down arrow or types in a new value. This control is used and needed to changed the integration time in a couple of different event cases. However now I'd like to use this numeric control (integration time) to not only change the integration time but also trigger one of the events (in addition to the normal button that I have been using to trigger the event I need to have happen). (The value of the numeric control when changed also executes a case structure when it is changed in one of the other events.)
However when I tried to do this, I ran into some problems.  If I change the numeric control value during one of the events in which I need to use it, and after stopping the event, then another event seems to execute (based on the changing of the numeric control, this event is the same event I ultimately would like to trigger). Basically I need to stop the numeric control from executing after stopping another event when its value has been changed and only executing when I need it to. Everything I seem to be doing hasn't been working and I'm just not seeing any type of walk around. But I need to be able to use the control in various events to change the integration time and also if needed to change it and thus trigger an event (besides using a boolean button to trigger the same event).
If needed I can post screen captures or sample code, but my main vi is rather large, so I'd have to cook something up as an example.
Any help provided would be much appreciated.
Using Labview 7.0 and 2010 SP1 with Windows XP and 7.

The attached amusing example is an architecture which will work for you. Read the documentation for details. It has two components - an event hander and a task handler. The event handler is the LabVIEW event structure. The task handler is the queue-based outer loop. If you need to add data to the tasks defined for the queue, make the queue element a cluster and add a variant to it.
As a general rule, most UI projects involve getting to the same task through different events, making this the standard design pattern for almost any UI driven program. You can separate the task handler (consumer) and the event handler (producer), but I have found that the synchronization problems are not worth it.
I posted 7.0 and 7.1 versions of the code.
This account is no longer active. Contact ShadesOfGray for current posts and information.
Attachments:
LargeGUIApplicationsInLabVIEW_70.zip ‏735 KB
LargeGUIApplicationsInLabVIEW.zip ‏711 KB

Labview 2013 cannot use event structure

Event structure can be added into the back panel, however when i add event case or try to edit the default event case, the program is crask and cannot response to my mouse.
when i launch windows task manager, it present " running" properly.
However this program run properly at my another computer with sample Win7 OS.
Can anyone tell me what the problem is?

Aaron1978 wrote:
sir, this issue does not related to code, even i create new empty VI, the event structure cannot work properly, i cannot add new event or edit the default even!
However, i installed the same eval version into my another computer, this event structure can work properly, both computers use same Win 7 OS.
Okay in that case I would recommend a repair install of LabVIEW.
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.

Stop execution of a loop in an event structure

I tried searching the forums to avoid posting a duplicate, but most I could not open most of the vi's as they were higher version.
I put in a dummy while loop in an event structire i intend to use. Once I start executing the while loop, I am not able to stop it using a control for some reason from the fornt panel control.
I am not able to change the vale of the Stop control at all. I tried creating a seperate event for STOP, and I still could not stop the program when the While loop was executing.
I imagine I am missing something really small. I would appreciate your feedback on this.
Thanks,
Nevil
Solved!
Go to Solution.
Attachments:
FrontPanel.vi ‏34 KB

Right click on the event structure and choose "Edit Events" for the case that is giving you trouble.
Be sure the checkbox to lock the front panel is unchecked.
I suspect yours is checked, so your front panel is locked out until the event completes, thus you can never stop your loop.

How to use an Event Structure responding to an image control that belongs to a parent VI.

Hi
I am loading a subpanel vi by pressing a button located in the user interface of the main vi which also contains an image display. Subpanel vi opens up on the side and doesn't hide the image display of the main vi. Subpanel vi contains an event structure that needs to respond to user clicking on the image display of main vi.
Since the bug that occured while creating an image reference control isn't fixed, I am passing the main vi pane reference onto the subpanel vi. From that point I've tried to edit event structure and have it respond to the image control/pane that belongs to main vi but I don't know how.
Any help would be appreciated.
Thanks

Post a screenshot of your subVI code where you register the events.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

Load defaults from file with event structure in vi

Hi All,
I've been trying to figure out how to do this but have not quite got there. Taken a look at lots of posts but can't quite find the answer to the question that i've got.
I've got a vi for controling 4 PCI cards making calls to some DLL's. I've got quite a number of controls on the FP and i use an event structure to update the values on calls to the DLL. On startup, one of the first calls that i make is initalise and that sets the cards up. I then want to load my own set of default values from a file to initalise the cards to my particular set up. While the software is running the user may change the values and wish to save a file with the new default values, or he may wish to load a different file of default values (depending on the test that he is running). I've got the Control Values:Get All [variant] and the Control Valueset [Variant] working to save all the controls values to a file and read that file in and set all the controls values. So far so good. Problem is i'm using an Event Stucture and it doesn't register that the values have changed. I could complish this by using Value(signaling) but the data from the Control Values:Get All is variant data and the Value(signaling) needs the same data type as the control. What do i do?
One thing i have thought about is to write all the values from the file to all the conrols and then have a read Value and a write Value (signaling) to trigger the events. Problem is i don't want to set this up for every control (it'll take me ages). Can i do it programitically? Is there a better way to do it?
Thanks,
Phil

You could create a boolean control/indicator and signal that value when you've updated the values on the FP.
Name it something like "update FP". The event case for that boolean will have the code to update the necessary parts of the FP.
André
Regards,
André
Using whatever version of LV the customer requires. (LV5.1-LV2012) (www.carya.nl)

How do i get a boolean indicator to trigger a event structure

I have two parallel loops running, and i need to use a boolean value, one that comes out from an OR gate, to trigger an event in the parallel, event structure loop. I've attached a simplified version of the loop. Is there a way to get this done? I've tried using local variables, value(signaling), etc. and they haven't worked
Solved!
Go to Solution.
Attachments:
Parallel Loop Trigger.vi ‏10 KB

Here is a revised version of your VI. I modified the mechanical actino of the stop button so it kept it's value until it was read. In addition, I added a delay to your upper loop. Without a delay it was running too fast to actually see the button press. I modifed the event in the the event structure to trigger on a value change of Boolean.
You don't really need the outer loop since it will only run a single time in all instances. On the first execution of that loop it will be sitting in the turn inner loops. Once you exit the two inner loops your outer loop will always exit. Therefore, it serves no purpose.
Your OR in the upper loop is completely uses. It serves no purpose since the result will always be equal to the value of the Stop button.
There are better ways of triggering events. a preferred method would be to use a user event and simply generate the event at the appropriate time. This has the advantage of not requiring additional controls/indicators simply to cause an event to occur.
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
Attachments:
Parallel Loop Trigger.vi ‏12 KB

Event structure vs case structure?

I am developing an application that is fairly user input based... lots of boolean control buttons to do different things.
In the past, I have avoided "value change" event structures, and instead went with a while loop, stacked sequence, and series of case structures. After having done it, I decided this was a terrible idea. This time, I intend to build an array from the booleans, convert it to a number, and feed it in to a single case structure. This will give me the option to add cases for different combinations of the booleans being pressed.
I guess the question is: What is the best method for doing something like this? Does one have advantages over the other?
Edit: I wasn't that clear. I would like a comparison between the "value change" event structure method, and just feeding everything in to an array -> case structure. I also am worried that with the bool array -> case structure that I will run in to problems where I end up with too many control variables, and the value of the resulting number gets ugly very quickly. The application has several buttons... next, last, save, load, several different configure setup buttons etc.
Thanks!
Solved!
Go to Solution.

Aalenox wrote:
I am developing an application that is fairly user input based... lots of boolean control buttons to do different things.
In the past, I have avoided "value change" event structures, and instead went with a while loop, stacked sequence, and series of case structures. After having done it, I decided this was a terrible idea. This time, I intend to build an array from the booleans, convert it to a number, and feed it in to a single case structure. This will give me the option to add cases for different combinations of the booleans being pressed.
I guess the question is: What is the best method for doing something like this? Does one have advantages over the other?
Edit: I wasn't that clear. I would like a comparison between the "value change" event structure method, and just feeding everything in to an array -> case structure. I also am worried that with the bool array -> case structure that I will run in to problems where I end up with too many control variables, and the value of the resulting number gets ugly very quickly. The application has several buttons... next, last, save, load, several different configure setup buttons etc.
Thanks!
Event structure. Among other things, it will allow your loop to "sleep." then wake up when an event happens. With a case structure it's going to be constantly polling. Event structure is pretty much always the right way to go in newer versions of LabVIEW that have it available. I assure you, your first solution was aboslutely wrong and you noticed that, your second is better and was common the way before event structures existed, now that event structures exist, you should go with those.
CLA, LabVIEW Versions 2010-2013

Unexpected effect of Lock Front Panel in Event Structure

I have been using LV intensely for only a short time, although I have dabbled with it many times since its first appearance. The "problem" that I have had may well be the intended behaviour, but it just seems unintuitive to me. I'm writing a small application to take measurements from a USB instrument. I have already written a basic driver for the instrument, which the application calls, and the driver is working as expected. In the application, the user can configure various settings and then click an Execute button to transfer them to the instrument. The click event is handled in an event structure along with other events. Since some of the instrument operations take an appreciable time, the first action that occurs in the click event case is to disable the Execute button using a property node so that further clicks are ignored until the operation completes, at which time the button is re-enabled.
When disabled, the Execute button is grayed out as expected and clicking it has no visual effect. However, it seems that clicks made during the disabled period are still queued and acted upon when the button is re-enabled, causing the operation to be repeated.
It is the solution I have found that seems unintuitive to me. The Lock Front Panel check box was checked (by default) for the click event, and I assumed that this would be the correct setting. However, unchecking the Lock check box actually makes everything worked as expected. Click events occurring during the disabled period are now ignored or discarded. I'm not suggesting that this is a bug, but I'm interested to learn why it happens, if anyone can explain. I have attached a picture of a simplified version of the event case.
Attachments:
Sample.png ‏7 KB

I would say what you see is expected behavior, even though it's a bit complicated.
The "Lock front panel until the event case for this event completes" option will only defer clicks and other things generating events until the current event handler completes. So this means that the click is placed in a queue and only evaluated once the event is finished. At this time, the button is no longer disabled, so an event is generated.
When the "Lock front panel until the event case for this event completes" is not checked, the click is immediately evaluated, but it's happening on a disabled control, so it does not generate an event.
From the LV help:
By default, when an event enters a queue, LabVIEW locks the front panel that contains the object that generated that event. LabVIEW keeps the front panel locked until all Event structures finish handling the event. While the front panel is locked, LabVIEW does not process front panel activity but places those interactions in a buffer and handles them when the front panel is unlocked.
Note If an event case that locks the front panel takes a significant amount of time to execute, consider using the Set Busy function or displaying a dialog box to notify the user that the front panel is locked.

Event structure in a subVI

I know this problem has been posted, but I've already am passing everything by reference. I can't get my subVI to respond to my top layer VI. It runs fine as a stand alone, but when I ask it to monitor events from a reference, it won't do anything. I've attached what my sub VI looks like. My goal is to have the the event structure respond when a new file path is sent, stop button pressed, or a enum is changed. The subVI is called Read Track shown in the top VI with all the references passed.
Top VI
Message Edited by d1sturbanc3 on 02-27-2008 12:30 PM
Message Edited by d1sturbanc3 on 02-27-2008 12:31 PM
Attachments:
event.JPG ‏163 KB
top event.JPG ‏301 KB

You should use dynamic events.
Your SubVI with the event structure should run in parallel with your main code.
What you currently have will never work.
Here's an idea of how the subVI should look like:
Try to use the Code Capture Tool to get images of your code...
Good luck,
Ton
Message Edited by TonP on 02-27-2008 07:45 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:
PathEventChange.png ‏5 KB

SubVI with while loop + event structure not working in multi tab VI

Hello Everyone,
I am developing an interface for the control of a prober using Labview 2012, and I am stuck with some issue.
To start with I provide you with a simplified version of my control interface VI, and with the sub-VI used to build and manage the wafer maps.
The VI consists of several tabs: Prober Initialization, Wafer Handling, Wafer Map, Status, Error.
The sub-VI can:
1/ initialize the grid to display the map (sub VI Init Grid not provided here)
2/ import XY coordinates from a txt file (sub VI Wafer Map Import)
3/ display the coordinates and index of the die below the cursor
4/ and when a die position is double clicked, and the boolean "Edit Wafer Map" is true, then the user can change the state (color) of the die between On-wafer die and Selected Die
My issue:
If I use the sub-VI by itself, it works fine. However when I use it as a sub-VI in the tab "Wafer Map", the map does not build up and I can no further use the embedded functionalities in the sub-VI.
I suspect the while loop + event structure of the sub-VI to be the bottleneck here.
However I don't know which way to go, that's why I'd be glad to have some advice and help here.
Thank you.
Florian
Solved!
Go to Solution.
Attachments:
Control Interface.zip ‏61 KB

Hi NitzZ,
Thank you for your reply.
I tried to save the VIs in LV10, please tell me if you can open them now.
Inside he event structure there is quite some code, and since I don't want to make the main vi too bulky, I would like to keep it as a sub-VI.
As you can see from the sub-VI, the event structure is used for extracting cursor position and tracking the double click action. These events are linked, through a property node, to the image "Wafer Map" which is passed to the main vi through connector pane.
All values are passed this way as well (through connector pane). Is there another way?
Maybe "refnum", but I don't really understand how to use them...
If I use the event structure in the main vi, the wafer map is still not working. I tried it earlier.
To implement the multi tab front panel, I used a tab control, and a for loop + case structure. For each element of the case structure, there is a corresponding action.
For the case where I put the code (element=2) for Wafer Map, I also control the execution of the code with a case structure activated by the button "REFRESH". Otherwise I end up with a freezing of the panel right after the start.
I hope these comments help you understand better.
Regards,
Florian
Attachments:
Control Interface.zip ‏104 KB

Event Structure hangs VI

I am using Tab Controls in my VI, and want to reset some Button
Controls (using property nodes) when the tab controls change value. So
i have tried to use an event structure which contains a FALSE constant
wired to the VALUE property of several Button Controls. It works just
fine, the only problem is that i cant operate any buttons or stop the
VI from the stop button. It seems like the event structure hangs the vi.
I guess there is a simple solution to this problem, but i cant find it and i am getting desperate... Please help!
Attachments:
event.jpg ‏29 KB

Hello Vatoloco,
I can't give a short (correct) answer but:
The vi structure will always get every event. If you have selected to 'lock front panel until event structure done' (as is by default) for this event it means that :
The front panel is unresponsive until the event has executed
This is a tricky thing because if the event structue isn't executing, it locks the front panel. A quick check for this is to deselect this option.
If that works you have to redesign your vi. Have a look at the design patterns that ship with labview. Or you could look with high-lite executing where your VI 'is' when you change the tab control.
Ton
PS For a more correct post, search this forum with a broader timespan (let's say 12 months or so) you're not the only one!
Message Edited by TonP on 04-21-2006 01:43 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!

Event Structure Components in Eval Version?

Similar Messages

Maybe you are looking for