Upload
henry-wilkins
View
219
Download
0
Tags:
Embed Size (px)
Citation preview
Outline:
Hw status (on the basis of last LED data); Plans / requests;
ECAL: status and plans
Set of several LED samples with different LED intensity settings in the range [LV(nominal)-1;LV(nominal)] with the step 0.1V
Another stability run, several hours at constant 2 Hz LED rate and [LV(nominal)-0.4V] intensity setting
Poor time alignment, but data can be used to produce preliminary LED intensities adjustment / roughly check hardware behavior.
Further: on 2d-maps LED amplitude is taken not from T0, but from BX with maximal LED signal
LED data (Friday afternoon – Saturday morning)
Hardware status, C-side
8 LEDs missing in previous data, are checked from our side (LED + LED driver + cabling). 3 LEDs of the group 2.06 – bad transporting cables both for voltages and fire signal (repaired, appeared in the data). The rest is OK (our side).
HV box number 4 – replaced with the spare one. DCU shows stable LV behavior.
Run 26679; LED signal, C-side
Unstable cells (run 26679, worse than 6%, C-side)
Majority of unstable cells are grouped in vertical columns. Each group matches one voltage delivery cable / connector on HV-box.
Within one cable: simultaneous change in LED amplitude in all cells
Before data taking: connectors on 6 voltage delivery cables, which showed instability in previous LED sample (26340) were replaced. The behavior of these lines: to be checked.
Run 26679; C-side
Hardware status, A-side
7 LEDs, missing in last data, are checked from our side. 1 LED (2.02.3) – bad transporting cable RJ-45. To be repaired. The rest is operational (on our side).
Cabling check after modification of HV boxes – done last Friday. All mistakes are fixed.
Run 26679; LED signal, A-side
Plans/requests for this week
Detailed analysis of the LED data, collected last Friday / Saturday:
Produce preliminary LED intensity settings; Produce map of dead / unstable cells;
On Friday: take data to check new LED intensity settings;
Next weekend: reserve ECAL PM/LED/PIN systems on both sides for the maintenance (readout is not needed);