<!-- Title: 23:04:06  Sun Oct 26 2003 -->
<!-- Crewchief: The SiliCrew -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<h1> finish up that shutdown. </h1>


<!-- Date: Sun Oct 26 23:07:46 2003 -->
<table border=0><td><tr><td bgcolor=#e0e030><center> <h1> Results of TestFest II </h1> </center></td></tr></td></table>
<!-- Author: The Silis -->
<!-- Comment: Sun Oct 26 23;11;16 comment by...Florencia, Julia, Jared, Jason, Reid, Rainer, Pete, SCN consulting.  -->
<center> aka  <h2> The Master(S)hitlist  </h2></center> <p>

<table> 
<tr><td> <BR>  <h1>b0fib00:</h1></tr>  
<tr> <th> ladder <th> slot# <th> new  ?<th> TF1? <th> comment <th> follow up?   </tr>

<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L3'>  SB0W3L3</a> <td> #11<td> X	<td>	        <td> <font color="blue">cap id problem which stays with ladder. NOT seen in TF1. - suggest LLM.             <td> Y </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L4'> SB0W3L4 </a><td> #11<td>   <td> 		<td> <font color="blue">persistent bit#2 low - swapped fibers - problem stays with DAQ channel. swap RX.    <td> Y </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=L0'> SB1W1L0 </a> <td> #12<td> X	<td> TF1	<td> <font color="blue">bit#6 low even after RX swap and fiber check - FIB or FTM problem. swap FIB.                        <td> Y </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L2'> SB1W2L2</a> <td> #13<td> X	<td> TF1 	<td> <font color="blue"> 'moving' bad chip - FIB or FTM problem. VRB excluded. swap FIB.                     <td> Y </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3L0 <td> #13<td>   <td>     TF1	<td> RX swap fixed problem. confirmed ok in TF2.                                        <td> N <tr><tr><td> <a href='http://www-cdfonline.fnal.gov/~lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2'> SB1W3L2 </a><td> #13<td>   <td>		<td> <font color="blue"> bit#3 problem NOT seen in TF1  - swapped fibers - problem stays with DAQ channel. swap RX. <td> Y </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W3&layer=L2'> SB2W3L2 </a> <td> #18<td><td>	TF1	<td>RX swap fixed problem. confirmed ok in TF2.                                         <td>N </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W2&layer=L4'> SB2W2L4 </a><td> #18<td> X	<td> TF1	<td> <font color="red">  no init, odd OO sequence - swapped fibers - stays with ladder. que faire ? no idea what to do. <td> Y </tr>
<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L4'> SB0W11L4 </a>  <td> #19 <td> <td>  <td>  <font color="blue"> no init, no data  - swapped fibers - problems stays with DAQ channel. swap RX.      <td> Y </tr>


 <tr> <td><BR><h1> b0fib01:</h1> </tr> 

<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W3&layer=L4'> IB1W3L4 </a>  <td> #10<td> X <td> TF1 <td> <font color="blue">    RX swap fixed problem. confirmed ok in TF2. However, is reported yellow in SVXMON in cosmics running. Needs further understanding.<td> Y </tr>

<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W4&layer=L4'> IB1W4L4 </a> <td> #11<td>   <td> ??  <td>   <font color="blue"> VBIAS1=0, no problem in PDB reported. Mostly current=0 but spikes of order of 10 muA were seen before shutdown.automatic and manual dnoise evaluation diasgree - redo latter and probe connector. <td> Y </tr>
<tr><td>  LB0W2L3 <td> #16<td>   <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W3L0 <td> #16<td>   <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W3L1 <td> #16<td>   <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W3L2 <td> #16<td>   <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector.<td> Y </tr> 
<tr><td>  LB0W3L3 <td> #16<td>   <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>


<tr><td><BR>  <h1>b0fib02:</h1></tr>  


<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W4&layer=L3'> SB1W4L3</a> <td> #12 <td> X  <td>       <td>   <font color="red">    flaky init, cap ID errors. NOT seen in TF1. tried second time, ladder runs fine. dooh ?  <td> N </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W5&layer=L4'> SB1W5L4 </a> <td> #12  <td>        <td>   TF1 <td>   bias unclear due to too many bit errors - probe connector.                      <td> Y </tr>
<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W6layer=L4'> SB1W6L4 </a> <td> #13 <td> X  <td> 	TF1 <td>   <font color="red"> persistent trip on DVDD after shutdowns. out of HWDB for now.                   <td> Y </tr>


<tr><td> <BR>  <h1>b0fib03:</h1></tr>  

<tr><td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B0W4&layer=L4'> IB0W4L4 </a>  <td> #8<td>    <td> TF1 <td>     RX swap fixed problem. confirmed ok in TF2. <td> N </tr>
<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B0W5&layer=L4'> IB0W5L4 </a> <td> #8<td>   <td> ??  <td>   <font color="blue">   VBIAS0=0, no problem in PDB reported and current ~5muA were seen before shutdown.automatic and manual dnoise evaluation diasgree - redo latter and probe connector. <td> Y </tr>



<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B0W0&layer=L0'>  LB0W0L0 </a> <td> #18 <td>    <td> TF1 <td>     intermittent bit#3 error. RX swap fixed problem. confirmed OK in TF2. bias unclear. probe connector        <td> Y </tr>
<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B0W0&layer=L1'>  LB0W0L1 </a> <td> #18  <td>     <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>

<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B0W0&layer=L2'>  LB0W0L2 </a>  <td> #18 <td>     <td>     <td>     no init once or twice but sees data, confirmed OK in TF2. also init ok.                            <td> N </tr>
<tr><td>  LB0W0L3 <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W1L3 <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W4L1 <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W4L2 <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W4L3 <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W5L1 <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W5L2 <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>


<tr><td> <BR> <h1>b0fib04:</h1></tr>  
<tr><td>  None! <td> </tr>


<tr><td>  <BR> <h1>b0fib05:</h1></tr>  
<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B4W4&layer=L4'> IB4W4L4 </a> <td> #10<td>   <td> ??  <td>   <font color="blue">   VBIAS1=0, no problem in PDB reported. Mostly current=0 but spikes up to 5 muA were seen before shutdown.automatic and manual dnoise evaluation diasgree - redo latter and probe connector. <td> Y </tr>

<tr><td>  LB1W2L0 <td> <td>       <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W2L1 <td> <td>       <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W2L2 <td> <td>       <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W2L3 <td> <td>       <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W3L0 <td> <td>       <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W3L1 <td> <td>       <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W3L2 <td> <td>       <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB0W3L3 <td> <td>        <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>


<tr><td>  <BR> <h1>b0fib06:</h1></tr>  

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B3W6&layer=L2'> SB3W6L2 </a> <td> #9 <td> <td> TF1         <td> no init, no data. RX  swap fixed problem. confirmed OK in TF2.   <td>  N </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B3W7&layer=L2'> SB3W7L2 </a> <td> #9 <td> X <td>  TF1 <td>     <font color="red">  no init, no data seen, persistent trips. out of HWDB for now.     <td> Y </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B3W8&layer=L0'> SB3W8L0 </a> <td>  #10 <td> X <td> TF1 <td>    no init every other time. has tendency to trip. OK for now.       <td> N </tr>

 </tr> <tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W4&layer=L0'> SB4W4L0 </a> <td>  #11 <td> X <td> TF1 <td>     DVDD/2VDOIM short, persistent tripper, out of HWDB for now.       <td> Y </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W4&layer=L3'> SB4W4L3 </a> 	<td> #11 <td> X <td> 	<td> <font color="red"> new persistent trip on AVDD/DVDD after this shutdown. Not seen in TF1. out of HWDB for now. <td> Y </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W6&layer=L3'> SB4W6L3 </a>	<td> #12 <td>  	<td>	<td>no init, bit#3 dead at bore, seen in TF1 and TF2. <td> Y </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W7&layer=L3'> SB4W7L3 </a>        <td>  #12 <td> X	<td>TF1	<td> <font color="red"> no init, data OK, seen in TF1. new init problem, RB masked.             <td> N </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W7&layer=L4'> SB4W7L4 </a>    <td>  #12 <td> X	<td>TF1	<td><font color="red"> no init, data OK, seen in TF1. new init problem, RB masked.            <td>  N </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W8&layer=L3'> SB4W8L3 </a><td>  #15 <td> X	<td>TF1	<td><font color="red">  no init, data OK in TF2. seen in TF1. new init problem, RB masked. <td> N </tr>

<tr><td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W7&layer=L0'> SB5W7L0 </a>	<td> #18 <td> X	<td>	<td>no init, no data, NOT seen in TF1. trips in RA mode but runs fine in Sparse/NN w/ SVXDAQ. inits fine in RC. 
                                            phi side gives data in SVXMON, z side is dead/chopped. <td>N  </tr>

<tr><td>  <BR> <h1>b0fib07:</h1></tr>  


<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L1'> IB5W1L1 </a> <td> #10<td>   <td> ??  <td>   <font color="red">   flaky init, data check ok with SVXDAQ. Rb masked. <td> N </tr>

<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B5W5&layer=L2'> IB5W5L2 </a> <td> #11<td>   <td> ??  <td>   <font color="blue">   VBIAS0=0, no problem in PDB reported and currents much in excess of 20 muA were seen before shutdown, but also fluctuating. automatic and manual dnoise evaluation diasgree - redo latter and probe connector. <td> Y </tr>

<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B1W0&layer=L0'> LB1W0L0  </a> <td> #16 <td> <td>      <td>bit#6 low fixed by RX swap. operator error on RX swap - retest TF2 result ok. bias unclear. probe connector. <td> Y </tr>
<tr><td>  LB1W0L1  <td> <td>         <td> <td> bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B1W0&layer=L2'>  LB1W0L2 </a> <td> #16  <td>		 <td>    <td>  wrong cable was plugged   - retest TF2 result ok.    bias unclear. probe connector <td> Y </tr>.
<tr><td>  LB1W0L3  <td> <td> 		<td>      <td>  bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W4L0  <td> <td>      <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W4L1  <td> <td>     <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W4L3  <td> <td>     <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W5L0  <td> <td>     <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W5L2  <td> <td>     <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>
<tr><td>  LB1W5L3  <td> <td>     <td> TF1 <td>     bias unclear in current and dnoise comparison N/A - probe connector. <td> Y </tr>

</table>



<!-- Comment: Wed Oct 29 11;13;38 comment by...David -->
<pre>The L00 leakage currents can be plotted with the power supply plotter from the quiet time bias scan done on August 28 (DS day 969) - run# 168313 (22:00-22:02) was set at nominal bias voltage. Compare these with the leakage currents now to find ladders that may be unbiased.</pre>
<!-- Date: Sun Oct 26 23:17:13 2003 -->
<b> Explanation of Color Code: </b> (somehow you gotta keep track of that sh..... ) <BR> 
 
<table> <tr> <th> </tr> 
<tr><td> <font color="red"> RED <td> new problem acquired in this shutdown. A step back wrt. to before shutdown.  </tr> 
<tr> <td> <font color="blue"> BLUE<td> work still be to performed on ladders. </tr> 
</table>
<!-- Author: Rainer -->


<!-- Date: Sun Oct 26 23:33:30 2003 -->
  <h1>More Happy Happy Laundry Lists:</h1> 
 
    <li> The NoInit TroubleMakers list is <a href='http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=23:22:50'>here.</a>  
 
    <li> The TakenOutOfHWDB  list is <a href='http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=21:58:14'> here.</a>  
 
 
 
    <li> The Pinkie list is <a href='http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=08:17:47'> 
here. </a>  
 
    <li> The ProbeTheBiasConnection list will be compiled by Reid. It will be useful to consult the scary 3+1 ISL Stooges with missing bias currents found <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=22:35:26'> 
 here.</a>  
 
    <li> The SwapTheRX'n'FIB list will probably be ticked off by David K. Clark 
         before it even is compiled/extracted from above.  
<!-- Author: Rainer -->


<!-- Date: Sun Oct 26 23:40:14 2003 -->
<h2> On How to Proceed </h2> <p> 
 
Tomorrow will bring involuntary power cycle due to IFIX  upgrade. <p> 
1) Swap RXs and FIBs. Resolve all RX/FIB/FTM issues. <BR> 
2) Re-evaluate Pete's program with increased statistics (running over night)  <BR> 
3) Probe 4 ISL connections plus any L00 connection not previously 
   checked during the baggy ring installation. <BR> 
 
4) With system back up, try to understand mismatches between 
   automatic and manual dnoise comparisons by re-running. 
<BR> 
5) Evaluate Error Log Files from Calibration  and Cosmic Runs/ SVXMon etc. <BR> 
 
<b> 6) based on 1) -5) (and more ?) decide whether re-opening of plug necessary. <BR> 
  
<!-- Author: Rainer -->
<!-- Comment: Mon Oct 27 12;45;29 comment by...HTML expert -->
</b>un-bold
<!-- Comment: Tue Oct 28 14;51;10 comment by...an html dummy -->
<pre>thx.</pre>
<!-- Date: Mon Oct 27 04:33:38 2003 -->
<p><font size=+1> D-mode Calibration Job Finished </font>
<p><pre>
This is a computer-generated silicon D-mode calibration status report.
Silicon D-mode calibration job 291 finished successfully.

Job info
--------
Calibration type : nonstandard
DPS-off run      : 172170
DPS-on run       : 172169
Requested by     : Monica D'Onofrio
Submitted        : 2003-10-26 19:47:14
Completed        : 2003-10-27 02:32:42
Status           : SUCCESS
Comment          : magnet-off + ignore Inhibits + L1Mode: calib cont.+L2Mode: auto L2 Accept
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->



<!-- Date: Mon Oct 27 07:25:03 2003 -->
<b> SVXMon displays of ~ 8 hours cosmics running  </b>
<!-- Author: Rainer -->


<!-- Date: Mon Oct 27 07:27:02 2003 -->
<center><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_072536.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2776' ></a><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_072602.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2778' ></a><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_072620.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2780' ></a><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_072638.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2782' ></a></center>
<!-- Author: Rainer -->
<!-- Comment: Mon Oct 27 10;47;59 comment by...Rainer,SCN -->
IB1W3L4 DRO c2c2 in cosmics running. was reluctant to init <a href=
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=09:38:28'>
earlier</a> in TF1, coming out of the long cold.




<!-- Date: Mon Oct 27 11:16:32 2003 -->
<b> Manual Dnoise Bias Investigation re-visited </b> on 
<li>IB0W5L4 
<li>IB1W4L4 
<li>IB4W4L4 
<li>IB5W5L2  
<p> 
The bias situation on these was unclear from automatic dnoise program by pete, see 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=22:35:26'> 
here </a> 
<!-- Author: Ben, Rainer -->
<!-- Comment: Mon Oct 27 18;11;20 comment by...Rainer -->
<pre>
IB0W5L4 IBIAS0=0
IB1W4L4 IBIAS1=0
IB4W4L4 IBIAS1=0
IB5W5L2 IBIAS0=0
</pre>
<!-- Date: Mon Oct 27 11:19:30 2003 -->
<center><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_111729.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2784' ></a><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_111742.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2786' ></a><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_111751.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2788' ></a><a href='/elog/notebooks/silicon/Mon_Oct_27_2003_111804.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2790' ></a></center>
<!-- Author: Ben, Rainer -->
<!-- Comment: Tue Oct 28 16;03;28 comment by...Rainer -->
Using the 
<a href=
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=172&frame=2&anchor=19:23:54'>
ISL dummy list </a> we conclude (from left to right to bottom): <BR>
<li> IB0W5L4 Bias0: maps to the third group of chips which show change (modulo one chip maybe ...) - BIASED. 
<li> IB1W4L4 Bias1: maps to last group of chips which show change - BIASED.
<li> IB4W4L4 Bias1: maps to last group of chips which show change - BIASED.
<li> IB5W5L2 Bias0: maps to the third group of chips which show change - BIASED.
<!-- Date: Mon Oct 27 12:46:50 2003 -->
Cooling back to normal after APACS firmware upgrade chaos. (SVX chiller compressor tripped, SVX/ISL main supply valves closed)
<!-- Author: Andy H. -->


<!-- Date: Mon Oct 27 17:06:12 2003 -->
<p>Tested Yimei and Andrew's 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=19:37:21'> 
software CAEN crate reset</a> on crate 2 (NW Top Bot) with David C. watching the crate front panel.  Seems to work fine.  
</p> 
<p>Now the question is, will this work on a crate when the communication has already failed?  <b>So, next time a crate needs to be "hockerized," please try typing "ResetCrate(n)" (without quotes) in the svxinter window.</b>  n is the crate number (which iFix will tell you). 
</p>
<!-- Author: Andy H. -->



<!-- Date: Mon Oct 27 19:23:54 2003 -->
 
<table> 
<tr> <th> type <th> ISL0 <th> ISL1  <th> phi <th> phi <th> z <th> z </tr> 
 <tr>   <td>      <td> B0-1,B4-5 <td> B2-3      <td>     <td>     <td>   <td>    </tr> 
 <tr>   <td> chip#     <td>      <td>  <td> 0...3<td> 4...7 <td> 8...11  <td>12...15 </tr> 
 <tr>   <td> chip id     <td>      <td>  <td> 8f...8c<td> 9b...98 <td>  b7...b4   <td>  a3...a0  </tr> 
 <tr>   <td> BIAS  <td>   <td>   <td>    1  <td>  0     <td>  0   <td>  1   <td>   <td>    </tr> 
 <tr>   <td> MICR    <td>  L0,L2,L4  <td>   <td>   p    <td>   p  <td>  n    <td>   n  <td>        </tr> 
 <tr>   <td> HPK   <td>  L1,L3  <td>  L0-L4     <td>   n  <td>   n  <td> p <td> p   </tr> 
<h1> ISL for Dummy Experts </h1> 
</table> 
<p> 
<table> <th> CAEN/HDI channel <th> JC channel nr. </tr> 
<tr> <td> 4 <td> 1 </tr> 
<tr> <td> 3 <td> 4 </tr> 
<tr> <td> 2 <td> 5 </tr> 
<tr> <td> 1 <td> 2 </tr> 
<tr> <td> 0 <td> 3 </tr> 
</table>  
<!-- Author: Rainer, CHill consulting -->

<!-- Date: Mon Oct 27 19:42:31 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W11L4 
<li>problem n: 1135 
<li>Status: needs_study_time
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: canelli 
<li>description is: The RX DOIM cable was broken. Needs testing<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0794">0794</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0695">0695</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Oct 27 19:49:39 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W0/1All 
<li>problem n: 1142 
<li>Status: needs_study_time
<li>Type: Other
<li>Action: Swap_FIB
<li>entered by: canelli 
<li>description is: bit#6 low in channel 5 even after swapped RX so we  swapped FIB. Needs testing.<table border=1>
<tr><td><b>IN</b></td><td>PREP:</td><td>550954</td><td>Serial:</td><td>153</td></tr>
<tr><td><b>OUT</b></td><td>PREP:</td><td>560608</td><td>Serial:</td><td>112</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W0/1&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Oct 27 19:49:39 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W1L0 
<li>problem n: 1122 
<li>Status: needs_study_time
<li>Type: Unknown
<li>Action: Action_request
<li>entered by: canelli 
<li>description is: swapped FIB, still needs testing. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Oct 27 19:53:38 2003 -->
<h1>Access Summary</h1> 
<ul><li> 
Swapped FIB in slot 12 of FIB00 for SB1W1L0.</li> 
<li>Swapped RX for SB0W11L4.</li></ul> 
Both still need testing and the FIB crate is off. 
<!-- Author: Florencia and David -->


<!-- Date: Tue Oct 28 10:21:22 2003 -->
<h2><font color=red>2 SRC testing</font></h2> 
Moving an upgraded SRC into b0svx02 for testing new  firmware with guinea pigs. So revert this if you want the conservative one SRC sneezy thing. 
  
<!-- Author: Lester Sal SCN -->
<!-- Comment: Tue Oct 28 10;42;52 comment by...Lester -->
<pre>Also turning on 5V enables to power guinea pig e481.
(Note someone should change Rdriver to 7 for this ladder in the
hdwdb).
</pre>

<!-- Comment: Tue Oct 28 11;46;11 comment by...SCN, Lester, Sal -->
<h3>Many Actions Taken to get Guinea Pig e481 into RC</h3>
<ol>
<li> Disabled the SVXII kill switch
<li> Enabled the Interlocks on BHE2 (Bulkhead 4).  Disabled them
on Bulkhead 3 (don't know why this one was left enabled, but that is how we found it)
<li> Edited CAENvolts.dat by hand to include e481
<li> Edited CAEN.map to remove all NW CAEN crates, since the 400 Hz is off there for the next few hours
<li> Edited HDWDB crate b0fib06 <ol>
<li> Set ONLINE = 0 for all FIBs except the one in Slot 15 (e48/9x)
<li> Set ONLINE = 0 for ChipChains 0,3,4,5,6,7,8,9 for FIB in slot 15  (ChipChain 2 is already set to 0, so was left untouched.)
<li> Set ONLINE = 1 for Chipchain 1 (e481) 
</ol>
</ol>
The development version of the SRC in running in Normal (non-tracer) mode now, roughly 30 Hz L1A = L2A, into the SEVB,
run number 172265.<P>
All this stuff needs to be undone before using b0fib06 in 
run control. Also, we need an executive decision near the end of the day as to whether to leave this SRC in or revert back to the old one.  The West side (currently NW, but it may move to SW as well) Racks have no 400 Hz.  When they are done (this afternoon?) they may move to the East side, or this may happen tomorrow.
<P>
As far the new SRC goes, we have verified that it will at minimum send a keepalive signal every 9 ms, if not earlier, independent
of the number of L1A pending (The L2 timeouts are on the order of 1 ms, so we should not interfere with real data taking).  The only thing this minimum depends upon is CDF CLOCK and power to the SRC (once initialized).

<!-- Comment: Tue Oct 28 13;50;55 comment by...SCN -->
Update.  400 Hz back on the West (actually, Northwest.  It was never gone on the South West).  Electricians have
moved to the North East.<BR>
Our plan is to get new firmware into the 2nd SRC, and attempt
a two SRC run with Guinea Pigs on each SRC.
<!-- Comment: Tue Oct 28 15;50;12 comment by...Lester -->
Further guinea pig configuration changes.<br>
<ul>
<li> Turned online b0fib03 slot 17 channel 0 (f840)
<li> Turned offline all ladders in b0fib03 slot 17 except channel 0 
(and 4 and 9 which don't exist in L00 wedges)
<li> Turned offline all other fibs in crate
<li> Turned online b0fib00 slot 10 channel 6 (e0b1)
<li> Turned offline all other channels in this fib 
<li> Turned offline all other fib slots in this crate
</ul>
In order to run this, just get up an svx calibration configuration and run with all VRBs and fibs 00,03,06.
Same for cosmics, just ask ace to add all vrbs and those fib crates. <br>
Lester
<!-- Comment: Tue Oct 28 18;17;26 comment by...Rainer -->
<pre>Plan is to run with three guinea pigs and 2 SRCs parasitically
over night in run control.</pre>
<!-- Date: Tue Oct 28 12:43:05 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W7L0 
<li>problem n: 1139 
<li>Status: fixed
<li>Type: jumper
<li>Action: Diagnosis_update
<li>entered by: bolla 
<li>description is: This is broken since a year. See thread 661. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W7&layer=L0">report</a></ul>
<!-- Author: Problem DB -->







<!-- Date: Tue Oct 28 17:03:58 2003 -->
<pre>Swapped RX in channel SB1W3L2 and SB0W3L4. 
FIB 00 is now ON.</pre>
<!-- Author: Florencia and David -->

<!-- Date: Tue Oct 28 17:10:20 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L4 
<li>problem n: 1137 
<li>Status: needs_study_time
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: canelli 
<li>description is: Swapped RX. Still needs testing.<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0855">0855</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0173">0173</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Oct 28 17:13:43 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_study_time
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: canelli 
<li>description is: Swapped RX. Still needs testing.<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0855">0855</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0173">0173</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Oct 28 17:20:39 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L4 
<li>problem n: 1137 
<li>Status: needs_study_time
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: canelli 
<li>description is: Ignore previous entry.<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0809">0809</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0294">0294</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Tue Oct 28 19:49:26 2003 -->
<h1> 2SRC Guinea Pig Fest! </h1> <BR> 
 
guinea pigs are happily oinking on 2 SRC for this night in a regular cosmics run and are left as a bait for the devil inside the SRC. if he does not show up by tomorrow morning, silicon is ready to wake up to 2SRCs -slowly, ladder by ladder and wedge by wedge. We will have to wait though for the electrician to finish work on NE corner.  <br> 
once this is done, the objective is to certify that the few bit errors we had on b0fib00 were taken care of by RX swaps and hopefully devote some time to TLC of SB4W4L3 and the likes. <br> 
There is still a bias question of L00  but there seems to be no ladder in L00 which had current earlier and does not show current now. maybe there is something to be learned by David & David's quiet time bias scans as well.  
<!-- Author: Rainer, thanks to the DAQ&SRC guys (Sal, Lester, SCN) -->
<!-- Comment: Wed Oct 29 00;06;27 comment by...a fan of the sili guinea pigs. -->
<pre><a href=
'/cgi/elog/elog.pl?nb=2003&action=view&page=902&frame=2&anchor=20:50:13.304'>
this </a> is how it should look like!</pre>

<!-- Comment: Wed Oct 29 00;06;48 comment by...a fan of the sili guinea pigs. -->
<pre><a href=
'/cgi/elog/elog.pl?nb=2003&action=view&page=902&frame=2&anchor=20:50:13.304'>
this </a> is how it should look like!</pre>

<!-- Comment: Wed Oct 29 00;07;44 comment by...fan of guinea pigs -->
more like <a href=
'/cgi/elog/elog.pl?nb=2003&action=view&page=902&frame=2&anchor=20:50:13.304'>
this </a> 

<!-- Comment: Wed Oct 29 00;14;04 comment by...rainer -->
<b> pigfest errors on terminate
run <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=172350'>172350 </a>

</b>
<pre>  State       ACTIVATE
(MLE) b0clc00:Messenger:11:24:53 PM->VISIONread/write failed in slot 8
(MLE) b0clc00:Messenger:11:24:53 PM->Event 16197: Bunchcounters in slot 16 (BC=131) and slot 21 (BC=54) disagree (L2B=0) 
L2B 16: 131  60  72 122
L2B 21:  54   0   0   0
EHx: 01C50577 01D20577 01E30577 01F40577
(MLE) b0clc00:Messenger:11:24:53 PM->Runtime Error 1, Event 16197: Bunch counter mismatch, mismatch count = 1
(MLE) b0dap73.fnal.gov:Thread-2952:11:25:01 PM->FrontEnd Error: VRB_SVX_02 
CT: 2003.10.28 23:25:05
25'5" 1 crate/s: b0svx02(112),  in error.[RXPT]
(TS)   0:25:30 ********* L2 trigger rate has dropped to 0 Hz! Events are not being logged !
(MLE) b0svx02:Messenger:11:39:01 PM->SRC Fatal Error:Sl 5 L2A w/o L1A 2 L1A to Buff 

(RC)   0:39:7 Halt -> HALTED
(RUN Comment) rundb.RunComment@c46cfc
  RunNumber   172330
  CreateTime  2003-10-28 23:49:57.0
  TextComment b0svx02 went red
  Name        Andrei x2080
  State       TERMINATE
</pre>

<!-- Comment: Wed Oct 29 00;16;16 comment by...rainer -->
correct link <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=172330'>here</a>


<!-- Comment: Thu Oct 30 14;48;58 comment by...Rainer -->
Seems like the SiliGuineaPigs have attracted a new
<a href=
'/cgi/elog/elog.pl?nb=2003&action=view&page=902&frame=2&anchor=20:50:13.304'>
fans </a>
<!-- Date: Wed Oct 29 08:52:33 2003 -->
<ol> 
<li> Electrician takes NE 400 Hz down for Electrical work-Removed 
NW CAEN crates from CAEN.map 
<li> Dervin is investigating problems with Motor Generator 3, and 
may trip all (Silicon) 400 Hz. 
</ol> 
As a result, all Guinea Pigs are turned <b>OFF</b> and Kill Switched are ENABLED.  We left the 2 SRCs playing with the TS, 
but address 0x28002080 in b0svx02 and 06 is set to 1 (ignore VRBs).  It should be set back to 0 before taking data with real ladders.
<!-- Author: SCN -->


<!-- Date: Wed Oct 29 09:39:16 2003 -->
<h3>SRC Errors as of late</h3> 
<ol> 
<li> <a href="http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=172177">Run 172177</a> (<a href="http://www-cdfonline.fnal.gov/daq/runSummary/errorlog/errorfile172177.log">Error Log</a>).  Error was "L2A w/o L1A" implying  
a L1A buffer was either dropped or swapped.  This was with the 
OLD trusty SRC.  HRR recovered. 
<li> <a href="http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=172307">Run 172307</a> (<a href="http://www-cdfonline.fnal.gov/daq/runSummary/errorlog/errorfile172307.log">Error Log</a>).  Error was "Gap Error" which is when the SRC thinks the Gap ended before a PREAMP RST Stop.  Run was ended (not clear a HRR wouldn't have fixed it)  This one and the following ones are all with the new SRC in b0svx02 
<li> <a href="http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=172330">Run 172330</a> (<a href="http://www-cdfonline.fnal.gov/daq/runSummary/errorlog/errorfile172330.log">Error Log</a>). Error was "L2A w/o L1A" and  "2 L1A to Buff". 
This also indicates that a L1A buffer was misconstrued, resulting in 
sending 2 L1A to the same buffer, and asking for a L2A on a buffer without a L1A.  Run ended (HRR may have worked?) 
<li> <a href="http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=172355">Run 172355</a> (<a href="http://www-cdfonline.fnal.gov/daq/runSummary/errorlog/errorfile172355.log">Error Log</a>). Error was "Gap Error", again, indicating some oddity with the Clock Structure 
</ol> 
Hypothesis: Misconstruing buffers means misreading TAXI commands, however the Gap structure issue implies something askew with SRC clocking, which could in principle also generate the TS problems. 
No indication of Clock Errors, however, I have noticed some finicky-ness of the SRC when nothing is loaded into its Clock Emulator-which I believe we did not do yesterday.  Since the problem exists with both old and new SRCs, it does not seem to 
be a "2 SRC firmware" issue.<P> 
Action: Download the Master Clock in both SRCs (even though it is unused) and try to see if it happens again?  Set up LA to trigger on Error.
<!-- Author: SCN -->



<!-- Date: Wed Oct 29 12:22:04 2003 -->
<h3>SRC Firmware Update : RSM 33</h3> 
<ul> Changes from RSM 32: 
<li> Added SRC ERROR to LA Port, RSM0, Port 7 </li> 
<li> Added DUMP_Q to clear TSLCOUNTER </li> 
</ul> 
 
<ol><b>Have 2 SRCS:</b> 
       <li> b0svx02, slot 5 = Crate 0 (SRC 1)</li> 
       <li> b0svx06, slot 5 = Crate 6 (SRC 2)</li> 
</ol> 
 
<ul><b> Checking them out:</b> 
<li> Installed the new proms (RSM 33) with ERROR on LA 0, port 7, 
  and DUMP_Q resetting TSLCOUNTER</li> 
<li> Downloaded mclock to both SRC's</li> 
<li> Set "NO_VRBS" flag for both: 
	  <ol> 
	    <li> Crate 0, Address 0x28002080 = 1</li> 
	    <li> Crate 6, Address 0x28002080 = 1</li> 
	  </ol></li> 
<li> Triggering on SRC ERROR from 1 or 2.  
	    <ol> Illegal commands: 
	      <li> Crate 0 (SRC 1): Two L1A's to the same buffer:Okay </li> 
	      <li> Crate 6 (SRC 2): Two L1A's to the same buffer:Okay </li> 
	      <li> Crate 0 (SRC 1): L2A w/o L1A : Okay </li> 
	      <li> Crate 6 (SRC 2): L2A w/o L1A : Okay </li> 
	     </ol></li> 
<li> Triggering on Keepalives in both SRC's. Present in Halt, Recover, Run 
    for both SRC's</li> 
<li> Used SRC FIFO Manager to test trigger on illegal conditions as well, checked okay</li> 
</ul>
<!-- Author: Sal and Lester -->


<!-- Date: Wed Oct 29 13:44:34 2003 -->
<h1>No cooling to ISL/SVX port cards</h1> 
<p> 
Apparently steel-movers damaged the main ISL supply pipe in the assembly hall.  A large amount of air was introduced into the system.  We currently have flow shut off to ISL and the SVX PCs and are trying to pump out the air as best we can.  Still need to assess how much repair to the pipe will need.</p>
<!-- Author: Andy H., Rob R. -->
<!-- Comment: Wed Oct 29 16;48;07 comment by...Andy H., Rob R., Mike L. -->
Found cracked pipe fitting at the supply/return jumper line.  Repaired jumper assembly, waiting for expoxy to cure.  After that we'll get system flowing again, get the air out, and then re-establish flow to detector.


<!-- Date: Wed Oct 29 22:11:35 2003 -->
<table border=0><td><tr><td bgcolor=#e0e030>Please use caution if you choose to put HTML into an entry.  Forgetting to use a close tag for each open tag will certainly cause problems. 
 
If you choose to use plain text, PLEASE USE CR's since this text window automatically wraps the text and gives the illusion of CR's.   (click to clear this message) 
</td></tr></td></table>
<!-- Author: Andy H. -->
<!-- Comment: Wed Oct 29 22;12;23 comment by...Andy H. -->
Let me try that again....


<!-- Date: Wed Oct 29 22:25:19 2003 -->
<table border=0><td><tr><td bgcolor=#e0e030><h1>Cooling status</h1> 
<p> 
ISL/L00 cooling is back to normal.  However, we appear to have air bubbles trapped in some of the SVX PC rings; we are not getting full flow through the PC cooling circuits and some of the PC temperatures are not reading +6 degrees, but several degrees cooler instead -- indicating that they are seeing the cold (not quite -6 degrees) SVX ambient temperature instead of the coolant temperature.</p> 
<p> 
We can probably get these air bubbles out by overpressuring these lines, but that requires some caution, discussion, and sign-offs.</p> 
 
</td></tr></td></table>
<!-- Author: Andy H. -->


<!-- Date: Thu Oct 30 10:10:49 2003 -->
Here is a link to the summary of the bias check-up after the january shutdown. At the time we relied on the changes in noise versus bias for the ladders with 0 current (this is true for ISL SVXII and L00) 
<p> 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=139&frame=2&anchor=08:11:00'> 
Link to the end of January shutdown </a>   
<!-- Author: Gino -->


<!-- Date: Thu Oct 30 10:37:58 2003 -->
<h3>SRC Errors</h3> 
Found 4 runs with SRC errors from last night: 
<ol> 
<li> <b>172469</b> : Too Many L1A 2 L1A to Buff.  </li> 
<li> <b>172470</b> : No Scan Buff Too Many L1A L2A w/o L1A 2 L1A to Buff Gap Error. </li> 
<li> <b>172471</b> : No Scan Buff Too Many L1A L2A w/o L1A 2 L1A to Buff Gap Error</li> 
<li> <b>172472</b> : No Scan Buff Too Many L1A L2A w/o L1A 2 L1A to Buff Gap Error</li> 
</ol> 
<font color="red"><b>These all happened about the same time we 
power cycled the TS crate, so I'm not too worried.</b></font>
<!-- Author: Sal Rappoccio -->


<!-- Date: Thu Oct 30 10:50:08 2003 -->
<h3>More SRC Errors</h3> 
 
The only real error I think we had was in Run 172550. Here, there were lots and lots of other errors coming from just about every crate imaginable. All the crates with TDC's went bonkers, and then the SRC threw <b>L2A w/o L1A</b> amidst the chaos. Interested parties should check out 
<a href="http://www-cdfonline.fnal.gov/daq/runSummary/errorlog/errorfile172550.log"> 
the error file</a>. I'm not sure what to conclude from this. See the plots below (explanations included there).
<!-- Author: Sal Rappoccio -->


<!-- Date: Thu Oct 30 10:58:26 2003 -->
<center><a href='/elog/notebooks/silicon/Thu_Oct_30_2003_105759.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2792' ></a><a href='/elog/notebooks/silicon/Thu_Oct_30_2003_105809.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2794' ></a></center>
<!-- Author: Sal Rappoccio -->
<!-- Comment: Thu Oct 30 15;19;11 comment by...SCN -->
Well, 0x91 on the TAXI is a CALIBRATION word, however <ul>
<li> A Special L2A is TAXI 0x01, not 0x91
<li> The SRC not in tracer mode (which pulled error) 
is suppossed to ignore special L2A
<li> The two SRCs are not seeing the same stuff on their TAXI lines (unless they TAXI LA mode in each is different?) i.e. TAXI1 != TAXI2
</ul>
It would all make sense if this were the Tracer SRC seeing 0x91 as a Special L2A and then complaining that it is a L2A without a L1A (though I don't know why it would see 0x91 when the other TAXI doesn't).  Note also that when the SRC pulled HALT, all the TDCs went absolutely crazy, which I told Ops people would happen
on 7/17/03, but noone has tried to do anything about it.
<!-- Date: Thu Oct 30 11:01:35 2003 -->
<h3>SRC Error Plots</h3> 
This is the last error that happened, for run 172550. Two views of the same trigger. It seems that the L1A actually happened, and 
the SRC threw error amidst confusion of the other things that were happening. I need to think about this more.
<!-- Author: Sal Rappoccio -->


<!-- Date: Thu Oct 30 14:45:39 2003 -->
<table border=0><td><tr><td bgcolor=#e0e030>Cooling is back.  Details <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=907&frame=2&anchor=14:44:02.483'> 
here.</a></td></tr></td></table>
<!-- Author: Andy H. -->



<!-- Date: Thu Oct 30 15:12:30 2003 -->
<p><b>CAEN reset lines</b></p> 
<p> 
George Wyatt fixed them, Florencia and I tested them.  All the lines are functional, one-to-one, and mapped correctly.</p>
<!-- Author: Andy H. -->



<!-- Date: Thu Oct 30 15:29:22 2003 -->
<h3>Coming back to Life</h3> 
In preparation for turing things on I <ul> 
<li> Reenabled the Tracer Rate Limiter (via the cardEditor on SRC_00) 
<li> Set the IGNORE_VRBs register 0x2080 to 0 on both SRCs (this 
prevents L2As from going by without at least one VRB responding) 
</ul> 
<!-- Author: SCN -->


<!-- Date: Thu Oct 30 19:04:18 2003 -->
<table border=0><td><tr><td bgcolor=#e0e030><h1> Who Are the <a href= 
'/cgi/elog/elog.pl?nb=2003&action=view&page=902&frame=2&anchor=20:50:13.304'> 
Pigs </a>  ? </h1></td></tr></td></table>
<!-- Author: Rainer -->
<!-- Comment: Thu Oct 30 19;13;35 comment by...Rainer -->

<li>
<a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W8&layer=L1'> SB4W8L1 </a>


<li>
<a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L1'> SB0W11L1 </a>

<li>
<a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B0W4&layer=L0'> LB0W4L0 </a>
<p>
...and if an ISL ladder is really necessary....
<p>
<li> 
<a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B2W3&layer=L1'> IB2W3L1 </a> aka SOC/SB1W7L1





<!-- Date: Thu Oct 30 22:54:00 2003 -->
<h1> (Almost Random Thoughts on) Next Steps </h1> 
<li> Take a SiliGuineaPig Run over night, varying and thereby debugging TS partitions,  try to excite/trap further 5 L1 SRC fatal errors or declare them solved/explained and us ready for 2SRC running - <i> Rainer/Greg Feild Owl SciCo taking ,SCN, Lester, Sal analyzing </i> 
<li> Follow up on RX/FIB/FTM work on b0fib00 - <i> David Clark, Florencia, Paul and Jared learning </i> 
<li> Follow up on dnoise investigations on the ladders which were missed in TF2 due to misread bias current readings and 'dnoise' them - <i> Florencia, David Clark , Paul and Jared learning</i> 
<li> Take a SVXDAQ run RA with L00 bias on  and off for Chris to analyze in DAQANA - <i> Chris Hill with some help, maybe Ben ? </i> 
<li> Make a list of L00 ladders which were biased before the shutdown (preferably as close as possible to shutdown but a cosmics run) but now read zero bias current - <i> Rainer, Ben </i> 
<li> Make a list of L00 ladders expected to give current now by extrapolating their leakage current from Ken Chow's leakage current study on the coarse scale to the end of the shutdown and compare them to the current coarse scale readings - requires knowledge of the offsets already provided by Matt - <i> Ben, Matt </i> 
 
<li> Commission b0sili01 and b0sili02 -  <i> Ben </i> 
<li> Scan through the zero current list of L00 ladders (and whatever is found to the addendum of TF2 with unclear dnoise prognosis) and sort out the ones with bias connection in the middle of the connector - there would be nothing we could do if they had lost bias - <i> Rainer, following a suggestion by Gino </i> 
<li> revive SB4W4L3 (please) - <i> Gino, if time </i> 
<li> Commission the automatic bias verification ala Pete by comparing TF2 with high statistics pete runs -<i> Pete, currently MIA </i> 
<li> take bias on/off dmod (?), magnet on calibration for David Stuart to chew on  for L00 bias continuity- <i> David Clark, David Stuart </i> 
<li> Probe remaining bias connectors of unclear cases, hopefully a handfull after all the above - <i> well, don't expect me to write any  names here now </i> 
<li> take cosmics with magnet and COT on  and keep system exercised  - <i> CDF  and the pager carrier</i> 

  
<!-- Author: Rainer -->
<p>
<!-- Comment: Thu Oct 30 23;00;24 comment by...Rainer -->
<i> Disclaimer </i>  - these are the almost personal thoughts of a somewhat exhausted SPL who wants to keep track of the necessary steps and won't be here full time on Friday. They are not legally binding, nor completely sorted out, nor prioritized. But in case somebody asks to do some work while I am gone ....


<!-- Date: Fri Oct 31 10:28:00 2003 -->
<b> RTServer jumps around again ... </b> 
 
moved for now to b0dap33 - rebooted svxinter, all FIB and SVX crates (hope that did not erase any settings), restarted the PSGui and IMON as well as PSMon and TempOut in the first floor PC.  
<!-- Author: Andy, Rainer -->


<!-- Date: Fri Oct 31 10:46:43 2003 -->
<h2> Bring the Silicon back to Life .... </h2> 
 
after RT server work, switch on some wedges to standby which works however. hwoever, ISL B2W2 trips on 2V/5V DOIM. had this before which was a flaky communication and/or 5V enable. decide to hockerize the whole shebang. also for trial of revival of SB4W4L3. 
 

<!-- Author: Rainer -->
<!-- Comment: Fri Oct 31 10;58;52 comment by...Rainer -->
I notice a lot of RTserver timeouts while his happened like <BR>
<pre>

Connecting to project <cdf_daq> on <tcp:b0dap33> RTserver.
Using tcp protocol.
connect: S_errno_ETIMEDOUT
Could not connect to <tcp:b0dap33> RTserver.
Skipping starting <start_never:tcp:b0dap33> RTserver.
</pre>

I hockerized all crates (noted that the power cord was still plugged in, now unplugged) and wait for this RTServer to 
calm down. Else <i> I </i> will timeout soon ...


<!-- Comment: Fri Oct 31 20;58;33 comment by...Rainer -->
<pre>I was out of my mind. IB2W2 in ISL is DEAD and I accidentally 
activated it on switching off the GuineaPigs.</pre>
<!-- Date: Fri Oct 31 13:39:11 2003 -->
<h3>Cleaning up a little</h3> 
Rainer asked me to come over and turn on "the rest of the wedges" whilst he went to get der Mutter.  I addressed <ul> 
<li> SB0W2 all - turned on and initialized with SVXDAQ no problem 
<li> SB1W0 all SB1W1 all - <B>found old (DEM) sequences</b> in <a href="http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=copyentry&page=172&time=19:49:39">recently swapped fib</a>.  Put nominal sequences in, all turned on and init'd OK 
<li> SB4W4 all - Attempted to turn them on, SB4W4L3 trips on AVDD.  <B><FONT COLOR=RED>This ladder needs some tender lovin' care</FONT></B>.  All else OK (L0 known to have a flaky short, and is offline) 
<li> SB4W7 all - PC trips on 5VDOIM OVV.  This usually indicates that the CAEN connector is not connected well, or we might have a Junction Card problem?  Need to go into the Hall and look. 
<li> SB4W8L2  This one has been dead since 12/02 but Rainer accidently reintegrated it when turning off Guinea Pig SB4W8L1. 
I turned it offline and redownloaded CAENvolts.dat 
</ul> 
Will look into the Hall regarding SB4W7  
<!-- Author: SCN -->
<!-- Comment: Fri Oct 31 13;57;14 comment by...SCN -->
No noticable problems for PS for SB4W7 (SE Bottom Top, Slot 2), replugged cables anyway for good measure, still tripped on
5VDOIM OVV.  <B>Boo!</B>


<!-- Comment: Sat Nov  1 00;59;21 comment by...mumford and herndon -->
<pre>Matt and I went in and took a look at it.  We believe that it is a blown fuse.  Most likely, the fuse will be dealt with on Monday at some point.  </pre>


<!-- Date: Sun Nov 2 04:02:30 2003 -->
Came in to look at e443 (SB4W4L3) as asked by the SPL. As you will se I did not get much out of my 3 hours in middle of the night but at least there is a to do list that I consider reasonable. 
<ul> 
 
	<li> Found that the Silicon is in STDBY (that I think is good) but  
	IMON is not running (that I know is bad)</li> 
	<li> Restarted IMON and found the following (purely to record a snapshot of it): 
	<ul> 
		<li> IB1W3L4 is PINK</li> 
		<li> SB0W7L4, SB0W10L1, SB1W1L4, SB2W2L4, SB5W7L4 are PINK</li> 
		<li> No PINKIES in L00</li> 
	</ul> 
        <li> Found a svxdaq running on b0dap42. I Killed it, nobody was working with it. I believe it is better this way.</li> 
	<li> Checked the log files for when/how e443 tripped:</li> 
	     <ul><li> 
	     <pre> 
October DVDD 
Sun Oct 05 09:48:31 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sun Oct 05 12:31:29 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Wed Oct 08 09:49:45 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Wed Oct 08 12:13:37 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Fri Oct 10 21:46:28 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 11 19:16:41 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 11 19:23:07 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 11 19:27:42 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 11 21:17:16 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 25 18:50:34 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 25 19:15:51 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 25 19:19:25 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 25 19:34:01 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Sat Oct 25 21:33:27 CDT 2003     TRIP: SVX  B4  W4 DVDD3 OverCurrent 
October AVDD	 
Sat Oct 11 12:16:21 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 12:27:24 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 12:28:01 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 13:29:11 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 17:44:16 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 19:20:08 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 19:26:18 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 19:59:28 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 21:11:34 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 11 21:12:10 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 24 22:08:57 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 24 22:10:06 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 24 23:41:29 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 24 23:55:39 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 24 23:56:00 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 04:22:36 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 04:32:55 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 04:33:23 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 09:32:31 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 09:34:07 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 14:06:37 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 14:14:54 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 17:52:54 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 17:54:08 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 17:54:56 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 17:55:48 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 18:40:05 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 18:41:00 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 18:46:23 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 18:51:51 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 18:53:00 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 19:18:47 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 19:22:49 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 19:25:16 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 19:26:29 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 19:27:06 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 19:28:30 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 19:34:38 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:33:52 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:34:32 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:38:27 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:40:49 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:43:37 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:48:18 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:52:22 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:54:42 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Sat Oct 25 21:55:10 CDT 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 31 11:17:47 CST 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 31 11:19:37 CST 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 31 13:00:56 CST 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 31 13:04:23 CST 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
Fri Oct 31 13:06:59 CST 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
<li>November DVDD 
none</li> 
<li>November AVDD 
Sat Nov 01 16:09:37 CST 2003     TRIP: SVX  B4  W4 AVDD3 OverCurrent 
	     </pre></li> 
<li><a href= 
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=12:26:35'> 
Here is a link to when it tripped the first time on AVDD this is during the testing of october 11th when the trouble started </a> </li> 
<li> My conclusion is that this ladder always trips on AVDD and the DVDD trips are spurious (when you switch it off for example)</li> 
	     </ul> 
	</li> 
	<li> Tried to turn SB4W4L3 to STDBY and it tripped on AVDD overcurrent</li> 
	<li> Here is a list of what I would do with it (if not already done) in the specific order I would do it (I wouldn't skip a single step):</li> 
	<ul> 
      <li> Measure the resistances between AVDD4/3/2/1 and GND to see if anything is anomalous with the L3</li> 
      <li> If a dead short is spotted try to locate if it is before the JC</li> 
      <ul> 
	<li> By visual inspection</li> 
	<li> By making carefull (precise) resistance measurements and compare tham on the bench with what you would get with real cable if you put a short on the ladder, on the portcard, on the junction card or somewhere on the cable. 
	  </ul> 
      <li> If the resistance look OK the first thing to do is to turn the ladder ON without the CPC being ON (this can be done on the front pannel of the CAEN crate).</li> 
      <li> if no luck so far I would try another supply (same test as previous bullet) 
      <li> If no luck so far than we should try to go there with the CAEN crate on a CART and try to run it with a LOWER AVDD voltage. This has been done succesfully before on <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=73&frame=2&anchor=21:29:46'> 
SB2W7L3 </a> a long long time ago by Gino and Jason. 
I make the point again that this should be done with the CART with the extension cables and not on the real supply (this is the least disturbing way to deal with it. </li> 
      </ul> 
      <li> For the time being I removed it from the HDWDB leaving the system as I found it (except that IMON is now running and the ghost svxdaq is not)</li> 
</ul>
<!-- Author: Gino -->
<!-- Comment: Sun Nov  2 04;05;58 comment by...Gino -->
<pre>Forgot to say that when I killed the svxdaq I qas asked if I wanted to clean it up and I did so. This is new for me so I report it here in case I made the wrong choice.</pre>

<!-- Date: Sun Nov 2 05:06:19 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W7L3 
<li>problem n: 1143 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Diagnosis
<li>entered by: bolla 
<li>description is: This ladder was broke at the beginning of time and fixed later on still before the problem database was born so I report here how it went according to what I can find in the e-log <li> <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=63&frame=2&anchor=02:16:47'> First trip reported on August 2001 </a>  <li> other trips reported during the same month I do not know if it was taken out of the HDWDB but it could be chacked in the HDWDB itself <li><a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=73&frame=2&anchor=21:29:46'> this is how it was fixed </a>  
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W7&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Nov 3 10:14:25 2003 -->
<b> Pinkies after 3 days of standby </b>
<!-- Author: Rainer -->


<!-- Date: Mon Nov 3 10:17:54 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2795&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2795' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2796&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2796' width='250'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2798&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2798' width='100'></a></center>
<!-- Author: Rainer -->


<!-- Date: Mon Nov 3 10:29:35 2003 -->
<pre>this is the second time when I noticed IB5W1L1 not pass coldstart on the first, but second time. a new flaky readback ?</pre>
<!-- Author: Rainer -->
<!-- Comment: Mon Nov  3 10;37;57 comment by...Rainer -->
<pre>yes, have masked RB for time being.</pre>
<!-- Date: Mon Nov 3 10:37:24 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W1L1 
<li>problem n: 902 
<li>Status: needs_observation
<li>Type: No_Init
<li>Action: Init_RB_mask
<li>entered by: rainer 
<li>description is: has flaky readback after TF2 of 2003 fall shutdown. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B5W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Mon Nov 3 16:30:29 2003 -->
<h3>CAEN Access Report</h3> 
Checked the following supplies:<br> 
<b>SB4W7</b>: Replaced a blown fuse.  Powered a single channel and the problem appears to have been fixed.  <br> 
<b>SB4W4L3</b>:  
<ul> 
<li>Persistent trips on AVDD.   
<li>We probed the LV cable and found that the L3 LV cable has a resistance of 40 Ohms while the others have a resistance on the order of 1.0kOhms.   
<li>We believe that this implies a short beyond the cable as the cable has a resistance on the order of 10 Ohms.  
</ul> 
<b>SB1W6L4</b>:  
<ul> 
<li>Persistent trips on DVDD.   
<li>Measured resistances on DVDD lines.  All lines look good (3.0MOhms/1.9MOhms depending on polarity).   
<li>Supply does power without the cables attached.   
<li>We tried cabling SB1W6 to a working supply and again L4 trips pointing to a problem with the layer and clearing the supply of guilt.   
<li>Tried to power the layer w/o the port card as suggested by Gino -- no success.   
<li>During one attempt at powering, we saw a flash of 960mA on the monitored current.  Don't know if this measurement is to be trusted but we make a note of it here all the same.   
</ul>  
<!-- Author: Mumford and Napora -->


<!-- Date: Mon Nov 3 17:52:15 2003 -->
<h3>Don't get fooled by Run Control</h3> 
Just took a run with no Event Builder and no Run Number, (DaqTest/SVX/COLDSTART configuration) and found that 
Run Control no longer counts L2A in this case (and perhaps others) 
so you cannot actually tell if a Run is progressing or not by 
looking at the GUI.  I confirmed that a run was going by looking at counters on the SRCs with svxdaq, and also by seeing the little red led on the TS blink.  Note that if RC does not count events. most likely it will not stop a DMODE calibration after 5000 events, since it doesn't have any idea when that might be.  Anyway, I conclude the DAQ is ready to go, so I am going away.
<!-- Author: SCN -->
<!-- Comment: Tue Nov  4 09;10;00 comment by...Rainer -->
<h2> Hunting the NoEvents in RC Bug </h2> <BR>
 
taking SCN's advice to heart, I decided not to be fooled but turns out more people have seen this, so Bill Badgett asks to send him
the following information in case  we see it again:
<li> hostname
<li> partition
<li> output of the following: <BR> <pre>
   echo $FER_DIR
   echo $JDK_DIR
   echo $JAVA_DIR
   echo $JFC_DIR
</pre>



<!-- Date: Tue Nov 4 09:48:12 2003 -->
<h2> Return of the reformatter error ? </h2> 
 
we are trying to take a series of dmod calibration runs, but shift crew reports high rate of l3 reformatter  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=922&frame=2&anchor=09:32:52.036'> 
errors.</a> Checking in the reformatter error log, we find: <pre> 
 RAWREF Error - BNK-SI-DUPL - with code 37 -- START 
 Line -  995 in: src/library/rr_refevt.c 
 Buffer position: -1 
 Error count: 1 of 1 
 Reject rate: 50.000 percent 
 
 Duplicate FIB ids:  0xadeadcdf  0xf8411bfc  0xf8421bfc  0xf8431bfc  0xf8441bfc  0xf8501bfc  0xf8511bfc  0xf8521bfc  0xf8531bfc  0xadeadcdf 
 
 Error location code: 0x05004540 
 
 
 Crate Id?: 0x00000050 
 
 Error during scanning MINI structure! 
 Last Unit prob. worked on (all counts from 0): 
  SCPU: 4 
  VRB : 5 
  LINK: 4 
  MINI: 0 
</pre> which decodes to b0eb23/b0svx06.  
<!-- Author: Julia, Rainer -->
<!-- Comment: Tue Nov  4 09;57;59 comment by...Julia, Rainer -->
<pre>so f840 is our beloved L00 guinea pig, but he is off in the HWDB. so is f854, which is a SVX power supply channel but no physical HDI.  </pre>

<!-- Comment: Tue Nov  4 10;33;27 comment by...Rainer -->
<pre>f844 (which is illegal) was accidentially activated/online since I just inverted the bit patterns (complement of GUINEA PIG=1) which was a bit premature ... now it works
</pre>


<!-- Date: Tue Nov 4 10:39:44 2003 -->
<h2> DMOD Calibration Fest </h2> 
 
will take 2 sets of two dmod calibrations: bias STDBY and ON (each with dps ON or OFF), 5K each. Then, proceed with a quiet time bias scan style run  L00 bias ON and STDBY for David Stuart to analyze.  
<!-- Author: Rainer -->
<!-- Comment: Tue Nov  4 12;46;17 comment by...Rainer -->
<table> <tr> <th>  Run  <th> # events <th> DPS <th> Bias  </tr>
<tr> <td> <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=173102'>173102</a>  <td> 5000 <td>  ON  <td> ALL STDBY <td> </tr>
<tr> <td> <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=173103'>173103</a>  <td> 5000 <td>  OFF  <td> ALL STDBY <td> </tr>
<tr> <td> <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=173104'>173104</a>  <td> 5000 <td>  OFF  <td> ALL ON <td> </tr>
<tr> <td> <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=173105'>173105</a>  <td> 5000 <td>  ON  <td> ALL ON <td> </tr>    
<tr> <td> <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=173115'>173115</a>  <td> 10000 <td>  OFF  <td> ALL ON <td> </tr>    
<tr> <td> <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=173116'>173116</a>  <td> 10000 <td>  OFF  <td> SVX+ISL ON, L00 STDBY <td> </tr>    

</table>


<!-- Comment: Tue Nov  4 12;46;55 comment by...Rainer -->
<pre>... all with magnetic field ON</pre>

<!-- Date: Tue Nov 4 15:20:16 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W1L0 
<li>problem n: 1122 
<li>Status: needs_access
<li>Type: Unknown
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: Tested and found bit 6 low still there.  Swap FTM. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 15:21:43 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W0/1All 
<li>problem n: 1142 
<li>Status: needs_access
<li>Type: Other
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: Bit 6 low still there in channel 5, suggest swap FTM. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W0/1&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 15:36:00 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W11L4 
<li>problem n: 1135 
<li>Status: needs_access
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: bit 4 low showed up in post testing.  suggest swapping DOIM cables to isolate. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 15:48:27 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W11L2 
<li>problem n: 765 
<li>Status: needs_observation
<li>Type: DropReadOut_nonRX
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: Looks like problem has returned.   
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 15:57:57 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_access
<li>Type: Unknown
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: bit 1 high and bit 4 low.  suggest swap DOIM cables 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 16:02:06 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L0 
<li>problem n: 1123 
<li>Status: needs_access
<li>Type: Unknown
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: bit 6 low still seen.   
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 16:10:23 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L4 
<li>problem n: 1137 
<li>Status: needs_access
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: Dropping read out 100%.  Suggest swapping DOIM cables to isolate. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 16:26:57 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W2L3 
<li>problem n: 1144 
<li>Status: needs_access
<li>Type: Unknown
<li>Action: Incident
<li>entered by: yamaoka 
<li>description is: See bit 4 low.  Possibly introduced during RX swap for ch 9.  Suggest swapping DOIM cables to confirm. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 16:29:01 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L0 
<li>problem n: 1145 
<li>Status: needs_access
<li>Type: Unknown
<li>Action: Incident
<li>entered by: yamaoka 
<li>description is: See bit 6 low.  swap DOIM cables to isolate. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 4 16:34:59 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L2 
<li>problem n: 1146 
<li>Status: needs_access
<li>Type: Unknown
<li>Action: Incident
<li>entered by: yamaoka 
<li>description is: Bit 3 low.  swap DOIM cables to isolate. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Nov 5 08:00:04 2003 -->
<h3> Pinkies after a night if cosmics data taking </h3>
 <center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2799&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2799' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2800&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2800' width='200'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2801&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2801' width='100'></a></center>
<!-- Author: Rainer -->
<!-- Comment: Wed Nov  5 09;01;15 comment by...Rainer -->
<table> <tr> <th> What <th>
Current Reading <th> Limits (Yellow) <th> Comments </tr> 
<tr> <td> SB2W2L4 AVDD <td> 1130 <td> [1082...1122] <td> high (seen

<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=08:17:47'>
before </a> )
 </tr> 
<tr> <td> SB1W10L3 AVDD <td> 745 <td> [749....771]  <td> low </tr>
<tr> <td> SB1W3L3 AVDD <td> 865<td> [828...860] <td> high </tr> <tr> <td> IB1W3L4 AVDD <td> 1200<td> [1140...1175] <td>high</tr> 

<tr> <td> SB0W10L1 AVDD <td> 480 <td> [489...506] <td> low </tr>
 </table> 



<!-- Date: Wed Nov 5 09:05:53 2003 -->
<h3> SVXMon complaints after a night of cosmics data taking  </h3> 
see link <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=924&frame=2&anchor=00:38:05.634'> 
here </a>   
<!-- Author: Rainer -->
<!-- Comment: Wed Nov  5 10;03;21 comment by...Rainer -->

<table> <tr> <th> ladder <th> fib <th> slot <th> status <th> SVXMon error logger <th> </tr>
<tr> <td>  <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W3&layer=L4'> IB1W3L4 </a> <td> b0fib01 <td> 10 <td> yellow 
<td> Drop Readout (c2c2)  This error was present in  5951 events out of  5951 </tr>

<tr> <td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L3'> SB0W4L3 </a> <td> b0fib02 <td>  8<td> red <td>
Bit 0 High This error was present in  5951 events out of  5951 </tr> 
<tr> <td><a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W7&layer=L1'> SB2W7L1 </a> <td> b0fib02 <td> 18

<td> red <td> Bit 1 Low  This error was present in  5920 events out of  5951 </tr>
<tr> <td> <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W3&layer=L0'> SB2W3L0 </a> <td>b0fib00 <td> 18
<td> red <td>
Bit1 Low, C2 Termination This error was present in  5852 events out of  5951 </tr>

    <hr>
</table>
<!-- Comment: Wed Nov  5 10;14;03 comment by...Rainer -->
SB2W7L1 has bit1 dead at bore, masked unfixable, why is it red in SVXMon ?
<!-- Date: Wed Nov 5 09:51:43 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W3L4 
<li>problem n: 1110 
<li>Status: needs_access
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: rainer 
<li>description is: DRO c2c2 'This error was present in  5951 events out of  5951' in post shutdown 2003 cosmics running. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Nov 5 10:10:17 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L3 
<li>problem n: 1147 
<li>Status: needs_access
<li>Type: RX
<li>Action: Incident
<li>entered by: rainer 
<li>description is: reported red in SVXMON after cosmics data taking w/ Bit 0 High  
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Nov 5 10:13:05 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W3L0 
<li>problem n: 1079 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Monitoring
<li>entered by: rainer 
<li>description is: Bit1 Low  and C2 termination in cosmics running. bit errors seem to be back.  
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Wed Nov 5 15:43:49 2003 -->
Swapped DOIM cables for the following in fib00 and found all bit errors to be in the DAQ channel: 
<pre> 
Ladder		Slot 
========================================================== 
SB0W2L3		11	introduced in RX swap for SB0W3L4 	 
SB0W3L0		11	introduced in RX swap for SB0W3L4  
SB0W3L2		11	introduced in RX swap for SB0W3L4  
SB0W3L4		11	started w/ B2L, now Dropping readout 
SB1W3L2		13	started w/ B3L, now B1H & B4L 
SB2W3L0		18	B1L 
SB0W11L4	10	B4L after swapping RX 
SB1W1L0		12	B6L still there after RX & FIB swapped 
SB1W3L0		13	B6L still after RX swap 
</pre> 
There is clearly something going on with this crate and a very likely culprit could be the back plane which was swapped out at the beginning of the shutdown. Next, I will inspect the back plane for bent pins or misalignment and perhaps move the boards in slot 11 to a spare slot for testing of the backplane.
<!-- Author: David, Ben -->
<!-- Comment: Wed Nov  5 17;14;57 comment by...David -->
<pre>Inspected backplane for slot 11 and found 4 bent pins. I will
talk to Dervin tomorrow about the possibility that the backplane 
is misaligned with the slots and look for more bent pins. In the
meantime, the crate is off and FTM for SB0W2/3 remains out (in
the Silicon office).</pre>
<!-- Date: Wed Nov 5 17:09:40 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L3 
<li>problem n: 1148 
<li>Status: needs_study_time
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: dkclark 
<li>description is: While pulling out the FTM I noticed the RX fiber was partially  chopped. Needs testing.<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0553">0553</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0484">0484</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L3">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Wed Nov 5 17:16:58 2003 -->
<h3>CAEN Access Report</h3> 
Went in to address two things. 
 
<ul> 
<li> Measured the resistance of a layer 3 cable that is shorted at the junction card.  I used the Pit Wib cables.  With the AVDD3 shorted at the junction card I measured 2.8Ohms.   
<li> <b>SB1W6L4</b>.  Got the rolling CAEN cart recomissioned to try to mess around with the AVDD voltages on this guy.  I was able to power the layer with the test supply but the layer has really high DVDD currents.  <br> 
<table border=1> 
<tr> 
<td>Channel</td> 
<td>VMON</td> 
<td>ISET</td> 
<td>IMON</td> 
</tr> 
<tr> 
<td>AVDD</td> 
<td>7.91V</td> 
<td>1400mA</td> 
<td>855mA</td> 
</tr> 
<tr> 
<td>DVDD</td> 
<td>5.71</td> 
<td>2000mA</td> 
<td>1000-975mA</td> 
</tr> 
<tr> 
<td>BIAS</td> 
<td>1.70</td> 
<td>2000uA</td> 
<td>0uA</td> 
</tr> 
</table> 
 
So it appears that the real problem lies in the high DVDD current.   
<!-- Author: Reid and Stan -->
<!-- Comment: Fri Nov  7 07;56;40 comment by...    -->
</ul>
<!-- Date: Thu Nov 6 14:45:27 2003 -->
<h3>More on SB4W4</h3> 
Went in and did extensive probing on LV connector for SB4W4.  Also probed SB3W5 (a healthy nearby wedge for comparison).  There are two measurements (one for each polarity) per pin combination seperated by a slash.   
<br> 
<table border=1> 
<tr> 
<th>JC Pins</th> 
<th>LV CAEN Pins</th> 
<th>SB4W4<br>( MOhms unless noted)</th> 
<th>SB3W5 (MOhms)</th> 
</tr> 
<tr> 
<td>2VDOIM-DVDD3</td> 
<td>2VDOIM-DVDD0</td> 
<td>3.6/18 Ohms</td> 
<td>3.6/24</td> 
</tr> 
<tr> 
<td>DVDD3-AG4</td> 
<td>DVP_LY0-AVN_LY3</td> 
<td>20.3/4.5</td> 
<td>6.5/2.8</td> 
</tr> 
<tr> 
<td>UAV4-AG4</td> 
<td>AVP_LY3-AVN_LY3</td> 
<td>44.6/44.6 Ohms</td> 
<td>1.0/1.3</td> 
</tr> 
<tr> 
<td>UAV4-DVDD5</td> 
<td>AVP_LY3-DVP_LY2</td> 
<td>2.6/1.7</td> 
<td>2.1/3.8</td> 
</tr> 
<tr> 
<td>AG1-DVDD5</td> 
<td>AVN_LY4-DVP_LY2</td> 
<td>2.6/1.7</td> 
<td>6.5/2.8</td> 
</tr> 
<tr> 
<td>AG1-UAV1</td> 
<td>AVN_LY4-AVP_LY4</td> 
<td>1.0/1.0 kOhms</td> 
<td>.85/.96</td> 
</tr> 
<tr> 
<td>UAV1-DVDD4</td> 
<td>AVP_LY4-DVP_LY3</td> 
<td>1.7/2.7</td> 
<td>2.3/4.4</td> 
</tr> 
<tr> 
<td>2VDOIM-DGND3</td> 
<td>2VDOIM_P-DVN_LY0</td> 
<td>20.6/4.5</td> 
<td>5.1/OL</td> 
</tr> 
<tr> 
<td>DGND3-AG4</td> 
<td>DVN_LY0-AVN_LY3</td> 
<td>3.2/3.9 Ohms</td> 
<td>2.1/1.5</td> 
</tr> 
<tr> 
<td>UAV4-DGND5</td> 
<td>AVP_LY3-DVN_LY2</td> 
<td>45/45 Ohms</td> 
<td>.6/.5</td> 
</tr> 
<tr> 
<td>DGND5-AG1</td> 
<td>DVN_LY2-AVN_LY4</td> 
<td>1.8/8 Ohms</td> 
<td>1.5/2.1</td> 
</tr> 
<tr> 
<td>UAV1-DGND4</td> 
<td>AVP_LY4-DVN_LY3</td> 
<td>1 kOhms</td> 
<td>.9/.8</td> 
</tr> 
</table>  
<!-- Author: reid and jared -->


<!-- Date: Thu Nov 6 14:48:11 2003 -->
<h3>FIB 00 Update</h3> 
I pulled all of the FTM's from FIB00 (and all of the blank boards) and looked at the backplane.  I saw at least 5 slots with bent pins.  Slots 11, 12, 13, 18, and 20.  <br> 
Apparently Dervin's people are looking at it today. <br> 
All FTM's and blanks are in pizza-boxes in the silicon office. 
<!-- Author: reid and jared -->


<!-- Date: Thu Nov 6 18:21:56 2003 -->
<h3> Software Protection TripFest </h3> 
<pre> 
Thu Nov 06 17:56:42 CST 2003     Software protection trip: High DVDD Current  SVX B0 W8 L1 current 191.0 softLimit 150.0 
Thu Nov 06 17:56:52 CST 2003     Software protection trip: High DVDD Current  SVX B0 W4 L1 current 161.0 softLimit 150.0 
Thu Nov 06 17:56:54 CST 2003     Software protection trip: High DVDD Current  SVX B0 W5 L1 current 163.0 softLimit 150.0 
Thu Nov 06 17:56:55 CST 2003     Software protection trip: High DVDD Current  SVX B0 W8 L1 current 191.0 softLimit 150.0 
Thu Nov 06 17:56:56 CST 2003     Software protection trip: High DVDD Current  SVX B1 W8 L1 current 180.0 softLimit 150.0 
Thu Nov 06 17:56:57 CST 2003     Software protection trip: High DVDD Current  SVX B2 W4 L1 current 181.0 softLimit 150.0 
Thu Nov 06 17:56:59 CST 2003     Software protection trip: High DVDD Current  SVX B2 W5 L1 current 153.0 softLimit 150.0 
Thu Nov 06 17:57:00 CST 2003     Software protection trip: High DVDD Current  SVX B3 W8 L1 current 171.0 softLimit 150.0 
Thu Nov 06 17:57:01 CST 2003     Software protection trip: High DVDD Current  SVX B4 W5 L1 current 157.0 softLimit 150.0 
Thu Nov 06 17:57:02 CST 2003     Software protection trip: High DVDD Current  SVX B4 W9 L1 current 175.0 softLimit 150.0 
Thu Nov 06 17:57:04 CST 2003     Software protection trip: High DVDD Current  SVX B5 W0 L1 current 172.0 softLimit 150.0 
Thu Nov 06 17:57:05 CST 2003     Software protection trip: High DVDD Current  SVX B5 W5 L1 current 161.0 softLimit 150.0 
Thu Nov 06 17:57:07 CST 2003     Software protection trip: High DVDD Current  SVX B5 W6 L1 current 181.0 softLimit 150.0 
Thu Nov 06 17:57:08 CST 2003     Software protection trip: High DVDD Current  SVX B5 W7 L1 current 158.0 softLimit 150.0 
Thu Nov 06 17:57:09 CST 2003     TRIP: SVX  B0  W8 DVDD0 OverCurrent 
Thu Nov 06 17:57:10 CST 2003     TRIP: SVX  B0  W8 DVDD1 OverCurrent 
Thu Nov 06 17:57:10 CST 2003     TRIP: SVX  B0  W8 DVDD3 OverCurrent 
Thu Nov 06 17:57:19 CST 2003     Software protection trip: High DVDD Current  SVX B5 W5 L1 current 161.0 softLimit 150.0 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B0  W5 DVDD0 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B2  W5 DVDD1 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B2  W5 DVDD2 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B3  W8 DVDD0 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B3  W8 DVDD2 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B4  W5 DVDD1 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B4  W9 DVDD0 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B5  W0 DVDD0 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B5  W0 DVDD1 OverCurrent 
Thu Nov 06 17:57:20 CST 2003     TRIP: SVX  B5  W0 DVDD2 OverCurrent 
Thu Nov 06 18:06:35 CST 2003     success: Resetting trips 
Thu Nov 06 18:14:19 CST 2003     success: Resetting trips 
</pre>
<!-- Author: Rainer -->


<!-- Date: Thu Nov 6 19:18:06 2003 -->
<h3> b0fib00 et al</h3> <p> 
 
fib00 backplane will be replaced by dervin tomorrow morning. SB4W4L1,L2,L4  taken out of HWDB for the moment (Reid's work).  
<!-- Author: Rainer -->



<!-- Date: Fri Nov 7 09:32:17 2003 -->
<h3> freaked ISL currents and lost GLink sync </h3>
<!-- Author: Rainer -->


<!-- Date: Fri Nov 7 09:32:43 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2802&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2802' width='300'></a></center>
<!-- Author: Rainer -->
<!-- Comment: Fri Nov  7 11;35;45 comment by...Rainer -->
these currents are all way too low. IB0W0/1 4/5 IB1W0/1. they belong to b0fib03 who complains
<pre>
Test Fifo Enabled?  No Way!
Test Fifo Enabled?  No Way!
Messenger: processStatechange Reset [0]
Sent ack to Run Control: 1 START SUCCESS 
State is START
Test Fifo Enabled?  No Way!
</pre>
which is odd because they went through run control. will re-synch

<!-- Comment: Fri Nov  7 11;38;17 comment by...rainer -->
<pre>reboot does not help, nor HRR....</pre>

<!-- Comment: Fri Nov  7 12;17;49 comment by...Rainer -->
<pre>GLINK err red LED is lit on FFO as well</pre>


<!-- Date: Fri Nov 7 12:32:59 2003 -->
<h3> continued b0fib00 saga </h3> 
Roberto (Tech of dervin's crew) put the FTMs back in place, we cabled them up. FIB crate syncs all right after powerup, but ladders in slot #12 SB1W0/1 don't pass cold start (channel#0 is maskes so formally it passes in RC). in SVXDAQ, we see: 
<pre>0x00000000:  00300702 20800000 00000000 00060006 00000000 00000000 00000000 00000000 
0x00000020:  e10035fc c2c20000 e10135fc c2c20000 0030070b 20800000 00000000 00060006 
0x00000040:  00000000 00000000 00000000 00000000 e10035fc c2c20000 e10135fc c2c20000 
0x00000060:  00300706 20800000 00000000 00060006 00000000 00000000 00000000 00000000 
0x00000080:  e10035fc c2c20000 e10135fc c2c20000 </pre> 
from this we would conclude that the fib is alright (to be cross checked by SCN) and  the suspicion is that it is FTM related. 
  
<!-- Author: Reid, Rainer, William -->
<!-- Comment: Fri Nov  7 13;19;07 comment by...Rainer, William -->
roberto inspected the backplane. no bent pins in slot#12. checking slot#12 wedges SB1W0/1 we can't believe our eyes to see an old friend  -the cazzo!
<pre>
R 10308 E 181 Error:Not Chip ID      Fib 0 Pipe 4  Chip 0  0 received
R 10308 E 181 Error:ChipState Format Fib 0 Pipe 5 Data 0
R 10308 E 181 Error: pcB Byte         Ch ID F 0 P 5 Expect 10 Recieve  0
R 10308 E 181 Error: ChipState        Fib 0 Expect ff, Recieve 0 Pipe 5
R 10308 E 181 Error:Not Chip ID      Fib 0 Pipe 5  Chip 0  0 received
R 10308 E 181 Error:ChipState Format Fib 0 Pipe 6 Data 0
</pre>
wasn't that overcome in 2 SRC mode ?

<!-- Comment: Fri Nov  7 14;15;28 comment by...Rainer -->
OK, no more time goofing around with this since the muon wall needs to be closed. I would assume  either the FTM has gone south or it is the FIB. In fact, the fib was 
<a href=
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=172&frame=2&anchor=19:53:38'> touched </a> ) so I assume for the moment that this was not successful and its the fib's fault (although all power LEDs are on etc. etc. ) and proceed with bit testing.

<!-- Comment: Fri Nov  7 16;58;38 comment by...SCN -->
This isn't that italian word.  Did you see the "pipes != sum" error (whihc is the signature for misbehaving VRBs)?  (My guess-no.)  From the error log, looks like wherever it
expected something it got 00. <P>
I suspect either the timing cables are not plugged in, the FTM
fuse is gone, or the wedges are simply not powered.
<!-- Date: Fri Nov 7 16:34:29 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W0/1All 
<li>problem n: 1142 
<li>Status: needs_observation
<li>Type: Other
<li>Action: Swap_FIB
<li>entered by: thom 
<li>description is: <pre>fixed after backplane swap and the old fib was put back in</pre><table border=1>
<tr><td><b>IN</b></td><td>PREP:</td><td>560608</td><td>Serial:</td><td>112</td></tr>
<tr><td><b>OUT</b></td><td>PREP:</td><td>550954</td><td>Serial:</td><td>153</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W0/1&layer=All">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Fri Nov 7 17:10:08 2003 -->
<pre>Noticed that the bias voltage for SB2W0L2 stays around 40V in the GUI whether it is off or standby. When ON, it goes to its nominal value of 55. The current reads 0 unless it's supposed to be on.</pre>
<!-- Author: David -->
<!-- Comment: Fri Nov  7 17;12;57 comment by...David -->
<pre>Disregard aBove entry, I forgot that this ladder's bias is touching the opposite ladder, SB3W0L2, which was on at the time.</pre>

<!-- Date: Fri Nov 7 18:22:11 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W11L2 
<li>problem n: 1149 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Incident
<li>entered by: canelli 
<li>description is: Intermitent CAP ID errors and DRO in post backplane swap test. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Nov 7 18:33:45 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W2L3 
<li>problem n: 1144 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: canelli 
<li>description is: ok after backplane swap. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Nov 7 18:36:04 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L2 
<li>problem n: 1146 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: canelli 
<li>description is: ok after backplane swap. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Nov 7 18:40:13 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L3 
<li>problem n: 1148 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: canelli 
<li>description is: no problems seen after backplane swap. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Nov 7 18:46:13 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L0 
<li>problem n: 1123 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: canelli 
<li>description is: ok after backplpane swap. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->

<!-- Date: Fri Nov 7 18:58:06 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_access
<li>Type: Unknown
<li>Action: Diagnosis_update
<li>entered by: canelli 
<li>description is: Still there after backplane swap. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Fri Nov  7 18;59;10 comment by...rainer, florencia -->
<pre>
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..4e,4f 42, 43..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..42,43 42, 43..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..46,47 46, 47..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..4a,4b 4a, 4b..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..4e,4f 4e, 4f..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..62,63 62, 63..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..66,67 66, 67..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..6a,6b 6a, 6b..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..6e,6f 6e, 6f..
R 10400 E 44 Error: OO Sequence      Fib 0 Pipe 7 Chip 9: ..6e,6f 62, 63..

</pre>

<!-- Date: Fri Nov 7 19:07:47 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W1L2 
<li>problem n: 928 
<li>Status: needs_access
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: canelli 
<li>description is: See intermitent bit 5 high. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Fri Nov  7 19;08;02 comment by...florencia, rainer -->
<pre> E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 2: ..3f,60 41, 42..
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 3: ..3f,60 41, 42..
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 4: ..3f,60 41, 42..
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 5: ..3f,60 41, 42..
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 6: ..3f,60 41, 42..
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 7: ..3f,60 41, 42..
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 8: ..3f,60 41, 42..
R 10405 E 2 Error: Illegal Chan     224 Fib 0 Pipe 7 Chip 8
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 8: ..7f,7f 00, 01..
R 10405 E 2 Error: OO Sequence      Fib 0 Pipe 7 Chip 8: ..3f,60 41, 42..
R 10405 E 2 Error: Truncate         EOR = c2c2
R 10405 E 3 Error: OO Sequence      Fib 0 Pipe 7 Chip 0: ..3f,60 41, 42..
</pre>

<!-- Date: Fri Nov 7 19:13:57 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W3L0 
<li>problem n: 1079 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: canelli 
<li>description is: no problem seen in post backplane swap. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Nov 7 19:24:19 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W11L4 
<li>problem n: 1135 
<li>Status: needs_access
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: swapped with ch#8, errors follow pipe, suggest swap RX. pipe#8 B5H in chip3  (8a) previously known pipe#9 B4L 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Nov 7 19:25:41 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_access
<li>Type: RX
<li>Action: Diagnosis_update
<li>entered by: yamaoka 
<li>description is: swapped with channel#8, problem stayed with pipe, swapp RX (pipe 8 OK, pipe 7 B1H and B4L) 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Fri Nov 7 19:49:45 2003 -->
<h2> Status of SB4W4 </h2> 
tried to take back SB4W4L1,2,4 but failed - portcard first switches on then trips off, or, to be more precise, switches off, no trip reported. suspect 5V enable still being pulled from  
 
<a href= 
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=172&frame=2&anchor=14:45:27'> 
last </a>  work. Need PS expert to investigate. taken out f HWDB for now.
<!-- Author: Rainer -->


<!-- Date: Fri Nov 7 21:24:09 2003 -->
<h3>  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=172&frame=2&anchor=09:32:17'> 
Follow </a> up on  $^#%^%$ Glink Sync Error </h3> 
 
Glink of b0fib03  would not sync for the longest time - rebooting would not help, reset glink from svxdaq as commended by SCN would not help. In fact we temporarily lost the glink of b0fib05 as well. they do share a SRC fanout but in light was seen and eventually b0fib05 came back. We could not just leave it, since the unresponsive fib crate seemed to confuse the power supply GUI  
which complained about an unitialized fib: <pre> 
ERROR: not all Fibs are initialized 
ERROR: no response from FIB , ps_n = 67SetChannelStatus, err = -1 
checkSt[1][67][1] = 1 
SVX B5W7L0 spontaneously turned off 
turning it back to standby 
Sending Request for e570 
Timeout 
ERROR: not all Fibs are initialized 
ERROR: no response from FIB , ps_n = 67SetChannelStatus, err = -1 
checkSt[1][67][0] = 1 
SVX B5W7L5 spontaneously turned off 
turning it back on 
Sending Request for e575 
Timeout 
 
</pre> said wedge e57 would eventually trip off (being asked to turn back on in such a way) and so we feared that more wedges would be brought down. in fact we did see several SVX wedges trip off on DVDD overcurrent/software protection trips 
<pre> 
Fri Nov 07 20:31:49 CST 2003     TRIP: SVX  B5  W3 DVDD4 OverCurrent 
Fri Nov 07 20:32:01 CST 2003     Software protection trip: High DVDD Current  SVX B0 W3 L0 current 173.0 softLimit 150.0 
Fri Nov 07 20:32:02 CST 2003     Software protection trip: High DVDD Current  SVX B0 W3 L1 current 165.0 softLimit 150.0 
Fri Nov 07 20:32:03 CST 2003     Software protection trip: High DVDD Current  SVX B1 W1 L0 current 181.0 softLimit 150.0 
Fri Nov 07 20:32:04 CST 2003     Software protection trip: High DVDD Current  SVX B1 W1 L1 current 152.0 softLimit 150.0 
Fri Nov 07 20:32:05 CST 2003     Software protection trip: High DVDD Current  SVX B2 W3 L0 current 156.0 softLimit 150.0 
Fri Nov 07 20:32:06 CST 2003     Software protection trip: High DVDD Current  SVX B2 W3 L1 current 157.0 softLimit 150.0 
Fri Nov 07 20:32:07 CST 2003     Software protection trip: High DVDD Current  SVX B3 W0 L1 current 161.0 softLimit 150.0 
Fri Nov 07 20:32:08 CST 2003     Software protection trip: High DVDD Current  SVX B4 W10 L1 current 160.0 softLimit 150.0 
Fri Nov 07 20:32:09 CST 2003     TRIP: SVX  B0  W6 DVDD1 OverCurrent 
Fri Nov 07 20:32:10 CST 2003     TRIP: SVX  B0  W6 DVDD3 OverCurrent 
Fri Nov 07 20:32:10 CST 2003     TRIP: SVX  B0  W7 DVDD0 OverCurrent 
Fri Nov 07 20:32:10 CST 2003     TRIP: SVX  B0  W7 DVDD1 OverCurrent 
</pre> 
taking b0fib03 out of CAEN.map also did not sound so appealing. Ultimately, we powered off all the wedges ob b0fib03 in anger and power cycled the fib crate - which worked. No more spontaneous trips of SVX wedges was observed (also svxinter stopped complaining) - the night will show more.
<!-- Author: David, Rainer -->


<!-- Date: Fri Nov 7 21:36:09 2003 -->
<h3> Bottom line of  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=172&frame=2&anchor=12:32:59'> 
b0fib00 </a>  
 (s)hitlist </h3> 
Have to perform two RX swaps (<a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2'> SB1W3L2 </a>  and <a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L4'> SB0W11L4 </a>) and one LLM (<a href='http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B2W1&layer=L2'> SB2W1L2 </a>). Rest is fixed w/ backplane swap. 
<!-- Author: Reid, Florencia, Rainer -->
<!-- Comment: Fri Nov  7 22;07;32 comment by...rainer -->
but there is also RX work to be done outside fib00 - check pdb.

<!-- Date: Sat Nov 8 15:27:44 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W5L4 
<li>problem n: 1150 
<li>Status: needs_access
<li>Type: Optical_other
<li>Action: Diagnosis
<li>entered by: dkclark 
<li>description is: Swapped DOIM cables with channel 8 (L3) and found that the DAQ channel (L4) is OK.  Since the OBDV clock is bad for L4, couldn't determine whether same errors showed up in L3 - only received c2c2. Check light output. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W5&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat Nov 8 15:32:25 2003 -->
Checked Bias status of all integrated SVXII and ISL ladders and found no new unbiased ladders. Will come back tomorrow to check L00 and perform RX swaps.
<!-- Author: David, Florencia -->
<!-- Comment: Sat Nov  8 17;25;58 comment by...rainer -->
<pre>some ladders were forgotten in TF2 so they are not 'new'. Florencia knows how many. did you check these as well ?</pre>


<!-- Date: Sat Nov 8 17:52:20 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2803&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2803' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2804&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2804' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2805&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2805' width='300'></a></center>
<!-- Author: yves -->
<!-- Comment: Sat Nov  8 17;54;46 comment by...yves -->
<pre>Rainer asked us to do some plots from IMON</pre>

<!-- Date: Sun Nov 9 11:16:18 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W3L4 
<li>problem n: 1110 
<li>Status: needs_study_time
<li>Type: DropReadOut_nonRX
<li>Action: Diagnosis_update
<li>entered by: rainer 
<li>description is: repeatedly DRO in cosmics running (see <a href= '/cgi/elog/elog.pl?nb=2003&action=view&page=936&frame=2&anchor=04:02:41.785'> here </a> for example). Need to test in NN mode w/ SVXDAQ.  
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sun Nov 9 12:14:00 2003 -->
run <a href='http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=173640'>  173640 </a> is a very long (9 hours) <b> cosmics run </b>.
<!-- Author: Rainrer -->

<!-- Date: Sun Nov 9 15:22:01 2003 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 292
Calibration type  : standard
Run period tag    : Nov_2003
DPS-off run       : 173662
DPS-on run        : 173661
Requested by      : Monica/Massimo/Eli
Main process id   : 26792007
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->


<!-- Date: Sun Nov 9 16:08:58 2003 -->
<p><font size=+1> D-mode Calibration Job Finished </font>
<p><pre>
This is a computer-generated silicon D-mode calibration status report.
Silicon D-mode calibration job 292 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 173662
DPS-on run       : 173661
Requested by     : Monica/Massimo/Eli
Submitted        : 2003-11-09 13:20:02
Completed        : 2003-11-09 14:06:56
Status           : FAILURE

Last processing stage reported : checking silicon configuration
Failure diagnostics :
error {There is an error in the biasInfo file for run 173662}
Exiting.
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->



<!-- Date: Sun Nov 9 16:43:06 2003 -->
<b> On SB2W2L4 DVDD</b>  
<!-- Author: Rainer -->


<!-- Date: Sun Nov 9 16:47:35 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2806&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2807' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2808&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2809' ></a></center>
<!-- Author: Rainer -->
<!-- Comment: Sun Nov  9 16;50;54 comment by...Rainer -->
this coincides with a dmod DPS=on run (DPS off run follows). is this normal ?? other ladders don't show this behaviour ...

<!-- Date: Sun Nov 9 17:53:25 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W3L4 
<li>problem n: 1110 
<li>Status: needs_observation
<li>Type: DropReadOut_nonRX
<li>Action: Diagnosis_update
<li>entered by: rainer 
<li>description is: Somebody (me) failed to perform 9+16 correctly so the HDI  was wrong, leading to DRO in data taking but OK in SVXDAQ. should be ok now. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sun Nov 9 20:54:10 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2/3All 
<li>problem n: 1151 
<li>Status: needs_observation
<li>Type: Other
<li>Action: Diagnosis_update
<li>entered by: rainer 
<li>description is: swapped fib from slot #13 to slot #15. slot #15 had a bent pin. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W2/3&layer=All">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sun Nov 9 21:12:32 2003 -->
<b> more on b0fib00 </b> <p> 
the neverending story ... found bent backplane pin on frontside (FIB side) of b0fib00. migrated slot #13 to slot #15. Could not write the relevant files in  <pre> 
/cdf/code-common/cdfonline/svxii/devel/b0crates/current/ 
</pre> which are  <pre> 
b0fib00: 
 
Slot: 15      Base Addr: 0x68000000    SVID: null     Cfg File: /cdf/code-common/cdfonline/svxii/devel/b0crates/current/f0013.cfg 
</pre>  
 
plus several entries <pre> 
Slot: 15              HDI: 0          Cfg File:/cdf/code-common/cdfonline/svxii/devel/b0crates/current/c0130.cfg 
</pre> 
in ~svxii/daq, needed to change <pre> 
 
svxii.links: 
GS123   b0fib00 15      b0svx01 10 
</pre> 
since we could not write to these files, created temporary files 
<pre>  
/cdf/people2/svxii/daq/svx/b0fib00_temp.crate 
/cdf/people2/svxii/daq/svx/svxii_temp.links 
</pre> 
and updated <pre> system.cfg </pre> file accordingly. <p> 
 
well, at least bit errors in SB1W3L4 disappeared.
<!-- Author: David, Rainer -->

<!-- Date: Sun Nov 9 21:20:30 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L4 
<li>problem n: 1140 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: rainer 
<li>description is: bit#2 error disappeared after migrating slot from #13 (bent pin) to #15. problem of thread 321 remains (stuck capid). 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sun Nov 9 21:41:56 2003 -->
<pre>found enable cable off SB4W4 and plugged it back in after consulting reid. re-enabled SB4W4 L1,2,4 in HWDB.</pre>
<!-- Author: Rainer -->


<!-- Date: Sun Nov 9 21:59:04 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2810&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2811  width='300' align='top'></td><td>this guy incessently draws high DVDD current - I HRR'ed him 3 times in a row, that helped.</a></td></tr></table>
<!-- Author: rainer -->

<!-- Date: Mon Nov 10 05:31:13 2003 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 293
Calibration type  : standard
Run period tag    : Nov_2003
DPS-off run       : 173701
DPS-on run        : 173700
Requested by      : Ben W
Main process id   : 27635324
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->


<!-- Date: Mon Nov 10 06:19:05 2003 -->
<p><font size=+1> D-mode Calibration Job Finished </font>
<p><pre>
This is a computer-generated silicon D-mode calibration status report.
Silicon D-mode calibration job 293 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 173701
DPS-on run       : 173700
Requested by     : Ben W
Submitted        : 2003-11-10 03:29:12
Completed        : 2003-11-10 04:15:26
Status           : FAILURE

Last processing stage reported : checking silicon configuration
Failure diagnostics :
error {There is an error in the biasInfo file for run 173701}
Exiting.
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->
<!-- Comment: Mon Nov 10 17;47;04 comment by...Jason -->
<pre>Both of these D-mode jobs failed because: 

1.  The trigger inhibit was ignored and
2.  The backup biasCheck framework was turned off in the
    svxii crontab file.

I have re-enabled the cron job now -- it is working on the
backlog of runs since Oct. 27!

</pre>
<!-- Date: Mon Nov 10 09:20:19 2003 -->
<h3>SVXII trips off on DVDD</h3> 
at about 8:08. Correlated with (from error log run 173725) <pre> 
8'41" 1 crate/s: b0svx02(112),  in error.[RXPT] 
(MLE) b0dap73.fnal.gov:Thread-26:8:08:41 AM->FrontEnd Crate Error Condition from: 
VRB_SVX_02 
 
(MLE) b0dap73.fnal.gov:Thread-26:8:08:41 AM->Requested Halt-Recover-Run issued [errmon] 
(MLE) b0dap73.fnal.gov:Thread-26:8:08:41 AM->FrontEnd Error: VRB_SVX_02 
(MLE) b0svx02:Messenger:8:08:32 AM->SRC Fatal Error:Sl 5 L2A w/o L1A 2 L1A to Buff 
(RC)   8:8:44 Halt -> HALTED 
</pre> 
Looks like a buffer number was misconstrued. (L2A on the wrong buffer?)<BR> 
Messenger process on b0svx02 found suspended trying to RECOVER, also RC hung in RECOVER.  Keepalives were still coming from SRC  
despite being in Error (checked with LA).  <BR> 
After 8 AM meeting (roughly 8:30, <b>post-trip</b>) TS crate was disturbed with SRC still hung in recover, ergo listening to the 
TS.  Examining the VRBs and SRC shows <ul> 
<li> Every SVXII VRB is hosed 
<li> The SRC has lots and lots of Fatal Errors 
</ul> 
This is assumed to be due to the fact that the TS was messed with, which is known to cause garbage on the TAXI, which is normally ignored because the SRC only listens to the TAXI line 
while running but this time it hung in RECOVER.  So though it confuses matters, it was post-trip so didn't cause the initial trip. 
Perhaps it is time to swap out this SRC.  In the meantime we will 
(hard) reboot b0svx00-05.  
<!-- Author: SCN, Rainer -->
<!-- Comment: Mon Nov 10 11;47;38 comment by...SCN, Sal -->
Plan is to (as I understand) turn off SVXII (done) and ISL (when
COT work allows!) compare clock signals between the two, and then swap the SRCS, running only L00 and ISL Guinea Pigs on the "bad SRC" and
SVXII on the other one. <P>
A preliminary investigation of SVXII SRC clocks shows no anomolies.  The 53 MHz CLock fanouts (which are new since the
shutdown) seem to be in synch, although we did a 0.5 nS adjustment to the SVXII one relative to the old one, just to center them (the new one seems to have a ~1 ns longer duty cycle.)  Doubtful that this could cause the problems seen today.

<!-- Date: Mon Nov 10 12:28:08 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_study_time
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: yamaoka 
<li>description is: Needs testing.<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0162">0162</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0855">0855</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Nov 10 12:33:04 2003 -->
<h1>Access Summary</h1> 
Swapped RX in SB1W3L2.  Left FIB00 off per Morris' request.  This board still needs to be tested. 
<!-- Author: Jared, David -->


<!-- Date: Mon Nov 10 15:04:20 2003 -->
<h2>SRC Swap</h2> 
I have swapped the two SRC's from b0svx02 and b0svx06. Now, the one labelled "Dopey" is driving the silicon, and the one labelled "Doc" is driving the ISL and L00. I have checked out both boards, and have run the following tests (a brief list since this was a simple swap): 
<ul> 
<li> Keepalives present in both SRC's</li> 
<li> L1A and L2A okay </li> 
<li> Error conditions are working (2 L1A to same buffer, etc) </li> 
</ul> 
I have the usual "fishnet trigger" (triggering on SRC error from either crate) set up on the LA to catch problems.  
<br></br><br> 
Steve and I checked the clock signals coming out of the clock fanout in the counting room, and everything is now synched within a ns or so. 
</br>  
<!-- Author: Sal R, SCN -->
<!-- Comment: Mon Nov 10 18;43;50 comment by...rainer -->
as a result .... <p>

<h1> Bring out the <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=172&frame=2&anchor=19:04:18'>
Pigs! </a>  </h1>

We will try excite the 2SRC fatal error by running a higher rate test on the guinea pigs of SVX and ISL/L00. Our working assumption is that the former SVX SRC is faulty, not firmware. 
<!-- Comment: Tue Nov 11 00;06;41 comment by...rainer -->
<pre>I have disabled in the hardware database: 

  b0fib00: f00 offline 
f01 offline 
f02:0000001000 (was 1111110111) 
f03 offline 
f04 offline 
f05 offline 
f06 offline 
f07 offline 
f08 offline 
  b0fib01 
whole crate offline 
  b0fib02 (needed for soc PS handshake?) 
f09 offline 
f10 offline 
f11 offline 
f12 offline 
f13 offline 
f14 offline 
f15 offline 
f16 offline 
f17 offline 
  b0fib03 
f41 offline 
f42 offline 
f43 offline 
f44:0000001000 (was 0000000000) 
f45 offline 
f46:1000000000 (was 0111011110) 
f47 offline 
  b0fib04 
whole crate offline 
  b0fib05 
whole crate offline 
  b0fib06
fib27 offline
fib28 offline
fib29 offline
fib30 offline
fib31 offline
fib32:01000000 (was 1001111111)
fib33 offline
fib34 offline
fib35 offline
  b0fib07 
whole crate offline </pre>
<!-- Comment: Tue Nov 11 12;18;24 comment by...Rainer -->
I accidentially marked the crate CPU offline, not the whole crate. I marked them online but marked now the crates offline. in addition, b0fib00 has all fibs marked offline. turned out it was not needed for soc handshake, but I leave it nonetheless for now.
<!-- Date: Mon Nov 10 17:51:53 2003 -->
Earlier I had modified the SVXCAL run configuration to IgnoreInhibits (see <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=171&frame=2&anchor=12:29:42'> 
this e-log entry</a>). 
<P> 
Now that the trigger inhibit crate seems to be back to normal (and faced with the biasCheck crontab fiasco of the past few weeks), I have restored the SVXCAL run configuration so that 
<UL> 
<LI>IgnoreInhibit is not selected (trigger inhibits are not ignored)</LI> 
<LI>TRIGGER_INHIBIT_00 crate is booked into the partition</LI> 
</UL> 
<P> 
It is trivial to change this back if there are any problems...  
<!-- Author: Jason -->




<!-- Date: Tue Nov 11 09:30:28 2003 -->
<h2>SRC Fishnet Status</h2> 
I have checked the error files for the L2 torture tests run overnight, and there were no errors at all. Keep on fishing!
<!-- Author: Sal R -->

<!-- Date: Tue Nov 11 10:25:27 2003 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 294
Calibration type  : standard
Run period tag    : Nov_2003
DPS-off run       : 173662
DPS-on run        : 173661
Requested by      : Jason Nielsen
Main process id   : 29325075
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Tue Nov 11 14:48:40 2003 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 295
Calibration type  : standard
Run period tag    : Nov_2003
DPS-off run       : 173701
DPS-on run        : 173700
Requested by      : Jason Nielsen
Main process id   : 29918693
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->


<!-- Date: Tue Nov 11 15:25:19 2003 -->
<p><font size=+1> D-mode Calibration Job Finished </font>
<p><pre>
This is a computer-generated silicon D-mode calibration status report.
Silicon D-mode calibration job 294 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 173662
DPS-on run       : 173661
Requested by     : Jason Nielsen
Submitted        : 2003-11-11 08:23:04
Completed        : 2003-11-11 13:22:23
Status           : FAILURE

Last processing stage reported : comparing to the reference calibration
Failure diagnostics :
The calibration failed the following reference comparison criteria:

             Cut Name    Sensor Set   Cut Value   Data Value
---------------------    ----------   ---------   ----------
dps_off_noise rel max    SVX_Z        0.025       0.040338  
     bad_chan rel max    SVX_PHI      0.25        0.540373  

Reference calibration runs are 165831 (DPS off) and 165830 (DPS on)
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->
<!-- Comment: Wed Nov 12 16;41;50 comment by...Jason -->
<BR>
This is VERY interesting.  The bad channel comparison failed because there are no bad strips at the SVX PHI sensor edges for this run.
<P>
Remember how we saw those anomalous ADC distributions at the SVX sensor edges (phi-side only) for the bunch crossings immediately following abort gaps?  (See report in Silicon mtg. of Jul. 11.)  They aren't there for these two calibration runs!  They return for the next calibration 173700/173701, taken one day later.
<P>
I cannot explain yet how we managed to do this for these two runs.  I wish we could do it for every run...  Any ideas?
<BR>
<!-- Date: Tue Nov 11 16:19:03 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_access
<li>Type: Other
<li>Action: Action_request
<li>entered by: sforrest 
<li>description is: bit 0 low, bit 1 high, bit 4 low in channels. Problem still there after fib swap.  Next swap FTM. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 11 16:19:37 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2/3All 
<li>problem n: 1151 
<li>Status: needs_access
<li>Type: Other
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is: Swapped fib for pipe 7 unsuccessful.  Next swap FTM 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W2/3&layer=All">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 11 16:21:24 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W11L4 
<li>problem n: 1135 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: sforrest 
<li>description is: Swapped Rx, problem solved.<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0223">0223</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0794">0794</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W11&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Nov 11 20:27:36 2003 -->
<p><font size=+1> D-mode Calibration Job Finished </font>
<p><pre>
This is a computer-generated silicon D-mode calibration status report.
Silicon D-mode calibration job 295 finished successfully.

Job info
--------
Calibration type : standard
DPS-off run      : 173701
DPS-on run       : 173700
Requested by     : Jason Nielsen
Submitted        : 2003-11-11 12:46:35
Completed        : 2003-11-11 18:24:14
Status           : SUCCESS
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->



<!-- Date: Wed Nov 12 08:50:42 2003 -->
<pre>Another quiet night of running with the guinea pigs - no trips. The plan today is to have the silicon guinea pigs included in test runs whenever possible and to finish the work in fib00 (swap out the FTM for SB1W3L2). Access keys must be returned by 1pm.</pre>
<!-- Author: David -->

<!-- Date: Wed Nov 12 11:13:38 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: needs_observation
<li>Type: Other
<li>Action: Diagnosis_update
<li>entered by: bbrau 
<li>description is: FTM Swapped.  No bit errors observed after swap. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Nov 12 11:15:43 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2/3All 
<li>problem n: 1151 
<li>Status: needs_observation
<li>Type: Other
<li>Action: Swap_FTM
<li>entered by: bbrau 
<li>description is: Swapped ftm to fix bit errors in Channel 7.  No ch 7 bit errors observed after swap.<table border=1>
<tr><td><b>IN</b></td><td>PREP:</td><td>163</td><td>Serial:</td><td>566696</td></tr>
<tr><td><b>OUT</b></td><td>PREP:</td><td>164</td><td>Serial:</td><td>566697</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W2/3&layer=All">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Nov 12 11:19:27 2003 -->
<H1> Access Summary 
</H1> 
 
Swapped FTM FIB00 Slot 15 to fix bit errors in channel 7.  Successful!  Ben's first optical grease job worked... 
<P> 
Removed slot 15 FIB from HW DB, back to only PIGS in. 
</P>  
<!-- Author: bbrau, dkclark -->



<!-- Date: Wed Nov 12 17:13:11 2003 -->
<h3>Probing Ultra Dynamic Prescaling and Resonances</h3> 
We have been using the Guinea Pigs in UDPS tests at rates of ~ 16 kHz or so, to see if there is any sign of resonant readout.  There isn't, however, I wouldn't expect it until UDPS pushes us up to rates of ~ 40 kHz.  So, we <ul> 
<li> took out and turned off the SVXII Guinea pigs - don't want to break them, don't really need them 
<li> left in the "readout at L2" ISL and L00 Guinea Pigs <BR>They don't have jumpers and they don't readout at L1A, so they should be ok - also they can affect the UDPS work 
<li> Disabled the Handbrake via crateEditor on SRC_00, and wrote a 1 to address 28002080 on crate b0svx02 to allow the SVXII SRC to ignore VRBs 
</ul> 
These things should be undone later.
<!-- Author: SCN -->
<!-- Comment: Wed Nov 12 19;29;40 comment by...SCN -->
Note to Sal-<BR>
We made many SRC errors this evening, some of the type <pre>b0svx02 Sl 5 Fib L3</pre> which means the Resonance Detector told the SRC to pull Error, and others of the type <pre>b0svx06: No Scan Buffer</pre> but this was for a run when the TS was ignoring the BUSY signal, so it was a real error with the TS. 
<!-- Date: Wed Nov 12 17:55:41 2003 -->
The svxinter crate and the interlock PLC crate fans were plugged into a different circuit on the first floor today, in preparation for electricians doing work on the original circuit at some ungodly hour of the morning tomorrow.  Will put them back when work is finished.
<!-- Author: Andy H. -->
<!-- Comment: Thu Nov 13 10;06;36 comment by...Andy H. -->
Done.
<!-- Date: Wed Nov 12 20:00:13 2003 -->
<h3>UDPS and Resonance Detector Testing</h3> 
Greg wanted to use the Guinea Pigs to do some UDPS testing, and I 
wanted to see how this effects the READOUT signal distributions with an eye towards resonating wire bonds.  We did, and found out 
that under the test configuration (no SVXII ladders on, so the 
time between READOUTs is the DIGITIZE time of 12.43 uS) the 
resonance catcher pulls CDF Error at around 25 kHz average L1A rate  when looking for 10 kicks in a row within a 1 uS time difference window.  We also found and fixed a bug in the code to enable the 
Error line in the SRC-so I left this error enabled - to gain some experience with it.  If it happens, you get a Front End error from b0svx02, and when one clicks on HALT, one gets a message from b0svx02 saying what sort of error.  Also you may get somke L1DONE timeouts.  It looks somethign like<pre> 
(MLE) b0dap20.fnal.gov:Thread-1190:7:05:52 PM->FrontEnd Error: VRB_SVX_02  
CT: 2003.11.12 19:05:56 
5'56" 1 crate/s: b0svx02(112),  in error.[RXPT] 
CT: 2003.11.12 19:05:59 
5'59" L1 Done Timeout.[RXPT] 
CT: 2003.11.12 19:06:00 
6'0" 1 crate/s: b0svx02(112),  in error.[RXPT] 
CT: 2003.11.12 19:06:04 
6'4" L1 Done Timeout.[RXPT] 
6'4" 1 crate/s: b0svx02(112),  in error.[RXPT] 
(MLE) b0svx02:Messenger:7:06:07 PM->SRC Fatal Error:Sl 5 Fib L 3  
 
(RC)   19:6:14 Halt -> HALTED 
</pre> The 25 kHz is somewhat of a worst case scenario, since adding a non-zero readout time can only randomize the READOUT timing distribution some more.<P> 
I reenabled the handbrake, set the SRC in b0svx02 to not ignore the VRBs, and turned the SVXII Guinea Pigs to standby.
<!-- Author: SCN -->



<!-- Date: Thu Nov 13 18:46:47 2003 -->
Silicon cooling recovered from power cut.  See 
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=950&frame=2&anchor=18:44:30.560'> 
here</a> for an oddity about the ISL chiller.   
<!-- Author: Andy H. -->


<!-- Date: Thu Nov 13 20:04:26 2003 -->
<p><b>Another power cut tomorrow morning at maybe 9:30-ish</b></p> 
<p> 
As a result, a lot of CDF remains off (including our racks).  Cooling is going (see entry above), and it looks like the RTServer is running, somehow.</p> 
<p> 
I tried to get the PS GUI running, but got the error "Can't find class CAEN.PSControlForm."  Is this because a full recovery of the CDF online machines hasn't happened?  Anyway, so that the iFix-GUI communication alarms won't mask any potential cooling alarms, I rigged iFix to ignore the GUI for now.</p>
<!-- Author: Andy H. -->


<!-- Date: Fri Nov 14 13:40:26 2003 -->
<b> Sanity Checks after Power Outage Fest </b> 
 
restarted computers. restarted cron jobs on b0dap43 using cratematch.pl. checked clock sanity at fanout. 
 
silicon racks would not come up immediately. turned out the quad logs needed a reset. brought racks up and they coldstart OK (except for still not attached silicon so init errors). First run fails on <pre> 
 
(RC)   12:32:4 Config -> READY 
(MLE) b0tsi00:Messenger:12:32:09 PM->TS failed when trying to Run (State 2) 
CT: 2003.11.14 12:32:11 
32'11" 1 crate/s: b0svx02(112),  in error.[RXPT] 
(MLE) b0dap44.fnal.gov:Thread-24:12:32:10 PM->FrontEnd Crate Error Condition from: 
(MLE) b0dap44.fnal.gov:Thread-24:12:32:10 PM->FrontEnd Error:  
(MLE) b0svx02:Messenger:12:33:12 PM->SRC Fatal Error:Sl 5 Fib L 3  
</pre> 
 
this was actually predicted by Dr. Nahn as the unitialized GB, he heartily recommended reseting the GB in various ways but did not tell us which registers were to be set. elog-Archeology lead us to assume <pre> 
 4800001c 0x21 and 48000020 0x0a  
</pre> 
after the necessary fiddling could coldstart a run with guniea pigs which works fine now.  
<!-- Author: Rainer, David -->
<!-- Comment: Fri Nov 14 13;52;49 comment by...Rainer -->
<pre>decide to retire now the good ol' pigs and revive the silicon - keep fingers crossed.</pre>

<!-- Comment: Fri Nov 14 15;23;46 comment by...Rainer -->
I get some flaky headshakes  <pre>
    success: Power Supply L00 WEST W0 OFF
Fri Nov 14 14:53:48 CST 2003     ERROR: Power Supply L00 WEST W0 Handshake - Could not turn on power - checked 10 times
</pre> plus the somewhat puzzling effect of clicking on i.e. L00 on and then get instant success but nothing happens. So elect to hockerize all crates and restart GUI as well as svxinter. this does it - things turn on normal now. <p>
RunControl annoys the sh... out of me by shelling me with error windows about a restarted ConsumerMonitor. I turn off the proxy  in my window. <p>

ISL and L00 turn on OK and their fibs pass coldstart. so at least this is good news. SVX is next.
 


<!-- Comment: Fri Nov 14 15;59;41 comment by...Rainer -->
<pre>Actually had again trouble with this GB and reset the registers. whats the persistency of this setting ?</pre>


<!-- Date: Fri Nov 14 17:32:04 2003 -->
<b> imon status in this dmod calibration </b> <p>  
<!-- Author: rainer -->


<!-- Date: Fri Nov 14 17:32:51 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2812&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2813' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2814&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2815' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2816&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2817' ></a></center>
<!-- Author: rainer -->
<!-- Comment: Fri Nov 14 17;45;19 comment by...rainer -->
<pre>shoot - forgot to include e154. has a lot of bit errors but no reason to exclude it. now put back into hwdb.
</pre>


<!-- Date: Fri Nov 14 18:47:28 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2820&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2821  width='300' align='top'></td><td>while waiting for the L3 guy to fix his stuff, several SVX ladders elect to get into a coherent higher current DVDD state as evidenced below. we are dmod calibration mode. eve of another SVX DVDD trip fest ?</a></td></tr></table>
<!-- Author: Rainer -->
<!-- Comment: Fri Nov 14 18;52;57 comment by...rainer -->
<pre>L00 & ISL stay unaffected.</pre>
<!-- Date: Fri Nov 14 18:51:51 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2826&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2827' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2824&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2825' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2822&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2823' ></a></center>
<!-- Author: rainer -->



<!-- Date: Fri Nov 14 19:09:36 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2828&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2829  width='300' align='top'></td><td>bvh</a></td></tr></table>
<!-- Author: rainer -->
<!-- Comment: Fri Nov 14 19;10;49 comment by...Rainer -->
<pre>... meaning, coldstart brings it down. bvh blech blech. bitte schoen.
ISL completely unaffected. is some KEEPALIVE glitching ?</pre>


<!-- Date: Fri Nov 14 19:58:46 2003 -->
On trying to run a PETE run with extra0=4359, the resobuster fires 
and several VRBs go bonkers, see <a href='http://www-cdfonline.fnal.gov/daq/runSummary/errorlog/errorfile174076.log' > 174076 </a>. Upon HRR we run for a while. Also still have super annoying <pre> 
 
(MLE) b0dap73.fnal.gov:Thread-30:7:23:51 PM->ConsumerMonitor Partition_5 is not 
running! 
Silicon could be in grave danger!Please start the ConsumerMonitor (aka ConsumerErrorReceiver)! 
 
</pre> which fills the screen with its error message such that there is no hope to click anything (about 50 windows/minute). SVXMon was restarted several times and it did not solve the problem. Procmon however is red all over the place (cali b consumer proxy, res mgr proxy, consumer monitor proxy etc) likely due to moving the jobs (see  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=952&frame=2&anchor=13:24:34.179'> 
here </a>). Aces were instructed this would not matter but it probably is the root of all RC evil. disapbled ComsumerMonitor Proxy and carried on regardless. bah.However, L3 kicks the bucket.  
 
  
<!-- Author: rainer -->
<!-- Comment: Sat Nov 15 00;09;16 comment by...rainer -->
<pre>made line 3 resobuster error non fatal for these dmod calibration runs w/o b filed.</pre>
<!-- Comment: Sun Nov 16 05;28;57 comment by...rainer -->
<pre>back to normal after runs.</pre>
<!-- Date: Fri Nov 14 20:33:31 2003 -->
<h3> post-crazed north muon wall incident checkout </h3> 
is defined  
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2003&action=view&page=953&frame=2&anchor=20:30:43.023'> 
here.</a>  food for pete and jason.   
<!-- Author: rainer -->



<!-- Date: Sat Nov 15 01:43:18 2003 -->
<h3> IB5W0  persistent PC trip </h3> <p> 
 
got paged at around midnight about a persistent trip of IB5W0. The silicon was taking dmod calibrations in standby for bias verification. the trigger inhibits were not booked but the run manually halted. Apparently from 2VDOIM, but I am confused about the 'external trip'. is this a handshake problem ? how are external trips defined ? 
<pre> 
Fri Nov 14 23:47:05 CST 2003     IFix -  success: Silicon to STANDBY   
Sat Nov 15 00:01:57 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:01:57 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:01:57 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:01:57 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:01:57 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:01:57 CST 2003     TRIP: ISL  B5  W0 2VDOIM OverCurrent 
Sat Nov 15 00:06:44 CST 2003     success: Resetting trips 
Sat Nov 15 00:08:10 CST 2003     success: Power Supply ISL B5 W0 to STANDBY 
Sat Nov 15 00:08:43 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:08:44 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:08:44 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:08:44 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:08:44 CST 2003     TRIP: ISL  B5  W0 External Trip 
Sat Nov 15 00:08:44 CST 2003     TRIP: ISL  B5  W0 2VDOIM OverCurrent 
Sat Nov 15 00:40:12 CST 2003     success: Port Card ISL B5 W0 ON 
Sat Nov 15 00:40:27 CST 2003     TRIP: ISL  B5  W0 2VDOIM OverCurrent 
Sat Nov 15 00:40:54 CST 2003     ALARM:   ISL  B5  W0 PC is reported OFF, but low/high voltage is above 2/5 V  
Sat Nov 15 00:43:03 CST 2003     success: Port Card ISL B5 W0 ON 
Sat Nov 15 00:43:19 CST 2003     TRIP: ISL  B5  W0 2VDOIM OverCurrent 
Sat Nov 15 00:43:29 CST 2003     ALARM:   ISL  B5  W0 PC is reported OFF, but low/high voltage is above 2/5 V  
Sat Nov 15 01:20:52 CST 2003     success: Port Card ISL B5 W0 ON 
Sat Nov 15 01:22:43 CST 2003     TRIP: ISL  B5  W0 2VDOIM OverCurrent 
</pre>  
<!-- Author: Rainer -->


<!-- Date: Sat Nov 15 01:50:25 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2834&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2835' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2830&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2831' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2832&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2833' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2836&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2837' ></a></center>
<!-- Author: Rainer -->
<!-- Comment: Sat Nov 15 02;01;23 comment by...Rainer -->
<pre>judging from this it more looks like 5VDOIM actually produced the trip off since it gradually increased, turned pink and then tripped. but is it reliable ? for comparison some AVDD current.</pre>

<!-- Comment: Sat Nov 15 02;15;04 comment by...rainer -->
limits are (caution levels are quoted):
<table><tr><th> what <th> min  <th>  max <th> last read <th> trip limit  </tr>
<tr><td> 2VDOIM<td> 795  <tD> 935 <td> 925,940,945 <td> 950 (*) </tr>
<tr> <td> 5VDOIM <td> 1635  <td> 1775 <td> 1735, 1740 <td> 1870 </tr>
</table>
The values creep up within 2 minutes, but long enough to see it actually happen in the display. so I conclude it IS 2VDOIM and it also looks like it is real, see next plots.


<!-- Date: Sat Nov 15 03:11:56 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2838&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2839' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2840&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2841' ></a><a href='/elog/notebooks/silicon/Sat_Nov_15_2003_031121.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2853' ></a></center>
<!-- Author: Rainer -->
<!-- Comment: Sat Nov 15 03;14;05 comment by...rainer -->
<pre>RED is IB5W0. BLACK is IB2W0 which is considered healthy. Day of northwall accident was thursday 11/14/03 = DS 1046. It is a fact that this ladder came out of its last sleep with increased 2V DOIM currents.
NB: where are the trip limits set ? they seem to vary from PC to PC. I don't find them in the HWDB.</pre>

<!-- Comment: Sat Nov 15 03;53;02 comment by...rainer -->
<pre>wanted to check 2V/5V DOIM voltage stability plus what happened to IB5W0 DVDD0 but the UCSB plotting is hosed somehow. time window was 1008.5 ... 1048.5.

last step will be hockerization of crate, hoping (but not believing) that it might be a fake reading. but you never know.</pre>


<!-- Comment: Sat Nov 15 04;44;10 comment by...rainer -->
<pre>of course, the only runs taken today are pretty wacky ones (different run setting, lower threshold) so maybe, after all no suprise that they stick out. in fact, let's see .... 1028 is the date of the last pete runs so, yes, pete runs make this guy draw more current on 2VDOIM (but apparently not the others ??)
</pre>
<!-- Comment: Sat Nov 15 13;39;36 comment by...rainer -->
<pre>but then again, some 2V DOIM seem to draw MORE current when running and some do LESS so this is not at all a clear picture ....</pre>
<!-- Date: Sat Nov 15 04:38:22 2003 -->
<pre>hmmm.... so first of all I hockerized #9/#10 instead of #15/#16 so that was not so good. then, after hockerization, 2VDOIM comes back at 900mA. I wouldn't claim that is because of the hockerization, but now the wedge is back on, albeit at elevated currents which is worrisome. furthermore worrisome is the fact  that the currents keep increasing when running, so it is load dependent and arguably a question of time until it hits 950 again and trips - I coldstart type idle running it went up all the way to 930 in a steep slope. this guy does have higher settings than the others, so first of all it must be possible to set the current trip limits indivdually but I don't know how.  some variance of course might come from the #@$#$#$% offsets, which I don't know whether they are taken out in the imon reading. also, there might be a prehistory I am missing and I did not find anything conclusive in the elog. chances are I am too tired. 
I will close this chapter know, resume the run and hope the wedge won't trip off.</pre>
<!-- Author: rainer -->


<!-- Date: Sat Nov 15 04:39:10 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2854&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2854' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2855&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2855' width='300'></a></center>
<!-- Author: rainer -->
<!-- Comment: Sat Nov 15 04;40;27 comment by...rainer -->
<pre>nucsb03 was finally kind to me and spat out at least these plots - on 'grounding' shift due to damaged wire or short to DVDD0 ala SB4W4L0 could be deduced from this. I hope this is MUCH faster on the b0sili's.
</pre>



<!-- Date: Sat Nov 15 05:03:11 2003 -->
<b> back in business ....  </b> well we'll see. taking run 174103 right now which is the pete 4359 unbiased run, and, as happened before, el resonatore fires on the first events, to be appreciated <a href=' http://www-cdfonline.fnal.gov/java/cdfdb/servlet/RunSummary?RUN_NUMBER=174103'> here </a>.
<!-- Author: rainer -->
<!-- Date: Sat Nov 15 05:17:54 2003 -->
<pre>
WARNING: found a power supply in the crate, which is not connected to a wedge i2 Caenet_write: Error number -253 received  cr = 16, bd = 2,Errcode 10                                       WARNING: found a power supply in the crate, which is not connected to a wedge i6 Caenet_write: Error number -253 received                                       
</pre> 
oddity picked up from svxinter BEFORE hockerization. dumdidum.
<!-- Author: rainer -->


<!-- Date: Sat Nov 15 05:36:46 2003 -->
<b> easterbunny </b> 58209 0 61953 2
<!-- Author: rainer -->
<!-- Comment: Sat Nov 15 14;30;59 comment by...rainer -->
<pre>undone now.</pre>
<!-- Date: Sat Nov 15 07:39:45 2003 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 296
Calibration type  : nonstandard
Run period tag    : Nov_2003
DPS-off run       : 174109
DPS-on run        : 174108
Requested by      : M. Casarsa
Main process id   : 34808135
Comment           : magnet off
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Sat Nov 15 07:56:22 2003 -->
<pre>The following calibration runs were taken during the night with solenoid OFF and trigger table COSMICS [11,284,403]:  
 
- 174103: extra0=4359 and bias in STDBY;  
- 174105: extra0=4359 and bias ON;  
- 174108: extra0=1 and bias ON;  
- 174109: extra0=0 and bias ON.  
 
b0trin00 crate was dropped. 
</pre>
<!-- Author: M.Casarsa/E.Ben-Haim -->
<!-- Comment: Tue Nov 25 01;07;39 comment by...rainer -->
<pre>unfortunately the setting was wrong - it should have been done with SVX_THRESHOLD_D, not dmod calibration style. my fault</pre>
<!-- Date: Sat Nov 15 16:14:07 2003 -->
<p><font size=+1> D-mode Calibration Job Finished </font>
<p><pre>
This is a computer-generated silicon D-mode calibration status report.
Silicon D-mode calibration job 296 finished successfully.

Job info
--------
Calibration type : nonstandard
DPS-off run      : 174109
DPS-on run       : 174108
Requested by     : M. Casarsa
Submitted        : 2003-11-15 05:37:58
Completed        : 2003-11-15 14:13:41
Status           : SUCCESS
Comment          : magnet off
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->


<!-- Date: Sat Nov 15 20:08:34 2003 -->
Entered in Silicon database: <ul>
<li>Ladder: IB5W0All 
<li>problem n: 146 
<li>Status: needs_observation
<li>Type: VDOIM
<li>Action: Incident
<li>entered by: rainer 
<li>description is: PC has tripped on 2VDOIM OC during special dmod calibration runs, see  <a href= '/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=172&frame=2&anchor=01:43:18'> here</a>. hockerization and vodoo brought it back to normal, but current levels seemed to be elevated by at leat 50mA. To be checked if they return to pre-shutdown levels during normal data taking.  
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B5W0&layer=All">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sun Nov 16 05:27:36 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2856&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2857  width='300' align='top'></td><td>PC currents 2VDOIM of IB5W0 over the last days. </a></td></tr></table>
<!-- Author: Rainer -->



<!-- Date: Sun Nov 16 09:12:44 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2862&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2862  width='300' align='top'></td><td>We saw a whole area turning pink in L00. Unmarked all cells.</a></td></tr></table>
<!-- Author: Claudia -->


<!-- Date: Sun Nov 16 09:36:37 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2874&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2874' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2871&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2871' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2870&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2870' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2873&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2873' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2869&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2869' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2872&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2872' width='300'></a></center>
<!-- Author: Claudia -->
<!-- Comment: Sun Nov 16 09;38;29 comment by...Claudia -->
<pre>plots of svx,ils and l00 before and after the unmarking of the cells</pre>


<!-- Date: Sun Nov 16 13:21:46 2003 -->
<h3> Hmm ??? </h3> 
<pre>Error Handler Log File 
All timestamps are referred to CT 
CT: 2003.11.16 13:03:34 
Partition:5 Run number: 174204 (0x2a87c) 
(MLE) b0fib00:Messenger:1:03:50 PM->Error Initializing HDI Slot 11 Chan 2: SVX B0W2 
(MLE) b0fib00:Messenger:1:03:51 PM->Statechange failed 
(MLE) b0svx06:Messenger:1:04:54 PM->Silicon Timeout:BUSY- Slots:  20:f840 
 
(MLE) b0svx02:Messenger:1:04:54 PM->Silicon Timeout:BUSY- Slots:  20:e2a0 
 
(MLE) b0svx06:Messenger:1:04:54 PM->Silicon Timeout:!DONE- Slots:  20:f840 
(MLE) b0svx02:Messenger:1:04:54 PM->Silicon Timeout:!DONE- Slots:  20:e2a0 
(MLE) b0svx02:Messenger:1:04:54 PM->SRC Fatal Error:Sl 5 L2A w/o L1A  
 
(RC)   13:5:13 Abort -> IDLE 
(RUN Comment) rundb.RunComment@94e76a 
  RunNumber   174204 
  CreateTime  2003-11-16 13:05:18.0 
  TextComment abort due to fib00 got red while configuring 
  Name        yves 2080 
  State       TERMINATE 
</pre> 
<li> why doesn't SB0W2L2 init ? second time it apparently worked. 
<li> what's this 5 L1 business ? 
they were running a dmod ...  
<!-- Author: rainer -->
<!-- Comment: Mon Nov 17 08;39;01 comment by...SCN -->
<pre>(MLE) b0svx02:Messenger:1:04:54 PM->: L2A w/o L1A </pre> is to be decoded as <ul>
<li> <i>(MLE)</i> Some Runcontrol-ese stating this is a Merlin message
<li> <i>b0svx02:Messenger:1:04:54 PM</i> The processor, process, and timestamp of the message
<li> <i>SRC Fatal Error</i> The class of Error
<li> <i>Sl 5</i> The <b>Slot</b> of the SRC (Slot 5 in this case)
<li> <i>L2A w/o L1A</i> The type of error
</ul>
There is no "5 L1A" business.  The error is that the first SRC saw a L2A without a corresponding L1A.
<!-- Date: Sun Nov 16 13:29:28 2003 -->
<h3> hmm hmm ???? </h3> 
<pre> 
Error Handler Log File 
All timestamps are referred to CT 
CT: 2003.11.16 13:08:42 
Partition:5 Run number: 174205 (0x2a87d) 
(RC)   13:9:8 Config -> READY 
(MLE) b0tsi00:Messenger:1:09:17 PM->TS L2 FSM failed to start (State 14) 
CT: 2003.11.16 13:09:19 
9'19" 1 crate/s: b0svx02(112),  in error.[RXPT] 
(MLE) b0dap73.fnal.gov:Thread-36:1:09:19 PM->FrontEnd Crate Error Condition from: 
 
(MLE) b0dap73.fnal.gov:Thread-36:1:09:19 PM->FrontEnd Error:  
(RUN Comment) rundb.RunComment@723278 
  RunNumber   174205 
  CreateTime  2003-11-16 13:10:13.0 
  TextComment shepherded fib00, now tsi00 is making problems again. 
WIll abort run 
  Name        yves 2080 
  State       ACTIVATE 
(MLE) b0svx06:Messenger:1:10:26 PM->Silicon Timeout:BUSY- Slots:  18:f820 
 
(MLE) b0svx02:Messenger:1:10:26 PM->Silicon Timeout:BUSY- Slots:  18:e280 
 
(MLE) b0svx06:Messenger:1:10:26 PM->Silicon Timeout:!DONE- Slots:  18:f820 20:f840 
(MLE) b0svx02:Messenger:1:10:26 PM->Silicon Timeout:!DONE- Slots:  18:e280 
(MLE) b0svx02:Messenger:1:10:26 PM->SRC Fatal Error:Sl 5 L2A w/o L1A  
 
(RC)   13:10:45 Abort -> IDLE 
(MLE) b0dap73.fnal.gov:Thread-36:1:10:55 PM->ConsumerMonitor Partition_5 is not running! 
Silicon could be in grave danger! 
Please start the ConsumerMonitor (aka ConsumerErrorReceiver)! 
</pre> 
Aces tried to shepherd b0fib00 which apprently worked but again a L2 w/o L1 ....
<!-- Author: rainer -->
<!-- Comment: Sun Nov 16 16;06;57 comment by...rainer -->
<pre>problem can be reproduced in SVXDAQ and local run control (if you survive the gazillion pop-up windows....)</pre>


<!-- Date: Sun Nov 16 16:24:58 2003 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2875&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2875' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2877&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2877' width='100'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2876&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2876' width='300'></a></center>
<!-- Author: rainer -->


<!-- Date: Sun Nov 16 18:17:32 2003 -->
<h2>SRC Status</h2> 
I tried to have a look at what was causing the problems seen earlier, but I (very stupidly) initialized the SRC's in svxdaq, and the problem went away. This is good because it went away, but of course it is bad because I didn't see what the problem was. It seems to be okay now. The D-Mode calibration seems to be happy.
<!-- Author: Sal R. -->


<!-- Date: Sun Nov 16 18:33:33 2003 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2878&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-2879  width='300' align='top'></td><td>old fellow SB2W2L4 again in high current DVDD state. HRR helped. </a></td></tr></table>
<!-- Author: rainer -->


<!-- Date: Sun Nov 16 18:48:09 2003 -->
<b< pending  <a href= 
'/cgi/elog/elog.pl?nb=2003&action=view&page=959&frame=2&anchor=18:27:50.659'> 
dmod calibrations </a> with B-field ON  
to be registered </b> because of some badgettism.mySQL currently down.
<!-- Author: rainer -->


<!-- Date: Sun Nov 16 22:00:39 2003 -->
<h3> Silicon is OFF </h3> in anticipation of some beam in TeV. <p> 
<li> PS interlocks disabled in IFIX (when will I ever to be able to dispense of this old paper dish ?) 
<li> kill switches enabled. 
<p> 
sogni d'oro.
<!-- Author: Rainer -->