<!-- Title: 10:38:09  Mon Sep  5 2005 -->
<!-- Crewchief: Juan Pablo -->
<!-- Op1: Marcel  -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<p> 4370 colliding </p> 
<p> First week for Madrid ! </p> 
<p> Ala Madrid !</p>


<!-- Date: Mon Sep 5 11:41:22 2005 -->
<p>La cucaracha ya SI puede caminar : 
</p> 
<p>We did a test to confirm our suspicition-hyphothesis 
that what makes the CAEN crate unhappy is a bad/non-existen 
conection on pin no. 8. 
</p> 
<p>For that we just got a working CAEN module, bent the correspondent 
leg on the chip-eprom (la cucaracha) and tested it. We reproduced 
the same failure that Sebastian and Jen saw down in the pitt. 
We unbent the leg and the module went back to its normal state 
of happiness. </p> 
<p> We learnt in the processs that happiness mean : "you know who you are" ... or somebody else does ... eitherway</p>  
<!-- Author: Juan Pablo / Sebastian -->


<!-- Date: Tue Sep 6 01:16:45 2005 -->
<h3>ISL Trip?</h3> 
Passing by the CR, Viktor told me of an ISL trip, see the 
main elog entry <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2005&action=view&page=744&frame=2&anchor=19:26:21.905'> 
here</a>. Apparently some ISL wedges tripped. Ladders of PS of CAEN cr 11 (IB1W1 is a typo, it was IB3W1). The trip is shown in the PS logs. However, the Gui log does not show anything: 
<pre> 
Mon Sep 05 05:19:37 CDT 2005     IFix -  success: Silicon ON   
Mon Sep 05 19:15:41 CDT 2005     success: Resetting trips 
Mon Sep 05 19:17:31 CDT 2005     success: Power Supply ISL B3 W0 ON 
Mon Sep 05 19:18:30 CDT 2005     success: Power Supply ISL B3 W1 ON 
Mon Sep 05 19:18:49 CDT 2005     success: Power Supply ISL B4 W2 ON 
Mon Sep 05 19:19:05 CDT 2005     success: Power Supply ISL B4 W3 ON 
Mon Sep 05 19:19:20 CDT 2005     success: Power Supply ISL B5 W3 ON 
</pre> 
 
And the PS log shows the correct state of all the wedges, 10 seconds later (the trip at 19:14:00, and at 19:14:10 we are fine). However an inhibit at 
19:14 shows in the errorlog for the run, after the first inhibit from flying wires. I am guessing that the PSgui did showed the ladders as tripped and so the Ace "recovered" them, this took about 5min.. turning on ladders that were on on the first place (would the gui complain??). Looks like the Gui did not see that the ladders were back 10sec after the "trip". I wonder how many of these episodes confuse us daily... looks like one needs some time to search through the log files to see what was going on, quite dificult to do in case of a trip and the need to continue with data taking.
<!-- Author: Sebastian -->
<!-- Comment: Tue Sep  6 01;27;21 comment by...Sebastian -->
Wrong! I was grepping through the logs but I forgot entries for a given ladder and measure are entered only when changed from previous value, so the ladders did trip and they were recoved by Viktor.. still the PS gui did not show the trip, any ideas why?

<!-- Comment: Tue Sep  6 08;40;25 comment by...Marcel and Juan Pablo -->
Victor is very weak in the force. Even in case of a spontaneous transition, IFIX will tell you a trip. But the CAEN just turns off. He is obviously not clever enough to look at the PSGUI to see, if there are TRIP messages there. I told the Aces several times already this simple fact. If it does not show in the GUI as trip, it is not a trip.<br>
As a background information, in this class of CAEN SEU's ,crate just turns all attached ladders. In this case of CAEN mad cow disease it was SE TOP TOP (11).



<!-- Comment: Tue Sep  6 14;16;07 comment by...s -->
So, the PS logs are correct, there was no trip, just the CAEN PS somehow got an OFF command, that's why it did not showed in the PSgui.
<!-- Date: Tue Sep 6 12:59:04 2005 -->
<pre>AVDD overcurrent on e550. After trying to bring it up several times and hockerizing the correspondent caen crate (14), we took it off from the database.Put it back because the whole wedge tripped  
again (DVDD overcurrent) inmediately after. So, suspect fib problem (b0fib06). Reboot fib helped. We are running ... for the moment ...</pre>
<!-- Author: Juan Pablo/Sebastian -->
<!-- Comment: Tue Sep  6 13;03;11 comment by...Juan Pablo / Sebastian -->
<pre>We suspect the fib sequencies. Restarting the run rewrited the
sequencies so the problem was solved consecuently.</pre>

<!-- Comment: Tue Sep  6 13;22;53 comment by...Juan Pablo / Sebastian -->
<p>Rebooting a fib does not rewrite the sequencies </p>
<p>Issuing a "reset_crate b0fibXX" DOES rewrite the sequencies </p>
For future referencies : the best thing to do if a fib sequence gets corrupted is
to issue a "reset_crate b0fibXX" because we do not need then
to restart the run (and save some time there)</p>


<!-- Comment: Tue Sep  6 14;13;49 comment by...M/JP/S -->
<br>
What we think might have happened:
<ul>
<li> FIB_33 (b0fib06) got corrupted somehow. e55 started acting up (specially e550 since it is already a troublesome ladder). Since e54 is OFF we only saw problems with e55.
<li> After some struggle a new run was started.. A FIB master reset is issued on the config transition which would clear the problem of a SEU on a IC.
<li> Looks unlikely that the problem was with the FIB sequences, since no report of corrupted MS was found on the logs.
</ul>

<!-- Date: Tue Sep 6 13:27:20 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7396&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7397  width='300' align='top'></a></td><td>SVT spy mon looks fine. SVXMon seems fine too.</td></tr></table>
<!-- Author: Juan Pablo -->




<!-- Date: Tue Sep 6 18:47:19 2005 -->
Problems with the Lost pbars, after consulting with MCR, they offered to rescape.  Silicon is going to Standby for the time being
<!-- Author: Marcel -->
<!-- Comment: Tue Sep  6 18;47;56 comment by...Marcel -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2005&action=view&page=-16008&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-16008 width='300' align='top'></a></td><td>Escalating Losses at D0 and CDF after TeV 28cm Beta* study.</td></tr></table>

Plots for CDF and D0 losses

<!-- Comment: Tue Sep  6 19;51;25 comment by...Marcel -->
ok, MCR did have to rescrape, after that things look much better now.


<!-- Date: Tue Sep 6 21:15:41 2005 -->
<pre>SB4W9 L4 tripped on AVDD overcurrent. Tried to bring it up alone 
failed. So I powered the whole wedge off and then on and this time 
worked. We are running again. </pre>
<!-- Author: Juan Pablo -->


<!-- Date: Wed Sep 7 11:40:45 2005 -->
<pre>Due to an RF station being lost, Marcel noticed  
a spike in the abort gap and proton losses. He put the silicon in standby, waited until the beam is stable again and ramped the silicon back up. 
 
</pre>
<!-- Author: Juan Pablo -->
<!-- Comment: Wed Sep  7 12;13;32 comment by...Juan Pablo -->
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2005&action=view&page=749&frame=2&anchor=11:39:18.448'>
this </a> is the abort gap and proton loss ACE plot for the RF station loss. The scale is 15k for all four plots.
<!-- Date: Wed Sep 7 12:04:41 2005 -->
TRF8 tripped off. Silicon went to Standby, CMX tripped off.   
<!-- Author: MArcel -->



<!-- Date: Wed Sep 7 13:50:06 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7402&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7402' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7398&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7398' width='300'></a></center>
<!-- Author:  Juan Pablo. -->
<!-- Comment: Wed Sep  7 13;54;28 comment by...Juan Pablo. -->
<p>SB0W6L2 (left plot) and SB3W5L1 (right plot): </p>
<p>These ladders are candidates for a non-flat pedestal behavior(therefore, high readout time).</p>
<p>Raising the thresold approx. 3 ADC counts might help.</p>



<!-- Date: Wed Sep 7 13:59:47 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7403&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7403' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7401&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7401' width='300'></a></center>
<!-- Author: Juan Pablo -->
<!-- Comment: Wed Sep  7 14;08;44 comment by...Juan Pablo -->

<p>SB1W10L4 (left plot) and SB2W2L4 (right plot) : </p>
<p>These two ladders need quiet time studies.</p>
<p>SB1W10L4 is probably super grassy and there is nothing else
we can do</p>
<p>Let's us just remember that the grassiness is at it worst
whenever we just bias the micron ladders</p>
<p>After 1/2 - 1 hour it calms down (though it never disapears)</p>
<p>SB2W2L4 is a different issue (not grassy related)</p>


<!-- Date: Wed Sep 7 14:10:22 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7399&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7399' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7400&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7400' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7405&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7405' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7404&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7404' width='300'></a></center>
<!-- Author: Juan Pablo -->
<!-- Comment: Wed Sep  7 14;17;10 comment by...Juan Pablo -->
<p>SB3W1L4 (top left), SB2W10L4 (top right), SB1W11L4-z (bottom left), SB1W11L4-rphi (bottom right) :</p>
<p>These ladders are too grasy and cause high readout time</p>
<p>(seen also by David Stuart)</p>



<!-- Date: Wed Sep 7 14:26:32 2005 -->
<pre>The way I spot these ladders is by just running a macro that Ulrich and I wrote. 
You are wellcome to use it : 
Just get it from b0dap30:~fernand/loopdir.C (or any other online machine) 
In order to run it just open a root sesion and do : 
root[] TFile *f1 = new TFile("/mnt/autofs/cdf/cdf-cf-data1/cdf_cf/results/SVXMon/svxmon_203799.root"); 
(or whichever SVXMon file you like) 
root[] f1->cd("SVXMon (expert)/Strip Plots/SVX/B0") 
(so cd to the directory on this file  with the occupancy plots; we can modify the code so it does these two step automaticaly ... I will let you know once I change it) 
root[] .x loopdir.C(gDirectory);</pre>
<!-- Author: Juan Pablo -->


<!-- Date: Wed Sep 7 14:50:18 2005 -->
The silicon detector is OFF. Ulrich and Jen will let the Silicon temperature to go up to 0 degrees.  
<!-- Author: Juan Pablo / Sebastian -->
<!-- Comment: Wed Sep  7 16;46;42 comment by...Ankush & Marcel -->
<p>While powering off the detector the racks tripped off.  The racks have been recovered and the FIBS are back.  As a check we did a COLD START....of course it failed as the ladders are off. But you can see in the mincom windows that the FIBS were <em>FIBing</em></p>

<!-- Comment: Wed Sep  7 16;53;27 comment by...Ankush & Marcel -->
Racks tripped off. Jim reseetd everything (Quadlog) and we everything came back up.
Crate 3 needed to be hockerized .... We flipped the interlocks, so nothing can be powered .


<!-- Date: Wed Sep 7 17:23:21 2005 -->
Jen about the boroscope Camera:<br> 
Its making noises .... good  it is working 
<!-- Author: Marcel -->


<!-- Date: Wed Sep 7 19:15:30 2005 -->
<h3>Warming up the silicon</h3> 
 
For the COT plug access we were asked to warm up the silicon by changing the temperature setpoint of the SVX chiller to 0C and the setpoint of the ISL chiller to 15C. The following steps have been performed: 
<ul> 
<li>We switch off the silicon. <b>Note: DO NOT switch off the silicon in one step, because this may cause a trip in motor generator 3. It is better switched off barrel by barrel.</b></li> 
<li>We change the temperature setpoints for the two chillers as indicated above. We realize that the spare chiller was working on a local instead of a remote setpoint. The local setpoint was still at 6C. We change the setting to 'remote setpoint'.</li> 
<li>The ISL chiller has been repaired yesterday (altogether, four broken valves had to be replaced). We ask Stefano Moccia and Jim Humbert to switch back from the spare chiller to the ISL chiller. In the course of this, we have a low-flow trip in the East half of the ISL.</li> 
<li>In addition to the low-flow trip, we encounter a SVX rack trip. The PLC interlock system is not related to the the racks, so the trip is caused by the Quadlock system. Jim suspects fluctuations in the chilled water supply (ECW). ECW is used both for the SVX/ISL chillers and the racks.</li> 
<li>Time constant for SVX: 0C reached in less than 1.5 hours</li> 
<li>Time constant for ISL: 15C reached in approx. 3.5 hours (including chiller swap, still rising)</li>  
<li>The "saturation temperature"  in the SVX is about -1C instead of 0C, so we (i.e. Marcel, pluralis maiestatis) decide to increase the setpoint to +1C. Unfortunately, this causes a power supply trip due to high temperature in L00.</li>  
</ul>
<!-- Author: Jennifer :-) & Ulrich -->
<!-- Comment: Thu Sep  8 05;15;32 comment by...Ulrich H. -->
<br>
The L00 (and later also ISL) temperature trips were actually caused by too  high temperatures in the portcards, a consequence of warming up the ISL chiller to 15C.
<!-- Date: Wed Sep 7 20:13:56 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7406&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7407' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7408&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7409' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7410&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7411' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7412&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7413' ></a></center>
<!-- Author: Ankush & Marcel -->
<!-- Comment: Wed Sep  7 20;15;53 comment by...Ankush & Marcel -->
<p>Pictures at the bore just after the COT baggy was cut.  We will need to check out SB5W1 and FB3W1.</p>

<!-- Comment: Wed Sep  7 21;04;39 comment by...Marcel -->
The good news on Superlayer 7 is,there are no cables from us ...
Bad news, for the work on Superlayer 4 there is a lot of it. 



<!-- Date: Wed Sep 7 23:17:23 2005 -->
<h3>IB0W3 again</h3> 
 
The FCC people made J38-A8 pin thicker. We tried it in the  
crate (3) during the long COT access but it failed again with the 
same error (wrong header checksum, wrong firmware checksum). 
We think that it is worth trying again (making the pin even thicker). We took some pictures with the borescope which 
may help us decide how the modified pin should look like. 
<br>
<!-- Author: Jen/Juan Pablo/Sebastian -->
<!-- Comment: Thu Sep  8 00;24;30 comment by...Another one bites the dust -->
Princess Jen: <em> Nobody is touching my supplies </em>


<!-- Comment: Thu Sep  8 04;52;40 comment by...Ankush/JP/Sebastian -->
<br>
<h3>Yet again</h3>

Checked the GND and A8 pins in the PS teststand crate, first
by looking at pins 14 and 25 of the X28C256 PROM (when the PS modules is connected) and then directly at the corresponding 
holes in the socket connector (A1 and A8), in both cases 
I saw a 2V signal. So we (first JP and I, then Ankush and I (*)) went to the collision hall to see if we can see the V drop also in crate 3 for slot 5.
The idea being that if we do see the voltage, then we have further indication that the problem is that the pin in the PS module is not making contact, and discourage the possibility 
of not having any signal coming from the mainframe for this socket hole (for this slot). <b>We did found the 2V on the 
backplane for this pin in crate 3</b>, so again, we suspect that the problem is that we are not making contact. The pin-probe that we used for
the socket conector (A8) is thicker (and is also somehow tiwsted) that the modified pin the PS right now.<br>



   

<!-- Comment: Thu Sep  8 04;54;36 comment by...Sebastian -->
<br>
(*)
While moving the lifts Juan Pablo hurt his hand, not badly, but
he fainted a few times while I was running around talking in spanish to Larry over the phone... The lack of sleep, the lack of food and the overwork (plus the soccer game yesterday) got the best of JP. He is fine now (sleeping).<br>

<!-- Date: Thu Sep 8 01:15:49 2005 -->
<h3>Access Report: The Cool Suckers</h3> 
After the COT work was finished, we went into the east bore to check out the dewpoint sensors, i.e. combined relative humidity (RH) and temperature (RTD) sensors. The east bore contains the SVX dewpoint sensor, which has shown negative RH for a month or so now. The west bore (inaccessible tonight) contains the ISL sensor, which broke recently (after showing negative RH for 2-3 months. Each dewpoint sensor has a spare sensor close to it.  
<p> 
In the SVX, the RH sensor was actually paired with the RTD sensor of the spare, because the original RTD sensor was broken. We rewired the setup such that also the RH sensor is connected to the spare. The spare RH sensor is showing a reasonable reading (0-1% RH). So it seems that the degradation of the sensor only takes place if it is powered.  
<p> 
We also measured the resistance between the four connectors. A working RH sensor shows: 
<ul> 
<li>3.2 MΩ between 'VDC out' (green, pin E) and 'ground' (black, pin D),</li> 
<li>2.7 MΩ between '+VDC supply' (red, pin C) and 'ground',</li> 
<li>3.4 MΩ between '+VDC supply' and 'VDC out',</li> 
<li>Infinite resistance between 'Case ground' (white, pin F) and all other connectors.</li> 
</ul> 
The degraded SVX RH sensor shows only 0.6 MΩ between 'VDC out' and 'ground', i.e. the data line really looks different compared to a working sensor. 
<p> 
Next we attacked the spare RTD sensor which was not working before the access. We measured infinite resistance between the lines for the excitation current and the voltage measurement on one side of the sensor (red wires). On the other hand, the RTD showed an ok resistance of 107 Ω. In order to check if the reason for this failure is a bad connector, we cut the connector and measure the resistance again - same results. Ergo, the connection is broken somewhere else. Anyway, we re-terminated the RTD such that we may use it later as a three-line RTD.  
<!-- Author: Jennifer :-), Andy, and Ulrich -->


<!-- Date: Thu Sep 8 01:49:44 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7414&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7415' ></a></center>
<!-- Author: Ankush -->
<!-- Comment: Thu Sep  8 01;55;43 comment by...Ankush, Marcel ,etc -->
<p>During the post-COT check out we noticed this bundle of fibres were sticking a little furthur from the COT end-plate compared to its neigbours.  We measured the distance ~2.5inches.  The end-face of the plug is supposed to be ~3inch from the COT face so it should be OK. </p>

<p>We made a second inspection and noticed other silicon cables which were sticking out just as far. So it <em>should</em> be OK.</p>  


<!-- Comment: Thu Sep  8 02;12;30 comment by...Ankush, Marcel and the padawans -->
anyway, we told Aron to check this thing with the plug distance meter, when they put the plug back in. Just to doublecheck ...
<!-- Date: Thu Sep 8 01:56:42 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7418&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7419' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7420&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7421' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7422&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7423' ></a></center>
<!-- Author: Paparazzi -->






<!-- Date: Thu Sep 8 09:36:50 2005 -->
<h2> Status of checkout </h2> 
So everything is back on, the only trouble maker is f214, that keeps tripping and also taking the whole wedge with him. We decided to give him some rest
<!-- Author: Marcel -->


<!-- Date: Thu Sep 8 10:16:23 2005 -->
<pre>The whole detector tripped. 
Some technitians were working downstairs in the alcobe but this does not necesarily mean that they were the of cause it. We are keeping the detector OFF for the moment.</pre>
<!-- Author: Juan Pablo / Sebastian -->
<!-- Comment: Thu Sep  8 10;45;51 comment by...Juan Pablo. -->
<pre>In ifix Rong noticed that the pressure on the East side of the COT face dropped considerably.</pre>

<!-- Comment: Thu Sep  8 11;07;06 comment by...JP -->
<pre>Acording to Ulrich, this is a consequence not a cause
of the underflow of the silicon detector.</pre>
<!-- Comment: Thu Sep  8 11;35;56 comment by...Jennifer/JP/Sebastian -->
<br>
With Jennifer we checked iFix alarm history and saw that the
cause of the trip was low flow to SVX (BHW1, BHW2,
BHW3) then: L00W, PCW, BHE1, BHE2, BHE3, L00E followed
by ISL. Looks like may be the valve that was touched after the
resin was changed caused this trip? 
<!-- Comment: Thu Sep  8 11;49;19 comment by...Sebastian -->
<h3>Cooling Warnings</h3>
At this time we have the following warning in iFix:
<ul>
<li> L00 east supply flow: 1.8 lpm
<li> L00 west supply flow: 1.7 lpm
<li> conductivity is low for ISL (3uS/cm)
<li> PCE supply flow is low: 3.2 lpm
</ul>
I think none of these is very worrisome.
<!-- Date: Thu Sep 8 10:47:57 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L4 
<li>problem n: 1528 
<li>Status: needs_observation
<li>Type: VDOIM
<li>Action: Incident
<li>entered by: fernand 
<li>description is: The symtoms are : a few seconds after we set this ladder to stdby, there is a trip on VDOIM2 that causes the other ladders in that wedge to trip (external trip) 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Thu Sep  8 13;52;20 comment by...Juan Pablo and Sebastian -->
We have tested each ladder one by one with svxdaq and had no problems
with none of them. It is just when trying to bring all up (at
standby) when we see the trip  on VDOIM2 overcurrent. For
now we decided to take f214 out of the database.


<!-- Comment: Fri Sep  9 08;29;44 comment by...Juan Pablo / Marcel  -->
<pre>After swapping back to the spare chiller, things are fine (temperature wise). So now we can bring up the ladder f214 since
now the portcard can handle all the ladders being on stdby.</pre>
<!-- Date: Thu Sep 8 14:25:17 2005 -->
<p>We saw ISL in ifix in alarm state due to several temperatures 
out of range.</p> 
<p>After talking to Rong we are ignoring the following variables: 
<p>Chiller inlet temperature (reading 10.5 celsius)</p> 
<p>Alcove filter pressure drop (reading 6.8 psid) </p> 
<p>CCWest 1-2 outlet temperature (reading 20.6 celsius)</p> 
<p>CCWest 2-1 outlet temperature (reading nonsense = -200)</p> 
<p>Put them on ignore and cross checked with Ulrich is this 
is ok. We keep an eye on them to see if they raise or not</p>
<!-- Author: Juan Pablo / Sebastian -->


<!-- Date: Thu Sep 8 14:37:54 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7425&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7425  width='300' align='top'></a></td><td>Many yellows in ISL. Looks like the temperatures which are out of range are causing pinkies/yellows in IMON. This is at the beginning of store <b>4374</b>.</td></tr></table>
<!-- Author: Juan Pablo/Sebastian -->
<!-- Comment: Thu Sep  8 14;50;31 comment by...Sebastian -->
These are all bias lines which are slightly above limits in IMON. For now I decide to keep the silicon in data taking, since we are
monitoring the temparetures and, thought they are slightly high (see above entry), they are not increasing.


<!-- Comment: Thu Sep  8 16;16;13 comment by...Marcel -->
Slightly is pushing it, it is 2 degrees to warm...
<!-- Comment: Thu Sep  8 17;19;26 comment by...boveia -->
<br>Online ADCMon is still being commissioned, but it can say something useful about this.  A spot check of ISL ladders with online ADCMon didn't come up with any bit errors.  I also get an hourly summary of siginificant differences between current and reference runs, and there are no large differences (from bit errors, for example) in SVX or ISL.  (If a ladder has no data at all (f214), the comparison doesn't happen, so for now please use other methods to spot missing ladders.)
<!-- Date: Thu Sep 8 15:58:32 2005 -->
<br> 
<b>Store 4374:</b> SVT spy mon and SVXMon both look fine. 
We have the issue of the slightly higher temperatures in ISL (after  we swapped back to the ISL chiller from the spare one). This  
is causing some pinkies in the ISL bias lines, but, as Rong pointed out, the limits on the pinkies for the ISL bias are too low anyhow. 
<br> 
There is going to be another 28 cm Beta* stunt in this store, around 8pm, JP is going to come in and Rong offer to help as well. And Marcel is back now.
<!-- Author: JP/Sebastian -->




<!-- Date: Thu Sep 8 18:13:32 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7426&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7426' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7428&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7428' width='300'></a></center>
<!-- Author: HAL 9000 -->
<!-- Comment: Thu Sep  8 18;14;12 comment by...HAL 9000 -->
<h3>Good Morning Dave</h3>

<p>Our detector speaks to us.......</p>


<!-- Date: Thu Sep 8 20:11:00 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7429&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7429' width='300'></a></center>
<!-- Author: Sebastian -->
<!-- Comment: Thu Sep  8 20;25;24 comment by...Jen/Ankush/Marcel/Sebastian -->
<h3>Switching chillers yet again</h3>
Since we did not have anything better to do... One can see
in the above plot that before 6:30pm, when we were running 
with the default ISL chiller, the temp were higher that 
normal (CCW OUT2 20.5C vs the normal value of 18.1C). 
A problem with the chiller refrigerating system of the 
ISL chiller may be the culprit, RAM people will work on it.
We swapped back to the spare chiller for ISL and you can see
that after 6:30pm the temp are back to the normal value (18C).
However the flows still remain low, according to Stefano, it is possible that a valve was accidentaly modified during the last long access.<br>
Should note that while running at a higher temperature no data corruption or higher error rate was detected (see the above entry by Antonio). However we decided to change to the spare chiller, since the possibility of being paged during the night is not very attractive at this point, considering last night activities...


<!-- Date: Thu Sep 8 21:34:05 2005 -->
<h3>Separator Spark</h3> 
 
<p>I just popped into the control room when TEVMON went red.  We immediatly put Silicon to standby as well as the other parts of CDF.  It turns out the B11 vertical separator sparked and we lost most of the beam.  The luminosity dropped from 30e30 to 8e30.</p> 
 
<p>Silicon seems to be fine.  No trips or pinkies. I'll ask the shift crew to do a post-quench checkout when the store is finally dropped.</p>
<!-- Author: Ankush -->


<!-- Date: Fri Sep 9 08:31:50 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L4 
<li>problem n: 1528 
<li>Status: fixed
<li>Type: VDOIM
<li>Action: Added_hdwdb
<li>entered by: fernand 
<li>description is: After swapping back to the spare chiller, things are fine (temperature wise). So now we can bring up the ladder f214 since now the portcard can handle all the ladders being on stdby. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Fri Sep 9 08:31:50 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB2W1L4 
<li>problem n: 1528 
<li>Status: fixed
<li>Type: VDOIM
<li>Action: Added_hdwdb
<li>entered by: fernand 
<li>description is: After swapping back to the spare chiller, things are fine (temperature wise). So now we can bring up the ladder f214 since now the portcard can handle all the ladders being on stdby. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B2W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Fri Sep 9 10:25:43 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7430&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7431  width='300' align='top'></a></td><td>SVTspyMon plot. Looks fine as well as SVXMON. f214 is back!</td></tr></table>
<!-- Author:  Juan Pablo -->


<!-- Date: Fri Sep 9 11:52:11 2005 -->
<h3> Massive SVX trip </h3> 
<pre> 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W0 DVDD1 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W4 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W5 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W6 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W7 DVDD3 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W7 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W8 DVDD2 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W8 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B3  W9 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W1 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W2 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W4 DVDD2 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W4 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W5 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W6 DVDD1 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W7 DVDD2 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W7 DVDD3 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W7 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W8 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W9 DVDD2 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W9 AVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B4  W11 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W1 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W2 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W3 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W5 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W6 DVDD1 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W6 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W7 DVDD2 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W7 DVDD3 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W7 DVDD4 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W8 DVDD0 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W8 DVDD2 OverCurrent 
Fri Sep 09 11:41:41 CDT 2005                        TRIP: SVX  B5  W8 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W0 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W0 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W0 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W0 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W0 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W1 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W1 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W1 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W1 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W2 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W2 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W2 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W2 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W3 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W3 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W3 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W3 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W4 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W4 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W4 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W4 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W5 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W5 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W5 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W5 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W5 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W6 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W6 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W6 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W6 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W7 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W7 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W7 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W7 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W7 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W8 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W8 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W8 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W8 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W9 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W9 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W9 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W9 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W9 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W10 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W10 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W10 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W10 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W10 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W11 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W11 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W11 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B0  W11 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W0 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W0 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W0 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W0 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W0 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W1 DVDD0 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W1 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W1 DVDD2 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W1 DVDD3 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W1 DVDD4 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W2 DVDD1 OverCurrent 
Fri Sep 09 11:41:51 CDT 2005                        TRIP: SVX  B1  W2 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W2 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W2 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W3 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W3 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W3 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W3 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W4 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W4 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W4 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W4 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W4 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W5 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W5 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W5 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W5 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W5 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W6 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W6 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W6 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W6 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W8 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W8 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W8 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W8 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W8 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W9 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W9 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W9 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W9 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W9 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W10 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W10 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W10 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W10 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W10 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W11 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W11 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W11 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W11 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B1  W11 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W0 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W0 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W0 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W0 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W0 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W1 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W1 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W1 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W1 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W1 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W2 DVDD0 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W2 DVDD1 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W2 DVDD2 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W2 DVDD3 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W2 DVDD4 OverCurrent 
Fri Sep 09 11:41:52 CDT 2005                        TRIP: SVX  B2  W3 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W3 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W3 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W3 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W3 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W4 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W4 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W4 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W4 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W4 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W5 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W5 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W5 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W5 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W5 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W6 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W6 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W6 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W6 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W7 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W7 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W7 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W7 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W7 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W8 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W8 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W8 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W8 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W8 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W9 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W9 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W9 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W9 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W9 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W10 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W10 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W10 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W10 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W10 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W11 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W11 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W11 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W11 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B2  W11 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W0 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W0 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W0 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W1 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W1 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W1 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W1 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W1 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W2 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W2 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W2 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W2 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W3 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W3 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W3 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W3 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W3 DVDD4 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W4 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W4 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W4 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W4 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W5 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W5 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W5 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W5 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W6 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W6 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W6 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W6 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W7 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W7 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W7 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W8 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W8 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W8 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W9 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W9 DVDD1 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W9 DVDD2 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W9 DVDD3 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W10 DVDD0 OverCurrent 
Fri Sep 09 11:41:53 CDT 2005                        TRIP: SVX  B3  W10 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B3  W10 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B3  W10 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B3  W11 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B3  W11 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B3  W11 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B3  W11 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B3  W11 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W0 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W0 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W0 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W0 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W1 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W1 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W1 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W2 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W2 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W2 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W3 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W3 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W3 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W3 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W3 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W4 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W4 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W4 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W5 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W5 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W5 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W5 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W6 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W6 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W6 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W7 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W7 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W8 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W8 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W9 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W9 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W9 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W10 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W10 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W10 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W10 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W10 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W11 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W11 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W11 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B4  W11 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W0 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W0 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W0 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W0 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W0 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W1 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W1 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W1 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W1 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W2 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W2 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W2 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W2 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W3 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W3 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W3 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W3 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W5 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W5 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W5 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W5 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W6 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W6 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W6 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W7 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W7 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W8 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W8 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W9 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W9 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W9 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W9 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W9 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W10 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W10 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W10 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W10 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W10 DVDD4 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W11 DVDD0 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W11 DVDD1 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W11 DVDD2 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W11 DVDD3 OverCurrent 
Fri Sep 09 11:41:54 CDT 2005                        TRIP: SVX  B5  W11 DVDD4 OverCurrent 
</pre>
<!-- Author: Marcel, Mark, Juan Pablo -->
<!-- Comment: Fri Sep  9 14;12;09 comment by...s -->
Saying that SVX tripped on DVDD overcurrint and the plot below is better than this entry...
<!-- Date: Fri Sep 9 11:59:52 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7432&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7432  width='300' align='top'></a></td><td>IMON after the trip</td></tr></table>
<!-- Author: Marcel, Mark, Juan Pablo -->
<!-- Comment: Fri Sep  9 12;06;49 comment by...Marcel and gang -->
<h2> What we know so far .... </h2>
So we came in and found IMON in this state:
<ul>

<li>Everything tripped on DVDD overcurrent, instantenously, nothing to see on IMON </li>
<li>No cooling problem </li>
<li>No clock errors reported </li>
<li>SRC looked fine, Happy was happy </li>
</ul>
Everything started with a problem in L1, that caused Done TO, and L1 Done TO. That could have started an avalanche, since also the TDCs are very unhappy. 
<!-- Comment: Fri Sep  9 12;19;31 comment by...Juan Pablo, Mark, David and Marcel -->
<h2> Update </h2>
Looks like an SRC freakout, although we are not sure, if it is the SRC's problem. Everything basically tripped instantly in all four SVX FIBS. The only thing in common is the SRC. <br>
We suspect a glitch of some kind ....

<!-- Comment: Fri Sep  9 14;28;17 comment by...Marcel -->
SRC? There is no indication of any SRC errors in the log file, plus the LA downstairs did not trigger. The log shows many DTO from
cal03:
<pre>
(MLE) b0dap73.fnal.gov:Thread-4214:Sep 9, 2005 11:11:26 AM->Done Timeout: LEVEL1_CAL_03 
</pre>
It is possible that the TSI communication could be garbled
<!-- Comment: Fri Sep  9 14;54;04 comment by...Sebastian -->
<br>Some comments:<br>
<ul>
<li> No SRC errors in the log files at the time (and of course
the LA downstairs did not trigger).
<li> The log files point that everything started with:
<pre>
(MLE) b0xft00:Messenger:Sep 9, 2005 11:08:45 AM->Event 13072: Bunchcounters in slot 13 (BC=33) and slot 9 (BC=106) disagree (L2B=0) 
(MLE) b0xft00:Messenger:Sep 9, 2005 11:08:45 AM->Runtime Error 1, Event 13072: Bunch counter mismatch, mismatch count = 1
(MLE) b0l1cl03:Messenger:Sep 9, 2005 11:11:25 AM->Event 40624: Bunchcounters in slot 13 (BC=109) and slot 11 (BC=78) disagree (L2B=0) 
(MLE) b0l1cl03:Messenger:Sep 9, 2005 11:11:25 AM->Runtime Error 1, Event 40624: Bunch counter mismatch, mismatch count = 1
(MLW) b0dap73.fnal.gov:Thread-4214:Sep 9, 2005 11:11:26 AM->Received error message: errmon Not a state HaltRecoverRun 1 crate/s: b0l1cl03(131),  Done TO. [RXPT]
(MLE) b0dap73.fnal.gov:Thread-4214:Sep 9, 2005 11:11:26 AM->Done Timeout: LEVEL1_CAL_03 
</pre>
Ei, problems with cal03. 
<li> Greg F confirms that there is a bad module in this crate (gives worng BX numbers and causes the DTO).
<li> When the TS sees the error from cal03 would send HALT (don't  see this in the log)
and then the ace would HRRed.
<li> If the TSI was somehow unhappy with the cal03 errors it could have sent an abnormal sequence to the SRC (though all that it sends are the L1/L2 and the buffer number).
<li> The SRC could have forward an unusual sequence of commands to the FIB and then we tripped on DVDD...
<li> I do not think that the wrong buffer number will affect the chips, intead it would affect the VRBs.
<li> Too many unknows.
</ul>
What is clear to me is that we were having problems with the trigger (b0l1cl03), this could have made the SRC send the wrong sequence of commands and then we tripped. However no errors are reported by the SRC.<br>


<!-- Comment: Fri Sep  9 15;05;35 comment by...s -->
Bill B tells me that b0l1cl03 is working correctly again. They did not fix anything, it just came back ok... May be some kind of glitch that afected the CLK caused this...
<!-- Date: Fri Sep 9 12:02:12 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7433&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7433  width='300' align='top'></a></td><td>f023</td></tr></table>
<!-- Author: boveia -->
<!-- Comment: Fri Sep  9 12;03;58 comment by...boveia -->
<pre>Physics occupancy on f023 chip 2 is lower than in the past.  (Chip 1 is unbiased because of an internal problem.)</pre>



<!-- Comment: Fri Sep  9 12;30;45 comment by...boveia -->
errrr... <b>this is f823</b>
<!-- Date: Fri Sep 9 12:14:19 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7434&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7434  width='300' align='top'></a></td><td>L00 offline efficiencies for run 0x031c69 
</td></tr></table>
<!-- Author: boveia -->
<!-- Comment: Fri Sep  9 12;30;09 comment by...boveia -->
<pre>These are Ben's offline efficiencies for some recent run.  The efficiency for f823 chip 1 and chip 2 are (1,4) and (2,4) respectively.  This seems to indicate that chip 1 has >0.5 efficiency for attaching hits while chip 2 has SiExpected=0...  I don't understand this.
</pre>


<!-- Date: Fri Sep 9 12:34:54 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: LB0W2L3 
<li>problem n: 1529 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Chip 2 may not be seeing physics.  See <<a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=265&frame=2&anchor=12:02:12'>e-log</a>.  Bias1 seems to be drawing current, however. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=L00&wedge=B0W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->





<!-- Date: Fri Sep 9 14:47:58 2005 -->
<pre>e494 tripped quite often on AVDD overcurrent (it had tripped also on Tuesday)</pre>
<!-- Author: Juan Pablo/ Sebastian -->




<!-- Date: Fri Sep 9 15:28:08 2005 -->
<br><b>e494 keeps tripping:</b><br> 
Just tripped again... Here is some recent history of this ladder: 
<pre> 
20050105.log:Wed Jan 05 10:15:06 CST 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050126.log:Wed Jan 26 22:17:44 CST 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050212.log:Sat Feb 12 23:30:44 CST 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050213.log:Sun Feb 13 04:59:20 CST 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050309.log:Wed Mar 09 11:09:46 CST 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050309.log:Wed Mar 09 11:54:52 CST 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050331.log:Thu Mar 31 22:26:17 CST 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050426.log:Tue Apr 26 12:24:22 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050612.log:Sun Jun 12 15:49:11 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050716.log:Sat Jul 16 02:45:50 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050716.log:Sat Jul 16 03:24:41 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050716.log:Sat Jul 16 03:30:31 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050716.log:Sat Jul 16 03:37:23 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050716.log:Sat Jul 16 04:02:19 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050716.log:Sat Jul 16 04:08:48 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050716.log:Sat Jul 16 04:17:01 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050823.log:Tue Aug 23 21:37:57 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050906.log:Tue Sep 06 06:47:37 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050906.log:Tue Sep 06 21:08:40 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050908.log:Thu Sep 08 06:49:55 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050908.log:Thu Sep 08 16:38:09 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050908.log:Thu Sep 08 16:53:50 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050908.log:Thu Sep 08 17:25:50 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050908.log:Thu Sep 08 17:43:17 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050909.log:Fri Sep 09 11:41:41 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050909.log:Fri Sep 09 14:35:10 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050909.log:Fri Sep 09 15:11:28 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
20050909.log:Fri Sep 09 15:18:42 CDT 2005     TRIP: SVX  B4  W9 AVDD4 OverCurrent 
</pre> 
So this one has intermitent problems quite often... 
  
<!-- Author: JP/Sebastian -->


<!-- Date: Fri Sep 9 15:31:30 2005 -->
<br>svxinter will show the right date upon reboot now.
<!-- Author: Sebastian -->


<!-- Date: Fri Sep 9 16:11:50 2005 -->
<h3>Sasha has the DWG Pager</h3> 
 
<p>While I'm away (Friday 9 September to 15:00 Thursday 22 September), Sasha Pronko will carry the DWG pager.</p> 
 
<em>Now I just have to tell Sasha ;-)</em>
<!-- Author: Ankush -->


<!-- Date: Fri Sep 9 17:26:59 2005 -->
<table border=0><td><tr><td bgcolor=#e0e030><h2>Rainer carries the my SPL pager </h2> 
Since  I will be away from tomorrow till next Sunday(18th)<br> 
He already knows about it( step ahead of Sasha). 
In case of severe troubles, feel free to call him. </td></tr></td></table>
<!-- Author: Marcel -->


<!-- Date: Fri Sep 9 20:39:25 2005 -->
f140 is reporting high occ on svxmon... nothing to do, see problem DB.
<!-- Author: Sebastian -->

<!-- Date: Sat Sep 10 08:38:40 2005 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 420
Calibration type  : standard
Run period tag    : Sep_2005
DPS-off run       : 204135
DPS-on run        : 204134
Requested by      : Michele Giunta
Main process id   : 18598
Comment           : OK
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Sat Sep 10 08:55:58 2005 -->
<pre>After the quench at 6:20 the quench test performed by the aces 
was ok. Now taking D-mode calibrations with no beam.</pre>
<!-- Author: Juan Pablo. -->


<!-- Date: Sat Sep 10 09:00:57 2005 -->
<pre>Schulamit found a pink bias ladder but did not page me (just 
ignore it). Then he told me when I came.  
The current seems to be really high to me (crazy I would say). Even  
when the detector is on staby (that means just a few volts on the 
VIAS line of the sensor) is the same. So I suspect there is something else going on.  
A pin hole would develop a lot on current but this would react 
with the bias voltage you apply (decrease when lowering, increase when raising).</pre>
<!-- Author: Juan Pablo. -->
<!-- Comment: Sat Sep 10 09;40;30 comment by...Juan Pablo. -->
<pre>I hockerize CAEN PS 6 and the BIAS current for e282 went back
to its normal numbers. It the process of bringing up the other
wedges associated with the hockerized CAEN PS, e290 gave an AVDD overcurrent but now is happy and in stdby as everybody else.</pre>

<!-- Comment: Sat Sep 10 11;28;56 comment by...rainer -->
this was exactly the right thing to do. single channel weirdness of this kind points to CAEN problem which hockerization takes care of (see for example 
<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=180&frame=2&anchor=02:18:19'>
here </a> or search for hockerize in the elog.





<!-- Date: Sat Sep 10 12:10:55 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7435&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7436  width='300' align='top'></a></td><td>BLM plot from this morning quench.</td></tr></table>
<!-- Author: Sebastian -->
<!-- Comment: Sat Sep 10 12;11;42 comment by...s -->
requested by rainer. We were not hit.

<!-- Date: Sat Sep 10 17:39:57 2005 -->
<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 420 finished successfully.

Job info
--------
Calibration type : standard
Beam condition   : off
DPS-off run      : 204135
DPS-on run       : 204134
Requested by     : Michele Giunta
Submitted        : 2005-09-10 08:37:36
Completed        : 2005-09-10 17:39:54
Status           : SUCCESS
Comment          : OK
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->



<!-- Date: Sun Sep 11 01:03:33 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7439&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7440  width='300' align='top'></a></td><td> <p>SVTspymon plot is fine as well as SVXMON. </p> 
 <p>Store is 4384 (started at ints lum = 60Xe32 ...)</p></td></tr></table>
<!-- Author: Juan Pablo -->
<!-- Comment: Sun Sep 11 01;09;14 comment by...sebastian -->
60E32? That would be a nice store...

<!-- Comment: Sun Sep 11 01;26;47 comment by...Juan Pablo -->
<pre>yes sorry! 60 X E30</pre>


<!-- Date: Sun Sep 11 07:47:04 2005 -->
<h3> 
<p> 
e240 was giving a stuck cell ID (from SVXMon) causing a HHR 
every minute.</p> </h3>
<p> Action taken : decided to get this ladder out of the database </p> 
<p>It took us more than expected because I forgot the very 
last step that is to restart SVXMon (I had done it before with 
Sebastian last week but it forgot and after paging him he inmediately told us) Sorry for not remembering. Could we anyway 
write it on the documentation? This is the only thing it is missing on the procedure "how to put a ladder out of the HDWdatabase" (either as an exceptional case or whatever)</p>  
<p>This ladder had no history on the problem database before (will study it during quite time). </p> 
<p>I was worried about this ladder showing other symtoms 
as well (like a drop on AVDD of 40-50 mA, drop in gain, 
drop in noise) but did not see it (at least I did not 
see a AVDD drop). In case this would have being the case, 
then I would have suspected a new AVDD2 candidate but 
being the fact that there is only a stuck cell id then 
it could be something else (well the problem is sitll 
there no matter what but it could less severe than an AVDD2). </p> 
<p>We did not loose that much time in the end (there was 
also a EB problem that was not silicon related)</p> 
</h3>
<!-- Author: Juan Pablo and Shulamit -->
<!-- Comment: Sun Sep 11 07;58;12 comment by...Sebastian -->
</b><br>
Yes, you are right. I added this to the 
<a href="http://b0sili01.fnal.gov/daqwg/procedures/procedures-1.html">
procedures</a>.
<!-- Comment: Sun Sep 11 08;11;32 comment by...Sebastian -->
Found no init problems for this ladder in the 
<a href="https://www-cdfonline.fnal.gov/cgi/internal/elog/nph-MCRproxy.pl/000/http/www-cdfonline.fnal.gov/svx/data1/datalog/daq/">
daq log files</a>. As you said, lets look at it during quiet time.
<!-- Comment: Sun Sep 11 10;45;00 comment by...rainer -->
it would be good to have the SVXMon histos for this ladder (occupancy) to verify that there was a problem.
<!-- Comment: Sun Sep 11 13;25;57 comment by...sebastian -->
SVXMon plot are empty for this ladder (see a few entries below).
<!-- Comment: Sun Sep 11 14;58;47 comment by...Juan Pablo -->
The error logger was also showing the cap-id errors on every minute.

<!-- Comment: Mon Sep 12 14;29;38 comment by...s -->
Rong pointed out that might be problems with svxmon, not the ladder (see also <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=266&frame=2&anchor=11:02:11'>
here</a>).
<!-- Comment: Mon Sep 12 14;30;41 comment by...s -->
... and since the SVXMon occ plots don't make sense, probably it was a problem with SVXMon...
<!-- Date: Sun Sep 11 07:54:51 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W4L0 
<li>problem n: 1530 
<li>Status: needs_study_time
<li>Type: Chip_capid
<li>Action: Removed_hdwdb
<li>entered by: fernand 
<li>description is: e240 was giving a stuck cell-ID. We need some time to diagnose this. No drop in AVDD asociated (so may be it is not an AVDD2 problem).  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->






<!-- Date: Sun Sep 11 13:21:42 2005 -->
<center><a href='/elog/notebooks/silicon/Sun_Sep_11_2005_132057.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7442' ></a><a href='/elog/notebooks/silicon/Sun_Sep_11_2005_132116.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7444' ></a></center>
<!-- Author: Sebastian -->
<!-- Comment: Sun Sep 11 13;23;44 comment by...s -->
Occupancy for run 204184 (since ~6am) when we started getting the stuck cellid errors from SVXMon. Right is run 204119, the previous run in which we took data, for comparison.




<!-- Comment: Mon Sep 12 08;16;15 comment by...JP/S -->
BTW, this is not what one expects for a stuck cellid...
<!-- Date: Sun Sep 11 19:49:44 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7446&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7447  width='300' align='top'></a></td><td>Photo of f03 backplane socket connector (which 
corresponds to J38 A8 on module) taken with borescope 
during Wed-Thu access. See <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=265&frame=2&anchor=23:17:23'> 
this</a> entry above.</td></tr></table>
<!-- Author: Sebastian -->

<!-- Date: Mon Sep 12 02:45:11 2005 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 421
Calibration type  : standard
Run period tag    : Sep_2005
DPS-off run       : 204187
DPS-on run        : 204186
Requested by      : Freeman
Main process id   : 30036
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Mon Sep 12 03:40:47 2005 -->
<p>Yesterday we took SVX B2 W4 out of the database because of stuck cell ID. The ladder did not trip or anything and I did not turned 
it off before doing the HDWdatabase operation.</p> 
<p>So this morning, at the end of the store, while bringing the 
silicon to stdby, this ladder would not respond to the PS GUI 
because it had been masked.</p> 
<p>Tevatron guys were nervous and waiting for Carmine (Scico) 
to call them that everything was fine in order to dump the beam. 
We made them waiting for ~25 minutes.</p> 
<p>I knew what to do but called Sebastian anyway (just in 
case something went wrong)</p> 
<p>We agreed on what to do : edit the Caenvolts file, remove the X from B2W4L0 (I was a bit nervous and the first time I edited 
L00, that was also masked, but inmediately realized about it), 
bring the ladder to stdby, then off and last put the X back 
(for the moment, until we understand what has hapenned with 
this ladder and its stuck cell id problem)</p> 
<p></p>
<!-- Author: Juan Pablo -->


<!-- Date: Mon Sep 12 05:48:32 2005 -->

 
<p>Summary of the week : </p> 
(incidents and accidents) 
 
<ul> 
<li>f03 : confirmed bad connection on pin no. 8;  
        found the 2V on the backplane for this pin during last s-access 
        (need to make a thicker pin at FCC and try again) 
 
<li> FIB_33 (b0fib06) got corrupted (this happens very rarely). After some struggle a new run was 
started. A FIB master reset is issued on the config transition which would clear the  
problem of a SEU on a IC.</li> 
 
<li> several times during the week : scalating Losses at D0 and CDF after 
TeV 28cm Beta* study </li> 
 
<li> non-flat pedestal studies on SVX : SB0W6L2 and SB3W5L1  
  (raising the thresold approx. 3 ADC counts might help). SB2W2L4 <b> needs 
quite time </b> studies </li> 
 
<li> During last s-access the ISL chiller was put in place. Since 
it was not providing with the proper temperature, the spare chiller was 
swapped back (the ISL chiller still needs to be fixed or a new one 
bought)</li> 
 
<li>f214 was taken out of the database due to non sufficient cooling of the 
associated port card and put back in again once the spare chiller was put 
back in </li> 
 
<li>Massive SVX trip for unknown reasons  
(suspect : a glitch of some kind affecting TS and/or SRC)</li> 
 
<li>e494 tripped often on AVDD overcurrent (keep an eye)</li>  
 
<li> in last access after COT squad did their repair work on the east bore, everything 
  was fine</li> 
<li> e240: stuck cell id <b> (needs quite time to study it) </b> </li> 
<li> So, devices that need quiet-time for this week :<b>e240, e062 and e351 (raise thresholds by 3 ADC) and e224 </b></li> 
</ul> 
<p> 
  Just for beginners on the MPC task (as me).</p> 
 
 <p> There are a some potential problems whenever the temperature of the chiller raises:</p> 
  <ul> 
 <li> 1) Since the ISL chiller cools the SVX port cards, the temperature difference may affect the DOIM outputs and cause some optical bit errors (this is most of the times the most worrysome issue, you can use ADCMon to pin-point any new troublesome ladder/Port Card).</li> 
<li>  2) There may be some alignment differences (I expect this to be small if not undetectable)</li> 
<li>  3)  Also one can notice an increase in the leakage current. The shot noise increases like the square root of the leakage current. For instance, if the leakage current increases by 16%, we should expect an 4% increase in dnoise (hard to notice in the SVXMon occupancy plots when comparing before and after).</li> 
<li>So, it seems there is no problem with running 2 degrees warmer, the problem is when running with a bad chiller.</li> 
 <li> As silicon MPC we should keep an eye on the temperature of the SVX and ISL chillers. In order to do it just go to IFIX -> Silicon Menu -> SVX Cooling/ISL Cooling (and look at the temperature in the upper left part of the window; the temperature for the SVX should be -10 +/- 1 degrees celsius for the SVX and +6 +- 1 for ISL </li> 
 </ul>
<p> I do not like being the bad example but anyway somebody has to do it. So just make sure you eat and sleep enough while being MPC. Thank you to Sebastian for being under my shoulder during all this week. </p> 
 
 
<!-- Author: Juan Pablo -->


<!-- Date: Mon Sep 12 06:28:00 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7448&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-7449  width='300' align='top'></a></td><td><p> SVTspyMon plot is fine as well as SVXMON. Store is <p>4385.</p> Initial luminosity in the sixties (Ex30). </p></td></tr></table>
<!-- Author:  Juan Pablo -->