08-25-2017 02:52 AM
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
08-25-2017 03:20 AM
08-25-2017 03:21 AM
Hello GerdW,
I have used LV2016.
Hemant
08-25-2017 03:27 AM - edited 08-25-2017 03:30 AM
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
08-25-2017 04:38 AM - edited 08-25-2017 04:40 AM
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?
08-25-2017 04:52 AM - edited 08-25-2017 04:57 AM
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
08-25-2017 05:00 AM
See below snap for merge error function with any datatype.
Hemant
08-25-2017 09:33 AM - edited 08-25-2017 09:34 AM
Try hitting Ctrl+Run Arrow to force recompile the VI.
08-25-2017 10:50 AM
@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
08-25-2017 11:07 AM
Correct, hidden feature with no consequence.
Hemant