This shows you the differences between two versions of the page.
Both sides previous revision Previous revision Next revision | Previous revision Next revision Both sides next revision | ||
s800_daq_tools [2016/02/29 11:49] pereira [Mesytec CFD GUI] |
s800_daq_tools [2017/06/16 19:04] pereira [Running in Slave mode with multilogger] |
||
---|---|---|---|
Line 2: | Line 2: | ||
* [[#Running the S800 DAQ]] | * [[#Running the S800 DAQ]] | ||
- | * [[#Run Control Window]] | + | * [[#Readout GUI]] |
- | * [[# | + | |
* [[#Mesytec CFD GUI]] | * [[#Mesytec CFD GUI]] | ||
* [[#Delay Window]] | * [[#Delay Window]] | ||
* [[#Trigger GUI]] | * [[#Trigger GUI]] | ||
* [[#Scaler Display]] | * [[#Scaler Display]] | ||
- | * [[#Troubleshooting]] | + | * [[#Running in Slave mode with multilogger]] |
- | * [[#S800 DAQ status tool]] | + | * [[#Troubleshooting]] |
- | * [[#Readout GUI tab]] | + | |
- | * [[# | + | |
- | * [[#Controls tab]] | + | |
- | * [[#How to run combined S800 + GRETINA]] | + | |
Line 23: | Line 19: | ||
==== Readout GUI ==== | ==== Readout GUI ==== | ||
- | The S800 Readout GUI is invoked by either clicking the icon **S800 DAQ** in the desktop of [[Software# | + | The S800 Readout GUI is invoked by either clicking the icon **S800 DAQ** in the desktop of [[Software# |
- | **IMPORTANT NOTE:** When running Readout GUI, make sure that the environment variables needed by the system | + | Before beginning taking data is necessary to initialize |
- | Before beginning taking data is necessary to initialize the system. This is done by clicking '' | ||
- | The figure below shows the Readout GUI window after initializing the system. After clicking '' | + | After initializing the contollers, the ReadoutGUI window will show the '' |
+ | |||
+ | The figure below shows the Readout GUI window after initializing the system. After clicking '' | ||
Line 41: | Line 38: | ||
The S800 electronics includes a Mesytec CFD (MCFD), used to " | The S800 electronics includes a Mesytec CFD (MCFD), used to " | ||
- | The MCFD GUI is invoked | + | The MCFD GUI can be started in three different ways: 1) by clicking the button '' |
- | {{: | + | {{: |
* To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/ | * To load the default CFD configuration go to **Load Setting**, select file **MCFD16.tcl** in directory **/ | ||
- | * 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 " | + | |
* 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**. | ||
+ | - Go to '' | ||
+ | - Click '' | ||
+ | - Select file **MCFD16tcl** and click '' | ||
+ | - A warning window will pop out to verify that you want to overwrite the existing file. Answer '' | ||
+ | - Click again '' | ||
+ | - Click '' | ||
* 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 | * 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 | ||
Line 62: | Line 66: | ||
- | 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. | + | 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 80: | Line 84: | ||
{{: | {{: | ||
- | 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 | + | 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 | ||
Line 94: | Line 100: | ||
- | ==== Troubleshooting | + | ==== Running in Slave mode with multilogger |
- | In the rare case that the RunControl GUI gets " | + | 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 |
- | ===== S800 DAQ status tool ===== | + | |
- | In order to remotely monitor | + | |
- | 1. On spdaq48 do: | ||
- | **/ | + | 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 '' |
- | which will open the status GUI. | + | 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: |
- | There are tabs for connections | + | * Click to the tab '' |
+ | * Select the option " | ||
- | ==== Readout GUI tab ==== | + | * Click again on the tab '' |
- | The communications port to the Readout GUI is tcp:7999 and it runs by default | + | |
- | {{:wiki: | + | * Check out the ring-buffer '' |
+ | * After this, S800 data from every run recorded by the experimenters, | ||
- | ==== Eventbuilder tab ==== | ||
- | The communications port to the eventbuilder is tcp:8100 and it runs by default on spdaq48. These options can be changed in a manner identical to the Readout GUI tab. Information about the current statistics (input/ | ||
- | {{: | ||
- | This is the only information available to the tcp protocol, but the pid of the processes responsible for these connections can be investigated by using the following commands: | ||
- | 1. For each remote host, log in as each user which may be connected to the DAQ (ie e11007, s800). Unfortunately, | ||
- | 2. Do **lsof -i | grep port** (where port is replaced by the local port information obtained from the status gui. This will look similar to: | ||
- | < | ||
- | netcat.tc 2498 e11007 | ||
- | </ | ||
- | where the second column shows the PID of the connecting process. In this case the pid is 2498. | + | ===== Troubleshooting ===== |
+ | There are several common reasons why the S800 DAQ may fails to start. The list below describes what to do to fix these problems. | ||
+ | * [[#Old processes still running]] | ||
+ | * [[#No data sources defined]] | ||
+ | * [[#CCUSB and/or VMUSB claimed by existing programs]] | ||
+ | * [[#Manual rebooting]] | ||
- | 3. Do **ps -aux | grep PID**. This will look similar to: | ||
- | < | + | ==== Old processes still running ==== |
- | e11007 | + | Sometimes, particularly if the previous S800 DAQ session ended in an uncontrolled way, there may be old processes running (CCUSB and/or VMUSB and/or S800 event builder) that will prevent Readout GUI to begin a run. Whenever this happens (typically after clicking '' |
- | </ | + | - Exit your Readout GUI properly |
+ | - On a Linux session, connect to spdaq19 by typing '' | ||
+ | - Type '' | ||
+ | - Type '' | ||
+ | - You will see a list of ringbuffers with information about their status (see figure below). Check that the producer value of each ringbuffer (see column '' | ||
+ | - If the producer value of a ringbuffer is not -1, take note of the PID, and kill the process by typing '' | ||
+ | - You should now be able to run Readout GUI and begin a run without problem | ||
- | which gives the program name associated with the PID that is connecting to the eventbuilder. | ||
- | If the eventbuilder is hanging, which is evidenced by non-increasing statistics and no data/ | + | {{:wiki:ringbuffer1.png?650|Ringbuffer status}} |
- | + | ||
- | + | ||
- | ==== Controls tab ==== | + | |
- | This tab allows forced control of the Readout GUI, and is for advanced users only. In the event that the run must be stopped, or the DAQ software exited without access to the Readout GUI itself these buttons may be used to perform these actions. The run MUST be ended before using the Force Exit button, or it is likely that the USB crate controllers will become stuck in DAQ mode and the crates will have to be reset. | + | |
- | + | ||
- | {{:wiki:controls.png?500|Controls tab}} | + | |
- | + | ||
- | + | ||
- | + | ||
- | ===== How to run combined S800 + GRETINA ===== | + | |
- | + | ||
- | In order to run the combined S800 + Gretina daq, the following steps need to be taken: | + | |
- | + | ||
- | 1. On spdaq48 in / | + | |
- | + | ||
- | **wish ./ | + | |
- | + | ||
- | or, on devop2 (the S800 MAC machine) | + | |
- | + | ||
- | click on the operations folder on the lower icon bar and select runcontrol.command | + | |
- | + | ||
- | 2. On a dataU machine logged in as the experimental account (e11007 for the June 2012 testing period) do | + | |
- | + | ||
- | **godaq** | + | |
- | + | ||
- | 3. On spdaq44 do: | + | |
- | + | ||
- | **/ | + | |
- | + | ||
- | < | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | | + | |
- | </ | + | |
- | + | ||
- | Upon start of run there will be another client of the s800 ring, which is the pushToGEB process. This should die on end run. | + | |
+ | ==== No data sources defined ==== | ||
+ | When clicking '' | ||
+ | - 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 **/ | ||
+ | - 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 | ||
+ | ==== CCUSB and/or VMUSB claimed by existing programs ==== | ||
+ | One of the most common reasons why the S800 DAQ fails to start is because the CCUSB and/or VMUSB are claimed by existing programs. This is shown by the error messages displayed by the system. If you find yourself in this situation try the following: | ||
+ | - Log on to S800 spdaq (spdaq19 as of October 2015) | ||
+ | - Type '' | ||
+ | - Use '' | ||
+ | - Use '' | ||
+ | - Try '' | ||
+ | - If this didn't help try rebooting the S800 DAQ manually (see below) | ||
+ | ==== Manual rebooting ==== | ||
+ | In the rare case that the RunControl GUI gets " | ||
- | The S800 daq will now be in slave mode, and run control is done from the NSCL daq window. | ||