From: Bill Christie (christie_at_bnl.gov)
Date: Tue Mar 18 2003 - 10:53:10 EST
Bill, Geary, and Frank,
It appears that whatever the problem is with the TOF busy, it is
still with us. Dan experienced trouble with a pedestal run overnight
(see shift log) where it appears that the TOF was the cause. Tonko
checked this morning, by running a pedestal run with the TPC and the
TOF, and observed that the TOF busy got stuck on after about 5 kevts.
Any other ideas on what can be tried? I'm hoping to find out within
the next hour whether of not there will be some access to the WAH
tomorrow (Wednesday). I'll send an E-mail to STAROPS as soon as I find
out one way or the other.
Greetings from Long Island,
Bill
Frank Geurts wrote:
>
> Fred, I think the busy is only part of the problem in fact it's the
> part that is seen by STAR DAQ... what we see on TOF DAQ's side is that
> the TCD words "trigger" our DAQ constantly at some point (the Bira
> fires LAMs all over the place). I agree that a loose connection of the
> rear connector may well be the reason why we see it happen after some
> random number of events ...
>
> Eleanor, is there a chance for a quick access during which the TCD
> connections can be checked?
>
>
> thanks,
> Frank
>
>
>
>
> fred bieser wrote:
>
>> Te TOF's TCD has NO internal logic to generate busy except as brought in
>> thru the front-panel LEMO labelled "DAQ Live." All the recent activity
>> in that area might have left some cable loose or dropped or ???? either
>> at the front or, more likely, in the rear.
>>
>> fred
>>
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:38 EDT