vetoshield:daq:vetodaqv5x_diag
Differences
This shows you the differences between two versions of the page.
| Both sides previous revisionPrevious revisionNext revision | Previous revision |
| vetoshield:daq:vetodaqv5x_diag [2013/02/20 17:22] – wgilbert | vetoshield:daq:vetodaqv5x_diag [2013/02/21 14:44] (current) – wgilbert |
|---|
| ===Version 5x Diagrams=== | ===main VetoDAQv5x Diagram=== |
| |
| 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 and closes again when terminated. |
| |
| ==VetoDAQv55 main (top level) vi== | The event loop at top right responds to the Toggle Mux and Modify Config buttons whenever they are enabled. |
| | |
| | The sequence frame below the event loop shows the middle(#1) of three sequence steps. Frame #0 merely configures the Symmetricom card on startup, and frame #2 triggers a strobe pulse on to shut down the muxes when the main vi is terminated. In the middle frame, three identical copies of **[[Vetoshield:daq:VetoDAQReadData diag|VetoDAQReadData.vi]]** are called in while loops, checking to see if their respective DAQ Start buttons have been clicked. Values for the front panel controls and indicators are passed in and out of the vis while they are running using control references. These vis and their subvis are reentrant, meaning that each copy maintains separate memory space for it's variables and data, allowing them to run simultaneously without blocking each other. If an individual DAQ loop is stopped using the DAQ Stop button, it will return to polling for DAQ Start. Clicking the red Exit button will pop up a dialog, whicj if confirmed, will shut down all the loops and terminate the main vi. |
| |
| 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 | |
| | |
| {{VetoDAQ:vetodaq_v54d.png?1280}} | {{VetoDAQ:vetodaq_v54d.png?1280}} |
vetoshield/daq/vetodaqv5x_diag.1361402529.txt.gz · Last modified: 2013/02/20 17:22 by wgilbert