Difference between revisions of "Tagger trigger timing"

From GlueXWiki
Jump to: navigation, search
m
m
Line 43: Line 43:
 
     </tr>
 
     </tr>
 
   <tr>
 
   <tr>
       <td valign="top">80 ns?<br></td>
+
       <td valign="top">66 ns<br></td>
       <td valign="top">cable to BCAL Trigger Supervisor (not installed yet)<br></td>
+
       <td valign="top">cable to BCAL Trigger Supervisor (just installed by Chris)<br></td>
 
     </tr>
 
     </tr>
 
   <tr>
 
   <tr>
Line 55: Line 55:
 
     </tr>
 
     </tr>
 
   <tr>
 
   <tr>
       <td valign="top">'''280 + 80 ns?'''<br></td>
+
       <td valign="top">'''280 + 66 ns'''<br></td>
 
       <td valign="top">'''total delay'''<br></td>
 
       <td valign="top">'''total delay'''<br></td>
 
     </tr>
 
     </tr>

Revision as of 11:54, 21 July 2006

Below is tagger trigger timing information I got from Eugene Pasyuk. Note that cables are trimmed so the sum of all delays is the same for all T-counters

Delay
Location
25 ns
electron flight time tagger radiator to farthest T-counter
20 ns
internal T-counter PMT
50 ns
cable to CFD
15 ns
internal CFD
5 ns
cable to L-R coincidence logic module
5 ns
internal L-R coincidence logic module
10 ns
cable to Master Or module
20 ns
internal MOR
80 ns
cable to forward carriage
66 ns
cable to BCAL Trigger Supervisor (just installed by Chris)
45 ns
internal Trigger Supervisor
5 ns
cable to ADC crate
280 + 66 ns
total delay


Note that the photon flight time from the radiator to the BCAL detector is 125 ns, and that the RadPhi setup has 250 ns delay cables (straight, or 80+170 using a patch panel).

If the trigger delay is 360 ns and given a flight time of 125 ns we are right on the edge. There are additional 170 ns delay cables in the RadPhi setup we can use if necessary (see Richard's note on RadPhi cables). We might consider cutting them in half, installing ends, and thus getting two 85 ns cables for each 170 ns cable.