How to implement a button function to trigger several buttons

[bhl3302]

Hi All, I have 6 buttons "Read" in front panel, each of them works seperately. In the block diagram, each button is inside an event.

Now if I want to create a new button, that by clicking it, all these 6 buttons can be triggered, how can I do it?

The attached picture shows what I want to do. Thanks for advising!

[Mark_Yedinak]

Define user events related to your buttons. Each of your current event cases would be modified to include the user event as well. When your magic button is pressed simply generate the appropriate user events for the other buttons you want to active.

[smercurio_fc]

I'm guessing you probably don't have a Producer-Consumer architecture or a Queued State machine, so you're probably actually doing the reading in the event case for the button. I'm also assuming you're using the buttons with the standard mechanical Latch action, which means you can't use the Value (Signaling) property. Otherwise, you could simply have the Value (Signaling) property for the other buttons, and write a True to them. So, your options are:

• Change the mechanical action of your buttons to "switch". This means you will need to reset them yourself in the event case. It will also mean you will need to initialize their values at the start of your code.
• Get a better architecture that will allow you to queue up each "event" that you want to do.
• Create a user event that reads all six values.

[tbob · Accepted solution]

Here is a simple example to show how it is done using the Vlaue(signaling) property node to cause an event for each other button.

[P@Anand]

---

@tbob wrote:

Here is a simple example to show how it is done using the Vlaue(signaling) property node to cause an event for each other button.

---

The value signaling works in the same way irrespective of the input whether it is true or false why is this behaviour?. Can you or anyone please explain any significance behind this?

[Mark_Yedinak]

---

@P Anand wrote:

---

@tbob wrote:

Here is a simple example to show how it is done using the Vlaue(signaling) property node to cause an event for each other button.

---

The value signaling works in the same way irrespective of the input whether it is true or false why is this behaviour?. Can you or anyone please explain any significance behind this?

---

Because you did change the value. It does not verify that the value is actually different, just that a value was written to it.

[smercurio_fc]

---

@P Anand wrote:

---

@tbob wrote:

Here is a simple example to show how it is done using the Vlaue(signaling) property node to cause an event for each other button.

---

The value signaling works in the same way irrespective of the input whether it is true or false why is this behaviour?. Can you or anyone please explain any significance behind this?

---

Why would you expect it to work differently? The event case provide the "NewVal" and the "OldVal" to use as a comparison.

[P@Anand]

---

@Mark_Yedinak wrote:

---

@P Anand wrote:

---

@tbob wrote:

Here is a simple example to show how it is done using the Vlaue(signaling) property node to cause an event for each other button.

---

The value signaling works in the same way irrespective of the input whether it is true or false why is this behaviour?. Can you or anyone please explain any significance behind this?

---

Because you did change the value. It does not verify that the value is actually different, just that a value was written to it.

---

Yes it is not checking the input thats why I am asking why this property is kept like this?. If you take the Re-initialize to default method it doesn't need take an input but here we need to wire the value but changing that doesn't make any difference.

[P@Anand]

---

@smercurio_fc wrote:

---

@P Anand wrote:

---

@tbob wrote:

Here is a simple example to show how it is done using the Vlaue(signaling) property node to cause an event for each other button.

---

The value signaling works in the same way irrespective of the input whether it is true or false why is this behaviour?. Can you or anyone please explain any significance behind this?

---

Why would you expect it to work differently? The event case provide the "NewVal" and the "OldVal" to use as a comparison.

---

Yes I got it but am just trying to understand why an input required for that. Does my question make sense?

[smercurio_fc]

To be honest, not really. The function is to write a value and generate a signaling event. It's not "only write the value if it changed".