LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

events in events

    Hi everybody,

Maybe this problem has been answered before but I couldn't find the topic
Here's my problem:
I'd like to control an event in an other event structure.

To now, the only result I get is that all my front panel is frozen.

It's certainly normal behaviour but i'd like to have confirmation.

Thanks for help

Have a nice day !!

0 Kudos
Message 1 of 10
(3,622 Views)
Hi asalles,

you know you should only have ONE event structure in your vi? And you can have more than one event per event structure?

Could you describe in more detail what you mean by "control an event"? Can you attach an example of your vi?
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 2 of 10
(3,605 Views)
Maybe you can try unchecking the Lock Ffront Panel option in the Edit Events dialog box.
 
Moreover using 2 ES in the same VI is not advisible.
 
Read the Caveats & Recommendations in using the Event Structures before you code with them.
- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 3 of 10
(3,599 Views)

See to the point highlighted in Red. This is what GerdW implied, I think...

I also meant this only.

This is available in the LV online help. Just read them, you ll understand more about them.

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 4 of 10
(3,589 Views)
What do you mean with "control an event"? Trigger another event, or read
another event?

The first can be done with Value (signalling) or with user events.

The second has to be done with user events. Nesting event structures will
never work, and even putting two event structures in one vi is not supported
(but will work sometimes).

Wiebe.


0 Kudos
Message 5 of 10
(3,584 Views)
Thanks all,
It's working now
parthabe's advice was right

It is necessary to uncheck "Lock front panel until the events case for this event completes"

please find the vi I realized.... it  will more clear for you.

Next step will be to use subVIs

Thanks
0 Kudos
Message 6 of 10
(3,575 Views)
Hi asalles,

I changed your vi to use only one event structure.
I also changed all the events to "value changed" and moved the terminals into the event structure (the values should be read somewhere&somewhen!)...
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 7 of 10
(3,569 Views)

You must avoid using nested ES. It is NOT AT ALL NEEDED.

All you need is this, see the attached VI. Smiley Happy

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 8 of 10
(3,568 Views)

But GerdW,

I observed one thing in his nested ES VI.

How many times you click on the Activate bool, that many times the Generate bool can also be clicked to generate a random number. Only after that many clicks, it gets invisible again.

It is like a 1-1, 2-2 & 3-3 times scenario.

Maybe a bit more modifications are required if that is the desired functionality.

- Partha ( CLD until Oct 2027 🙂 )
0 Kudos
Message 9 of 10
(3,565 Views)
Hi Partha,

I would prefer the non-chattering behaviour of a switch. For me it doesn't make sense to click "activate" more than once when the "get value" is still visible...

Well, in the end we need more specifications from asalles to decide on this! (As usual: you need a well-defined problem to write software for it...)
Best regards,
GerdW


using LV2016/2019/2021 on Win10/11+cRIO, TestStand2016/2019
0 Kudos
Message 10 of 10
(3,555 Views)