Difference between revisions of "Private:Trigger Types"
From GlueXWiki
| Line 14: | Line 14: | ||
: The trigger is sent from the SSP front pannel to the master TI. | : The trigger is sent from the SSP front pannel to the master TI. | ||
: Algorithm is being implemented into the CTP. | : Algorithm is being implemented into the CTP. | ||
| − | + | * Pulser | |
| + | : Initiated by 2 CAEN 1495 board (24 TTL outputs) | ||
| + | : LED pattern programmed through EPICS | ||
| + | : LVDS output is used as an external trigger for the master TI | ||
Revision as of 10:51, 2 August 2013
The main installation and trigger activities can be organized into the three main phases:
- Initial installation phase, where only a few crates with electronics are installed and connected to the sub-detector.
- Run stand alone DAC for each sub-detector. Start calibration of fadc pedestals, implementing calibration triggers and tuning trigger parameters
- Final Detector installation
- Detector Calibration with the Beam
BCAL
- Cosmics
- Generated by CTP in each crate. Possibility to generate the trigger for each BCAL module.
- ID of the 'fired' module is sent to the SSP along with the energy sum.
- The trigger is sent from the SSP front pannel to the master TI.
- Algorithm is being implemented into the CTP.
- Pulser
- Initiated by 2 CAEN 1495 board (24 TTL outputs)
- LED pattern programmed through EPICS
- LVDS output is used as an external trigger for the master TI
| Detector | Trigger Types | Descriptions | Start Date |
|---|---|---|---|
| BCAL | Cosmics | Generated by CTP in each crate (for each BCAL module)
Send to SSP and subsequently to master TI </br> |
unknown |
