LabVIEW

cancel
Showing results for 
Search instead for 
Did you mean: 

Why able to connect Boolean constant to the input of the Merge Error function.

Hello All, 

 

Why able to connect Boolean constant to the input of the Merge Error function,see snap below. Ideally merge should not allowed to connect Boolean constant.

 

But when running the code as mentioned in the snap gives error and then the both terminal to the merge error get broken.

 

Why this behavior with the error merge function.

 

Hemant 

 

 

0 Kudos
Message 1 of 11
(1,779 Views)

Hi Hemant,

 

which LabVIEW version do you use?

LV2011 doesn't allow to connect booleans to MergeError. Also LV2017 doesn't allow…

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
Message 2 of 11
(1,766 Views)

Hello GerdW,

 

I have used LV2016.

 

Hemant

0 Kudos
Message 3 of 11
(1,763 Views)

Hello GerdW

 

Steps that i have followed,

 

1. Connect Boolean constant to the first, top terminal of the merge error. It will show broken.

2.   Then same constant connect to the second, last terminal of the merge error.It will show broken.

3.  Then did undo, then Boolean constant got connected.

 

Hemant

0 Kudos
Message 4 of 11
(1,753 Views)

Hi Hemant,

 

why do you even do step 2 when step 1 indicates you can't connect booelans to MergeError???

Yes, I can create the same in LV2011 when following your 3 steps.

 

I agree, it's a problem when you can connect booleans after those 3 steps. But as soon as you try to run your VI (or force a recompile by editing) the VI will be broken again. So what is your problem?

Best regards,
GerdW

using LV2011SP1 + LV2017 (+LV2020 sometimes) on Win10+cRIO
0 Kudos
Message 5 of 11
(1,690 Views)

Hello GerdW,

 

Its not only those three step cause this connection of Boolean constant to the merge error, other steps also do this behavior.

 

Steps. 

1. Connect Boolean constant or any datatype to the merge error input.

2. Drop any Boolean function like AND, Error Merge function.

3. Then undo, then you will get the same behavior.

Its seems there is problem with these steps.

Correct as soon as run the VI it will broken again.

Its not problem for me i was just checking why merge function giving this behavior.

 

Hemant

 

 

0 Kudos
Message 6 of 11
(1,682 Views)

See below snap for merge error function with any datatype.

 

Hemant

0 Kudos
Message 7 of 11
(1,676 Views)

 

Try hitting Ctrl+Run Arrow to force recompile the VI.

Matt J | National Instruments | CLA
0 Kudos
Message 8 of 11
(1,619 Views)

@LV_COder wrote:

See below snap for merge error function with any datatype.

 

Hemant


Did you notice that the three data types you illustrate are all components of the Error Cluster?  I'm not sure when NI did this, but they did us all a Huge favor by allowing the Error Cluster, with its initial Boolean, to be wired to Boolean indicators (such as the Stop Indicator, allow you to have a While Loop "Stop on Error" without needing to unbundle the Error Line).  Possibly one side effect of this is the interesting observation that you've made, one that does not survive the compilation step, but gets flagged as an Error (which it is, of course ...).

 

So you've found an Odd Hidden "Feature" of no consequence.  Shrug, and Move On.

 

Bob Schor

0 Kudos
Message 9 of 11
(1,586 Views)

Correct, hidden feature with no consequence.

 

Hemant

0 Kudos
Message 10 of 11
(1,574 Views)