<!-- Title: 10:03:00  Tue Jul  1 2003 -->
<!-- Crewchief: Prof. TOF -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Log for the New Quarter</pre>


<!-- Date: Sun Jul 6 18:45:10 2003 -->
<pre>We had an heart beat from TOF. We checked the TOF pc on the first floor after some minutes and ti was frozen. We rebooted it according to procedures and it worked again. HB on the ifix global alarm cleared.</pre>
<!-- Author: Pierluigi -->


<!-- Date: Wed Jul 16 17:55:09 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Wed_Jul_16_2003_175502.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-182  align='top'></td><td>YMon for latest data taken. Still shows red background!</a></td></tr></table>
<!-- Author: Gervasio -->


<!-- Date: Fri Jul 18 08:22:58 2003 -->
<pre>TOF PC was frozen. restarted</pre>
<!-- Author: Pierluigi -->


<!-- Date: Tue Jul 22 03:02:41 2003 -->
<pre>We had an alarm from TOF during data taking. We checked the TOF pc it was frozen. We rebooted it following the instruction relative to the data taking. The alarm cleared.</pre>
<!-- Author: Paola -->


<!-- Date: Tue Jul 22 10:50:32 2003 -->
<pre>TOF TAC calibrations changed again. TAC parameters gamma and tau 
shifted back to their previous normal values. Will make DBANA 
limits wide enough to accomodate both TAC "modes".</pre>
<!-- Author: Gervasio -->
<!-- Comment: Tue Jul 22 10;51;20 comment by...Gervasio -->
<pre>The changed happened right after an access on July 15, apparently.</pre>


<!-- Date: Tue Jul 22 12:34:30 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-184&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-184' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-183&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-183' width='300'></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Tue Jul 22 12;39;06 comment by...Gervasio -->
<pre>TAC calibration for runs 166056 (07/13/2003) and 
166087 (07/15/2003). Now DBANA has a range wide enough 
to display both "modes". 
Jack Cranshaw will make this the default DBANA in the control
room soon.</pre>


<!-- Date: Fri Jul 25 15:46:18 2003 -->
<pre> 
                    TOF Pager Activity 
                   ==================== 
 
BEAM DATA: 
========== 
 
date   run number   L3 accepts   lumi(nb-1)   TOF YMON      comments 
----   ----------   ----------   ----------   --------      -------- 
 
Jul-12   166007       733,703     397.16         OK         ch 350 off 
Jul-12   166008     2,258,020     981.98         OK         ch 350 off 
Jul-12   166011         9,243       0.99         OK         ch 350 off 
Jul-13   166037       671,198     356.38         OK         ch 350 off 
Jul-13   166038     2,072,213     890.80         OK         ch 350 off 
Jul-14   166063     2,368,742    1062.99         OK         ch 350 off 
Jul-14   166073       361,255     139.02         OK         ch 350 off 
Jul-16   166227       183,775     100.72         OK         ch 350 off 
Jul-17   166248       187,871      92.80         OK         ch 350 off 
Jul-17   166249       205,779     109.74         OK         ch 350 off 
Jul-17   166250         5,284       3.18         no file 
Jul-17   166251       490,938     204.27         OK         ch 350 off 
Jul-18   166325       542,080     279.62         OK         ch 350 off 
Jul-18   166328       650,698     285.53         OK         ch 350 off 
Jul-19   166367       557,437     274.40         OK         ch 350 off 
Jul-19   166369       276,374     122.22         OK         ch 350 off 
Jul-19   166370         1,176       0.76         no file 
Jul-19   166371       759,402     318.42         OK         ch 350 off 
Jul-19   166373       361,158     144.13         OK         ch 350 off 
Jul-19   166374       177,149      68.52         OK         ch 350 off 
Jul-19   166377        15,363       6.47         OK         ch 350 off 
Jul-20   166403       282,899     159.17         OK         ch 350 off 
Jul-20   166406     2,392,956    1054.36         OK         ch 350 off 
Jul-20   166407        85,038      33.75         OK         ch 350 off 
Jul-21   166429        22,773       6.43         OK         ch 350 off 
Jul-21   166430        67,047      17.13         OK         ch 350 off 
Jul-21   166472       153,704      83.28         OK         ch 350 off 
Jul-22   166479     2,392,181    1003.41         OK         ch 350 off 
Jul-22   166481        53,220      20.57         OK         ch 350 off 
Jul-22   166482       186,934      68.02         OK         ch 350 off 
Jul-22   166525       446,484     240.95         OK         ch 350 off 
Jul-23   166529     2,340,061     998.16         OK         ch 350 off 
Jul-24   166567     2,968,391    1474.73         OK         ch 350 off 
Jul-25   166614     1,561,440     906.79         OK         ch 350 off 
Jul-25   166615       169,176      87.38         still going ..... 
 
 
up to 9:30 am Fri, Jul 25,2003 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
 
============================================================================= 
 
July 12: 
======== 
 
- Got pager from Mike around 4 pm. He had no pages. 
- Some tests of double diffraction trigger using TOF!! 
- Take data. 
 
July 13: 
======== 
 
- Shot setup around 2:40 am. Taking data. 
 
July 14: 
======== 
 
- Shot setup around 3:10 am. Taking data. 
- Store lost at 22:19. TeV RF trip, clean abort with no quench. 
- TeV studies followed by D0 access. 
 
July 15: 
======== 
 
- No beam all day.  
- TAC calibration parameters tau and gamma have moved again, this time 
  back to their previous normal values! Will change DBANA. 
 
July 16: 
======== 
 
- Shot setup around 4 pm. Taking data. 
 
July 17: 
======== 
 
- TeV quench around 4:50 am. 
- Shot setup around 8 am, followed by data taking. 
- Beam (and stack) lost to power glitch around 5 pm. 
 
July 18: 
======== 
 
- ACE restarted TOF PC around 8:10 am (it was frozen). 
- Shot setup under way.... 
 
July 19: 
======== 
 
- Scraping complete ~ 3:30 am. 
 
July 20: 
======== 
 
- Shot setup around 1 am. 
 
July 21: 
======== 
 
- Low lum store dropped around 1 am. 
- Access for Si. 
- Shot setup ~ 2:30 pm. 
 
July 22: 
======== 
 
- Data taking. Beam dumped around 2 pm. 
- BMU and SI access followed by shot setup. 
 
July 23: 
======== 
 
- Beam lost ~ 3:23 pm due to quench.  
- Shot setup. Finish scraping ~ 10:35 pm. Take data. 
 
July 24: 
======== 
 
- Data taking. 
- Paged ~ 3 pm because: 
 
"Run Control reports a trigger inhibit from TOF. TOF LED is not  
lit in the inhibit panel, nor the IFIX monitor shows anything  
wrong. Paused run to check status of the TOF PC. No apparent  
problem. Resumed Run. " 
 
this happened 3 times in an hour. Went down to check the HV log file. No 
apparent errors or alarms or warnings from July 24... ???  
 
 
- Beam lost around 4:10 pm.  
- Scraping for new store complete ~ 10:40 pm. 
 
July 25 
======= 
 
- Take data 
</pre>
<!-- Author: Gervasio -->


<!-- Date: Tue Jul 29 19:15:45 2003 -->
<pre>TOF HV tripped.  PC on first floor was frozen.  Rebooted it.</pre>
<!-- Author: Mitch -->


<!-- Date: Wed Jul 30 05:19:10 2003 -->
<P>At 4 am, the shift crew was unable to turn off the TOF HV from upstairs.  Since the store was ending, the emergency shutdown procedure was used.  When I looked at the TOF PC, everything seemed to be running properly, except there was an warning about "System Alert Buffer Overflowed".  Upon rebooting the PC, twice, there were more errors both upstairs and downstairs "CDF_S1.sine.b_egu:   Connection NOT established with node."  After about 5 to 10 minutes, this error went away, and the heart beat was re-established.  Now everything seems fine.
<!-- Author: mulhearn -->


<!-- Date: Sun Aug 3 02:39:17 2003 -->
<pre>TOF PC was frozen. Rebooted according procedures.</pre>
<!-- Author: Pierluigi -->


<!-- Date: Sat Aug 9 20:31:08 2003 -->
<pre>HV board in Crate 2 #7 crapped out, all 16 channels. 
removed board B0 (575503) and replaced it by 
board A4 (5754497)---this occurred during Run 167297 
(marked "bad" for TOF)...then tried to restart run with 
TOF, and TOF is giving a trigger inhibit---which I do 
not understand. looks like a hardware in inhibit rather 
than a software one (smacs looks happy), but see no 
problem with hardware. 
  restarted new run (167299) with TOF inhibit overridden.</pre>
<!-- Author: bauer -->


<!-- Date: Sun Aug 10 06:53:27 2003 -->
<pre>Paged at 5:38 am: after quench the TOF PC lost its heartbeat. 
Restarted iFIX and SMACS and things went back to normal from  
an HV operations point of view. Will find out very shortly 
if the TOF trigger inhibit is cleared (doubtful) during a cosmic 
run. If not cleared, will instruct to run with TOF trigger  
inhibit disables and pay special attention to YMon plots. 
Don't know who to call about trigger inhibit problem: Jonathan 
Lewis? Some TOF HV expert? 
</pre>
<!-- Author: Gervasio. -->


<!-- Date: Sun Aug 10 07:15:58 2003 -->
<pre>TOF trigger inhibit is now cleared and everything looks fine 
for TOF. Still don't know what caused the inhibit in the first  
place and why it is clear now. Perhaps it was software related?</pre>
<!-- Author: Gervasio. -->


<!-- Date: Sun Aug 10 17:55:12 2003 -->
<pre>Around 4:15pm the TOF PC was found hung while the anti-proton 
bunches were being loaded. Not to waste any time I asked the 
sci-co to page ToF and rebooted the PC. Following instructions 
I started the SMACS program. Things went back to normal.</pre>
<!-- Author: Satyajit (MonACE) -->


<!-- Date: Tue Aug 12 15:31:45 2003 -->
<center><a href='/elog/notebooks/tof/Tue_Aug_12_2003_153031.ps'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-188' ></a><a href='/elog/notebooks/tof/Tue_Aug_12_2003_153050.ps'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-190' ></a><a href='/elog/notebooks/tof/Tue_Aug_12_2003_153111.ps'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-192' ></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Tue Aug 12 15;35;52 comment by...Gervasio -->
<pre>Run 167297 is BAD for TOF: crate 2 board 7 bad.
Run 167324: occupancies seem slightly high.
Run 167325: back to normal.

All runs except 167297 and 167324 look OK. 
YMon canvas color still not understood.</pre>


<!-- Date: Thu Aug 14 11:35:07 2003 -->
<pre>When bringing up HV for Cosmic run the TOF system had heartbeat alarm and was not being monitored on iFix HV Summary.  Checked the PC downstairs.  It was frozen so I restarted it, using the 'use current CAEN settings' option since HV was on. 
</pre>
<!-- Author: Mitch Soderberg -->


<!-- Date: Fri Aug 15 09:27:03 2003 -->
<pre> 
                    TOF Pager Activity 
                   ==================== 
 
BEAM DATA: 
========== 
 
date   run number   L3 accepts   lumi(nb-1)   TOF YMON      comments 
----   ----------   ----------   ----------   --------      -------- 
 
Aug-08   167258        15,751      16.57         OK         ch 350 off 
Aug-09   167259       476,924     281.01         OK         ch 350 off 
Aug-09   167261       121,742      68.66         OK         ch 350 off 
Aug-09   167265        32,620      20.13         OK         ch 350 off 
Aug-09   167266       159,602      84.23         OK         ch 350 off 
Aug-09   167289        44,313      45.30         OK         ch 350 off 
Aug-09   167290       141,439      85.59         OK         ch 350 off 
Aug-09   167292        71,036      42.01         OK         ch 350 off 
Aug-09   167297       289,344     156.72         BAD        board 7 crate 2 bad 
Aug-10   167299     1,325,145     595.58         OK         ch 350 off 
Aug-10   167324       272,989      86.94         ??         high occupancies 
Aug-10   167325     1,321,459     810.91         OK         ch 350 off 
Aug-12   167444       693,673     380.27         OK         ch 350 off 
Aug-13   167445     1,368,672     618.65         OK         ch 350 off 
Aug-14   167506     1,589,915     896.49         OK         ch 350 off 
Aug-15   167549       130,541     129.15         OK         ch 350 off 
Aug-15   167551     still going.... 
 
up to 09:30 am Fri, Aug 15, 2003 
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ 
 
============================================================================= 
 
August 8: 
======== 
 
- Got pager from Mike around 10 am. He had no pages. 
- Test studies in progress while stacking. 
- Beam towards 11 pm. 
 
August 9: 
========= 
 
- Beam lost around 5:10 am.  
- Paged around 6:30 pm. Board 7 in crate 2 is burned out. Gerry Bauer came in 
  to replace the board.  
- TOF trigger inhibit did not clear (!?) so they ran ignoring it. Asked 
  to be paged at end of store to investigate inhibit problem. 
 
August 10: 
========== 
 
- Lost store due to quench around 05:10 am. 
- Paged at 5:30 am. TOF HV did not respond. HV was on when I got there around 
  6 am. Restarted iFIX and SMACS and turned off TOF. Everything back to normal. 
- Trigger inhibit cleared itself after startup of HV monitoring programs, as 
  confirmed by a cosmics run including TOF. 
- Shot setup finally around 4 pm... 
- Paged at 4:30 pm. TOF PC had to be rebooted around 4:40 pm during p-bar  
  injection. 
 
 
August 11: 
========== 
- Store lost at 00:06 am due to quench. Stacking..... 
- Stack lost at 9:45 due to quench. 
- Access. 
 
August 12: 
========== 
 
- Quench early morning ~01:53 am. 
- New store finally around 9:50 pm 
 
August 13: 
========== 
 
- Taking data.... 
- Quench around 11:30 am. 
- Paged at 3:30 pm to check QIE and TAC calibs after CAL access. Two CAFE cards 
  were replaced due to high trigger rates: 
 
The first replacement was for CHA phi 19W, eta 0R, which showed up as a  
sometimes hot channel. This particular problem had not been seen before, but  
the CAFE is definitely responsible. The second replacement was for WHA phi 7E,  
eta 6R, a dead channel. 
 
- TAC calibration looks fine before and after CAFE swap (as expected). 
- QIE calibration looks fine before and after CAFE swap. 
 
 
August 14: 
========== 
 
- New store in, data taking starts around 00:40 am. 
- Store lost to quench around 9:10 am. 
- Paged at 11:45 because TOF trigger inhibit did not clear for cosmics. 
- iFIX was in a strange mode: hearbeat was fine, but HV seemed to be OFF 
  in the VNIDE1 picture, and I could not turn it on from the control room. 
  Donwstairs everything looked OK in the PC, so I forced the HV on from 
  SMACS and everything went back to normal, including the trigger which cleared 
  itself.  
- Now taking cosmics with TOF. 
- New store in. Started taking data around 5:00 pm. 
- Quench around 9:40 pm (store lost). 
 
August 15: 
========== 
 
- New store in and data taking began around 5:15 am. 
- Taking data..... 
</pre>
<!-- Author: Gervasio -->


<!-- Date: Fri Aug 22 00:16:10 2003 -->
<pre>TOF PC hung.  Rebooted and kept current voltage settings.  There was a trialware message that popped up on reboot.  I left it open.</pre>
<!-- Author: dan -->
<!-- Comment: Sat Aug 23 15;23;25 comment by...Stefano -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>The trialware message is normal and can be ignored w/o problems.</pre></td></tr></td></table>


<!-- Date: Mon Aug 25 19:51:54 2003 -->
<pre>I had to restart the TOF PC because it was hung.  I followed the posted instructions and everything seems fine now. See cdf e-log for more information.</pre>
<!-- Author: Alberto -->


<!-- Date: Fri Aug 29 14:45:00 2003 -->
<pre>The TOF pc was hung so I rebooted it following the instructions posted next to it. We were NOT taking DATA at the time, it was during shot setup</pre>
<!-- Author: anant -->


<!-- Date: Wed Sep 3 10:50:36 2003 -->
<pre>Updating ADC gate widths in hardware database: 
 
SQL&gt; UPDATE CARDS SET 
  2  GATEWIDTH0=120,GATEWIDTH1=120,GATEWIDTH2=120,          
  3  GATEWIDTH3=120,GATEWIDTH4=120,GATEWIDTH5=120, 
  4  GATEWIDTH6=120,GATEWIDTH7=120,GATEWIDTH8=120 
  5  WHERE COMPONENT='TOF' AND CR_CRATENAME LIKE 'WCAL%'; 
 
48 rows updated. 
SQL&gt; COMMIT; 
 
Commit complete. 
 
SQL&gt; 
 
This will set the ADC gate width to about 13 ns.  Previously 
it was about 20 ns.  It is expected that we will need a new 
offline calibration for this data.  We expect it to only be 
about 2 /pb before the shutdown.</pre>
<!-- Author: M Jones -->


<!-- Date: Sat Sep 6 10:58:20 2003 -->
<pre>Got a TOF alarm from the global HV panel. Found the PC hung. 
Rebooted it and restarted the monitoring program. Things are 
back to normal.</pre>
<!-- Author: Satyajit -->


<!-- Date: Wed Sep 10 07:44:52 2003 -->
<pre>PC and Caen's were shut down monday morning for power outage. 
PC was brought back up, but not Caen supplies. 
I just turned them on, and loaded the 50V files....but we  
need to make them the default for the shutdown!</pre>
<!-- Author: bauerg -->


<!-- Date: Thu Sep 11 14:20:10 2003 -->
<P>We have done some prep work for fixing the TOF pmt 350 located on the 
west side, at 223 degrees.  We have disconnected the oval card from 
its 3-pack, enclosed it in a keplon lined baggy, and taped the bag out 
of the way (between COT and solenoid).  Also, cables 350 and 353 have 
been swapped back to their normal configuration (no SMACs setting 
change!).</P>
<!-- Author: mulhearn and bauer -->


<!-- Date: Fri Sep 12 16:02:30 2003 -->
<pre>Early this morning raised ch350 to 2kV and let it cook. 
forgot to make the entry earlier. 
to do this 1-caen supply has its solenoid interlock disabled. 
*******please do not fool around with the HV without talkign 
to me!!**** 
 
...i'm carrying the pager: 722-6176</pre>
<!-- Author: bauerg -->


<!-- Date: Sat Sep 13 07:58:32 2003 -->
<pre>Raised voltage on chan 350 to 2.2kV. also lowered current 
limit to 6uAmps.....everything still well behaved.</pre>
<!-- Author: bauerg -->


<!-- Date: Sat Sep 13 18:56:49 2003 -->
<pre>TOF PC hung up (reportedly been this way for a long time), 
rebooted it: mouse was moveable for a few seconds, then 
everything froze. had to reboot by hardware reset.</pre>
<!-- Author: bauerg -->


<!-- Date: Mon Sep 15 08:15:43 2003 -->
<pre>Raise Ch350 to 2.3 kV</pre>
<!-- Author: bauerg -->


<!-- Date: Tue Sep 16 08:19:13 2003 -->
<pre>Raise Hv on 350 to 2.4kV---no sign of any problems so far!</pre>
<!-- Author: bauerg -->


<!-- Date: Wed Sep 17 15:48:03 2003 -->
<pre>This afternooon there was some sort of network "event",  
HV PC froze up. i rebooted by hardware, voltage on 350  
was uninterrupted....and merrily cooking along. 
:-( 
</pre>
<!-- Author: bauerg -->


<!-- Date: Fri Sep 19 21:50:00 2003 -->
<pre>Voltage on ch 350 got turned off (i don't quite know the 
history), but now have turned it back on.</pre>
<!-- Author: bauerg -->


<!-- Date: Sun Sep 21 21:40:57 2003 -->
<P> PC was hung.  Tried rebooting and restarting IFIX 3 times, but continue to get "Connection Not Established with node" errors.  I will leave SMACS running, wait, and try again later, which has worked before...</P>
<!-- Author: mulhearn -->


<!-- Date: Wed Sep 24 14:29:11 2003 -->
<pre>Raise HV to 2480 V on CH 350</pre>
<!-- Author: bauerg -->


<!-- Date: Thu Sep 25 11:50:50 2003 -->
<pre>For some reason, ch 350 HV was OFF!...did not seem to be 
in trip condition? what is going on? did we succeed? or was 
something screwed up in iFix/Smacs?.....raise CH 350 up again 
to 2400 V!</pre>
<!-- Author: bauerg -->


<!-- Date: Thu Sep 25 22:46:37 2003 -->
<pre>PC was completely frozen, press reset, bring back up...chan 350 
still merrily at 2450 V. 
</pre>
<!-- Author: bauerg -->


<!-- Date: Fri Sep 26 14:22:34 2003 -->
<pre>Found SMACS was stopped....restarted iFix and SMACS. 
Ch 350 maintained its voltage at 2.45 kV</pre>
<!-- Author: bauerg -->


<!-- Date: Sat Sep 27 14:37:20 2003 -->
<pre>TOF HV turned down by shift crew for calib run, but they 
could not turn back up cuz of solenoid interlock. i turn 
ch350 back up, to 2480 V</pre>
<!-- Author: bauerg -->


<!-- Date: Mon Oct 6 11:08:23 2003 -->
Found TOF PC logged off, and don't know why...didn't find/notice 
any elog entries explaining status. did find that there was 
a problem <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=826&frame=2&anchor=12:55:23.536'> 
last friday</a>....in any case, login and restart SMACS. load in 
"current caen status" settings....ch350 is/was still on! 
 
  
<!-- Author: bauerg -->


<!-- Date: Fri Oct 10 06:34:13 2003 -->
<pre>TOF PC hang - restarted it 
 </pre>
<!-- Author: Andrei -->


<!-- Date: Sun Oct 12 18:09:31 2003 -->
<pre>I stop the current run to test new set up with Caen card A1303. 
 
</pre>
<!-- Author: daniele -->


<!-- Date: Sun Oct 12 21:51:45 2003 -->
<pre>I restart the previous run 
</pre>
<!-- Author: daniele -->


<!-- Date: Sun Oct 12 23:44:27 2003 -->
<pre>shut down TOF HV for tomorrow's power outage.</pre>
<!-- Author: bauerg -->


<!-- Date: Mon Oct 13 10:10:27 2003 -->
<pre>powerup TOF HV, put ch350 at 2850V</pre>
<!-- Author: bauerg -->


<!-- Date: Wed Oct 15 21:53:59 2003 -->
<P>We made some progress on the channel 350 HV repair today.  We removed the old HV cable from the oval card, then soldered, strain relieved and cleaned the new HV cable.  We trimmed, insulated and labeled the old HV cable.  We tucked everthing out of the way.  We also tested that there is no short.  We can't do any further testing until we connect the other end to HV. </P>
<!-- Author: mulhearn and bauer -->


<!-- Date: Fri Oct 17 00:08:37 2003 -->
<pre>forgot to make the entry earlier: 
  while on access to work on CH350, plugged in the auxilary 
crate power supply interlock (the two jumper wires going to 
the ADMEM test point) on the bottom north east crate....supply 
voltage duly came on....</pre>
<!-- Author: baeurg -->


<!-- Date: Fri Oct 17 11:25:44 2003 -->
<pre>Taking TAC calibration 0x29d5d before upgrading clock fanout 
module.  b0wcal05 was left out because of power supply problems.</pre>
<!-- Author: M Jones -->


<!-- Date: Fri Oct 17 11:32:49 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-193&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-193  width='300' align='top'></td><td>Except for b0wcal05, things are basically fine.</a></td></tr></table>
<!-- Author: M Jones -->


<!-- Date: Fri Oct 17 15:35:12 2003 -->
<pre>Installed new LCF module in b0wcal07.  Updated hardware database 
to give approximately the same delay/width: 
 
SQL&gt; UPDATE CARDS SET AUXPORT0=40 WHERE CR_CRATENAME='WCAL_07' 
            AND COMPONENT='TOF'; 
</pre>
<!-- Author: M Jones -->


<!-- Date: Sat Oct 18 19:44:27 2003 -->
<pre>I take the system to do some software work. 
 
At present I found ch 350 Off. I leave so.</pre>
<!-- Author: daniele -->


<!-- Date: Wed Oct 22 02:21:17 2003 -->
<pre>I fully rewrite the driver for A303 Caenet card. This was triggered by a crosscheck between the supplied C drivers for A303 and for A1303. The discrepancy suggest me to rebuilt our home made driver in different phylosofy.  
Results :the previous caenet communication error fully disapeared (I had time for only short test runs of max 12 hours) but the number of errors were 0 (zero) to compear with the many hundred of previous version. I hope this was the source of hangs problems !!! 
 
Note: please someone should check periodically histos for those errors choosing the System/SistemHistos tab, then CaenetError in the combo box.  
 
Other fixed point: 
- The discrepancy shown on the iFix picture (two rings) between the pointed bar and the pop up property tab has been fixed. 
 
- To allow to detect broken cables and/or deviders, introduced a new check to verify if the current seek is below a threshold (4uA), in this case the background of IMon value become red. 
 
- The data written in the logger file reformatted in more readable and useful format. 
 
- Many other small change and fix. 
 
&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;  WARNING &lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt;&lt; 
 
PM 105 in crate 2 board 3 channel 2 shows beaviour compatible with broken cable !!!!!! 
 
 
Cross the figers for future runs. 
  
</pre>
<!-- Author: daniele -->


<!-- Date: Mon Oct 27 13:37:36 2003 -->
<P>Here's a late entry.  On Friday, Nov 17, we replaced the HV cable for channel 350 at the patch-panel.  We were not able to get permission to use heat guns, so we put shrink wrap in place, then held it in place with black electrical tape.  We tested this with HV (2.5 kV) for a few hours.</P> 
<P> On Tuesday, Nov 21, we plugged the oval card in place, locked it in place with a standoff, tested the HV load (10.5 MOhms), and connected the low voltage.</P>
<!-- Author: palencia and mulhearn -->


<!-- Date: Fri Oct 31 12:16:40 2003 -->
<pre>PC lost heartbeat. Cursor moved briefly, then whole PC froze 
up. Had to restart by hardware.</pre>
<!-- Author: bauerg -->


<!-- Date: Mon Nov 3 09:01:15 2003 -->
<pre>--Started investigating problem with no current on Ch 105. 
Made brief acces to the hall to see the physical situation. 
Ch 105 is up at top SE corner. Plugs are closed right now, 
and it is not obvious to me how to monkey around up there? 
Ask Rob to survey the situation and see how he recommends 
working up there. 
 
---Last night checked the SHV cable at the back of the CAEN 
to see that there is no load. There is none, so blame the 
cable and not the CAEN channel. 
 
---This morning turned all chan on with 50 V file, and  
manually scanned through all channels to see that currents 
were being drawn. Saw no other problem channels. (Note: the 
system histogram  for currents doesn't seem to work properly 
in that Ch105 does not show up!. Beware!)</pre>
<!-- Author: bauerg -->


<!-- Date: Mon Nov 3 12:29:05 2003 -->
<pre>Gerry and I put the clock cables in wcal05 back to the old 
configuration.  I requested a TAC calibration that might take 
place later on today...</pre>
<!-- Author: M Jones -->


<!-- Date: Wed Nov 5 21:24:47 2003 -->
<P>We have successfully used the laser calibration system in combination with the TOF cosmic trigger.  We turned the rep rate up to achieve a combined rate (underlying cosmics + laser events) of 7 Hz.  Here's the whole procedure in detail for the next try: 
<UL> 
<LI> Using key, make sure interlock is off (0) 
<LI> Turn on power. 
<LI> Wait for orange light to turn on, visible through the fan vent.  Note:  LED indicator does NOT work. 
<LI> Using key, turn on interlock (1) 
<LI> Press start. 
<LI> Take data. 
<LI> Press stop.   
<LI> Using key, turn off interlock (0) 
<LI> Turn off power. 
</UL> 
For data taking, we start a normal cosmic run, immediately pause it, pre-scale away all but the TOF and MB trigger, then unpause the run. </P>  
<!-- Author: mulhearn and bauer -->


<!-- Date: Thu Nov 6 19:42:08 2003 -->
Bill Badget reported a "line error" in WCAL04. Bill and Steve Hahn 
made access (I was prohibited) and  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=929&frame=2&anchor=19:09:35.544'> 
swapped ADMEM cards</a> in slot 9 (serial 342 replaced by 369). 
The crate was not reading back the cards properly, Rick Tesarak 
happened to be passing through, and he properly reseated them. 
Mike dowloaded ADMEM TOF trigger firmware and ET lookup table for the entire crate. 
<BR> 
<BR> 
Mike also switched the ribbon cable from the new clock fanout module to the old clock fanout module in crate b0wcal07 which should fix the problems in that crate. 
<BR> 
<BR> 
So we THINK everything should be wonderful now....ACE ran 
QIE and TAC calibs (Runs 173425 & 173427). 
<BR> 
<BR> 
 
Gerry, Mike, Bill, and the Evil Steve Hahn
<!-- Author: bauerg -->


<!-- Date: Thu Nov 6 19:44:23 2003 -->
<pre>  Rob R. made access and used his high-wire skills to take a closer 
look at our HV patch panel. He identified cables for ch105, found 
nothing suspicious mechanically. Checked the resistance looking 
into the detector, found no load! 
  ....Looks like we need the plug to be opened  :-(</pre>
<!-- Author: bauerg -->


<!-- Date: Thu Nov 6 19:54:46 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Thu_Nov__6_2003_195413.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-197  align='top'></td><td>QIE results</a></td></tr></table>
<!-- Author: bauerg -->


<!-- Date: Thu Nov 6 20:00:28 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Thu_Nov__6_2003_200022.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-199  align='top'></td><td>..more...</a></td></tr></table>
<!-- Author: bauerg -->


<!-- Date: Thu Nov 6 20:27:31 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Thu_Nov__6_2003_202724.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-201  align='top'></td><td>TAC calibration summary for run 173427.</a></td></tr></table>
<!-- Author: mulhearn -->


<!-- Date: Mon Nov 10 11:20:59 2003 -->
<pre>Looked at cosmic runs this weekend....WCAL04 crate has not 
hits. Make access to investigate whether it might be a problem 
with the 2V supply. detector buttoned up, and cannot see 
where the supply is to check if it is on. see that the connections are plugged in, try pulling them out to try a different ADMEM, either break or find that the GRND connection is 
broken.  
...go on a hunt to repair the pin & cable... 
</pre>
<!-- Author: bauerg & Palencia -->


<!-- Date: Mon Nov 10 13:38:37 2003 -->
<pre>Talked to Steve-H, he asked Roberto to help fix the 2V enable 
cable. Sniped off end with pin and resistor, remade pin end 
on a small jumper cable that was crimped back on to wires 
(this way we avoid problem of soldering in the pit). everything 
reconnected. Unfortunately with detector closed up we can't 
actually see the supply light come back on. 
  ask to have a short cosmic run to see if hits are showing 
up in WCAL04, but L3 having trouble right now....</pre>
<!-- Author: bauerg -->


<!-- Date: Mon Nov 10 14:31:17 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Mon_Nov_10_2003_143106.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-203  align='top'></td><td>took quick cosmic run....WCAL04 now seems to appear, but looks like chan 364-432 on the west are now GONE!</a></td></tr></table>
<!-- Author: bauerg -->


<!-- Date: Tue Nov 11 09:56:16 2003 -->
<table><tr><td><a href=/elog/notebooks/tof/Tue_Nov_11_2003_095605.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-205  align='top'></td><td>Yesterday went down to look at missing crate. Found the 2V enable cable unplugged. Plugged it back in, supply light came on....now, finally, this morning they were able to take a cosmic run and EVERYBODY is showing up in YMon!</a></td></tr></table>
<!-- Author: bauerg -->


<!-- Date: Tue Nov 11 22:43:17 2003 -->
<pre>from this morning things looked ok... 
 
...but this afternoon, ace reports errors: 
 
(MLE) b0wcal04:Readout_Calib:1:52:10 PM-&gt;ADMEM=9 QIE=0 Fail 14: Sigma(off) 
big      (1.4950881) (0) (0) 
(b0wcal04) QIE calib: slot 09, qie 00:Fail 14: Sigma(off) big     , val 
01.4951, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 02:Fail 14: Sigma(off) big     , val 
01.6953, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 04:Fail 14: Sigma(off) big     , val 
01.7088, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 06:Fail 14: Sigma(off) big     , val 
01.9035, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 08:Fail 14: Sigma(off) big     , val 
01.2535, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 10:Fail 14: Sigma(off) big     , val 
01.6899, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 12:Fail 14: Sigma(off) big     , val 
01.4878, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 14:Fail 14: Sigma(off) big     , val 
01.5788, cap 0, rng0. 
(b0wcal04) QIE calib: slot 09, qie 16:Fail 14: Sigma(off) big     , val 
01.3495, cap 0, rng0. 
(b0wcal02) QIE calib: slot 05, qie 02:Warn 11: Sigma(off) high    , val 
00.6766, cap 0, rng0. 
(b0wcal02) QIE calib: slot 05, qie 02:Warn 10: Slope low          , val 
01.5449, cap 0, rng1. 
(b0wcal02) QIE calib: slot 05, qie 04:Warn 11: Sigma(off) high    , val 
00.7796, cap 0, rng0. 
(b0wcal02) QIE calib: slot 05, qie 04:Warn 10: Slope low          , val 
01.5171, cap 0, rng1. 
(b0wcal02) QIE calib: slot 06, qie 04:Warn 11: Sigma(off) high    , val 
00.7057, cap 0, rng0. 
(b0wcal02) QIE calib: slot 07, qie 00:Warn 11: Sigma(off) high    , val 
00.7891, cap 0, rng0. 
(b0wcal02) QIE calib: slot 07, qie 00:Warn 10: Slope low          , val 
01.5157, cap 0, rng1. 
(b0wcal02) QIE calib: slot 07, qie 04:Warn 11: Sigma(off) high    , val 
00.7415, cap 0, rng0. 
(b0wcal02) QIE calib: slot 07, qie 04:Warn 10: Slope low          , val 
01.5140, cap 0, rng1. 
(b0wcal02) QIE calib: slot 07, qie 10:Warn 11: Sigma(off) high    , val 
00.6173, cap 0, rng0. 
(b0wcal02) QIE calib: slot 08, qie 00:Warn 11: Sigma(off) high    , val 
00.7003, cap 0, rng0. 
(b0wcal02) QIE calib: slot 08, qie 02:Warn 11: Sigma(off) high    , val 
00.6171, cap 0, rng0. 
(b0wcal02) QIE calib: slot 08, qie 02:Warn 10: Slope low          , val 
01.5628, cap 0, rng1. 
(b0wcal02) QIE calib: slot 08, qie 14:Warn 11: Sigma(off) high    , val 
00.6413, cap 0, rng0. 
(b0wcal02) QIE calib: slot 09, qie 00:Warn 11: Sigma(off) high    , val 
00.7181, cap 0, rng0. 
(b0wcal02) QIE calib: slot 09, qie 00:Warn 10: Slope low          , val 
01.5259, cap 0, rng1. 
(b0wcal02) QIE calib:  
: 
: 
etc 
 
WCAL04 generally looks sort of ok when looking at calibs...but 
Gervasio saw problems with WCAL02. 
 
checked crate voltages, do not get a reliable reading for 2V: 
 
b0dap32.fnal.gov% ./tools/readadc b0wcal02 6 -get VTT 
[ 6.6] VTT = -943 bipolar internal clock 
  VTT voltage =  -1.936 V 
b0dap32.fnal.gov% ./tools/readadc b0wcal02 6 -get VTT 
[ 6.6] VTT = -381 bipolar internal clock 
  VTT voltage =  -0.782 V 
b0dap32.fnal.gov% ./tools/readadc b0wcal02 6 -get VTT 
[ 6.6] VTT = -381 bipolar internal clock 
  VTT voltage =  -0.782 V 
b0dap32.fnal.gov% ./tools/readadc b0wcal02 6 -get VTT 
[ 6.6] VTT = -381 bipolar internal clock 
  VTT voltage =  -0.782 V 
b0dap32.fnal.gov% ./tools/readadc b0wcal02 6 -get VTT 
[ 6.6] VTT = -944 bipolar internal clock 
  VTT voltage =  -1.938 V 
 
 
...so is it a read-back problem? or is the voltage flaky? 
couldn't make access late this afternoon cuz all locked up. 
try tomorrow to inspect in person.</pre>
<!-- Author: bauerg -->


<!-- Date: Wed Nov 12 09:24:44 2003 -->
<pre>Made access this morning to check out WCAL02. The 2V supply 
light is not on, and it looks like the (-5V) enable pin is not 
pushed all the way in. Pushe it in, PS light comes on, but 
flickers. Is that just the light? or is the PS actually flaky? 
Reading back VTT from readout now consistently returns 2V. 
Asked for a TOF calibration run, but it will take awhile before 
Ace can do it.</pre>
<!-- Author: bauerg & sumorok -->


<!-- Date: Wed Nov 12 11:25:24 2003 -->
<center><a href='/elog/notebooks/tof/Wed_Nov_12_2003_112438.ps'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-207' ></a><a href='/elog/notebooks/tof/Wed_Nov_12_2003_112505.ps'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-209' ></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Wed Nov 12 11;26;21 comment by...Gervasio -->
<pre>QIE calibration from November 11 at 20:25 </pre>


<!-- Date: Wed Nov 12 11:28:08 2003 -->
<center><a href='/elog/notebooks/tof/Wed_Nov_12_2003_112730.ps'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-211' ></a><a href='/elog/notebooks/tof/Wed_Nov_12_2003_112751.ps'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-213' ></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Wed Nov 12 11;28;48 comment by...Gervasio -->
<pre>TAC calibration from November 11 at 20:22</pre>


<!-- Date: Wed Nov 12 13:19:10 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-214&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-214  width='300' align='top'></td><td>TOF TAC calibration run 0x2a776 looks good.</a></td></tr></table>
<!-- Author: M Jones -->


<!-- Date: Wed Nov 12 14:12:31 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-215&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-215' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-216&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-216' width='300'></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Wed Nov 12 14;13;20 comment by...Gervasio -->
<pre>QIE calibration from November 12 at 12:45. Everything looks fine now.</pre>


<!-- Date: Wed Nov 12 14:22:23 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-217&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-217' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-218&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=-218' width='300'></a></center>
<!-- Author: Gervasio -->
<!-- Comment: Wed Nov 12 14;23;31 comment by...Gervasio -->
<pre>TAC calibration from November 12 at 13:06. 
All channels within "sanity" limits and all crates OK! </pre>


<!-- Date: Mon Nov 17 13:24:02 2003 -->
<pre>All TAC calibrations (runs 0x2a791, 2a7b9, 2a7c1, 2a80f, 2a8a6, 2a8c0) taken since the search and secure on 11/12 look fine. 
The QIE calibrations still indicate a minor problem with the 
ADMEM in slot 9 of b0wcal04.</pre>
<!-- Author: M Jones -->


<!-- Date: Mon Nov 17 13:30:33 2003 -->
Aha...  The ADMEM in slot 9 of b0wcal04 has serial number 369. 
You can check this using the 'admemsn' utility in the cdf_tof 
tools directory: 
<PRE> 
b0dap32:/cdf/people2/cdf_tof/tools/ ./admemsn b0wcal04 9 
Opened b0wcal04 - geo32:slot=9 
b0wcal04 slot 9: '0369 003 ADMEM_V4.0          460' 
</PRE> 
Searching for '369' in the TOF e-log brings up 
<a href= 
'/cgi/elog/det-system-elog.pl?nb=tof&action=view&page=1&frame=2&anchor=23:02:58'> 
this</a> entry.  It appears that this ADMEM was removed from the 
system for exactly this problem, but was returned to the pool of 
spares without being repaired.  We can probably run with it in 
this state, but we should plan to replace it soon.  It would be 
good to line up another spare.
<!-- Author: M Jones -->


<!-- Date: Mon Nov 17 23:37:27 2003 -->
<pre>Experimental TOF HV Control/Monitor Software 
Installed.  
 
~60-120 sec latency is expected between the turn on/off command   
in the HV Summary window in iFix and the time when the   
channel status is updated (both TOF HV bars and TOF rings display).  
 
The new software is experimental and will be upgarded asap,  
we expect anyway a much less rate of fake warning/alarms from  
TOF HV ...</pre>
<!-- Author: Stefano & Lucia -->


<!-- Date: Tue Nov 18 06:08:57 2003 -->
We lost the TOF heartbeat, and discovered the TOF HV PC performing in a sluggish Windows pseudo-hung sort of way. Irina and I followed the posted instructions to logout and restart the control processes; the heartbeat has returned.
<!-- Author: JeffMiles, IrinaShreyber -->


<!-- Date: Tue Nov 18 19:35:22 2003 -->
<pre>TOF PC crashed. 
PC rebooted, smacs&iFix restarted and DEF. HV setup file  
reloaded. 
Everything fine now.</pre>
<!-- Author: Stefano -->


<!-- Date: Sat Nov 22 23:04:22 2003 -->
<pre>TOF had a heartbeat problem.  I looked at the PC on the first floor, and SMACS had crashed with the following error: 
 
Run-time error '6', Overflow 
 
I restarted SMACS via the instructions, and it looks OK now.</pre>
<!-- Author: Ben (Monitoring Ace) -->


<!-- Date: Sun Nov 23 08:09:37 2003 -->
<pre>TOF PC was hung. I had to reboot it.</pre>
<!-- Author: M. Casarsa -->


<!-- Date: Sun Nov 23 12:05:39 2003 -->
<pre>The last two TOF TAC calibrations have been bad.  It looks like 
no valid data is found in any channel.  So something is screwed 
up... maybe the clock?</pre>
<!-- Author: M Jones -->


<!-- Date: Sun Nov 23 21:51:47 2003 -->
<pre>I looked into the calibration problem.  I verified that we 
do see the common stop and the reset signal in the crates 
so I expect that we can take valid data.  But, there is no 
CAL output from the CIC card that triggers the DDG.  I tried 
to get an output from the other DDG in the crate which appears 
to have TS code 127, but also did not see a CAL signal out of 
the CIC card.  I rebooted b0puls01 but that had no effect. 
So, I think the next things to try are: 
1.  Swap the CIC card for the TOF DDG...  Actually, just put in 
    a new CIC card but don't install the DDG until you see that 
    the CAL signal comes out of the new CIC card.  The TS 
    address on the DIP switches needs to be set the same on 
    both old and new cards to give TScode=3. 
2.  If that doesn't work, then maybe there is a run control or 
    other software problem.  Maybe Bill Badgett has an idea 
    about this. 
3.  If it's a crate problem then maybe we need Frank. 
 
I'll be back on Wednesday and will be in touch be e-mail and 
phone.  Have fun...  </pre>
<!-- Author: M Jones -->


<!-- Date: Thu Nov 27 11:18:15 2003 -->
<pre>TOC PC was frozen. Was reset/rebooted. We were taking data, 
so followed the procedure accordingly. It was fine after that.</pre>
<!-- Author: R. Tafirout -->