Wire enumeration conflict

[przemo1526]

[altenbach]

Your enum diagram constants are different, as the error message says.

Delete the three diagram constants and do a "right-click... create constant" for each property node to get the correct enum.

(Overall, your code "smells" bad. Can you show the rest? Most likely the use of value property nodes is inefficient and convoluted here.)

[paul_a_cardinale]

Did you read the details?

[GerdW]

Hi przemo,

to add to the other answers:

Whenever you work with enums on your frontpanel you should create (and use!) a typedefinition fro them in your project!

[JimB.]

Either do as altenbach or create a typedef if this is the same enum you are intending to use in multiple places.

You currently have a type mismatch, and if you don't manage the enum using a typedef then this will continue to happen every time that you modify the list of values for a control.

[przemo1526]

Which are three diagram constants ?

[altenbach]

---

@altenbach wrote:

(Overall, your code "smells" bad. Can you show the rest? Most likely the use of value property nodes is inefficient and convoluted here.)

---

If all three value property nodes refer to the same control/indicator (assuming you don't have several with the same label!!!), only the last one written will win, but depending on where else it is read you could get unpredictable race conditions. All you need is a selector based on the two booleans to select the appropriate value and write it to a local variable (Or the terminal if this is an indicator).

[altenbach]

---

@przemo1526 wrote:

Which are three diagram constants ?

---

Maybe you should start with a few basic tutorials. You have three diagram constant wired to three instances of  value property nodes. Right?

Why don't you attach your VI so we can give more specific advice?

[przemo1526]

[przemo1526]

This is how was look like before changes made