Difference: AMC13UserManual (14 vs. 15)

Revision 1501 May 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: 79 to 79

The AMC13 has the ability to generate simulated TTC signals and distribute them to AMC cards in the crate. This allows operation of a stand-alone test setup with only an AMC13 and AMC cards in a single crate without

Changed:

<
< requiring any external TTC hardware. The simulated TTC signal will include a BC0 sent once per LHC orbit.

>
> requiring any external TTC hardware. The simulated TTC signal will always include a BC0 sent once per LHC orbit. Four "BGO" channels are provided which can send programmed short or long format TTC commands either once under program command or periodically.

In addition, ECR (event count reset) and OCR (orbit count reset) TTC commands may be sent by writing to the ACTION.LOCAL_TRIG.SEND_ECR and ACTION.LOCAL_TRIG.SEND_OCR registers, respectively.

Line: 87 to 89

the next L1A, as the current EvN and OrN in the AMC13 are not visible; they are used only to stamp an event in in response to L1A.

Added:

>
>

The "BGO" channels are programmed using registers 0x24-0x27 (CONF.TTC.BGOn). Each of the four channels requires the following settings, where BGOn is BGO0, BGO1, BGO2 or BGO3.

Register	Function
`CONF.TTC.BGOn.COMMAND`	Short (bits 0-7) or long (bits 0-31) format TTC command
`CONF.TTC.BGOn.LONG_CMD`	Bit '1' for long-format command, '0' for short format
`CONF.TTC.BGOn.ENABLE_PERIODIC`	Bit '1' to enable periodic (repeated) commands
`CONF.TTC.BGOn.ENABLE_SINGLE`	Bit '1' to enable single command (trigger with `ACTION.TTC.SINGLE_CMD`)
`CONF.TTC.BGOn.ORBIT_PRESCALE`	Orbit prescale (prescale is value + 1)
`CONF.TTC.BGOn.BX`	Bunch crossing number on which to send command

Locally-generated triggers may be sent in a rather flexible way. See the next section for details.

Changed:

<
< The simulated TTC signal is transmitted on the output side of the TTC

>
> The simulated TTC function requires a clock which is transmitted on the output side of the TTC

SFP optical transceiver and must be received on the input side, so a short loop-back cable must be plugged between the input and output sides of the bottom SFP.

This feature is enabled by setting CONF.DIAG.FAKE_TTC_ENABLE to 1. The local L1A generator must also be enabled (CONF.TTC.ENABLE_INTERNAL_L1A set to 1).

Changed:

<
< The TTC commands generated by the TTC simulator are as follows

>
>

TTC Command Details

The AMC13 can transmit and take action on several specific TTC commands.

Command	Default Value	Programmable?	Notes
BC0	1	No	Bunch Count Reset (sent every orbit)... CMS standard?
EC0	3	No[1]	Event Count Reset (send at the start of each lumisection to set the EvN to 1)
OC0	9	Yes	Orbit Count Reset - reset orbit count to 0
Resync	0x28	Yes	Resync after error

Note that for the programmable commands, there is both a command value register (8 bits) and a mask value register (8 bits) which allows only specific bits to be matched when decoding a received command.

Changed:

<
<

BC0	1	Bunch Count Reset (sent every orbit)	CMS standard?
EC0	3	Event Count Reset (send at the start of each lumisection to set the EvN to 1)	Bit 1 set = CMS standard?
OC0	9	Orbit Count Reset - reset orbit count to 0	HCAL-specific ?

>
> [1] This should be programmable

These are taken originally from this table maintained by HCAL:

View topic | History: r43 < r42 < r41 < r40 | More topic actions...