This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision | ||
s800_daq_tools [2020/03/05 12:23] pereira [No data sources defined] |
s800_daq_tools [2023/10/19 17:25] (current) swartzj [Running in Slave mode with multilogger] |
||
---|---|---|---|
Line 15: | Line 15: | ||
===== Running the S800 DAQ ===== | ===== Running the S800 DAQ ===== | ||
- | This page gives user-level instructions on how to run the S800 data acquisition (DAQ) system for an experiment. Presently this is run from the linux machine [[Software#u6pc5 (data U6)|u6pc5]] in data-U6. | + | This page gives user-level instructions on how to run the S800 data acquisition (DAQ) system for an experiment. Presently this is run from the linux machine [[Software#u4pc8 (data U4)|u4pc8]] in data-U4. |
==== Readout GUI ==== | ==== Readout GUI ==== | ||
- | 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 **/ | + | The S800 Readout GUI is invoked by either clicking the icon **S800 DAQ** in the desktop of [[Software#u4pc8 (data U6)|u4pc8]] or by navigating in a Linux terminal to the directory **/ |
- | Before beginning | + | Before beginning data taking, it is necessary to initialize the system. This is done by clicking '' |
- | After initializing the contollers, the ReadoutGUI window will show the '' | + | After initializing the controllers, the ReadoutGUI window will show the '' |
Before beginning a run, you have to make sure that the ULM trigger module is properly configured. This can be done by clicking the button [[#Trigger GUI|Launch ULM GUI]] in the ReadoutGUI window. | Before beginning a run, you have to make sure that the ULM trigger module is properly configured. This can be done by clicking the button [[#Trigger GUI|Launch ULM GUI]] in the ReadoutGUI window. | ||
Line 41: | Line 41: | ||
The S800 electronics includes a Mesytec CFD (MCFD), used to " | The S800 electronics includes a Mesytec CFD (MCFD), used to " | ||
- | The MCFD GUI can be started in three different ways: 1) by clicking the button '' | + | The MCFD GUI can be started in three different ways: 1) by clicking the button '' |
Line 47: | Line 47: | ||
- | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/user/operations/daq/usb/Config**, and click **Load** | + | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/user/s800/s800daq/Configurations**, and click **Load** |
* Alternatively, | * Alternatively, | ||
- | * By default, the CFD parameters can be adjusted individually for each of the 16 channels. It is also possible use the module in a " | + | * By default, the CFD parameters can be adjusted individually for each of the 16 channels. It is also possible |
* After modifying any of the CFD parameters, click **Commit to Device** | * After modifying any of the CFD parameters, click **Commit to Device** | ||
* Don't forget to save the new settings in file **MCF16.tcl**. | * Don't forget to save the new settings in file **MCF16.tcl**. | ||
- Go to '' | - Go to '' | ||
- | - Click '' | + | - Click '' |
- Select file **MCFD16tcl** and click '' | - Select file **MCFD16tcl** and click '' | ||
- A warning window will pop out to verify that you want to overwrite the existing file. Answer '' | - A warning window will pop out to verify that you want to overwrite the existing file. Answer '' | ||
Line 73: | Line 73: | ||
Some important things to remember: | Some important things to remember: | ||
- | * There are four "Delay Inspect" | + | * There are four "Delay Inspect" |
* These "Delay Inspect" | * These "Delay Inspect" | ||
- | * TDCs of last 4 listed signals (including XF and object scintillators) are bypassed with cable delays and thus their delays cannot be controlled with the GUI. They can be inspected, however using the GUI | + | * TDCs of last 4 listed signals (including XF (DB5) and object scintillators) are bypassed with cable delays and thus their delays cannot be controlled with the GUI. They can be inspected, however using the GUI |
* It is possible to bypass the delay of a given channel by checking the " | * It is possible to bypass the delay of a given channel by checking the " | ||
* The TDC delays can only be changed when the run control is stopped; must SAVE settings before starting run control not to overwrite adjustments being made | * The TDC delays can only be changed when the run control is stopped; must SAVE settings before starting run control not to overwrite adjustments being made | ||
Line 104: | Line 104: | ||
==== Running in Slave mode with multilogger ==== | ==== 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 | + | The S800 DAQ can be run in Standalone mode (as described above), or in Slave mode. The latter |
- | 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 '' | + | 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 '' |
When running XDT for an experiment with a Master DAQ (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: | When running XDT for an experiment with a Master DAQ (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: | ||
Line 132: | Line 132: | ||
* [[#CCUSB and/or VMUSB claimed by existing programs]] | * [[#CCUSB and/or VMUSB claimed by existing programs]] | ||
* [[#Manual rebooting]] | * [[#Manual rebooting]] | ||
+ | * [[#For hodoscope runs, cannot read signal from hodoscope]] | ||
Line 152: | Line 153: | ||
- Go to **/ | - Go to **/ | ||
- Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing to the new experiment directory **/ | - Copy the file **.settings.tcl** from that directory to the current stagearea. **NOTE**: we are assuming that the stagearea is pointing to the new experiment directory **/ | ||
- | - If you cannot find that file, there is an old version that can be copied from the directory **/ | + | - If you cannot find that file, there is an old version that can be copied from the directory **/ |
- You should now be able to run ReadoutGUI without problem | - You should now be able to run ReadoutGUI without problem | ||
==== CCUSB and/or VMUSB claimed by existing programs ==== | ==== CCUSB and/or VMUSB claimed by existing programs ==== | ||
Line 164: | Line 165: | ||
==== Manual rebooting ==== | ==== Manual rebooting ==== | ||
In the rare case that the RunControl GUI gets " | In the rare case that the RunControl GUI gets " | ||
+ | |||
+ | ==== For hodoscope runs, cannot read signal from hodoscope ==== | ||
+ | If you see this kind error message when starting the DAQ with the hodoscope in the trigger (Ext. 1 in ULM gui), check the voltages on the crate which holds the hodoscope shaper modules. If they are not at the correct values, follow this procedure: | ||
+ | - Turn crate off | ||
+ | - Unplug both shapers (for both hodoscopes). Just pull them but don’t fully remove the cards. | ||
+ | - With shapers unplugged, turn crate on and check voltages | ||
+ | - With crate on, firmly push one of the shapers in. | ||
+ | - Push second shaper in | ||
+ | - Verify crate voltages | ||
+ | This procedure works for the electronic configuration with CAEN shaper modules. | ||
+ | |||
+ | |||