HOW TO FIX THIS CODE LABVIEW

[abimkeren.]

how to fix this?

[pincpanter]

Use Merge errors from the Dialog & User Interface palette instead of Build Array.

[abimkeren.]

[pincpanter]

Well now please explain why you insist in building an array...

[BertMcMahan]

Throw another Merge Errors after the Build Array.

(Just kidding- get rid of Build Array altogether)

[PinguX]

Change the mechanical action of the control to a "switch" mode. By default it's "latch when released".

Boolean control on latch do not permit to use local variable for it.

[crossrulz]

---

@PinguX wrote:

Change the mechanical action of the control to a "switch" mode. By default it's "latch when released".

Boolean control on latch do not permit to use local variable for it.

---

This is bad advice.  First of all, it doesn't look like the OP is even using a second loop.  Secondly, a different way of passing the data should be used over local variables, a Notifier immediately comes to mind.

[altenbach]

---

@PinguX wrote:

Change the mechanical action of the control to a "switch" mode. By default it's "latch when released".

Boolean control on latch do not permit to use local variable for it.

---

The broken wire has absolutely nothing to do with mechanical action or local variables. Your response is completely off-topic.

(And if somebody blindly changes to switch action in order to create swarms of local variables, something else is wrong 😄 )

[PinguX]

True @crossrulz, thanks for correcting.

[niravdesai]

Use unbundle by name and use error status of each error and do logical OR of each error status then stop if true condition works ok and broken error will be removed