From: W.J. Llope (llope_at_physics.rice.edu)
Date: Sun Mar 16 2003 - 10:10:03 EST
i saw that message, but still i cannot believe that is
the actual problem.
we run for ~5k events just fine, then we hang daq.
how does this cable know to disconnect itself
in the middle of a run?
On Sat, 15 Mar 2003, Geary Eppley wrote:
> hi,
>
> we heard from freddy yesterday. presumabkly we are waiting for an access
> for eleanor to go check the connections.
>
> g
>
> ---------- Forwarded message ----------
> Date: Fri, 14 Mar 2003 16:53:56 -0600
> From: Frank Geurts <geurts_at_rice.edu>
> To: fred bieser <bieser_at_lbl.gov>, Eleanor G Judd <EGJudd_at_lbl.gov>
> Cc: tofp_at_physics.rice.edu, Tonko A. Ljubicic <tonko_at_bnl.gov>,
> Bill Christie <christie_at_bnl.gov>
> Subject: So we need an access? Re: [Fwd: Changes to TOF TCD? ]
>
>
> 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
> >
>
>
>
--
_________________________________________________________
W.J. Llope, Ph.D. Res. Assoc. Professor
http://wjllope.rice.edu/default.html
llope_at_physics.rice.edu
T.W. Bonner Nuclear Lab.
Rice University, MS-315
6100 S. Main phone: 713-348-4741
Houston, TX 77005-1892 fax: 713-348-5215
This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:37 EDT