Difference: AMC13UserManual (42 vs. 43)

Revision 4310 Jul 2018 - 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: 47 to 47
  The AMC13 outputs the TTS state as the four-bit code described in the links above:
Changed:
<
<
  0000 Disconnected Hardware Failure or broken cable
  0001 Overflow Warning Imminent buffer overflow
  0110 DAQ Overflow Warning Overflow warning due to DAQ link backpressure (2018)
  0010 Sync Lost AMC13 is not synchronized with DAQ due to buffer overflow
  0100 Busy Cannot accept triggers
  1000 Ready Ready to accept triggers
  1001 Private Request 1 Available for private use (2018)
  1010 Private Request 2 Available for private use (2018)
  1011 Private Request 3 Available for private use (2018)
  1100 Error Any other state that prevents functioning
  1111 Disconnected Hardware failure or broken cable
>
>
0 0000 Disconnected Hardware Failure or broken cable
1 0001 Overflow Warning Imminent buffer overflow
6 0110 DAQ Overflow Warning Overflow warning due to DAQ link backpressure (2018)
2 0010 Sync Lost AMC13 is not synchronized with DAQ due to buffer overflow
4 0100 Busy Cannot accept triggers
8 1000 Ready Ready to accept triggers
9 1001 Private Request 1 Available for private use (2018)
a 1010 Private Request 2 Available for private use (2018)
b 1011 Private Request 3 Available for private use (2018)
c 1100 Error Any other state that prevents functioning
f 1111 Disconnected Hardware failure or broken cable
 The states "Private Request 1..3" have the same priority as "Ready". They are never internally generated by the AMC13 but are passed on if received from connected AMC cards in the crate.
Line: 88 to 89
  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.
>
>
When the TTS state changes, a control word is sent across the link to transfer the information with minimum latency to the AMC13. A TTS state must persist for at least two BX to be guaranteed to be transmitted. Latency is "minimum" but not guaranteed to be any specific value.
  Here are some more details on how the TTS state is generated in the AMC13:
Line: 474 to 481
 

Resetting the PLL

The PLL which recovers the clock on the TTC input may lose lock if e.g. the TTC clock is interrupted for some reason. This PLL may be reset using the following command in '''AMC13Tool2''':

Changed:
<
<
  > wv 0x0 0x8 

>
>
  > wv 0x0 0x8 

 
Changed:
<
<
Currently there is no address table entry nor dedicated command to accomplish this. Also, I am fairly certain that this reset is performed only at power-up and not as part of any software initialization sequence in the AMC13 or HCAL software!
>
>
Currently there is no address table entry nor dedicated command to accomplish this. This reset is performed only at power-up and not as part of any software initialization sequence in the AMC13 or HCAL software! It can require up to 100us for the PLL to lock.
  -- Eric Hazen - 21 Jun 2018
Line: 630 to 635
 

Monitoring Registers

This section provides documentation on a few of the monitoring registers which have proven to be confusing. Eventually there should be detailed description for all registers, but who knows when this will get done!

Changed:
<
<
AMC_EvN_Mismatch (offset 0x6/0x7)

>
>
AMC_EvN_Mismatch (offset 0x6/0x7)

  This checks that the EvN in bits 32-55 of the first word sent by the AMC Matches the current EvN in the AMC13 (reset to 1 on EcR, increment each L1A) This check is performed in our link firmware in the AMC card.
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright © 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback