Difference: DaqProblems (1 vs. 10)

Revision 10
27 Nov 2018 - Main.PeterZumbruch
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 33 to 33
 
  1. Restart DAQ, if this does not help:
  2. Switch off/on tof0 crate,
  3. Sometimes a TIP board is completely hanging (see error message in error_watch)
Changed:
<
<
  1. In this case, reboot the corresponding crate by going to the SlowControl Window and hit the button named after the TOF crate mentioned in the message of the "error_watch"-window, turn off/on the crate and wait for the message "TOF-X init done" in the "error_watch" window.
>
>
  1. In this case, reboot the corresponding crate by going to the DetectorControlSystem Window and hit the button named after the TOF crate mentioned in the message of the "error_watch"-window, turn off/on the crate and wait for the message "TOF-X init done" in the "error_watch" window.
 

TRB problems

  1. no known at the moment
Revision 9
04 Apr 2007 - Main.HadesDaq
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 13 to 13
 

No busy on the trigger crate, but no events are written
Changed:
<
<
  1. Restart the EB by the "Apple"->"EB start". If this does not help
  2. Restart DAQ by "Apple"->"Fast DAQ start"
>
>
  1. Restart the EB by the "blue-arrow-down"->"EventBuilder Start". If this does not help
  2. Restart DAQ by "blue-arrow-down"->"Fast DAQ start"
 

Busy problems

Line: 33 to 33
 
  1. Restart DAQ, if this does not help:
  2. Switch off/on tof0 crate,
  3. Sometimes a TIP board is completely hanging (see error message in error_watch)
Changed:
<
<
  1. In this case, reboot the corresponding crate
>
>
  1. In this case, reboot the corresponding crate by going to the SlowControl Window and hit the button named after the TOF crate mentioned in the message of the "error_watch"-window, turn off/on the crate and wait for the message "TOF-X init done" in the "error_watch" window.
 

TRB problems

Changed:
<
<

  1. If TRB is busy even after daq reset then use: trb reset, if this not help
  2. Connect vi web browser to:
    - http://haepc05.gsi.de/ - when there is a problem with TRB1 (start), switch off and on,
    - http://haepc06.gsi.de/ - when there is a problem with TRB2 (veto), switch off and on.

Login on the board:
telnet de-etrax001 #if it is TRB1
telnet de-etrax002 #if it is TRB2
User: root ; password: pass.
cd /home/hadaq.
Then run trb init (it will take about 1 min) after this trb reset.
>
>
  1. no known at the moment
 

Unknown problem and all of the above didn't help

Revision 8
29 Mar 2007 - Main.IngoFroehlich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 26 to 26
 
  1. For TRB, see below
  2. After a power cycle of a VME crate, you have to wait for the "init done" message in the Error_Watch
Added:
>
>

TOF problems

  Red messages from the TOF crates like "counter mismatch"

  1. Restart DAQ, if this does not help:
  2. Switch off/on tof0 crate,
Added:
>
>
  1. Sometimes a TIP board is completely hanging (see error message in error_watch)
  2. In this case, reboot the corresponding crate
 

TRB problems

Revision 7
04 May 2006 - Main.MartinJurkovic
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 21 to 21
  One system shows permanent busies, No red messages

  1. Try to restart DAQ, if this does not help:
Changed:
<
<
  1. Find out which subsystem causes the problem (first check LVL2, then LVL1). Reboot the VME CPU(s)
>
>
  1. Find out which subsystem causes the problem (first check LVL2, then LVL1). Reboot (turn off/on the power of the crate) the VME CPU(s)
  of this system by using the slow control. Rich could be more complicated, ask a RICH expert.
  1. For TRB, see below
  2. After a power cycle of a VME crate, you have to wait for the "init done" message in the Error_Watch
Revision 6
03 May 2006 - Main.IngoFroehlich
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 6 to 6
 

  1. Are still events written to tape?
  2. Is one crate turned off? (use slow control window to check)
Changed:
<
<
  1. Is one system busy? (use "apple button"->"Open trigger windows"->"busy_monitor")
>
>
  1. Is one system busy? (use the "DAQ monitor" to find this out)
 
  1. Does the "error watch" show red messages?

Event builder problems

No busy on the trigger crate, but no events are written
Changed:
<
<
  1. Stop and start run, if this does not help:
  2. Stop run, restart DAQ, start run
>
>
  1. Restart the EB by the "Apple"->"EB start". If this does not help
  2. Restart DAQ by "Apple"->"Fast DAQ start"
 

Busy problems

One system shows permanent busies, No red messages
Changed:
<
<
  1. Try to restart DAQ
>
>
  1. Try to restart DAQ, if this does not help:
  2. Find out which subsystem causes the problem (first check LVL2, then LVL1). Reboot the VME CPU(s)
of this system by using the slow control. Rich could be more complicated, ask a RICH expert.
  1. For TRB, see below
  2. After a power cycle of a VME crate, you have to wait for the "init done" message in the Error_Watch
 

Red messages from the TOF crates like "counter mismatch"

  1. Restart DAQ, if this does not help:
Changed:
<
<
  1. Switch off/on tof0 crate, close hadaq, click on "apple"->"Start hades mini runctrl"->"start DAQ"
  2. Same, but keep crate off for some minutes
>
>
  1. Switch off/on tof0 crate,
 

TRB problems

Line: 49 to 52
 
  1. don't turn off the Front End Electronics Low Voltage if the High Voltage is still on! Only do this if the detector responsible allows you to do this!
  2. turn them on after a short while
  3. wait until for all subsystems the following message appeared in the error-watch: Sep 29 09:01:26 r2-29 bash[128]: init hardware shw done, or just wait ca. 5 minutes
Changed:
<
<
  1. restart the DAQ-mini-runctrl (close hadaq, click on "apple"->"Start hades mini runctrl"->"start DAQ")
  2. restart DAQ
>
>
  1. restart the DAQ
 
  1. Remark: RICH power-off/on is a little bit more dangerous, so first try just a "user_reboot" command on all three rich CPUs: R2F-28:rich2 R2F-27:rich1 R2F-24:rich0.

If all didn't help:

Revision 5
28 Apr 2006 - Main.MarekPalka
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 28 to 28
 
  1. Switch off/on tof0 crate, close hadaq, click on "apple"->"Start hades mini runctrl"->"start DAQ"
  2. Same, but keep crate off for some minutes
Added:
>
>

TRB problems

  1. If TRB is busy even after daq reset then use: trb reset, if this not help
  2. Connect vi web browser to:
    - http://haepc05.gsi.de/ - when there is a problem with TRB1 (start), switch off and on,
    - http://haepc06.gsi.de/ - when there is a problem with TRB2 (veto), switch off and on.

Login on the board:
telnet de-etrax001 #if it is TRB1
telnet de-etrax002 #if it is TRB2
User: root ; password: pass.
cd /home/hadaq.
Then run trb init (it will take about 1 min) after this trb reset.
 

Unknown problem and all of the above didn't help

Revision 4
11 Oct 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 31 to 31
 

Unknown problem and all of the above didn't help

Changed:
<
<
  1. turn off all DAQ crates on the slow control panel: MDC, TOF0-4, trigger, Preshw, MDC2
>
>
  1. turn off all DAQ (VME) crates on the slow control panel: MDC, TOF0-4, trigger, Preshw, MDC2
  2. don't turn off the Front End Electronics Low Voltage if the High Voltage is still on! Only do this if the detector responsible allows you to do this!
 
  1. turn them on after a short while
  2. wait until for all subsystems the following message appeared in the error-watch: Sep 29 09:01:26 r2-29 bash[128]: init hardware shw done, or just wait ca. 5 minutes
  3. restart the DAQ-mini-runctrl (close hadaq, click on "apple"->"Start hades mini runctrl"->"start DAQ")
Revision 3
29 Sep 2005 - Main.JehadMousa
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"

When you have DAQ problems, please follow this procedure

Line: 33 to 33
 

  1. turn off all DAQ crates on the slow control panel: MDC, TOF0-4, trigger, Preshw, MDC2
  2. turn them on after a short while
Changed:
<
<
  1. wait until for all subsystems the following message appeared in the error-watch:
     Sep 29 09:01:26 r2-29 bash[128]: init hardware shw done
     
    , or just wait ca. 5 minutes
>
>
  1. wait until for all subsystems the following message appeared in the error-watch: Sep 29 09:01:26 r2-29 bash[128]: init hardware shw done, or just wait ca. 5 minutes
 
  1. restart the DAQ-mini-runctrl (close hadaq, click on "apple"->"Start hades mini runctrl"->"start DAQ")
  2. restart DAQ
Changed:
<
<
  1. Remark: RICH power-off/on is a little bit more dangerous, so first try just a "user_reboot" command on all three rich CPUs:
     R2F-28:rich2  R2F-27:rich1 R2F-24:rich0 
    .
>
>
  1. Remark: RICH power-off/on is a little bit more dangerous, so first try just a "user_reboot" command on all three rich CPUs: R2F-28:rich2 R2F-27:rich1 R2F-24:rich0.
 

If all didn't help:

  1. Please call somebody who has some experience with the DAQ, for example: M.Traxler, I. Fröhlich, M. Jurkovic, J. Pietraszko and so on...
Revision 2
29 Sep 2005 - Main.MichaelTraxler
Line: 1 to 1
 
META TOPICPARENT name="HadesDaqDocumentation"
Changed:
<
<
When you have DAQ problems, please follow this procedure
>
>

When you have DAQ problems, please follow this procedure

 
Changed:
<
<
Checks:
>
>

Checks:

 

  1. Are still events written to tape?
Changed:
<
<
  1. Is one crate off (use slow control window)
  2. Is one system busy? (use "apple button"->"Open trigger windows"->"busy_monitor"
>
>
  1. Is one crate turned off? (use slow control window to check)
  2. Is one system busy? (use "apple button"->"Open trigger windows"->"busy_monitor")
 
  1. Does the "error watch" show red messages?
Changed:
<
<

Event builder problems

>
>

Event builder problems

 

No busy on the trigger crate, but no events are written

  1. Stop and start run, if this does not help:
  2. Stop run, restart DAQ, start run
Changed:
<
<

Busy problems

>
>

Busy problems

 

One system shows permanent busies, No red messages
Line: 29 to 29
 
  1. Same, but keep crate off for some minutes
Added:
>
>

Unknown problem and all of the above didn't help

  1. turn off all DAQ crates on the slow control panel: MDC, TOF0-4, trigger, Preshw, MDC2
  2. turn them on after a short while
  3. wait until for all subsystems the following message appeared in the error-watch:
     Sep 29 09:01:26 r2-29 bash[128]: init hardware shw done
     
    , or just wait ca. 5 minutes
  4. restart the DAQ-mini-runctrl (close hadaq, click on "apple"->"Start hades mini runctrl"->"start DAQ")
  5. restart DAQ
  6. Remark: RICH power-off/on is a little bit more dangerous, so first try just a "user_reboot" command on all three rich CPUs:
     R2F-28:rich2  R2F-27:rich1 R2F-24:rich0 
    .

If all didn't help:

  1. Please call somebody who has some experience with the DAQ, for example: M.Traxler, I. Fröhlich, M. Jurkovic, J. Pietraszko and so on...
 

 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)