User Tools

Site Tools


s800_daq_tools

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision
Previous revision
Next revision Both sides next revision
s800_daq_tools [2017/04/08 13:29]
pereira [Delay Window]
s800_daq_tools [2017/06/16 18:59]
pereira [Running in Slave mode with multilogger]
Line 7: Line 7:
     * [[#Trigger GUI]]     * [[#Trigger GUI]]
     * [[#Scaler Display]]     * [[#Scaler Display]]
 +    * [[#Running in Slave mode with multilogger]]
   * [[#Troubleshooting]]   * [[#Troubleshooting]]
  
Line 65: Line 66:
  
  
-This window appears when the "Launch Gate Delay GUI" button is pressed on the [[#Readout GUI|Readout GUI]]. 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. +This window appears when the "Launch Gate Delay GUI" button is pressed on the [[#Readout GUI|Readout GUI]]. 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: Some important things to remember:
Line 83: Line 84:
 {{:wiki:800px-TriggerGUI.png?800|right|Trigger GUI}} {{:wiki:800px-TriggerGUI.png?800|right|Trigger GUI}}
  
-The Trigger GUI appears when the "Init" button is pressed on the CAMAC crate controller tab as part of the initial setup of the [[s800 daq tools#run control window|S800 USB daq]]. The Trigger GUI is a visual display of the various Gate and Delay Generators and logic elements that make up the configurable trigger of the S800. The logic of the trigger decision is readily discerned from a visual inspection of this GUI. Setting the trigger configuration is also done using this GUI by right clicking on any of the wires to put that signal onto one of the four "Trigger Inspect" channels available at the patch panel of Data-U6. By inspecting the various delays, widths and overlaps the user trigger can be configured. The Trigger GUI is discussed in greater detail [[Trigger|here]].+The Trigger GUI appears when the "Launch ULM GUI" button is pressed on [[#Readout GUI]]. The Trigger GUI is a visual display of the various Gate and Delay Generators and logic elements that make up the configurable trigger of the S800. The logic of the trigger decision is readily discerned from a visual inspection of this GUI. Setting the trigger configuration is also done using this GUI  
 + 
 +The different signal going through the trigger scheme can be inspected in th Data-U6 oscilloscope. Simply right click on any of the wires to put that signal onto one of the four "Trigger Inspect" channels available at the patch panel of Data-U6, and connect that patch-panel cable to the oscilloscope. By inspecting the various delays, widths and overlaps the user trigger can be configured. The Trigger GUI is discussed in greater detail [[Trigger|here]].
  
  
Line 95: Line 98:
  
 {{:wiki:Scalers.jpg?700|Scaler Display}} {{:wiki:Scalers.jpg?700|Scaler Display}}
 +
 +
 +==== Running in Slave mode with multilogger ====
 +The S800 DAQ can be run in Standalone mode (as described above), or in Slave mode. The later means that the S800 DAQ is controlled by an external DAQ (e.g. GRETINA). In this mode, the S800 ULM receives external clock and external synchronization  signals from the master DAQ. Running in Slave mode requires to change the script **CC0105Begin.tcl** in directory **/user/s800/converged_daq/Scripts**. In this file, there are two variables ''extsynch'' and ''extclock'' to define if the external synchronization and clock signals are enabled (=1) or disabled (=0). Make sure that you set these variables to 1 if you want to run in Slave mode.
 +
 +
 +By default, when running in Slave mode, data are recorded in the stagearea of the Master DAQ (experiment account). It is however possible to record simultaneously data from the S800 into the S800 stagearea, using the ''multilogger'' option (see ReadoutGUI figure above). The S800 ReadougGUI offers the possibility to record data from four different S800 ring-buffers: rawccusb, rawvmusb, s800built, and s800filter. The later is the most important since data from this ring buffer can be immediately processed by the S800 SpecTcl. 
 +
 +Before running an experiment with a Master system (e.g. GRETINA), it is recommendable to run the S800 DAQ in Slave mode with the s800filter multilogger enabled. This can be done following the steps:
 +
 +  * Click to the tab ''multilogger'' in the **ReadoutGUI**
 +  * Select the option "always record"
 +  * Click again on the tab ''multilogger'' and select "enable loggers". A window will pop out with a list of multiloggers {{:wiki:multilogger.png|Multilogger window}}
 +  * Enable multilogger "s800filter"
 +  * After this, S800 data from every run recorded by the experimenters, will also be recorded in the S800 stagearea.
 +
 +
 +
 +
  
  
s800_daq_tools.txt · Last modified: 2023/10/19 17:25 by swartzj