LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

HOW TO FIX THIS CODE LABVIEW

how to fix this?

abimkeren_0-1716195172620.png

 

0 Kudos
Message 1 of 21
(702 Views)

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

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
Message 2 of 21
(700 Views)

abimkeren_0-1716218489970.png

 

0 Kudos
Message 3 of 21
(615 Views)

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

Paolo
-------------------
LV 7.1, 2011, 2017, 2019, 2021
Message 4 of 21
(610 Views)

Throw another Merge Errors after the Build Array.

 

(Just kidding- get rid of Build Array altogether)

0 Kudos
Message 5 of 21
(599 Views)

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.

 

PinguX_0-1716228261653.png

 

0 Kudos
Message 6 of 21
(576 Views)

@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.


GCentral
There are only two ways to tell somebody thanks: Kudos and Marked Solutions
Unofficial Forum Rules and Guidelines
"Not that we are sufficient in ourselves to claim anything as coming from us, but our sufficiency is from God" - 2 Corinthians 3:5
Message 7 of 21
(564 Views)

@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 😄 )

0 Kudos
Message 8 of 21
(558 Views)

True @crossrulz, thanks for correcting.

0 Kudos
Message 9 of 21
(537 Views)

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 

0 Kudos
Message 10 of 21
(412 Views)