3 Nov 2009G. Rakness (UCLA)1 Weekend of 24 – 25 October Loaded all TMB firmware –Version 15 Oct 2009 XML file created using Jay’s muonic timing constants for TOF parameters…

3 Nov 2009G. Rakness (UCLA)2 Timing parameters measured 1.Define TOF parameters alct_tof_delay tmb_to_alct_data_delay 2.Measure ALCT tx/rx communication parameters alct_tx_clock_delay, alct_tx_posneg alct_rx_clock_delay, alct_posneg 3.Measure CFEB rx communication parameters cfeb[0-4]delay, cfeb[0-4]posneg 4.Equalize BC0 round trip from TMB  ALCT  TMB tmb_bxn_offset alct_bx0_delay match_trig_alct_delay 5.Measure L1A receipt windows and DAV bits at DMB tmb_l1a_delay, alct_l1a_delay, tmb_lct_cable_delay alct_dav_delay, cfeb_dav_delay After each step, load the measured values into the userPROM

3 Nov 2009G. Rakness (UCLA)3 One button per timing scan per endcap: Steps: 1.Click the button 2.Wait 3.Log all output 4.Log Test Summary 5.Use script to insert (234 * N) values from scan into xml file…

3 Nov 2009G. Rakness (UCLA)4 CFEB timing scans With CFEB digital phase shifters, we need to… Determine cfeb[0-4]posneg … and then there was an issue with ME1/1…

3 Nov 2009G. Rakness (UCLA)5 Determining cfeb[0-4]posneg Use the idea that the wrong posneg bit will cause the scan to have “holes”… posneg = 0 gives a total of 8 good windows... TimeDelay CFEB Id= CFEB Id= CFEB Id= CFEB Id= CFEB Id= posneg = 1 gives a total of 5 good windows... TimeDelay CFEB Id= CFEB Id= CFEB Id= CFEB Id= CFEB Id= Count the number of windows per CFEB If N window = 1 per CFEB (for at least 4 CFEB’s), use this posneg value and determine centroid for each CFEB If one CFEB fails (i.e., N window  1), use the centroid from neighboring CFEB

3 Nov 2009G. Rakness (UCLA)6 ME1/1: injecting in ½-strips Recall: not staggered strips for ME1/1… (temporarily “solved” this by requiring 5/6 layers in the CLCT pattern)  Also had to fix the mapping for ME1/1a and ME1/1b… Normal CFEB pulsing pulses the following CFEB strips…

3 Nov 2009G. Rakness (UCLA)7 BC0 alignment Did the scans work?

3 Nov 2009G. Rakness (UCLA)8 ALCT-CLCT BC0 alignment at TMB ME For dead ALCT’s, set alct_bx0_enable=0 to set ALCT BC0 == CLCT BC0 ME– Read ALCT_BC0==CLCT_BC0 bit 100 times…

3 Nov 2009G. Rakness (UCLA)9 BC0 is (mostly) aligned at the CSCTF… CSC SP counted 14 “Short orbits” in 35 minutes for SP#1, inputs 4 – 6 (VMEp1_3) All the rest of the links count 0 (= good) SP counter of “short orbits”

3 Nov 2009G. Rakness (UCLA)10 Unexpected constraints to implementing muonic timing at point 5…

3 Nov 2009G. Rakness (UCLA)11 Signal leaving TMB Signal returning to TMB TX 1 integer delay tx 1 fine delay S 1 cable propagation rx 1 fine delay RX 1 integer delay  time (bx) Signal at ALCT Constraint on TX: DMB expects the “Data AVailable” (DAV) bit from ALCT to arrive back at DMB within a ~fixed time after receiving the L1A… (“~fixed” means the dynamic range of the xml parameter alct_dav_cable_delay must span the range of TMB  ALCT cable lengths)  Effect of this constraint on muonic timing for the system at point 5… TX needed to be minimized (smallest value = 0) New DMB firmware was needed

3 Nov 2009G. Rakness (UCLA)12 Signal leaving TMB Signal returning to TMB TX 1 integer delay tx 1 fine delay S 1 cable propagation rx 1 fine delay RX 1 integer delay  time (bx) Signal at ALCT Constraint on RX: CFEB expects the L1A back at a ~fixed time relative to the CLCT pretrigger (“~fixed” means the dynamic range of tmb_lct_cable_delay must span the range of TMB  ALCT cable lengths)  Effect of this constraint on muonic timing for the system at point 5… The time T needed to be tuned to ~match what we have now … N.B. I don’t think I have it quite right… (~1 – 2 bx off in some chambers) but the wide CFEB windows are saving me…  T

3 Nov 2009G. Rakness (UCLA)13 Time taken last week at p5 1.Define TOF parameters alct_tof_delay tmb_to_alct_data_delay 2.Measure ALCT tx/rx communication parameters alct_tx_clock_delay, alct_tx_posneg alct_rx_clock_delay, alct_posneg 3.Measure CFEB rx communication parameters cfeb[0-4]delay, cfeb[0-4]posneg 4.Equalize BC0 round trip from TMB  ALCT  TMB tmb_bxn_offset alct_bx0_delay match_trig_alct_delay 5.Measure L1A receipt windows and DAV bits at DMB tmb_l1a_delay, alct_l1a_delay, tmb_lct_cable_delay alct_dav_delay, cfeb_dav_delay After each step, load the measured values into the userPROM 4.5h Time taken for 473 chambers 2.5h ~few min 4.5h Much is dependent on the TOF parameters, including communication, L1A, and the timing of L1A at ALCT  Need fast turnaround time on these scans…

3 Nov 2009G. Rakness (UCLA)14 Streamline the procedure 1.Define TOF parameters alct_tof_delay tmb_to_alct_data_delay 2.Measure ALCT tx/rx communication parameters alct_tx_clock_delay, alct_tx_posneg alct_rx_clock_delay, alct_posneg 3.Measure CFEB rx communication parameters cfeb[0-4]delay, cfeb[0-4]posneg 4.Equalize BC0 round trip from TMB  ALCT  TMB tmb_bxn_offset alct_bx0_delay match_trig_alct_delay 5.Measure L1A receipt windows and DAV bits at DMB tmb_l1a_delay, alct_l1a_delay, tmb_lct_cable_delay alct_dav_delay, cfeb_dav_delay After each step, load the measured values into the userPROM Streamlined by removing unnecessary “sleeps”… Time taken for 473 chambers = 3h20 min using “collision timing” on both endcaps… Test to be done tomorrow with these constants…

3 Nov 2009G. Rakness (UCLA)15 To do Beam injections into Sector 4-5 scheduled for this weekend –“Beam splash” data to be collected at CMS… Planning to use collision TOF parameters for both endcaps…