<!-- Title: 21:07:16  Fri Jan 11 2002 -->
<!-- Crewchief: silicon people -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Current run plan: 
----------------- 
1. do charge injection geometry runs as occasion allows,  
   taking advantage of shot setup and/or studies tomorrow. 
   Specifications for these runs: Lester or Doug or David. 
   Jean also can look them up in email. 
 
2. Stay with current set until next studies day - Tuesday next  
   week.  At that point integrate remaining ladders such as the  
   ones Sav found and David's list. Lester is in charge of the 
   integration list. 
 
   ----&gt; must decide what to do about AVDD2 ladders &lt;------ 
 
3. Saturday night or sunday AM, David will change some ISEL  
   bits on ISL to decide if this is how they will run. We want  
   this decision made and implemented ( or not) before the  
   upcoming parameterscans. 
 
4. Make every effort to be ready to do the special runs as per 
   Doug and Lester's list on Monday day shift, beam allowing. 
 
5. Otherwise for this weekend, run integrated and evaluate the 
   current base set.  Jason will be in for diagnostic shift on 
   Saturday. 
 
6. Steve may have X-mode runs to take., 
 
7. don't forget, we have requested the aces to do a D-mode 
   calibration every shot.  The instructions for doing this 
   are linked off of the DAQ Ace page for silicon.  
    
 
 
 
</pre>


<!-- Date: Sat Jan 12 10:42:48 2002 -->
<pre>Teh monitoring aces showed me 3 persistent pink boxes on IMON 
for SVX.  I checked them all with Auke's program and they have 
been bad since midnight.  Saverio is now investigating them. 
   SB4W0L4  AVDD 105 - nominal is 1150 
   SB0W11L4 AVDD 940 - nominal is 1010 
   SB0W3L3  DVDD  90 - nominal is  140 
I put these on a yellow sticky as "known".</pre>
<!-- Author: Jean -->


<!-- Date: Sat Jan 12 10:44:48 2002 -->
<pre>SB4W0L4  
AVdd is Power Supply channel 1081 
on Jan 11th  
external trip Fri Jan 11 09:00:50 2002 
Turned on     Fri Jan 11 09:01:10 2002 
at 09:20:44 current was 1020 mA 
at 09:20:55 current was  240 mA 
 
</pre>
<!-- Author: Sav -->
<!-- Comment: Sat Jan 12 10;50;06 comment by...Sav -->
<pre>The trip was due to bias overcurrent &gt; 500 uA</pre>


<!-- Date: Sat Jan 12 12:30:42 2002 -->
<pre>Accelerator  is having lot's of problems.  this would be a good 
 time to do any special runs that don't require biasing the 
 detector - like charge injection.  Joel points out, however,  
that there is some beam sometimes in the machine which could 
 cause some signals even if we are unbiased, but I doubt that 
 will be much compared to charge injection, particularly if 
thresholds are set high on everything except the guys getting charge injection.  Instuctions for charge inejection using 
run control can be found by doing a logbook search on 
"charge injection".</pre>
<!-- Author: Jean -->


<!-- Date: Sat Jan 12 15:28:26 2002 -->
I summarized the monitoring errors from last night's runs in 
<a href= 
'/cgi/elog/det-system-elog.pl?nb=barrel4&action=view&page=50&frame=2&anchor=15:21:46'> 
today's entry in the Barrel 4/Diagnosis e-log</a>  
<p> 
The highlights are the AVDD problem on SB4W0L4 (as noted above 
by Jean and Saverio) and the appearance of L00 in our list. 
<p> 
Unfortunately these runs aren't yet available in the  
error parser because of the fcdfsgi2 downtime.  The errors can 
be categorized better when they appear there.  
<!-- Author: Jason -->


<!-- Date: Sat Jan 12 18:16:39 2002 -->
<pre>When biasing silicon for Store 900, the ISL 6-C ladders didn't 
turn ON from STBY when clicking "POWER ON."  They had to be 
turned by clicking the "ISL bulkhead 2 ON" button.</pre>
<!-- Author: Andy H. (ace-in-training) -->
<!-- Comment: Sat Jan 12 18;42;24 comment by...David -->
<pre>Interesting. Yesterday, I found them on when everything else was at standby. This was probably for the same reason. Could someone please check if the powerset is correct? If not, please run cratematch.pl and reload the powerset in the gui.

</pre>


<!-- Comment: Sat Jan 12 20;34;46 comment by...Mary  -->
<pre>I checked the powerset and they are there. I reloaded it anyway.</pre>
<!-- Date: Sat Jan 12 19:06:38 2002 -->
<pre>MORE MYSTERIOUS PS GUI/system BEHAVIOUR. EXT-TRIPS WITHOUT 
GUI ALERTING SHIFTER!!!!! 
----------------------------------------------------------- 
 
When turning from ON to STDBY. IFIX reported a trip the GUI 
didn't but Andy persisted and found an ext trip on ISL VBIAS1 
of ISL B4 W5. That hdi is off. Svxinter reports the following: 
 
setDetectorStatus,err = -1, detector = 2Module busy 
Module busy 
Module busy 
Module busy 
detector = 1, ps_n = 29, layer_n = 0 spontaneously turned off 
turning it back standby 
Sending Request for e250 
checkSt[1][29][0] = 1 
detector = 2, ps_n = 24, layer_n = 4 spontaneously turned standby 
turning it back off 
checkSt[2][24][4] = 2 
detector = 2, ps_n = 24, layer_n = 3 spontaneously turned standby 
turning it back off 
checkSt[2][24][3] = 1 
detector = 2, ps_n = 24, layer_n = 2 spontaneously turned standby 
turning it back off 
checkSt[2][24][2] = 1 
detector = 2, ps_n = 24, layer_n = 1 spontaneously turned standby 
turning it back off 
checkSt[2][24][1] = 1 
detector = 2, ps_n = 24, layer_n = 0 spontaneously turned standby 
turning it back off 
checkSt[2][24][0] = 1 
 
Turned that HDI on and ran cratematch.  
 
 The following wedges should be Stand-By or ON and are OFF:  
 
IB5W0L0  IB5W0L1  IB5W0L2  IB5W0L3  IB5W0L4   
 * * * Cold Start would fail ! * * *  
 
Checing IB5W0 we find an ext-trip on PC 5V DOIM! 
 
SHIFTERS PLEASE ALWAYS RUN CRATEMATCH TO CHECK THAT EVERYTHING 
IS ON AFTER SWITCHING ON OR STDBY FROM GUI OR IFIX. 
</pre>
<!-- Author: Mary and Andy H. -->
<!-- Comment: Sat Jan 12 20;03;12 comment by...MAry -->
<pre>From CAEN.map detecotr = 2 ps_n=24 is indeed IB5W0 !! Why did
the server side code or the GUI turn it off when it was turned to
STDBY. SOMEONE PLEASE CHECK THE CODE THAT MONITORS "SPONTANEOUS"
turn ons and turn offs and disable it while we are changing
states.
</pre>


<!-- Comment: Sun Jan 13 19;53;12 comment by...Andrew -->
<pre>I believe what happened here is that ISL was turned ON, but the GUI gave an error: setDetectorStatus,err = -1, detector = 2.
I am not what sure what was a reason of this error, but that could result in not turning  IB5W0.</pre>
<!-- Date: Sat Jan 12 20:20:31 2002 -->
<pre>Seems they lost all the protons the last store so Tev studies 
now. Called Dave Stuart - sgi2 is still down so he will do the 
ISEL bits study tomorrow. Noone around for charge injection 
runs. But maybe they read the e-log :)</pre>
<!-- Author: Mary. -->


<!-- Date: Sat Jan 12 20:32:11 2002 -->
<pre>PErsistent pinks noted aroud 20:00 on SB0W2 AVDD1,2,3 
SB1W11 AVDD2 DVDD2 SB2W0 AVDD0 
 
All recovered after a manual handshake</pre>
<!-- Author: Mary -->



<!-- Date: Sat Jan 12 20:39:38 2002 -->
<pre>FCDFSGI2 IS ALIVE</pre>
<!-- Author: me -->


<!-- Date: Sun Jan 13 06:41:23 2002 -->
<pre>Silicon ON for collisions. 
 
SB0W3 L3 will not bias (overcurrent); biased at 
50 V (should be 100)</pre>
<!-- Author: ADF -->
<!-- Comment: Sun Jan 13 08;44;15 comment by...Joel -->
<pre>ISL B2 wedges were still in standby when I checked - they don't ramp with the rest of the silicon.</pre>
<!-- Date: Sun Jan 13 08:39:36 2002 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>FIB01 power supply died. Wedges (IB0W2,3,IB1W2,3,4,5,IB2W0,1) switched off and removed from powersets.dat.</pre></td></tr></td></table>
<!-- Author: Joel -->



<!-- Date: Sun Jan 13 12:20:56 2002 -->
<pre>email from Aaron on the cal inject special geometry runs 
 
    * Settings: 
          * Sparse (not neighbors mode) 
          * Thresh 40-50 
          * DAC setting 8 
          * DPS-on 
    * Runs 
          * Inject charge into channel 0 of each side of each hybird in 
            whole detector (100 events).  By this I mean channel 0 of 
             the phi side and channel 0 of the z side of each hdi, 
            except for L00 of course.  Channel 0 means the first channel 
            in the first chip that passes priority on each side of the 
            half-ladder.  Forget about ganging complications, just think 
            of how a single side of a hybrid reads out.  This is how the 
            offline code thinks of things. 
          * Inject charge into last channel of each side of each hybrid 
            in whole detector (100 events) 
          * Don't inject charge into any channel, but still run the 
            DACs.  This will let us indentify any noisy regions that 
            could be throwing us off. 
 
Unfortunately, there is some magic in making these charge injection 
runs.  To make the DACs work, you need to use the special run parameter 
file called GAINSCAN (or something like that), which has SVX_PEDESTALS_D 
trigger type.  But, this forces the detector to be in readall mode.  So 
after the cold start, you have to play a trick and update the chip 
chains to be SPARSE instead of READALL with the chip editor. 
 
Maybe Steve has a better way to (trick) put the chips into sparse mode... 
</pre>
<!-- Author: aaron&#39;s email -->



<!-- Date: Sun Jan 13 23:27:40 2002 -->
<pre>L00 to STBY since (a) losses are getting nasty and (b) Dave S. 
is going home.</pre>
<!-- Author: Andy H. -->


<!-- Date: Sun Jan 13 23:42:40 2002 -->
<P> 
I changed the ISEL and Bias Ratio bits for what parts of ISL are not affected by the FIB01 death. The goal is to reduce the power consumption and hence the temperature. 
<P> 
There are three "free" ways to save power: 
<UL> 
<LI> Change the READ AMP current.<BR> 
The only performance effect this can have is to reduce the gain if the sequence does not give enough time for the pipeline charge transfers to settle. We saw this sort of effect when debugging the p-n asymmetry. It mostly went away with the sequence fix, but still remains a little. It affects only the n-side because of the "readout order" bit. 
<LI> Change the WRITE AMP current.<BR> 
Similar to above. 
<LI> Turn off the BIAS RATIO SELECT bit.<BR> 
This is only needed by a few percent of chips. 
</UL> 
<P> 
The following runs were taken in various configurations: 
<BR> 
<UL> 
<LI> Run 136950<BR> 
     nominal, high current state, RA=11, WA=011, BRS=1 
<LI> Run 136952 <BR> 
READAMP current set to 01 for phi and z sides of B0, B1W2-5, B4, and B5W0-3. B5W4-5 had the change applied to only the phi side. 
<BR> 
Coldstart occurred at 19:17. Currents changed from ~1250 to 1175mA. 
<LI> Run 136953<BR> 
Kept the RA settings of Run 136952 except for B0W0 where I set it to 10 on the z side and 01 on the phi side. (f004 chip#3 was 11). 
<BR> Set BRS=0 on B0W0-1, B0W4-5, B4, B5.<BR> 
Coldstart occurred at 20:07. Currents dropped from ~1175 to 1080mA.  
<LI> Run 136955-6<BR> 
Kept RA and BRS same as above. Set WA=001 on B0W0-1, B0W4-5, B4, B5, except for B5W4-5 where I set WA=011 on the zside and WA=001 on the phi side. 
</UL> 
<P> 
It will take all night to get all the monitoring plots. So far, I've only been able to look at 136952. It behaved as expected. 
<P> 
Please hold off on the BW scan, latch all runs until I get a chance to verify the other runs and set the final configurations on Monday morning. 
<P>  
<!-- Author: David -->


<!-- Date: Mon Jan 14 03:49:33 2002 -->
<pre>Took SVX calibration (runs 136965 and 136966). 
 
SB0W3L3 tripped on bias so I left it on standby. 
 
fib01 wouldn't handshake with svxinter, so these ladders stayed off. 
</pre>
<!-- Author: Joel -->