User Tools

Site Tools


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
s800_daq_tools [2017/07/17 17:55]
pereira [Troubleshooting]
s800_daq_tools [2017/12/16 12:26] (current)
pereira [CCUSB and/or VMUSB claimed by existing programs]
Line 136: Line 136:
       - Exit your Readout GUI        - 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)       - 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       - 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)       - 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 153:
 ==== CCUSB and/or VMUSB claimed by existing programs ==== ==== 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: 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''​       - 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 CCUSBReadout or VMUSBReadout processes that show up
s800_daq_tools.1500328535.txt.gz ยท Last modified: 2017/07/17 17:55 by pereira