02-10-2015 02:53 PM
When I connect a strict VI reference to a property node, I see "VI Interface Type #" on the node. Why? What does it mean? How many numbers are possible?
Example:
02-10-2015 03:04 PM - edited 02-10-2015 03:05 PM
It just appears because it's a strictly typed VI reference so the connector pane of the VI must match the VI. The interface type just refers to the arrangement (e.g. inputs/outputs) of the connector pane - different connector panes will have different interface types. I think the number of types depends on the number of different types of VI connector panes (on your block diagram? or strictly typed VI references?). A non-strict VI reference could have any connector pane arrangement.
I think you can change it from either the start asynchronous call or the strictly typed VI reference - it'll allow you to select different interface types.
02-11-2015 09:22 AM
Hey random question. Where did you get that ring type def constant that is wired to the open VI reference? That seems like a neat thing to have, and have be built as a constant to the options input.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
16 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord
02-18-2021 08:15 PM
The enum data represents the VI options for this method, x80 is one option we use
02-18-2021 08:50 PM
@Hooovahh wrote:
Hey random question. Where did you get that ring type def constant that is wired to the open VI reference? That seems like a neat thing to have, and have be built as a constant to the options input.
I’ve shared an XNode for that. I think it’s called something like “Named Numeric Constant”.
02-18-2021 08:55 PM
@paul_cardinale wrote:
@Hooovahh wrote:
Hey random question. Where did you get that ring type def constant that is wired to the open VI reference? That seems like a neat thing to have, and have be built as a constant to the options input.
I’ve shared an XNode for that. I think it’s called something like “Named Numeric Constant”.
Or maybe it was something like “Numeric Constant with Named Bits”.