Campuses:
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:25] – wgilbert | vetoshield:daq:vetodaqv5x_diag [2013/02/21 14:44] (current) – wgilbert | ||
|---|---|---|---|
| Line 5: | Line 5: | ||
| The event loop at top right responds to the Toggle Mux and Modify Config buttons whenever they are enabled. | 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 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 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: |
| {{VetoDAQ: | {{VetoDAQ: | ||
| - | |||