S800 Documentation

User Tools

Site Tools

Trace:
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 [2016/02/29 11:54]
pereira [S800 Software tools] 		s800_daq_tools [2016/02/29 13:27]
pereira [Troubleshooting]
Line 7: Line 7:
     * [[#Trigger GUI]]     * [[#Trigger GUI]]
     * [[#Scaler Display]]     * [[#Scaler Display]]
-    * [[#Troubleshooting]]+  * [[#Troubleshooting]]
   * [[#How to run combined S800 + GRETINA]]   * [[#How to run combined S800 + GRETINA]]
  
Line 87: Line 87:
  
  
-==== Troubleshooting ====+===== 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.    
 +  * [[#No data sources defined]] 
 +==== No data sources defined ==== 
 +When clicking ''Begin'' in the S800 Readout GUI, you get the error message: "No data sources are running so a run cannot be started". Very likely, the setting file **.settings.tcl** is missing. On a Linux session in u6pc5, type ''ls -lisa ~/stagearea''. You should see a hidden file **.settings.tcl**. If no, try the following: 
 +      - Go to **/mnt/daqtesting/s800/exxxxlast**, where **exxxxlast** corresponds to the experiment number of the last (successfully) run experiment 
 +      - 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 **/mnt/daqtesting/s800/exxxxnew** 
 +      - If you cannot find that file, there is an old version that can be copied from the directory **/user/s800/converged_daq** 
 +      - 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 ''ps aux | grep Readout'' 
 +      - Use ''kill -9 PID'', where PID identifies any CCUSBReadout or VMUSBReadout processes that show up 
 +      - Use ''kill -9 PID'', where PID identifies any tclsh ReadoutShell process that might show up 
 +      - Try ''godaq'' to see if this works now 
 +      - If this didn't help try rebooting the S800 DAQ manually (see below) 
 +==== Manual rebooting ====
 In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the S3 vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq. In the rare case that the RunControl GUI gets "frozen", it is possible to reboot the whole system manually. This operation requires to turn off the VME and CAMAC crates, and the spdaq computer, all them located in the rack seating near the FP box in the S3 vault. Then, the system must be turned back on in the following order. First, CAMAC crate, second VME crate, and third spdaq.
  
s800_daq_tools.txt · Last modified: 2023/10/19 17:25 by swartzj

Page Tools

Except where otherwise noted, content on this wiki is licensed under the following license: CC Attribution-Noncommercial-Share Alike 4.0 International
CC Attribution-Noncommercial-Share Alike 4.0 International Donate Powered by PHP Valid HTML5 Valid CSS Driven by DokuWiki