Coersion dot at boolean AND by using I16 and Hex controls. What is LabVIEW doing in the background?

[D-Kid]

Hello Community,

I am struggling to understand what LabVIEW is doing exactly in the background if you connect an integer 16 value and a Hex-Value to a boolean AND.

I just saw a conversion dot but I am not sure what LabVIEW is doing exactly.
Is it breaking down the problem by using boolean arrays which represents the bit structure of these numbers or is it doing something else?

In the attachment you will find a snippet for explaination reasons (LV17)

Thanks for your help

Regards

[Intaris · Accepted solution]

What are the datatypes of the two constants attached to the AND?

HEX is only a display option, it has nothing whatsoever to do with the actual datatype.

My guess is that the datatype of both constants do not match, hence a coercion (which doesn't show up in the snippet BTW).

[pincpanter]

Opened with LV17. I don't see any conversion dot, which is expected as both constants are I16 values.

[D-Kid]

Hi,

thank you very much for your quick answer.

You are right. It is just a display setting. I did not see it obviously.

The coercion dot gave me some confusion referring the bit-wise comparison of the input.