1 / 6

Status of the CSC system

Status of the CSC system. M. Ignatenko (UCLA) CSC Operation and DPG meeting CERN January 18, 2012. Cooling was “on” on Friday Jan.13. Monday Jan.16 - Valeri Andreev published that the 5%CF4 gas mixture is flushing. It needs 2-3 days.

major
Download Presentation

Status of the CSC system

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Status of the CSC system M. Ignatenko (UCLA) CSC Operation and DPG meeting CERN January 18, 2012

  2. Cooling was “on” on Friday Jan.13. Monday Jan.16 - Valeri Andreev published that the 5%CF4 gas mixture is flushing. It needs 2-3 days. Tuesday - we (Armando) requested all racks on. But we found quit a few racks were off and we had to switch them on through central DCS GUI. No problems with OPFCs. Local DCS was not in a good shape – lost communication with hardware, HV server was not started, no control over Maratons, … Experience with switching on CSC after Christmas break

  3. No communication with plus VME crates – restored in 2 minutes. No communication with VME-4/1 crate. Power cycling an optical switch restored communication with VME-4/1 but brought about loss of communications with some other crates. Only power cycling the whole optical switch restore the 100% communication. Problems with configuration of the TTC. Was fixed by power cycling a TTC PC and a TTC crate. Lost communication with all +VME crates again. Rebooting the csc-pc1 helped to restore communication. Experience with switching on CSC after Christmas break

  4. During the night we lost communication with all plus side crates + DCS DIM server for plus side was found down (most likely 2 correlated things). After DIM server was restarted it was clear that the csc-dcs-pc1 can communicate with all +VME crates. Rebooting the csc-pc1 didn’t help. Savannah ticket related to the csc-pc1 has been submitted. We tried to find out a recipe to start the yellow page on csc-dcs-pc1 and we failed. Karoly was able to do that and make an instruction for the experts. Experience with switching on CSC after Christmas break

  5. Because of the mess with TTC and communication losses we were able to reproduce the Bug in our Power-up/Init procedure – all CCBs were found not configured. The biggest problem is – starting from this point the “right procedure” (Power up/Init from the blue page and then TTC configuration) doesn’t work. Based on our experience from the LHC proton run we were able to configured the system doing Greg’s firmware check!? Shell we modify the “firmware check procedure” for crate configuration? The system was given to the DCS guys to switch on new Can-bus hardware/software. The first local run can be taken only after gas is back. We are almost on schedule. Experience with switching on CSC after Christmas break

  6. Experience with switching on CSC after Christmas break After 40 days when the system was off and there were no beam in the LHC we had to restore firmware in EPROMS of only 4 CFEBs, 1 TMB and 1 DMB. During the proton run we had to do that for at least 1-2 boards a day. The 7 V reading on me-1/1/30 LVDB is 7.24 V – there is a little hope that it can be back.

More Related