Conflict of 2 control events

[GerdW]

Hi Pavel,

NEVER use "default if unwired" tunnels when you want to store values in shift registers!

[Pavel_47]

Thanks for suggestions

I've wired phi and theta through all avent case.

These values are changed when "Regenerate B0" clicked, but events doesn't result B0x, B0y, B0z changes.

The new values phi and theta are taken into account once I modify B0max.

Best Regards

[crossrulz]

You need to force a Value Change event on the BOmax.

[Pavel_47]

Thanks, it works.

Unfortunately events created by B0max and Regenerate B0 aren't taken into account by XY Graph.

LabView doesn't allow to duplicate event - so I can't add B0max and Regenerate B0 into event case [1], where XY Graph is processed.

Any ideas ?

Best Regards

[GerdW]

Hi Pavel,

you don't need to "duplicate" an event, you only need to enforce the next element by using the "Value signalling" property or by employing user events…

[Pavel_47]

Hi GerdW,

Here I didn't properly understand what you mean.

Graph XY is processed in case [1].

I've employed "Value signalling" property for B0x, B0y, B0z in the case [3] where B0max event is processed.

I've searched for something similar for Graph XY to put it there ... but found nothing.

Cpild you please, develop a little bit your idea.

Thanks

Pavel.

[crossrulz · Accepted solution]

---

@Pavel_47 wrote:

I've employed "Value signalling" property for B0x, B0y, B0z in the case [3] where B0max event is processed.

---

Those controls/indicators are do not have any registrations for a value change.  They are read in the [3] even case, but that case is not triggered by their value change.  Even then, you only need to have 1 of them trigger the event, not all of them which would just cause that event case to be called three times.

[Pavel_47]

Of course ...

Thanks !