Difference: TriggerCodes (1 vs. 3)

Revision 3
12 Dec 2009 - Main.JanMichel
Line: 1 to 1
Added:
>
>
META TOPICPARENT name="OutdatedPages"
  This text is stolen from Michael Böhmer:

http://www-hades.gsi.de/daq/rc99/richel_page.html
Revision 2
21 Jul 2006 - Main.MichaelTraxler
Line: 1 to 1
  This text is stolen from Michael Böhmer:

http://www-hades.gsi.de/daq/rc99/richel_page.html
Line: 38 to 38
 
--- --- --- --- --- 0x0 0x8 ILLEGAL error
--- --- --- --- --- 0x7 0xf ILLEGAL error
Changed:
<
<

Rules of engagement part I (or: HowTo LVL1 bus)

>
>

Rules of engagement part I (or: EtraxEPICSHowTo LVL1 bus)

  For the LVL1 bus, there are some rules on how to react on triggers coming into the DTU:

  1. Set your own busy as soon as a trigger on the LVL1 bus is entering your DTU.
Line: 52 to 52
 
  • BEGRUN trigger: store trigger tag for distribution with the next trigger, do no further action.
  • ENDRUN trigger: (optionally) try to get all data from the pipes on your frontends to the IPUs
Changed:
<
<

Rules of engagement part II (or: HowTo LVL2 bus)

>
>

Rules of engagement part II (or: EtraxEPICSHowTo LVL2 bus)

  In earlier revisions of the HADES trigger system all LVL1 trigger were reproduced 1:1 on the LVL2 bus, except that the decision bit was set according to the MU's decision. This is not longer the case. The LVL2 bus has been simplified and now only transports the readout triggers together with the decision. To take into account that some detector systems use the new SPECx triggers for calibrating, while others don't, the reaction on the readout triggers on the LVL2 bus is to be specified:
 
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Hades Wiki? Send feedback
Imprint (in German)
Privacy Policy (in German)