Differences
This shows you the differences between two versions of the page.
| Both sides previous revision
Previous revision
|
Next revision
Both sides next revision
|
s800_daq_tools [2015/10/20 10:11]
pereira [S800 Software tools] |
s800_daq_tools [2015/10/25 16:42]
pereira [Delay Window] |
| {{:wiki:Delay-Window.png|Delay Window}} | {{:wiki:Delay-Window.png|Delay Window}} |
| |
| This window appears when the "Init" button is pressed on the VME crate controller tab as part of the initial setup of the [[s800 daq tools#run control window|S800 USB daq]]. It can also be accessed by pressing the "Show GUIs" button. The delay module allows software configurable delays to be applied to each of the signals indicated in the Channel column, which then form the TDC stops. It is configurable to enable delays to be set with beam on target, as the needed delay may change depending on experimental conditions. There are four "Delay Inspect" channels which are routed to the patch panel in data-U6. These signals can be compared with any one of the four "Trigger Inspect" channels in order to set proper delays for the TDCs. | This window appears when the "Init" button is pressed on the VME crate controller tab as part of the initial setup of the [[s800 daq tools#run control window|S800 USB daq]]. It can also be accessed by pressing the "Show GUIs" button. The delay module allows software configurable delays to be applied to each of the signals indicated in the Channel column, which then form the TDC stops. It is configurable to enable delays to be set with beam on target, as the needed delay may change depending on experimental conditions. |
| |
| | Some important things to remember: |
| | |
| | * There are four "Delay Inspect" channels (routed to the patch panel in data U6) which can be selected using the Delay GUI |
| | * These "Delay Inspect" signals can be compared with any one of the four "Trigger Inspect" channels in order to set proper delays for the TDCs. The "Trigger Inspect" channels can be selected using the [[S800 DAQ tools#Trigger GUI|ULM trigger GUI]] |
| | |
| | |
| | * Information |
| | * The signal delays controlled by the GUI (and not by cable delays) are not “pipelined” -– i.e., any new signals that arrive during the delay time of a previous signal are lost and thus deadtime is introduced into the system. The signals delayed passively by cables are “pipelined” and thus are not subject to deadtime losses |
| | * All of the trigger signals are not pipelined and are thus subject to deadtime |
| |
| |
