Difference: AMC13UserManual (22 vs. 23)

Revision 2308 Sep 2015 - EricHazen

Line: 1 to 1
 
META TOPICPARENT name="HcalDTC"
THIS MANUAL IS INCOMPLETE but what is written here should be more accurate and up to date than the old "functional specification". Please e-mail me if you find mistakes/omissions here (Eric H).
Line: 73 to 73
  TTS : in std_logic_vector (3 downto 0);
Changed:
<
<
When the TTS state changes, a control word is sent across the link to transfer the information with minimum latency to the AMC13. The final TTS output state is simply a priority encoding of the 12 AMC states plus the local AM13 one.
>
>
When the TTS state changes, a control word is sent across the link to transfer the information with minimum latency to the AMC13.

Here are some more details on how the TTS state is generated in the AMC13:

The AMC13 contains an L1A FIFO into which L1A are stored when received by the TTC or generated by the internal L1A generator. The event builders (up to 3) read L1A from the FIFO and wait for available event fragments from each enabled AMC input. Then the event is built and sent out the corresponding DAQ link and/or stored in the SDRAM monitor buffer. The AMC13 internal TTS state is generated exclusively based on the number of L1A stored in the L1A FIFO.

Additionally, up to 12 TTS states are received as described above from AMC cards. The final TTS output state is simply a priority encoding of the 12 AMC states plus the local AM13 one.

 

TTC Simulator

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2021 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback