Leaderboard

MangoTree technology can support any Xilinx FPGA by LabVIEW , greatly speeding up the development of FPGA and reduce the difficulty of the development of FPGA The technology has been monopolized by international giants for several years; At the same time, we are now providing two products are Pocket-RIO and Atom-RIO to prove that the content can be achieved. We have the ability to break the monopoly of technology, as well as the benefits of the technology to benefit more people. website：en.mangotree.cn

When you execute a Open VI reference node you ALWAYS receive a new and unique VI reference. This VI reference manages the data space, calling mechanism and also flags like how the VI can be invoked (asynchronous, clone, type of clone, etc, etc). As such it is indeed a completely independent instance of the VI from your original static VI reference. Basically the behavior you expect about VI references used to be true in a far ago past when LabVIEW did not support reentrancy, clones and asynchronous call, but it has changed dramatically under the hood with the introduction of these features. You usually don't feel much about those fundamental changes under the hood, but can run into it in such situations where the current behavior can sometimes surprise you. And there is something else to this. The datatype input to the Open VI Reference node is only there to define the type of the outgoing strict VI reference. The actual VI to instantiate is defined by the VI Path or VI Name input. The VI Open Reference function will then inspect the VI connector pane to match the datatype input and throw an error if they don't match. But nothing of the refnum instance passed to the datatype input is used, except the connector pane info. Not even the name or path as you would otherwise not have to provide that for a static VI reference.