Differences

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

--- s800_daq_tools [2017/07/17 17:46]
pereira [Old processes still running]
+++ s800_daq_tools [2020/03/04 17:54]
pereira [Trigger GUI]
@@ Line 82: / Line 82: @@
 ==== Trigger GUI ====
-{{:wiki:800px-TriggerGUI.png?800|right|Trigger GUI}}
+{{:wiki:ULM_updated.png?800|right|Trigger GUI}}
 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 trigger GUI allows the user to select the source of the S800 clock and clock-reset signals (internal, from the ULM module), or external from (e.g.) GRETINA. If you are using external clock and reset signals, make sure to check the boxes labeled ""
 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 125: / Line 129: @@
 ===== Troubleshooting =====
 There are several common reasons why the S800 DAQ may fail. The list below describes what to do to fix some of these problems.
-  * [[#Old processes still running|Error message: "Socket ID already in use"]]
+  * [[#Old processes still running|Error message "Socket ID already in use"]]
-  * [[#No data sources defined]]
+  * [[#No data sources defined|Error message "No data sources are running so a run cannot be started"]]
   * [[#CCUSB and/or VMUSB claimed by existing programs]]
   * [[#Manual rebooting]]
@@ Line 136: / Line 140: @@
       - Exit your Readout GUI
       - On a Linux session, connect to the S800 spdaq by typing ''ssh -Y s800@spdaqXX'' (Contact the Device Physicist to get the spdaq number XX and S800 password)
-      - Type ''ps aux | grep Readout'' to ensure that Readout is indeed not running
+      - Type ''ps aux | grep Readout'' to ensure that Readout is indeed not running. If "Readout" is still running, use ''kill -9 PID'', where PID identifies the Readout process ID
       - Type ''/usr/opt/nscldaq/xxxx/bin/ringbuffer status'', where xxxx is the daq version, e.g. 11.0-020
       - 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 ''producer'') is **-1**. (Don't worry about the ringbuffer **s800filter**, which is automatically killed when starting ReadoutGUI)
@@ Line 153: / Line 157: @@
 ==== 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)
+      - Log on to S800 spdaq (spdaqXX as of October 2015)
       - Type ''ps aux | grep Readout''
       - Use ''kill -9 PID'', where PID identifies any CCUSBReadout or VMUSBReadout processes that show up

S800 Documentation

User Tools

Site Tools

Differences

Page Tools