Bug Report: Select function accepts combination of inputs with and without unit

[X.]

Start from this:

and the following diagram doesn't break:

If you create an indicator for the "Select" function output you'll get one with a unit.

Of course, if you remove the unit of either the input with unit or the output, you break the VI.

If you add the correct unit to the unitless input, the VI is still fine.

However, if you next remove the unit from that "Numeric Control" input (essentially returning to the initial state), you break the VI.

I'd say something is buggy.

And yes, I tried Ctrl-Run arrow in the state shown above: it doesn't break the VI.

Tested in LV 2103 SP1.

[natasftw]

ni.com/ask

After you login, there's a link to file bug reports.  I'd assume that's more official than forum posts.

[BTC_Admin]

---

@X. wrote:

Start from this:

and the following diagram doesn't break:

If you create an indicator for the "Select" function output you'll get one with a unit.

Of course, if you remove the unit of either the input with unit or the output, you break the VI.

If you add the correct unit to the unitless input, the VI is still fine.

However, if you next remove the unit from that "Numeric Control" input (essentially returning to the initial state), you break the VI.

I'd say something is buggy.

And yes, I tried Ctrl-Run arrow in the state shown above: it doesn't break the VI.

Tested in LV 2103 SP1.

---

Yep, it's repeatable in LV 2014 (32bit) too...  Here's more on it - if you swap the wires going into the "Select" function, the control which breaks it also swaps.  In other words, the error stays tied to the Select-function-input which was originally connected to the control with a unit.)

[X.]

The reason I am posting bug report here is so that:

1) they can be confirmed or discussed by others.

2) they can be found by others in the future.

3) they can be acknowledged by NI and tagged with a public CAR number (sometimes).