40 likes | 148 Views
Team A: Update on VME+1/[4-9] (ME+1 far side). Communication with VME+1/7 Optical transceiver successfully replaced at switch in USC55 CSC Elog 2977 Firmware upgrades Conflict of firmware uploading with DCS monitoring solved via explicit communication with Valeri
E N D
Team A: Update on VME+1/[4-9] (ME+1 far side) • Communication with VME+1/7 • Optical transceiver successfully replaced at switch in USC55 • CSC Elog 2977 • Firmware upgrades • Conflict of firmware uploading with DCS monitoring solved via explicit communication with Valeri • Broadcast + Individual downloading used to download firmware for all modules (except VCC) • CSC Elog 2981 and 2985 • CCB replaced in VME+1/7 and VME+1/8 • CSC Elog 2987 • Replaced blown fuse in Junction Box ME+1/2/16 (VME+1/6 slot 10) • CSC Elog 2981 G. Rakness (UCLA)
Team A: Summary for VME+1/[4-9] (ME+1 far side) • Communication has been established • Firmware has been updated to versions… • DMB VME: v11 r1 • DMB FPGA: v24 r1 • CFEB FPGA: v10 r2 • TMB: 11 Oct. 2007 • RAT: 28 Aug. 2006 • ALCT: 28 Aug. 2007 • MPC: 27 Oct. 2006 • CCB: 5 Mar. 2007 • “Problem” chambers/slots for Team C • VME+1/5 slot 7 (ME+1/1/14): CFEB did not accept firmware (this is what I gather the problem is from the elog…) • VME+1/8 slot 7 (ME+1/1/23): DMB firmware not updating G. Rakness (UCLA)
Communication phase parameters for ME1/1 chambers • Recall: predictions for synchronization parameters are based on lengths of skew clear cables • Windows for good communication measured for three ME1/1 chambers (VME+1/4) • CSC Elog 2986 • Predicted values do not work for ME1/1… • ALCT tx/rx predictions fall outside the measured window • CFEB rx predictions fall on the edge of the measured window • Possibly due to patch panel between ME1/1 chambers and peripheral crates… • Required actions (from my point of view): • establish that predictions for ME1/2 and ME1/3 are OK (or not…) • Then, either… • perform communication and synchronization scans for ME1/1 • approximate patch cable lengths into predictions for ME1/1 chambers (I don’t like this) G. Rakness (UCLA)
Team A Workshop • Short workshop held to describe details of how to perform current Team A tasks • 10-15 people present • Plan to begin Team A shifts next week • Slides available as attachment to twiki page: • https://twiki.cern.ch/twiki/bin/view/CMS/CSCcommissioningTeamA • Discussion included suggestions to: • Formalize DCS as step 0 prior to Team A work • Make “overall” status screen to monitor firmware versions • Put estimates of how long to broadcast each firmware type • Make logfile easily accessible G. Rakness (UCLA)