Difference between revisions of "Overall trigger timing"

From GlueXWiki
Jump to: navigation, search
Line 22: Line 22:
 
       <td>Photon hits BCAL<br></td>
 
       <td>Photon hits BCAL<br></td>
 
       <td>125 ns to alcove, but BCAL is about 10 feet upstream on the platform<br></td>
 
       <td>125 ns to alcove, but BCAL is about 10 feet upstream on the platform<br></td>
 +
    </tr>
 +
 +
    <tr>
 +
      <td>230 ns<br></td>
 +
      <td>Tagger MOR reaches BCAL crates<br></td>
 +
      <td>150 ns + 80 ns new fast cable, see [[Tagger trigger timing]]<br></td>
 
     </tr>
 
     </tr>
  
Line 32: Line 38:
 
     <tr>  
 
     <tr>  
 
       <td>265 ns<br></td>
 
       <td>265 ns<br></td>
       <td>Discriminator sum outputs available<br></td>
+
       <td>Discriminator sum outputs arrive at trigger logic<br></td>
       <td>30 ns a guess, but must be delayed before final AND in any case<br></td>
+
       <td>30 ns is a guess<br></td>
 
     </tr>
 
     </tr>
  
 
     <tr>  
 
     <tr>  
       <td>230 ns<br></td>
+
       <td>265 ns<br></td>
       <td>Tagger MOR reaches BCAL crates<br></td>
+
       <td>MOR arrives at trigger logic<br></td>
       <td>150 ns + 80 ns new fast cable, see [[Tagger trigger timing]]<br></td>
+
       <td>Delayed to match discriminator sum outputs<br></td>
    </tr>
+
  </tr>
  
  <tr>  
+
    <tr>  
       <td>230 ns<br></td>
+
       <td>295 ns<br></td>
      <td>Discriminator sums available<br></td>
+
      <td>Delayed to match MOR<br></td>
+
    </tr>
+
 
+
    <tr>
+
      <td>260 ns<br></td>
+
 
       <td>Trigger reaches trigger supervisor<br></td>
 
       <td>Trigger reaches trigger supervisor<br></td>
       <td>Guess 30 ns coincidence logic<br></td>
+
       <td>Guess 30 ns coincidence logic plus cable<br></td>
 
     </tr>
 
     </tr>
  
 
     <tr>  
 
     <tr>  
       <td>305 ns<br></td>
+
       <td>340 ns<br></td>
 
       <td>L1 accept available at TS<br></td>
 
       <td>L1 accept available at TS<br></td>
 
       <td>45 ns internal trigger supervisor<br></td>
 
       <td>45 ns internal trigger supervisor<br></td>
Line 61: Line 61:
  
 
     <tr>  
 
     <tr>  
       <td>355 ns<br></td>
+
       <td>390 ns<br></td>
 
       <td>ADC gate active</td>
 
       <td>ADC gate active</td>
 
       <td>50 ns ADC gate generation, cables to ADC crate, ADC internalbr></td>
 
       <td>50 ns ADC gate generation, cables to ADC crate, ADC internalbr></td>
 
     </tr>
 
     </tr>
  
 
+
    <tr>  
  <tr>  
+
 
       <td>435 ns<br></td>
 
       <td>435 ns<br></td>
 
       <td>BCAL signals reach ADC crate<br></td>
 
       <td>BCAL signals reach ADC crate<br></td>
Line 82: Line 81:
 
==Comments==
 
==Comments==
  
(comment below referred to earlier scheme, now superceded...ejw)<br>
+
(Zisis' comment referred to am earlier scheme, now superceded...ejw)<br>
 
I agree that this will not work.  I also agree on the plan of action, in the following priority: 1) Try to shorten MOR, 2) Cut unused 170ns cable (if there are enough and if this is ok with folks like Richard) and 3) Purchase new cables.  -- Zisis
 
I agree that this will not work.  I also agree on the plan of action, in the following priority: 1) Try to shorten MOR, 2) Cut unused 170ns cable (if there are enough and if this is ok with folks like Richard) and 3) Purchase new cables.  -- Zisis
  
21-Jul...preliminary measurement of the RadPhi cables gives 100 and 300 ns, not 80 and 250 ns.  If correct we gain an additional 50 ns delay.  If we run a new MOR cable (save 66 ns) we gain a total of over 100 ns.  This should be adequate to cover items missing above (patch cables, additional logic delays not accounted for yet, etc).  I propose we still plan to run a new MOR cable even if the signal cables are 50 ns longer.  -- Elliott
+
(my comment also referred to the older scheme, now superceded...ejw)<br>
 +
21-Jul...preliminary measurement of the RadPhi cables gives 100 and 300 ns, not 80 and 250 ns.  If correct we gain an additional 50 ns delay.  If we run a new MOR cable (save 150 ns) we gain a total of over 100 ns.  This should be adequate to cover items missing above (patch cables, additional logic delays not accounted for yet, etc).  I propose we still plan to run a new MOR cable even if the signal cables are 50 ns longer.  -- Elliott
  
 
21-Jul...everything updated based on latest understanding -- Elliott
 
21-Jul...everything updated based on latest understanding -- Elliott

Revision as of 15:51, 21 July 2006

Timing Scheme

From Elliott: Below is my current understanding of the trigger timing for the BCAL test:


Time
What
Comment
0 ns
Electron hits tagger foil

115 ns
Photon hits BCAL
125 ns to alcove, but BCAL is about 10 feet upstream on the platform
230 ns
Tagger MOR reaches BCAL crates
150 ns + 80 ns new fast cable, see Tagger trigger timing
235 ns
BCAL PMT signals reach discriminators
20 ns in PMT plus 100 ns cable
265 ns
Discriminator sum outputs arrive at trigger logic
30 ns is a guess
265 ns
MOR arrives at trigger logic
Delayed to match discriminator sum outputs
295 ns
Trigger reaches trigger supervisor
Guess 30 ns coincidence logic plus cable
340 ns
L1 accept available at TS
45 ns internal trigger supervisor
390 ns
ADC gate active 50 ns ADC gate generation, cables to ADC crate, ADC internalbr>
435 ns
BCAL signals reach ADC crate
20 ns in PMT plus 300 ns cable plus photon flight time



The above timing works if we can get less than xxx ns (80 ns is target) between the MOR and the BCAL crates. If not we will have to add delay to the ADC signals. If so there are a few possibilities, including purchase of cables, cutting some of the unused 170 ns in half and installing new ends to give 85 ns delay cables, etc.


Comments

(Zisis' comment referred to am earlier scheme, now superceded...ejw)
I agree that this will not work. I also agree on the plan of action, in the following priority: 1) Try to shorten MOR, 2) Cut unused 170ns cable (if there are enough and if this is ok with folks like Richard) and 3) Purchase new cables. -- Zisis

(my comment also referred to the older scheme, now superceded...ejw)
21-Jul...preliminary measurement of the RadPhi cables gives 100 and 300 ns, not 80 and 250 ns. If correct we gain an additional 50 ns delay. If we run a new MOR cable (save 150 ns) we gain a total of over 100 ns. This should be adequate to cover items missing above (patch cables, additional logic delays not accounted for yet, etc). I propose we still plan to run a new MOR cable even if the signal cables are 50 ns longer. -- Elliott

21-Jul...everything updated based on latest understanding -- Elliott