MDT – PC Monitoring and Control

Amsterdam MDT Workshop

Adriaan Konig`s list of issues to be looked into at Amsterdam MDT Workshop:

1) Monitoring (checking):

a)Which parameters are being monitored in the sub-system (e.g. Vcc, I, T, ...)?

b)How many sensors of each type will be installed (specify analog or digital)?

c)How often must the sensors be read out (e.g. continuously, each run, daily etc.)?

d)Which parameters should be monitored during data taking?

e)Is there any on-sub-system multiplexing?

f)To what (sub-)system is the monitoring directly connected to (e.g. Mezz. connected to CSM)?

2) Control (initialization/steering):

a)What is the default power-up status of the sub-system?

b)Which (digital) parameters need be loaded after power-up?

c)Which sub-system or device will initiate the transfer of this information (e.g. the sub-system itself, the MDT Local-DAQ, ...)?

d)How often need these bits be loaded (e.g. "every start of run")?

e)What is the approx. # bits?

f)What is the supposed source of these bit-strings?

g)Are the bit-strings always identical or can there be dynamic modifications (e.g. between runs) and if so, who (which device) is supposed to make such modifications?

h)Which is the route foreseen for the bits to get from the source to the sub-system (details!)?

3) General:

a)What voltage(s) (Vcc) is/are required by the sub-system?

b)Where does the Vcc supposedly come from?

c)How is the trigger/timing distribution done?

On-chamber electronics: Mezzanine (JTAG-Controller, ASD, AMT) – CSM

1) a) Which parameters are being monitored in the sub-system (e.g. Vcc, I, T, ...)?

Analog and digital Vdd, Temperature on the Mezzanine.

1) b) How many sensors of each type will be installed (specify analog or digital)?

One temperature sensor on the Mezzanine (analog).

1) c) How often must the sensors be read out (e.g. continuously, each run, daily etc.)?

More or less continously.

1) d) Which parameters should be monitored during data taking?

All 1) a).

1) e) Is there any on-sub-system multiplexing?

What?!!?

1) f) To what (sub-)system is the monitoring directly connected to (e.g. Mezz. connected to CSM)?

Exactly.

2) a) What is the default power-up status of the sub-system?

Defined! Set of default parameters loaded into ASD/AMT

2) b) Which (digital) parameters need be loaded after power-up?

None immediately. Change ASD/AMT settings as desired.

2) c) Which sub-system or device will initiate the transfer of this information (e.g. the sub-system itself, the MDT Local-DAQ, ...)?

CSM will send control bit-streams or RESET requests to ASD/AMT as desired.

2) d) How often need these bits be loaded (e.g. "every start of run")?

??

2) e) What is the approx. # bits?

ASD: 53, AMT: xxx, JTAG controller: xx.

2) f) What is the supposed source of these bit-strings?

ASD: JTAG controller
AMT, JTAG controller: CSM

2) g) Are the bit-strings always identical or can there be dynamic modifications (e.g. between runs) and if so, who (which device) is supposed to make such modifications?

No. Yes. CSM or ROD.

2) h) Which is the route foreseen for the bits to get from the source to the sub-system (details!)?

User  MROD  CSM  Mezzanine