Difference between revisions of "Tagger trigger timing"
From GlueXWiki
m |
|||
Line 49: | Line 49: | ||
<td valign="top">230 + 50 ns? <br></td> | <td valign="top">230 + 50 ns? <br></td> | ||
<td valign="top">total delay<br></td> | <td valign="top">total delay<br></td> | ||
− | |||
</tr> | </tr> | ||
</table> | </table> | ||
<br> | <br> | ||
Note that the photon flight time from the radiator to the BCAL detector is about 100 ns, and that the RadPhi setup has 250 ns delay cables (straight, or 80+170 using a patch panel). | Note that the photon flight time from the radiator to the BCAL detector is about 100 ns, and that the RadPhi setup has 250 ns delay cables (straight, or 80+170 using a patch panel). |
Revision as of 16:44, 14 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 |
flight time tagger radiator to farthest T-counter |
20 ns |
in 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 MOR to forward carriage |
50? ns |
cable forward carriage to BCAL racks (not installed yet) |
230 + 50 ns? |
total delay |
Note that the photon flight time from the radiator to the BCAL detector is about 100 ns, and that the RadPhi setup has 250 ns delay cables (straight, or 80+170 using a patch panel).