structure of the event fires two times

Similar Questions

• How to manage the structure of the event with two loops

  I have a question about the structure of the user event with 2 buttons?

  key 1: START LOGGING DATA

  key 2: STOP LOGGING DATA

  How do I control my

  structure of the event so that it will work? because now that the loop is save data... I can't stop the loop, when I clicked on buttons.

  

  

  

  super_saiyans wrote:

  the problem with moving it is that I don't have control of the DATA RECORD STARTING?

  Of course, you do.  When you get your press conference button, you say your state machine to move to the State of logging.  You must also make sure that you return to visit the State to wait for the event to check out the events of the stop button.

• Update the reference in the structure of the event

  Hello

  I would really appreciate if someone can help me with the next issue:

  I have a main VI with the structure of the event in the while loop.

  There is a case of a button initiating the Subvi, which extends an engine.

  To stop the loop inside the Sub - VI I pass a strict type reference him out of the main façade of VI.

  The problem is that in the event structure is not updated to reference, i.e. on press the abort button I can't stop the engine.

  The strange thing is that, without the structure of the event (only in time loop) it works. I try to put the button on the outside another loop: it does not depend on it. Without the structure of the event - everything works.

  LabVIEW 2012 32 bit

  Thanks in advance,

  Dirs

  You have the checkbox in the case where the matter set to Lock the front until the end of the case of the event?

  Is the case of the event start quickly, or is it stuck in the Subvi?

  Have you put in custody and recommendations for using events in LabVIEW - LabVIEW 2013 help ?

• References to cluster in the structures of the event?

  Hello

  I'm building a front panel with, say, a bunch of buttons/indicators in both groups. Inside a while loop, I had a structure of the event with two cases, one for each cluster, waiting for a change in the value of each cluster. I know which button has been activated by comparing OldVal, NewVal.

  Now, I want to generalize a Subvi comparison since I will soon add loads of button clusters. The Subvi I have managed to get to now me returns a string containing the name of the control that has changed its value.

  However my Subvi accepts only one type of clusters only and is not generalizable. I understand that this cannot even be done directly and I have to use control references to move inside my Subvi. But I can't create references of control for the two OldVal and NewVal clusters, only for the control on the front panel.

  So, how to create a Subvi, which returns me a string containing the name of the control with a different value between two identical groups of any type within a structure of the event?

  My LV version is 7.0 and I can't open most attachments on this forum, so I would appreciate your screenshot solutions.

  Here, you can code like this so that you will come to know what button was pressed.

  

• reset the timer using a structure of the event

  I wrote a simple code to count the second and the timer can be reset if I press the button "reset".

  It works; However, there are two problems,

  1. when I run the program, the timer takes 1 second to start

  2 when I press the reset button, the timer also takes a second to answer

  I think it's the 1000ms that is connected to the left corner of the structure of the event. Is there a better way to overcome this problem? (the timer starts and resets immediately

  When I launch the program and press the "reset" button)

  Thank you!!

  Dear ivy037

  You can make the time outside the structure of the event as in the attached code.  I would like to know if this is satisfactory.

  Thank you

• reading two sensors (alternately) in a structure of the event permanently

  Hello

  I have a structure of event with various functions of the user interface. The entire application is on a laser diode control and playback of two light sensors IR which cover different wavelengths (if and InGaAs). The two sensors are connected to the same AD converter, but to different channels. So if I want to read the two sensors, I have to change the setting of the "Converter" AD channels. The real question is how to implement playback continues two sensors in the structure of the event? I want to be able to read alternately each sensor in a span of 50 or 100 m is possible, another using function of time-out of the structure of the event with a kind of logic xor for switching channels? Maybe something with more features (somehow by a timed loop)?

  Any idea is welcome.

  Thank you and best regards,

  Gregor first

  P.s. The sensor reading is done by a National Instruments SPI map where SPI is the master.

  2010 VI converted down

• A structure of the event within a certain time out loop.

  I'm relatively new to LabView and in particular the structure of the event. I was looking at the previous posts regarding the structure of the event and the difficulty to stop people. In my VI, I have two cases of event besides the time-out. I use this VI for control of stepper motor. I have 2 buttons (for each case), a movement to the left, the other to the right. It works as it is supposed to, but when I try to turn it off I have to press the two buttons before it stops. As if the loop should run everything inside before stopping.

  In my VI, how can I do the execution stops when I press the stop button? I tried many configurations of the stop button and boolean logic (which I believe was correct), but I am now stuck.

  Thank you very much

  Alek

  
  

• problems with timing in a time loop in a structure of the event

  Hello

  I'm using labview to control three motors stepper, running the three stages of different translation in different axes (X, Y and Z). Please see the attached VI, focusing on the structure of the event on the RIGHT side.

  In the Z axis, I am trying to run the engine for 5 seconds, after clicking on a button. I have attampted to do by adding a sub of elapsed time VI within a while loop, located in the tab 'Mouse before Z down' the structure of the event. A similar "elapsed time while loop" is also included in tab 'Z reverse the mouse down' the structure of the event.

  Separately these "elapsed time loops" work very well, BUT when I run a Z direction after another, say 'Z Reverse' and then 'Before Z' then they annoyingly interact. The calendar is gone, with the moment where we add, rather than rebooting.

  No idea how I can reset the time elapsed while loops? Or is there another method better do?

  Thank you very much

  Charlie

  charlieryan wrote:

  I take a wire from the 'i' of the while loop at the entrance of the Sub autoreset - VI of tiem will blink?

  No, connect you to the "reset", not "autoreset".

  

• Front panel locked, but not due to the structure of the event

  Hi it LV community.

  I did a staemachine program that executes an oscilloscope (screenshot of a provided below... the State of the problem). I ran my program yesterday and it worked very well. Then, like a model, a dialog box opens and I just clicked on it in a hurry. now my front hangs as soon as I move the above-mentioned State "the Oscilloscope settings.

  As indicated, I have go a repeat loop that collects successive impulses of my oscilloscope and displays on the front panel (it works fine). In parallel, I have a structure of the event that makes the tail for the real-time feedback of changes to parameters that I placed on the façade (exodus of state change).

  Here's the problem: as soon as I State 'Oscilloscope Settings' using a Boolean button on the front panel for get me there, the front hangs... No event triggered by this point, and even if it did, I already deselected the "Lock panel until the end of the matter for this event" checkbox in the case where the structure menu.

  So WHY is my front lock now? Thoughts anyone?

  Read the detailed help for event structures.

  He urged that a single event structure serve in a VI. There are moments where more can be used effectively, but caution and a thorough understanding of the structure are needed.

  The problem is that you have several structures of the event in the various cases of the state machine and they are set to respond to the same events.

  When the button Set Oscilloscope, the structures of the event in the purchase Menu and home screen States receive the event. The two lock the screen, but only one of these cases may work. It can transfer control to the State of the Oscilloscope settings, but the other event responding to this same event structure maintains the locked Panel.

  The solution is not not to release any of the event. The default value is usually the best setting. The best solution is to spend on an architecture of producer/consumer (events). Who uses two parallel loops. The producer has the one and the only structure of the event and passes orders to consumer loop through a queue.

  Probalby want as the mechanical action on the buttons to lock when you press. Put kiosks inside the respective case of event changed value and local variables becomes unnecessary.

  Lynn

• leads the value change in the structure of the event

  Hello

  Please the the VI attached.

  I would like to know what event triggers when the value true or false of the changes led?

  In the case of structure above the structure of the event, the values of true or false of the led are changed.

  From the change, the analog output for Acquisition Card changes. However, the change event of the value in the structure of the event never fires, I know that I run the Vi with the selected highlight enforcement tool.

  Thank you

  Venkat Rao

  Changing the value in an event structure occurs only if one of the two following situations occurs.

  1. the user who modifies the control on front panel.  That may not happen since these LEDs are indicators and does not control.

  2. the program writes a value of property of the Value indicator/control (signalling) node.  Writing to the terminal of the indicator, or the local control variable / indicator not fire the event.  Given that you do not use value property (signalling) nodes in your program from this moment, won't happen either.

  Note that the value change event is a bit misnamed.  The change event is triggered, even if you do not actually change the data.  So if your LED is currently worth, and you write a True Boolean value for the Value property node (signalling), the event always fires even if you're not technically change the data.

• get the structure of the event inside the while loop to wait for event occurs before the execution

  Hello

  I have a small problem, when I raise an event using a value change button, which works very well.  The problem is that the VI does not wait for me raise an event and instead runs the same event again, even if I have not pressed the button to start again.  The mechanical action of the button switch is released is.

  I was wondering how you get the structure of the event to wait for a user event, after that he executed the first time.

  James.Morris wrote:

  There is no reason that the event should be raised twice as much that the only way that it fires in your code is by the user by clicking on 'Hall measure only'.

  Oh yes, there is, and I deserve a kudo for this one.  Mechanical action on the button is set on the switch until published, so click to generate an event, on the bottom and on the square, attached is an example.

  My boy has my students hate this question, and to be honest, I hated it.  When never would you do that intentionally?  Honestly?  Anyway to change the button back to normal (as default latch when released) and move the terminal button in the structure of the event where it is managed and it will work as usual.

• Several events in the Structure of the event

  Hi all

  I was wondering if there was a way to combine with the operator AND user events to an event. For example, I would an event when button1 AND button2, AND button3 were pressed. Mabye event strutures are not the right way to do it, but now when I add multiple events to an event framework, it seems to happen when one of the events is triggered, as event1 OR event2, OR event3 and I can not understand how to change that.

  I hope it makes sense what I want to do. I Nestle my structures of the event, but I'm sure it is bad and would give unexpected errors. Please notify.

  Thank you!

  Use a shift register and maintain States whose keys were pressed. Then, you can actually run code you want once all have been pressed. If you do this you afflicted to a timeout to clear the buttons not pressed state if only one or two have been pressed and nothing more certain period of time.

• Structure of the event can be triggered a 1 event

  I am using a structure of the event to trigger a 1 off the coast of the event.  I thought that I could check the State I want to trigger the event and this thread the Val (signaling) a Boolean property.  Then I created an event to change the value on this command expects the event fires when the value from false to true.  I think it is this writing in Val Signaling property raises the event each time not only when the value changes.

  The attachment is a simple vi to try to illustrate this point by using the iteration count to try to trigger a 1 off the coast of the event on the 10th iteration.  The Boolean 'once' varies from iteration from False to True on the 10th, but the event is fired for each iteration.  Need to run in debugging

  Any help much appreciated

  Ken

  I've seen this confusion on the value of property front of signage. You expect it would only trigger an event, if you write a different value than the control or the indicator has been set to. This is not the case. She fires whenever you write to it.

  Your simplified example wrote to the property value of signage in the while loop for each iteration. That triggers the event value changed whenever you write to it. Notice that the property is 'signs of value' and not 'value has changed the signs '.

  Some of the examples were complex with the authors of notifications and user events. But the easiest way is just to put the property within a business structure node while it is written only when you want that one off the coast of the event. It does not matter what you write to the node if you send all the data for the case of the event.

  If there is a reason you must write to the Boolean value of traffic property on each iteration of the loop you can use the value written in sub condition to run code in the event. But notifiers, queues and the user just looks complicated events.

• structure of the event recorded does not change value

  I have a VI that communicates with an FPGA via a telnet interface.  I have several Boolean controls on the front panel.  When you click a control, it sends a write command on the face i in telnet to the FPGA.  Similarly, if a process in the FPGA himself wrote the same registry (that control written when I clicked on it), an order is generated in the FPGA and returned to the VI and the control (via a local variable) lights or unlights accordingly (based on value).  In other words, these controls are read-write...

  It's all workers, except for one important thing.  I have the code that runs through a structure of event whenever the value of the control changes.  I can see that this code executes in fact when I click on the control via the front panel.  HOWEVER - when something is generated in the FPGA finally changes the value of the control, the structure of the event does not, even if I see the value of the change of control on my front.

  A specific example, I have a control named CLIENT_LB.  When I click on CLIENT_LB, I see it lights up, and I see the event structure code run.  Now, if I have the FPGA process to set CLIENT_LB to 0, I see unlight on my front, but does not run the code structure of the event.  I have probes in place who have checked the associated local variable CLIENT_LB evolving impact of values.  The structure of the event reads: 'CLIENT_LB': value change.

  Shouldn't an event structure "value change" run when the value changes, regardless of whether if it happened manually (i.e. me by clicking on the control) or automatically (i.e. the FPGA written in VI and changes the value of the control)?

  The VI is great, and you would not be able to test it in any case unrelated to the material, to remedy that I've attached 2 screenshots, I have described below.

  1. This is where the string from the FPGA analysis occurs.  The chain between the sub - VI, and then the data chain part is hidden to determine if the Boolean value of the control is true or false.  I put a probe on CLIENT_LB, and I see that as the FPGA changes the value of the register, CLIENT_LB passes from false to true as a result.  I checked this several times.

  2. it is the structure of the event.  This code runs when I click on CLIENT_LB on my face, but does not run when the peak CLIENT_LB #1 local variable is changed.

  Writing to variables never fires events to "change the value. If writing should raise this event, use the property "Value (follow the signs).

  Norbert

• Structure of the event - controlled motor not variable

  I have a state machine that includes certain structures of the event. These event structures are used to control stepper motors using an Arduino Mega microcontroller. I'm using labview in 2012.

  The entrance to one of the events is the variable "pour the entry. I want to use it to control the motor speed and direction.

  If I control the motor as shown in the attached image Working.jpg, then the motor functions correctly. If I fix the motor to the steps variable # then the engine moves at the speed set in the right direction depending on whether the entry "pour" is positive or negative.

  However, I want to control the speed of the engine, not the number of steps, with the variable "pay Input". I checked that the values read by the indicator image INPUT_VALUE works do not are of the same order as the specified values, working, by using the "Set Speed". When I connect the value of the entry to the spindle speed of the motors of the Arduino (not_working.jpg) icon, the engine is running, apparently indefinitely at maximum speed. I don't understand why there is a difference in motor behavior between the value provided by these two methods at the entrance to the speed of the motor. I am confused by the present and don't know where to go from here.

  The structure of the event somehow behaves differently when taking a value from outside the structure to this data inside? or y at - it something to do with the opening of the structure on its first loop?

  I have also attached my vi together, even though she may not be the easiest to follow and requires an arduino Mega to run.

  Carlr wrote:

  I have a state machine that includes certain structures of the event. These event structures are used to control stepper motors using an Arduino Mega microcontroller. I'm using labview in 2012.

  The entrance to one of the events is the variable "pour the entry. I want to use it to control the motor speed and direction.

  If I control the motor as shown in the attached image Working.jpg, then the motor functions correctly. If I fix the motor to the steps variable # then the engine moves at the speed set in the right direction depending on whether the entry "pour" is positive or negative.

  However, I want to control the speed of the engine, not the number of steps, with the variable "pay Input". I checked that the values read by the indicator image INPUT_VALUE works do not are of the same order as the specified values, working, by using the "Set Speed". When I connect the value of the entry to the spindle speed of the motors of the Arduino (not_working.jpg) icon, the engine is running, apparently indefinitely at maximum speed. I don't understand why there is a difference in motor behavior between the value provided by these two methods at the entrance to the speed of the motor. I am confused by the present and don't know where to go from here.

  The structure of the event somehow behaves differently when taking a value from outside the structure to this data inside? or y at - it something to do with the opening of the structure on its first loop?

  I have also attached my vi together, even though she may not be the easiest to follow and requires an arduino Mega to run.

  You have a very inappropriate design of "state machine" - even if you do not have same event in more than one of your structures of the event (in addition to time-out), looks that get some of your treatment to go forward until you get something very specific (and in which none of your other user events are being processed).

  I strongly suggest that first set you design of State machine - perhaps follow producer/consumer Design Pattern (events) rather than having everything in a loop, the way you have.  If you keep everything in a loop, you should consider redesign so that you at least allow events to deal with rather than stay in a loop for an indefinite period!

  In any case, in the case where work, you send variable "Set Speed (steps per second)" for engines step by step write vi.  But otherwise, you're feeding 'Entry for' value - are they the same? And to let you know, you send only command "write" step by step when the input value to be paid.

  It's a big mess!  For starters, look at the attached picture, get rid of your structure of the event that has "for the entry" and replace it with what I showed in the picture. (In fact, all your event structures can / must be replaced with a similar logic.) Does not need the event structure in all this, you're just more complicated it must be!

  -DP