We'll explain in general terms how the DAQ vi's work, but to get beyond that, one really has to open the source code in the development system and navigate through the diagrams with the context sensitive help window open. That way, one can identify terminals in the subvi connector icons just by mousing over them, without neccsarily opening them.

The rectangular sequence structure on the left contains things that have to happen first on execution. Variables and property nodes are initialized. Most of the front panel indicator and control terminals are here. Many have no connection here, it just makes them easy to find. The real inputs and outputs occur in local variables scattered through the diagram. The PCI-6534 DIO cards are enumerated, and the names assigned in MAX are read into and array in increasing numeric order. Two arrays are created that disable and gray out DAQ loop controls for which there is no card installed. The device names are inserted in the Clock Source and Physical Channel fields of the DAQ Cfg Prototype, generating the DAQ Cfg Array. One cluster element is indexed out sent to each DAQ loop to service a card. The Modify VetoDAQ Config vi pops up on execution