Re: going offline

Date view Thread view Subject view Author view Attachment view

From: Frank Geurts (geurts_at_rice.edu)
Date: Fri Feb 28 2003 - 13:27:50 EST


Jack -- as far as I can tell these *should* be the TCD connections for TOF:
* TOFp-L0 at TCD-Out 2
* TOFp-Pulser at TCD-Out 4
* TOF-System-Live at TCD Det Live (that's is easy because that one has a
proper label at the TCD).

This is how John documented it in
http://mac8.rice.edu/~TOF/TOFp/operations/manuals/TOF_logic_16Dec02.pdf
and I assume that Fred did not change any pin assignments as such when
our old TCD got replaced with the new one.

-frank

JMEngelage_at_lbl.gov wrote:
> guys ---
> i talked with fred. he wasn't sure of the connections either.
> however, he thought the busy cable that was reinstalled in the
> port labeled "daq live" was correct. the other two connections
> were a "TOF out" and a "TOF pulser". any info/pictures would
> be apreciated.
>
> -j.
>
>
> ----- Original Message -----
> From: Frank Geurts <geurts_at_rice.edu>
> Date: Friday, February 28, 2003 11:42 am
> Subject: Re: going offline
>
>
>> (i cc'd this message to Jack, Hank and Jeff too)
>>
>> I have asked Geary to join Jack as soon as he has arranged his
>>access.
>>As far as i can tell these are the most likely scenarios:
>>
>>1) wrong TCD connection: Hank mentioned that he had a little
>>problem
>>recognizing which of our connectors should go into which TCD
>>in/output.
>>We have our cables properly labeled but there are (no more) labels
>>on
>>these new TCDs ... could there be a mix-up?
>>
>>2) Jeff suspects a busy problem and frankly i think this might
>>well be
>>it: I recall that when testing the basic TCD connectivity (after
>>Hank
>>reconnected) I noticed that only one non-zero token made it
>>through the
>>system. The TCD stopped issueing tokens after that usually because
>>it
>>sees our system busy and waits for it to come alive again for the
>>next
>>token. Disconnecting the input to the NIM->TTL converter at 2-1-1-
>>1 made
>>the TCD fire the rest of the tokens again. Our busy is
>>constructed from
>>our LocalBusy, the LocalDAQBusy *and* the "L0 TCD Out2" pulse ...
>>so
>>either this is again related to item 1 (very likely) or this is a
>>hardware failure in the BUSY construct (we didn't change anything
>>to
>>that in the last access).
>>
>>
>>John: do you remember where the L0 TCD connection should be on the
>>TCD
>>(or does Fred Bieser know?)
>>
>>-frank
>>
>>
>>
>>
>>
>>W.J. Llope wrote:
>>
>>>hi guys,
>>> i have to go offline for the weekend in a few mins-
>>>i suspect this latest problem is not us but since frank is all
>>>over it if it is us i'm sure he will find the problem....
>>>if it is and we can't fix it remotely i wouldn't consider it
>>>a complete disaster if we missed a day or two until there was
>>
>>some kind of
>>
>>>access... the machine and star are not in good shape recently
>>>anyway.
>>>
>>>good luck frank - have fun at BB
>>>
>>>_________________________________________________________
>>>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
>>>
>>>
>>
>>
>


Date view Thread view Subject view Author view Attachment view

This archive was generated by hypermail 2.1.4 : Thu Jul 24 2003 - 00:39:36 EDT