Copy event structure

Hi,
I use LV DSC RT 8.2.1
Why can't I copy&paste an event structure together with his events specification (to the same VI)?
(I can create a copy of an event structure but his events specification are blank)
Is there a way to do it ?
Amitai Abramson.
Solved!
Go to Solution.

Amitai Abramson wrote:
do you have a solution ?
Never hide event structures inside case structures. Event structures queue up events even if they are not in the datapath. Also, by default event are set to "lock the front panel until the event completes" (you can change that, but why would you?). Since you fire an event that is not in the datapath, the event can never complete and the front panel will be locked forever!
You also need an event for the stop button. This way you don't need to needlessly spin the loop via the timeout event.
Here's a quick draft, modify as needed.
LabVIEW Champion . Do more with less code and in less time .
Attachments:
EXAMPLE2_MOD.vi ‏13 KB

Similar Messages

IPhoto export of events structure

I have been trying to export my current iPhoto structure (events, places, faces, etc...) from my laptop to my iMac but every action I tried just separate all the pictures out of the evenet. and when I try to import back it just add all the pictures randomly without structure and also congest my photo stream adding all of them there...it's very messy. does anyone have any suggestion on a proper procedure to follow to export the event structure from iPhoto on 1 mac to iPhoto in another mac?
I have already read most of the posts and nothing worked properly.
thanks for helping guys.
SMM

To move a Library:
To move an iPhoto Library to a new machine:
Link the two Macs together: there are several ways to do this: Wireless Network,Firewire Target Disk Mode, Ethernet, or even just copy the Library to an external HD and then on to the new machine...
But however you do choose to link the two machines...
Simply copy the iPhoto Library from the Pictures Folder on the old Machine to the Pictures Folder on the new Machine.
Then launch iPhoto. That's it.
This moves photos, events, albums, books, keywords, slideshows and everything else.
What do you mean by "Sync".
The general term means when two Libraries (A and B) are compared and files in Library A are copied to Library B, while files in Library B are also copied to Library A so that both Libraries are identical.
This is bi-directional copying and you cannot do this automatically with iPhoto. No Syncing software is capable of parsing the iPhoto Library in this manner. One or both of your Libraries will be damaged if you try this.
You can have uni-directional copying - files in Library A are copied to Library B - this is essentially backing up. Obviously you can also copy from Library B to Library A.
The nearest you can get to syncing is to use iPhoto Library Manager to move files/Albums/Events plus associated metadata between Libraries. This process cannot be automated.

Can I use Event structures in a subVI?

Hi,
I have a subVI (ProvaEv1.vi) that use an event structure inside. But when I use it in a VI (ProvaVI.vi) the event structure in the subVI doesn't catch the events.
I tried to insert the event structure in a while loop but it doesn't work too.
Could you help me?
Thanks Ius
Attachments:
ProvaVI.vi ‏11 KB
ProvaEv1.vi ‏15 KB

"iusn" <[email protected]> wrote in message news:[email protected]...
Thanks to all for your answers!
Wiebe! I tried to do as you suggested but I am not able to link the Event Reference Number inside te SubVI with the Event Register Number of the Register for Event in Main VI. There is e class conflict. Another question: how the SubVI can know the structure of the Register event outside?My aim was to create a modular structure but it seems very difficult, wath do you think about these problems?
The broken wire is related to your question. The event structure inside the sub vi knows about the events you register in the main, because the reference wire/control has a "strong" type. It contains information about the registered events. That is also why the wire is broken. You have to register all events, then create an indicator/control of the output. Use that control in the subvi. You have to do this every time the events change (you might use a type def if you use the control a lot).
Usually, the events that you would want to put inside subvi's are those related to user interface objects. I've had this a lot. You make a nice interface, but it's not reuseable, because the events are mixed with all the other events. Only solotion is to manually add the needed event cases in your program, and copy the code.
Even if you can put the events in a sub vi, I'd expect hanging vi's when more subvi's are registered for the same event. It's hard to tell without trying. So it's not a real solution either.
Like Chrisger suggested, the event callback might help a little, but they are tricky, and actually ment for this (they are intended for activex callbacks).
Perhaps you should look at XControls (if you use 8.2). It would be more work to replace your code to XControls, but once you're done, you have reusable code.. Haven't worked with them jet, but they are invented for this problem...
Regards,
Wiebe.
I have already create my application using event structure just in Main VI but it seems very complicate to read and keep update, I would have wanted to give modularity to my application.
Thanks Ius
SubVIEventMain.vi:
http://forums.ni.com/attachments/ni/170/203225/1/SubVIEventMain.vi
SubVIEvent.vi:
http://forums.ni.com/attachments/ni/170/203225/2/SubVIEvent.vi

Event selector missing in Event Structure

Hi, the event selector in my Event Structure is suddenly missing. How do I get it back?
This is how it look in the block diagram:
If I copy it and past it in paint I can see the selector.

Since i have never seen such a thing, three more questions:
- How many cases does your event structure contain?
- What is the longest strong for a single event case (the screenshot indicates way longer strings than the selector can display in the box)?
- Can you try copy the whole code and put it into a complete new VI?
Norbert
CEO: What exactly is stopping us from doing this?
Expert: Geometry
Marketing Manager: Just ignore it.

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.

Ghost pane in event structure

I an new to using event structures so pardon me if this is a known LV2009 issue...
I have a simple event structure hat has a ghost pane that shows up when viewing or editing the structure properties.
I have tried removing it but it will not go away....
Attachments:
ghost1.jpg ‏64 KB
Ghost2.jpg ‏78 KB
ghost3.jpg ‏67 KB

falkpl wrote:
Is this isolated to this vi, is it possible you renamed the pane. Panes have names by default it should be named pane this can be changed through the property node pane.label.text.
This VI must have got corrupted somehow.
I deleted everything and created a new event structure in this VI and the default Pane name is in hieroglyphics.
Now copy and paste this structure to a new VI and it is fine.
Strange...
Message Edited by RTSLVU on 01-26-2010 11:08 AM
I fixed it so teh vi would not run on open...
Message Edited by RTSLVU on 01-26-2010 11:09 AM
Attachments:
Pane in the butt.vi ‏13 KB

I using an event structure for an input box and also for hardware input

Hi there!
I have many input boxes and display boxes on my user interface and i have a case for it in the event structure. If the user changes the values of the input boxes, the particular event case writes this new value to the hardware. However, in the timeout section of the event structure, we read the inputs from the hardware and we set the value for its related display object. Within the timeout section i set the value for the related user interface display component, by making use of the property node value.
Furthermore, for most of the display components, i have a event case for a value change associated with it. In that event case, i check for range errors and so forth.
My assumption was that when i read the value in from the hardware and set the property node value, the user interface component's value will change and it would then trigger the event of the value changed for that component.
My assumption worked to the point of updating the component's value, however, it did not trigger the event for the value changed for this component.
Please advise me on how to achieve what i wish to.
Thanks.
Regards,

Local variables are actually much more efficient than property nodes as far as execution speed goes. Take that same VI and delete the property node and instead write to a local variable inside the loop. You'll see the speed nearly identical to writing directly to the indicator. But note that variables also cause a copy of the data to be created. So if you're just using the "Value" property, you're much better off using a local variable. But don't use both at the same time. If you are reading/writing other properties when you update/read the value, you might as well use the value property.
Sometimes you can't get around using either variables or property nodes. Initializing controls to saved values from an ini file is one example. But in this case, they are only written to once as the application starts so the performance hit is negligible.
One thing you can do is store values in a shift register as they are read and pass this through your application so the last value read can be accessed from anywhere. You can even create a cluster that runs through the shift register to hold several values in a single register. This can be expanded a bit farther to create what's called a Functional Global. This basically a subVI with a While loop that only runs once on each call. It has a shift register to store data and a Case structure to Read or Write data into the register. There's a pretty good example that ships with LabVIEW showing how these work. Open the Example finder and search for "Functional Global Communication". This example shows how to use them to pass data between two independent loops, but they work just as well in a single loop application.
One of the big advantages of these Functional Globals over the standard LabVIEW Globals and local variables is that you can add cases to manipulate the data in addition to just storing it. Also, since it's a subVI, access to the data is protected to one caller at a time whereas variables can have multiple reads and/or writes at the same time. This can cause race conditions.
Hope that helps a bit.
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.

Event structure - general

hello
this is probably something that had been treated millions times, however i could not find direct answers from previous threads on that, so i ask directly.
i am a bit confused by the utilisation of event structures:
first, one would expect that if the event is used, say in a while loop, then outgoing data would be kept trough the sequence, without having to wire trough the other events, unlike as depicted in the pic below. that should be to my understanding the definition of "use default values" on the outgoing data nodes.
however it seems not to work like that. why? is there a way to force LV to do as i want (instead of "use default values", make him "use last input value")?
wiring trough all the nodes make the event structures very unelegant.
second: this is probably a very naive one, but i dont like the way i do it: in some events i have same operations going on as on turn on of the vi. in other words, when i initialise my system, i pass trough several operations, which also exist in the event structure. to make the diagram more elegant it would be usefull to call all those events programmatically a first time. up to now i do it by programatically signalling the values of some controls. however there must be a more elegant way, where i could just queue the events needed. any suggestions?
Message Edited by Gabi1 on 05-17-2007 06:11 PM
Message Edited by Gabi1 on 05-17-2007 06:13 PM
... And here's where I keep assorted lengths of wires...
Attachments:
event structure.PNG ‏10 KB

Jarrod S. wrote:
Triggering events forces a thread swap to the
user interface thread, which can slow down execution. It can also make
a redundant copy of the data that has to get stored in the control
whose value change was triggered, which you might not need. Enqueuing
commands onto a queue does not have these limitations.
To clarify Jarrod's comment, it's important to note that neither the event structure itself nor dynamic events cause a switch to the User Interface Thread. Functions inside the event structure (e.g. property nodes, invoke nodes) can cause a switch to the UI Thread when they operate on UI components.
In that discussion, Jason King points out that:
"There is nothing specific about the event
structure that requires the event-handling case to run in the UI
thread. In fact, there is not any event that will force it to run in
the UI thread"
"Reading from or writing to a front panel terminal or local variable does not cause the diagram to run in the UI thread."
"Any actual processing of user interaction,
however - either looking at user interaction to determine which events
to generate or finishing processing a filter event after the event
structure has had a chance to discard it or modify any of the event
details - requires the UI thread."
"Pretty much anything you do with the reference to
a control or indicator will cause a switch to the UI thread (property
nodes, invoke nodes, etc)"
Certified LabVIEW Architect
Wait for Flag / Set Flag
Separate Views from Implementation for Strict Type Defs

Event Structure with Event source: This VI and Event: Mouse Up

I downloaded an old example from 2008 on this forum and would like to duplicate it. It uses an event structure with an event case of just Mouse Up. Under Event Specifiers: the Event Source is <This VI> and Event: Mouse Up. This works like I want in LV 2009.
In LV 2009 if I choose for Event Source <This VI> under Events Mouse Up is not an option! I tried Event Source: Pane, and then Event Mouse Up is an option, but this does not trigger the event if you drag the mouse off the pane before you lift the mouse button.
I can copy the Event Structure over to my VI and rewire every case but that does not seem to be a good solution cuz I want this in several VIs.
I have attached the original VI with the Event Specifier I want. How do I get this Event Specifier in LV 2009?
Attachments:
Slider event control.vi ‏19 KB

phillman wrote:
I downloaded an old example from 2008 on this forum and would like to duplicate it. It uses an event structure with an event case of just Mouse Up. Under Event Specifiers: the Event Source is <This VI> and Event: Mouse Up. This works like I want in LV 2009.
In LV 2009 if I choose for Event Source <This VI> under Events Mouse Up is not an option! I tried Event Source: Pane, and then Event Mouse Up is an option, but this does not trigger the event if you drag the mouse off the pane before you lift the mouse button.
So what you can do is monitor the 'Mouse Leave' event for th pane, and then start polling the mouse state.
Technically it is correct that there is no Mouse Up event detected since the Mouse Up is not happening on th epane.
Ton
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!

Slow execution of a event structure(Calling VI)

The VI i created is gettin slow after execution of a particular set of event in an event structure(Calling VI).Is it because of improper use of shift register?
I have attatched the VIs...Please run GUIdev and suggest solutions.Its really gettin on my nerves.
Attachments:
GUIFDR.zip ‏88 KB

Hi altenbach
Thanks for finding ways to optimize the code...but i have a few doubts.
CPU burner:I took care of the cpu burner condition.I jst called those for trying out t main VI.I will be replacing those VI with developed ones.
    * Why are you bundling and then immediately unbundling all these pictures?
     Ans:chgd it
    * You have many overlapping objects on the front panel. Not good for performance.
     Ans:I am making a GUI so i thk i have no other choice but to overlap them.Also is there ny way to remove the frame from the picture box.I have just minimized and kept it.
    * Use an array of paths and index the desired element instead of reading via value property nodes.
     Ans: Can u site an eg for it..i dnt hav tht level of experience
    * There is no event for the stop button.
       Ans:Is it necessary?I will be modifying it in the future.
    * You don't need the timeout event.
       Ans: Modified it
    * Lots of near duplicate event cases. Once instance of each is enough, simply use control references.
       Ans:Each event case is either for moving out,moving in or clicking of the sliding button.How do i use a control referece for it?
    * Lots of duplicate code for the pictures and paths. Use an array of names, autoindex it on a FOR loop, and use only one copy of the code fragment.
      Anslease site an example so i can follow suite.
    * You seem to insert a VI at every iteration of the loop. Is this really necessary?
     Ans:Actually i wanted to insert a Vi only on the mouse down event, and continue running the same VI even if other mouse events take place.But i cant thk of a logic to avoid thm.But i really need a solution for tht.
Can you explain in a bit more detail what you are actually trying to achieve with all this? Thanks! :
My Vi as u can see is a GUI for downloading data from a hard disk and viewing and modifying the video and audio data.I will be interfacing the video and audio part later on as it is still being developed by my frnds.
Also the problem of inserting a VI at every iteration is goig to pose a problem in the future as i want to load each VI only for mouse clicks and let it run for all other instances.
Please help me out
regards
Sankar

Stop events structure

Hi all!
Here I am! I'm using a events case in a while loop. The problem is that
I should press twice on the stop button to stop the while loop...WHY!!!
That my question...I set Switch when release for my stop button...(I
must use a local variable of it...) Now, I can't stop my VI it seems
that the value of my Stop booleen must be read before the while loop
begin...then, when I press once my Stop booleen, then, it stay at true
value, end it seems that the while loop start an other time...So, I
press the control again, and the Vi stop correctly...( By closing, I
send a false value to the stop booleen, to recover a ready to use
control Like a latch mechanical action...)
Now there is the problem...To figure out where is the problem, I
highlight this...and now, I got no problem! each time it is highlight,
my VI stop correctly, but in normal mode, I should push twice on the
control to stop it...Is it common? Do you know something weird with
event case? By the way, I need to have an event case with no time out,
because I use some shift registry each time I make an event action...
An other weird tings, is when I recreate the "same" thing in an other
VI, Or even I copy paste the inner part of my VI in a brand new VI, it
working...
In addition, I can't send you an example, because it is a part of a
very huge program...(So I should send you too many subVI and special
driver...So...)
Nevertheless, I took a picture
Thanks for help this...
Fakstory
Attachments:
Doc12.doc ‏77 KB

Look, if you only attach a picture, we can only comment on what we see!
The main diagnosis ("race condition"!) has already been mentioned. The point about the event structure inside a case structure is serious and could possibly cause problems like you observe, but it is not possible to tell from the picture for sure. Your picture shows very little, but what it shows does not make sense. I just pointed out the two most glaring observations. Since you say yourself that you are a noob, such comments can help. A program that is clear and does not contain unecessary things is much easier to debug.
Typically, the quality of the answer cannot be better than the quality of the question. You don't provide enough details and the image you posted is useless to pinpoint the problem.
Analogy:
You don't bring a picture of your motor to the mechanic and ask why the car does not start. Unless the picture show that the motor is missing or on fire, nonbody will be able to tell what's wrong.
All we can say for sure so far is that have a race condition. Provide some code (even broken) and we can give a more detailed analysis.
LabVIEW Champion . Do more with less code and in less time .

Can you share FP Controls between different Event Structures

I'm creating a program that will either read real-time data from an VNA on the GPIB bus, or read a saved s2p (Agilent) file and analyze it. The FP consists of 5 graphs, and various controls which handle events like printing, changing filters, or exiting. on the BD I have a case structure controlled by an operator selection pop-up. I tried using the same FP controls in the event structures I have setup in each case, as only one event structure would ever be executing at any given time, but the program doesn't seem to like it ast run-time. I've worked around the issue by creating "duplicate" controls and using the property setting to make them visible/disabled, etc., but the is seriously congesting my BD.
Anyone know a way to share controls with seperate event structures?

It sounds like the root problem is the overall structure of your program. I highly recommend that you check out the Queued Message Handler project template in LabVIEW 2012, that will show you how to utilize a single event structure and pass events to a consumer loop. If you program is too large to consider an architecture change at this stage of the game, then there is a workaround for your problem.
What is most likely happening is that you have the event structures all set to lock the front panel until the event completes. However the case structure that you have wrapped around these event structures is causing all but one of these event structures to be unreachable thus preventing you from handling the event. Again, as I stated above, the "RIGHT WAY" to fix this is to select a better program structure but the "kluge work-around" fix is this: Dynamically register for the value change event on all of the controls you are trying to trap events for. Dynamic events can be deregistered and re-registered at run time. This will allow only the event structure in the active owning case structure to be registered for the events, thus no other event structures will get in your way.
Disclaimer: This advice is given based on very minimal information and a great deal of speculation and may not be correct. Please include your code if you need further assistance.
Charles Chickering
Architecture is art with rules.
...and the rules are more like guidelines

Daqmx "Done" event not triggering event structure

I would like the user to be able to abort my daqmx task by pressing a button.
I am attempting to use the method in this VI:
https://decibel.ni.com/content/docs/DOC-15815
It utilizes an event structure with the daqmx Control Task VI to abort.
The example VI above works for me, on my system with my USB-6356 device, as expected.
When I attempt to incorporate the same method into my VI it does not--despite having an identical arrangement, so far as I can tell.
I believe that my problem lies with the event structure, and the dynamic registration. I am unfamiliar with this and must be using it incorrectly.
I have attached my VI, though it is cumbersome. The code which I am struggling with is in the "Acquire" case. As far as I can tell, I am doing exactly the same this in this particular case as in the example mentioned. Yet in the example, the event structure completes, or aborts, whatever you want to call it, right after the "Wait Until Done" VI executes. In my own VI, the "Wait Until Done" and "Clear Task" VIs execute, but the event structure does not register it.
Here are my specific questions: is there anything extra or special that one must do in order for the Task to properly trigger a "Done" event and pass through the event structure? At what point is the daqmx task "Done"?
thanks,
Matt
Attachments:
BoomTubeMain.vi ‏175 KB

natasftw,
My event structure is identical to theirs; what you are seeing are the two different cases that exist in the event structure. In both the example and the VI, there is a <task out>: Done and a "Dynamic Event": Value Change. In the dynamic event case, I have my abort button and relevant code--this I believe is the code you were referring to, which you thought I was missing... Regarding my multiple event structures, they should operate completely independently as they respond to different events.

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.

Event structure in Sub VI

Hello ,
I have a developed a program which captures video and user can save images out of it. I have used .NET reference to handle the video part, and the VI is attached in this post. Now i have to make this VI as a sub VI and running this from Main VI. I tried creating event structure in Main VI which i used in sub VI , still i could not suceed. Kindly assist me in this regard
Solved!
Go to Solution.
Attachments:
Webcam-Control-Projekt-mit-Reference-Design-2013_original.zip ‏286 KB

Hello Michael,
I have attached a model in which Main VI calls the Sub VI using Event Structure. Two events can occur in Main VI and their corresponding event Structure is called in Sub VI using Register events. When i run this VI the out put is fine some times but other times i need to trigger event many times before i can see its effect in Sub VI, my doubt is that Register events are reliable, whenever (during the execution of LV) if event occurs will surely its code in the sub Vi gets executed?
also I have put a indictor(numeric) in the SUb VI which i connect back to Main VI, when i run, i can see the result only in the sub VI not in the main VI.how to see in Main VI?
I have used the this model (which is attached ) to implement my project(which i already mentioned) . one switch for starting the video and other for recording the image. The video is getting started with out any trouble, but imgae is recorded only few times when i press the button which is for image recording, most of the time second event fails to get executed. Also there are difference in output when i run with and without "Highlight execution", why this happens, is this because of Reg events?
any more info if required let me know, i will provide.
Attachments:
Main_sub_VI.zip ‏18 KB

Copy event structure

Similar Messages

Maybe you are looking for