| Both sides previous revision
Previous revision
Next revision
|
Previous revision
Next revision
Both sides next revision
|
s800_daq_tools [2015/10/26 17:00]
pereira [Delay Window] |
s800_daq_tools [2016/02/29 11:25]
pereira [Run Control Window] |
| * [[#Run Control Window]] | * [[#Run Control Window]] |
| * [[#EventBuilder Window]] | * [[#EventBuilder Window]] |
| | * [[#Mesytec CFD GUI]] |
| * [[#Delay Window]] | * [[#Delay Window]] |
| * [[#Trigger GUI]] | * [[#Trigger GUI]] |
| |
| |
| ==== Run Control Window ==== | ==== Readout GUI ==== |
| The Run Control GUI is invoked by either clicking the icon **RunControl** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal to the directory **/user/s800/operations/daq/usb/TclXXUSB** and typing ''/usr/bin/wish RunControl.tcl''. The Run Control window and the EventBuilder window will appear. The image shows the typical configuration for stand-alone mode. | The S800 Readout GUI is invoked by either clicking the icon **S800 DAQ** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal to the directory **/user/s800/converged_daq** and typing ''godaq''. The Readout GUI window will appear. The image shows the typical configuration for stand-alone mode. |
| |
| Before beginning taking data is necessary to initialize the VME and CAMAC USB controllers. This is done by selecting the crate (either VM0079 for VME or CM0105 for CAMAC) and selecting the corresponding initialization file by clicking in the **Browsing** button. The initialization files are ''/user/s800/operations/daq/usb/Scripts/VM0079Init.tcl'' for VME and ''/user/s800/operations/daq/usb/Scripts/CM0105Init.tcl'' for CAMAC. Once the files are selected, the modules can be initialized by clicking in the button *Init*. After initializing the VME crate, the [[s800 daq tools#delay window|TDC delay window]] should pop out. Likewise, the [[s800 daq tools##Trigger GUI|Trigger GUI]] will appear after initializing the CAMAC crate. It is very important that both Save and Broadcast are checked. Failure to do so will result in settings files not being saved, data from the USB controllers not being broadcast to the eventbuilder, and the S800 evt files not being saved. | Before beginning taking data is necessary to initialize the VME and CAMAC USB controllers. This is done by selecting the crate (either VM0079 for VME or CM0105 for CAMAC) and selecting the corresponding initialization file by clicking in the **Browsing** button. The initialization files are ''/user/s800/operations/daq/usb/Scripts/VM0079Init.tcl'' for VME and ''/user/s800/operations/daq/usb/Scripts/CM0105Init.tcl'' for CAMAC. Once the files are selected, the modules can be initialized by clicking in the button *Init*. After initializing the VME crate, the [[s800 daq tools#delay window|TDC delay window]] should pop out. Likewise, the [[s800 daq tools##Trigger GUI|Trigger GUI]] will appear after initializing the CAMAC crate. It is very important that both Save and Broadcast are checked. Failure to do so will result in settings files not being saved, data from the USB controllers not being broadcast to the eventbuilder, and the S800 evt files not being saved. |
| |
| ==== Mesytec CFD GUI ==== | ==== Mesytec CFD GUI ==== |
| | The S800 electronics includes a Mesytec CFD (MCFD), used to "filter" the detector signals going to the Scaler and Mesytec TDC. The configuration parameters of the CFD (thresholds, delays, fraction, etc.) can be remotely adjusted via a MCFD GUI developed by the NSCL DAQ group. During tuning of the S800, one typically needs to adjust thresholds only. |
| |
| The Mesytec CFD (MCFD) GUI is invoked by either clicking the icon **MCFD GUI** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal and typing ''$DAQBIN/MCFDControl16 --protocol usb --serialfile /dev/ttyUSB0''. The environment variable DAQBIN is defined by sourcing the **daqsetup.bash** file in directory **/usr/opt/nscldaq/xxxx/bin**, where xxxx is the nscldaq version number (11.0-015 on Oct 26, 2015). | The MCFD GUI is invoked by either clicking the icon **MCFD GUI** in the desktop of [[Software#u6pc5 (data U6)|u6pc5]] or by navigating in a Linux terminal and typing ''$DAQBIN/MCFDControl16 --protocol usb --serialfile /dev/ttyUSB0''. The environment variable DAQBIN is defined by sourcing the **daqsetup.bash** file in directory **/usr/opt/nscldaq/xxxx/bin**, where xxxx is the nscldaq version number (11.0-015 on Oct 26, 2015). |
| |
| |
| {{:wiki:mcfd16gui.jpg|MCFD GUI}} | {{:wiki:mcfd16gui.jpg|MCFD GUI}} |
| |
| | |
| | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/user/operations/daq/usb/Config**, and click **Load** |
| | * Alternatively, it is possible to lead the configuration directly from the module by clicking **Update from Device** |
| | * By default, the CFD parameters can be adjusted individually for each of the 16 channels. It is also possible use the module in a "common" mode to set the same CFD parameters to all channels. Just check **common** |
| | * After modifying any of the CFD parameters, click **Commit to Device** |
| | * The MCFD module includes the possibility to send a periodic pulsing signal to all the channels. Two frequencies can be selected: 1.22 KHz, and 2.5 MHz |
| | |
| | |
| |
| ==== Delay Window ==== | ==== Delay Window ==== |
| {{:wiki:482px-Runcontrol.png|Run Control Window}} | {{:wiki:delay-window.png|Delay GUI}} |
| |
| |
