<!-- Title: 10:37:17  Mon Apr 26 2004 -->
<!-- Crewchief: Pete -->
<!-- Op1: Silicon Crew -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
New week, taking data now.


<!-- Date: Mon Apr 26 10:41:48 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Mon_Apr_26_2004_104135.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4000  align='top'></a></td><td>SVT SpyMon plot for run 182162</td></tr></table>
<!-- Author: Pete -->


<!-- Date: Mon Apr 26 11:55:59 2004 -->
<pre>Abort gap losses went thru the roof.  Requestred silicon taken out of run.  Silicon now in stby. MCR called to let us know about.  Looking like losses are coming down, but still no explaination.</pre>
<!-- Author: ssf and pete -->
<!-- Comment: Mon Apr 26 12;35;07 comment by...Pete and Stan -->
Losses stable and reasonable (14KhZ) for an extended period, so brought silicon back up.


<!-- Date: Mon Apr 26 14:25:02 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4001&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4002' ></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4003&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4004' ></a></center>
<!-- Author: rainer -->
<!-- Comment: Mon Apr 26 14;25;34 comment by...rainer -->
<pre>recent AVDD pinkies with excursions.</pre>


<!-- Date: Mon Apr 26 16:14:59 2004 -->
<b> another trip fest </b> 
 
most likely b0fib02 FFO got unsynched - like   
<a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=189&frame=2&anchor=14:14:09'> 
here </a> 
 
  
<!-- Author: rainer -->
<!-- Comment: Mon Apr 26 16;15;32 comment by...pete, david, marcel, rainer -->
<pre>... and pete, and david, and marcel.</pre>

<!-- Comment: Mon Apr 26 16;30;04 comment by...SCN -->
From <i>/data1/hmon/log/runSVXBootLoader.log</i> <ul>
<li> FFO unsynched at 15:23:43, was not allowed to resynch because we were still running<pre>Received Directive on /mapSVX/svx/vrb/02from /_b0fib02_14148104 at Mon Apr 26 15:23:43 CDT 2004: Glink Synch
Received Directive on /mapSVX/svx/vrb/02from /_b0fib02_14148104 at Mon Apr 26 15:23:45 CDT 2004: Glink Synch
Received Directive on /mapSVX/svx/vrb/02from /_b0fib02_14148104 at Mon Apr 26 15:23:47 CDT 2004: Glink Synch
Received Directive on /mapSVX/svx/vrb/02from /_b0fib02_14148104 at Mon Apr 26 15:23:49 CDT 2004: Glink Synch
Received Directive on /mapSVX/svx/vrb/02from /_b0fib02_14148104 at Mon Apr 26 15:23:51 CDT 2004: Glink Synch
Received Directive on /mapSVX/svx/vrb/02from /_b0fib02_14148104 at Mon Apr 26 15:23:53 CDT 2004: Glink Synch</pre>
<li> Crate was rebooted at 15:42 and synched up<pre>
Crate b0fib02 -> FIB_SVX_02 started at Mon Apr 26 15:42:22 CDT 2004 Boot Time: MON APR 26 15:42:18 2004 
...junk deleted...
Loading Message
Received Directive on /mapSVX/svx/vrb/02from /_b0fib02_14148432 at Mon Apr 26 15:42:26 CDT 2004: Glink Synch
</pre>
<li> Crate rebooted again at 15:51 <pre>
Crate b0fib02 -> FIB_SVX_02 started at Mon Apr 26 15:51:36 CDT 2004 Boot Time: MON APR 26 15:51:32 2004</pre>
</ul>
So what one would really like to know is why did the FFO in b0fib02 unsynch at 15:23?  Any correlation with anything else?


<!-- Comment: Tue Apr 27 17;28;14 comment by...David -->
There was a spike in the LostP of ~24kHz around 15:22. Also, a L2 decision TO coincided with the spike and SVX FIB02 trips but that was probably due to unsynced glinks and trips. Could a spike in losses affect the glinks? 
<!-- Date: Mon Apr 26 16:36:08 2004 -->
Several wedges of SVX tripped off simultaneously, all from b0fib02 (SB0-3W4-9L0-4 with the exception of 2 or 3 ladders), and could not be brought up with IFIX (DAQ was in halt state, so this was not responsible).  Errors seen of the following type: 
<br><br> 
<tt> 
Sending Request for e056 
Timeout 
ERROR: not all Fibs are initialized 
ERROR: FIB does not respond to Request for handshake, ps_n = 5setPSStatus,err = -1, detector = 1, ps_n = 5 
</tt> 
<br><br> 
After trying to bring up single ladders unsuccessfully, Dave logged into fib02 and rebooted it, but he reported seeing no problems in the crate.  At approximately the same time that the crate was rebooted, several other ladders also tripped off. 
<br><br> 
Tried resetting the trips again, which caused the PSGUI to hang.  Restarting this, unfortunately, killed IMON, as they had been running on the same machine (for now, at least, IMON is now running on 44, PSGUI on 43). 
<br><br> 
Once the PSGUI was restarted, it was once again possible to bring ladders back to ON, so all ladders brought to ON in IFIX.  After an HRR, everything seems to have gone back to normal. 
<br><br> 
This problem (from a Silicon perspective) seems to have fixed itself with time.  The working hypothesis is that it may have been a clock glitch that caused a glink problem for b0fib02, which after a period of time dragged down the others.
<!-- Author: Pete -->


<!-- Date: Mon Apr 26 16:38:08 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4005&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4005  width='300' align='top'></a></td><td>State of IMON for SVX after everything went south.</td></tr></table>
<!-- Author: Pete -->

<!-- Date: Mon Apr 26 17:24:06 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W0L0 
<li>problem n: 1232 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: not seen for another two weeks.  declaring fixed. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W0&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Apr 26 17:32:24 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W3L3 
<li>problem n: 752 
<li>Status: fixed
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: still not seen after waiting two more weeks.  fixed. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W3&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Apr 26 18:19:59 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4006&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4006  width='300' align='top'></a></td><td>IB1W4L0(f140) occupancy plot after threshold adjust on chips 12-15.  Try to reduce noise with isel bits.</td></tr></table>
<!-- Author: ssf -->

<!-- Date: Mon Apr 26 18:23:55 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W4L0 
<li>problem n: 974 
<li>Status: needs_study_time
<li>Type: FE_amp_osc
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is:  <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=18:19:59'> Occupancy plots </a> post changes to chips 12-15.  Still needs work .  Look at in svxdaq to see if isel bit changes can reduce noise.  Also look at DPS changes, how much physics would be lost if DPS used to clean up occupancy? 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Apr 26 18:26:05 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W5L2 
<li>problem n: 63 
<li>Status: needs_access_2hr
<li>Type: Optical_other
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is: perform light level measurement. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W5&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Apr 26 18:26:21 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W6L4 
<li>problem n: 63 
<li>Status: needs_access_2hr
<li>Type: Optical_other
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is: perform light level measurement. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W6&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Apr 26 18:26:42 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W6L4 
<li>problem n: 63 
<li>Status: needs_access_2hr
<li>Type: Optical_other
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is: perform light level measurement. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W6&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Apr 26 18:30:30 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W6L4 
<li>problem n: 63 
<li>Status: needs_access_2hr
<li>Type: Optical_other
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is: Last 3 entries made in error 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W6&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Apr 26 18:37:03 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L3 
<li>problem n: 1147 
<li>Status: needs_access
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is: Change to needs access.  Swapping fiber will not take 2 hours. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Apr 26 18:48:26 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4008&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4008  width='300' align='top'></a></td><td>AVDD current for e062.  Only change in current was 2 days later.</td></tr></table>
<!-- Author: ssf -->
<!-- Comment: Mon Apr 26 18;49;26 comment by...ssf -->
<pre>verticle line is on David Stuart day 1198 (day chip chain was chopped) current change shows up two days latter.</pre>

<!-- Date: Mon Apr 26 18:53:32 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: LB0W2L3 
<li>problem n: 975 
<li>Status: needs_study_time
<li>Type: Optical_other
<li>Action: Diagnosis_update
<li>entered by: sforrest 
<li>description is: Change to needs study time.  See if problem always shows up in same VRB. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=L00&wedge=B0W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Apr 27 11:40:46 2004 -->
ISL tripped off because of an ISL cooling trip.  Rest of silicon brought immediately to standby.  Problem was with chiller freon system, so everything was brought to off, and Andy, Rob and the cryo crew switched to spare system.  Tevatron is now going to be doing studies, so will leave silicon in off state for now.  For more details, see <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=276&frame=2&anchor=09:58:00.334'> 
here</a>, <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=276&frame=2&anchor=10:09:43.793'> 
here</a>, <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=276&frame=2&anchor=10:40:58.921'> 
here</a>, and <a href= 
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=276&frame=2&anchor=11:36:09.701'> 
here</a>.
<!-- Author: Pete -->


<!-- Date: Tue Apr 27 11:40:50 2004 -->
<p><b>ISL cooling trip</b></p> 
<p> 
The compressor tripped off on the ISL chiller, taking down the ISL (and eventually would've taken down SVX and L00 as well).  Tried to reset the compressor to no avail.  Turned the silicon OFF and then 
valved in the spare chiller.  Cooling is up and running again; 
HVAC techs will have a look at the broken chiller.</p>
<!-- Author: Andy H. -->
<!-- Comment: Tue Apr 27 11;41;27 comment by...Andy H. -->
Beat me by four seconds!

<!-- Date: Tue Apr 27 14:13:50 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L3 
<li>problem n: 1147 
<li>Status: needs_observation
<li>Type: RX
<li>Action: Swap_RX
<li>entered by: dkclark 
<li>description is: Swapped RX to fix bit 0 low. No errors in post test except for bit 7 high on z side (thread 60).<table border=1>
<tr><td><b>IN:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0592">0592</a></td></tr>
<tr><td><b>OUT:</b></td><td><a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/rxdb/DBreport.pl?serial=0728">0728</a></td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Apr 27 15:09:03 2004 -->
<h2>Silicon Access Report</h2> 
Swapped DOIM cables on SB0W4L3 and determined bit 0 error follows pipe so we swapped the RX. 
<!-- Author: David, Rong-Shyang, Stan, Erik, Pete -->


<!-- Date: Tue Apr 27 15:17:42 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Tue_Apr_27_2004_151731.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4010  align='top'></a></td><td>IB4W1L1 Bias vs. unbiased SVXDAQ plots show that bias 1 (first 4 chips and last 4 chips in readout order) looks unbiased even though the current in PSGUI for bias1 is 9uA (bias0 shows 29uA).</td></tr></table>
<!-- Author: David, Rong-Shyang -->
<!-- Comment: Wed Apr 28 12;44;05 comment by...rainer -->
<pre>what was the bias current before ? any obvious steps ?</pre>
<!-- Date: Tue Apr 27 15:22:37 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W1L1 
<li>problem n: 1250 
<li>Status: needs_study_time
<li>Type: BIAS
<li>Action: Incident
<li>entered by: dkclark 
<li>description is: There is little to no physics on 1st halfladder (chips 8f-8c, a3-a0), it looks unbiased. Bias1 current from PSGUI is 9uA though. See <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=15:17:42'> bias vs unbiased svxdaq plots</a> which confirm that this ladder is unbiased. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B4W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Apr 27 16:10:42 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W6L4 
<li>problem n: 856 
<li>Status: needs_quiet_time
<li>Type: DVDD
<li>Action: Diagnosis_update
<li>entered by: rong 
<li>description is: Doesn't trip during today's quiet time study. Multi-bit errors showed up, it needs to have Rdriver set to 5 for all chips. Need quiet time to run on cosmics to comfirm it won't trip again. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W6&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Apr 27 16:10:42 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W6L4 
<li>problem n: 856 
<li>Status: needs_quiet_time
<li>Type: DVDD
<li>Action: Diagnosis_update
<li>entered by: rong 
<li>description is: Doesn't trip during today's quiet time study. Multi-bit errors showed up, it needs to have Rdriver set to 5 for all chips. Need quiet time to run on cosmics to comfirm it won't trip again. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W6&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Apr 27 16:40:56 2004 -->
<table border=0><td><tr><td bgcolor=#e0e030><h2>PDB entry errors</h2> 
 
A duplication of the problem threads has recently been noticed in a couple of hdis in the PDB. This happens when you manually edit the URL to go to the next hdi on your list immediately after submitting an entry for another hdi. You are resubmitting to the update script (DBupdate) with the wrong hdi when you do this. In order to avoid this, only use the links and buttons on the PDB webforms. If you see a thread that is out of place please forward it to Lester (lmiller@fnal.gov) so he can edit it out. 
</td></tr></td></table>
<!-- Author: David -->



<!-- Date: Tue Apr 27 19:40:15 2004 -->
After a rocky start of the store, silicon brought on.  As a result of a spike in LOSTP and LOSTPB during ramping and another a few minutes later (making 3 in ~10 minutes), brought it back to standby.
<!-- Author: Pete -->

<!-- Date: Tue Apr 27 20:34:13 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W10L2 
<li>problem n: 1226 
<li>Status: fixed
<li>Type: DRO_00F3
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Not seen for another two weeks. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B4W10&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Apr 27 21:35:04 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4011&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4011' width='300'></a></center>
<!-- Author: boveia -->
<!-- Comment: Tue Apr 27 21;35;43 comment by...boveia -->
<pre>SB0W4 IBias0L0 vs Days</pre>

<!-- Date: Tue Apr 27 21:38:37 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L0 
<li>problem n: 1101 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: boveia 
<li>description is: IBias0L0 <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=21:35:04'> still</a> jumping around.  Continue to monitor. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Tue Apr 27 21;46;46 comment by...boveia -->
These extra entry happened when I hit "refresh" back at the hdi pdb page after submitting the first.  I've informed Lester as mentioned <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=16:40:56'>
here</a>.
<!-- Date: Tue Apr 27 21:38:37 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L0 
<li>problem n: 1101 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: boveia 
<li>description is: IBias0L0 <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=21:35:04'> still</a> jumping around.  Continue to monitor. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Apr 27 21:38:37 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L0 
<li>problem n: 1101 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: boveia 
<li>description is: IBias0L0 <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=21:35:04'> still</a> jumping around.  Continue to monitor. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Apr 27 21:38:37 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L0 
<li>problem n: 1101 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: boveia 
<li>description is: IBias0L0 <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=21:35:04'> still</a> jumping around.  Continue to monitor. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L0">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Wed Apr 28 08:16:23 2004 -->
Access until ~9:30.  Rong-Shyang will take advantage of quiet time.
<!-- Author: Pete -->


<!-- Date: Wed Apr 28 09:35:53 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4012&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4013  width='300' align='top'></a></td><td>e553 (SB5W5L3) failed cold start. It is pinky on IMon with current at 500mA while the nominal value should be 815mA. 
This guy is the victim of AVDD2 due to Apr15 Kicker prefire.</td></tr></table>
<!-- Author: Rong-Shyang -->


<!-- Date: Wed Apr 28 09:38:11 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Apr_28_2004_093800.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4015  align='top'></a></td><td>Run on Svxdaq and try to bring e553 back but failed. 
Try to set the ISEL bits to all 0 for the 4th chips but  
still had no INIT readback nor downstream chips.</td></tr></table>
<!-- Author: Rong-Shyang -->
<!-- Comment: Wed Apr 28 10;07;37 comment by...Rong-Shyang -->
More for documetation
<li> Set ISEL bits to all 0 for the faulty chip but didn't see AVDD current change
<li> By changing RampPed, we see pedestal level jump up on the this chip. So no problem talk to BackEnd.



<!-- Comment: Wed Apr 28 10;52;54 comment by...Rong-Shyang -->
Talk to David, we decide to chop the downstream chips.
<li> Mask the Init back at CardEditor, HDIaddress from 8 -> 24
<li> Change last chip ID from 32 -> 6 (chip 86)
<li> set all ISEL bits and Rdrivers to 0 for chopped chips.


<!-- Date: Wed Apr 28 10:20:24 2004 -->
I used the quiet time to reboot the crate cpus to get the latest version of the VRB resfinder Software. I took the system through a cold start afterwards. Everything looked ok.<br> 
The only thing I found is, that there was something wrong with the minicom to b0svx03, I could see the messages, but I was not able to type anything. However vxlogin worked without any problems.  
<!-- Author:  Marcel -->


<!-- Date: Wed Apr 28 10:31:10 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4016&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4017  width='300' align='top'></a></td><td>AVDD Current of e553 on Apr 27, 2004. 
The current drop after the messy store and just didn't come back.</td></tr></table>
<!-- Author: Rong-Shyang -->
<!-- Comment: Wed Apr 28 13;46;13 comment by...Rong-Shyang -->
<pre>The IMon limit should be adjusted accordingly on the next store to avoid pinky.</pre>
<!-- Date: Wed Apr 28 10:50:23 2004 -->
<pre>More quiet time. So we decided to have cosmics run with silicon. 
e164 is in also. It tripped at 1st config but was be able to pass after several 'abort-config' on b0fib06.</pre>
<!-- Author: Rong-Shyang -->
<!-- Comment: Wed Apr 28 11;48;56 comment by...Rong-Shyang -->
<pre>After the cosmics data taking, e164 should be taken out of HWDB.
Also if e164 trips several time in a short period, it should be out, too.
 </pre>
<!-- Date: Wed Apr 28 11:46:47 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W5L3 
<li>problem n: 1238 
<li>Status: needs_observation
<li>Type: AVDD2
<li>Action: Incident
<li>entered by: rong 
<li>description is: AVDD current drop again after a messy store<a href= 'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=277&frame=2&anchor=18:47:03.520'> see shift elog</a>. The chips are chip86 are all gone. Try to set ISEL bits to 0 but still can't bring them back. INIT is masked and downstream chips are chopped. Now the last chip in HWDB is 86 and the rest of chips has ISEL and Rdriver set to 0. See also<a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=09:38:11'>  quiet time study</a> and <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=10:31:10'> AVDD current plot </a> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->





<!-- Date: Wed Apr 28 13:17:20 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4020&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4021  width='300' align='top'></a></td><td>IB4W1L1 bias currents. Drop in current for Bias1 (black) on day 1200 (4/15) coincides with abort kicker prefire. Bias0 (red) has not changed and is shown for comparison.</td></tr></table>
<!-- Author: David -->


<!-- Date: Wed Apr 28 18:10:31 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L4 
<li>problem n: 1243 
<li>Status: needs_observation
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: dkclark 
<li>description is: Physics is seen on all chips in recent runs. What changed? Monitor for a couple more weeks. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Apr 28 19:03:43 2004 -->
Clock problem caused about half of SVX to trip off.  After clock was restored, started bringing silicon up.  A few ladders in SVX layer 0 trip off too quickly for us to config, but we are working on it.
<!-- Author: Pete & Rong-Shyang -->
<!-- Comment: Wed Apr 28 19;20;55 comment by...Pete, Rong-Shyang & David -->
Persistence and a few extra tricks paid off, and everything is back up.  The stubborn ladders were: e000, e160, e250, e320, e3A0.


<!-- Comment: Wed Apr 28 20;25;35 comment by...Pete -->
Entry in shift elog can be found <a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=280&frame=2&anchor=18:23:05.562'>
here</a>.



<!-- Date: Wed Apr 28 20:22:32 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4022&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4022' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4023&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4023' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4024&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4024' width='300'></a></center>
<!-- Author: Pete -->
<!-- Comment: Wed Apr 28 20;24;05 comment by...Pete -->
State immediately after Clock incident



<!-- Date: Wed Apr 28 20:27:19 2004 -->
<pre>Reintegrated e382, which seems to have been taken out erroneously.</pre>
<!-- Author: Pete and David -->

<!-- Date: Wed Apr 28 20:31:52 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W8L2 
<li>problem n: 1191 
<li>Status: needs_access_2hr
<li>Type: Chip_bit_error
<li>Action: Added_hdwdb
<li>entered by: dkclark 
<li>description is: This ladder was removed on 4/8 or 4/9 by mistake. Added back in. Keep an eye out for B7L. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B3W8&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Apr 28 20:56:58 2004 -->
On aborting the run, saw:<br><br> 
<tt> 
CT: 2004.04.28 20:47:14<br> 
47'14" b0svx02:Messenger:8:47:15 PM->SRC Fatal Error:Sl 5 Gap Error <br> 
 -->  <br> 
 Additional Information: <br> 
<br> 
 Attention !!!. FERML_SRC_FATALITY ERROR !!! <br> 
<br>  
 SRC Fatal Error from b0svx02: Sl 5 Gap Error <br> 
 <br> 
 - HALT the run    <br> 
 - record any relevant information in e-log     <br> 
 - RECOVER - RUN     <br> 
[MLE]<br> 
</tt>
<!-- Author: Pete -->


<!-- Date: Wed Apr 28 21:50:31 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Apr_28_2004_215020.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4026  align='top'></a></td><td>SVT plot for run 182263</td></tr></table>
<!-- Author: Pete -->

<!-- Date: Wed Apr 28 22:07:47 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W5L3 
<li>problem n: 1251 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: petemc 
<li>description is: Changed AVDD Nominal value from 815 to 495 as a result of thread 1238.  See that thread for more details.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>815</td><td>495</td></tr>
<tr><td><b>Lower</b></td><td>785</td><td>465</td></tr>
<tr><td><b>Upper</b></td><td>830</td><td>510</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Apr 28 22:31:57 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L3 
<li>problem n: 1099 
<li>Status: needs_work
<li>Type: Wedgewide_DRO
<li>Action: Monitoring
<li>entered by: petemc 
<li>description is: Bit 7 low problem has reappeared.  No data on all but the first chip. It looks like the problems that previously disapeared have returned.  
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Apr 28 23:33:06 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Apr_28_2004_233303.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4038  align='top'></a></td><td>RMS Charge on IB1W5L4, second chip (34)</td></tr></table>
<!-- Author: Pete -->
<!-- Comment: Wed Apr 28 23;39;38 comment by...Pete -->
Oops, see below for the rest of the plots.
<!-- Date: Wed Apr 28 23:33:45 2004 -->
<center><a href='/elog/notebooks/silicon/Wed_Apr_28_2004_233024.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4028' ></a><a href='/elog/notebooks/silicon/Wed_Apr_28_2004_233045.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4030' ></a><a href='/elog/notebooks/silicon/Wed_Apr_28_2004_233157.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4032' ></a><a href='/elog/notebooks/silicon/Wed_Apr_28_2004_233214.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4034' ></a><a href='/elog/notebooks/silicon/Wed_Apr_28_2004_233244.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4036' ></a><a href='/elog/notebooks/silicon/Wed_Apr_28_2004_233303.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4038' ></a></center>
<!-- Author: Pete -->
<!-- Comment: Wed Apr 28 23;35;07 comment by...Pete -->
SVXMon plots for IB1W5L4 Z side, which reads out "No Data" in SVXMon.

<!-- Date: Wed Apr 28 23:39:18 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W5L4 
<li>problem n: 1252 
<li>Status: needs_work
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: petemc 
<li>description is: SVXMon complains of 'no data' on the Z side.  See <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=23:33:45'> here</a> for some more information. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=ISL&wedge=B1W5&layer=L4">report</a></ul>
<!-- Author: Problem DB -->




<!-- Date: Wed Apr 28 23:53:24 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4039&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4039  width='300' align='top'></a></td><td>Recent AVDD current for SB0W7L4.</td></tr></table>
<!-- Author: Pete -->


<!-- Date: Thu Apr 29 00:05:59 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4040&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4040  width='300' align='top'></a></td><td>DVDD for SB0W7L4.</td></tr></table>
<!-- Author: Pete -->

<!-- Date: Thu Apr 29 00:17:24 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W7L4 
<li>problem n: 1253 
<li>Status: needs_observation
<li>Type: Unknown
<li>Action: IMON_limits
<li>entered by: petemc 
<li>description is: AVDD oscillating between 985 and 925, sliding just below IMON lower limit.  Possibly some chips being lost and recovered?  See <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=23:53:24'> AVDD</a> and <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=00:05:59'> DVDD</a> recent history.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>1200</td><td>985</td></tr>
<tr><td><b>Lower</b></td><td>930</td><td>920</td></tr>
<tr><td><b>Upper</b></td><td>1350</td><td>1100</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B0W7&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Thu Apr 29 08:42:36 2004 -->
SB5W5L3 AVDD current up from 495 to 590 overnight.  Looks like the chips may be back, but give it some time to see if it sticks.
<!-- Author: Pete -->


<!-- Date: Thu Apr 29 11:08:39 2004 -->
SVX and L00 tripped off due to cooling alarm.  Apparently now a problem with SVX chiller compressor pump.
<!-- Author: Pete -->
<!-- Comment: Thu Apr 29 11;18;25 comment by...Andy H. -->
Compressor tripped off on "HPS" (I have to remind myself what this means, exactly).  Same thing that happened to the ISL chiller a couple days ago, but in this case I was able to reset the compressor.

<!-- Comment: Thu Apr 29 11;38;07 comment by...Pete -->
Andy turned the pump back on, and it worked, unlike the ISL chiller a few days ago.  SVX and L00 brought back without incident (the troublesome ladders from yesterday experienced no problems).

<!-- Comment: Thu Apr 29 12;31;25 comment by...Pete -->
It has happened a second time.  Leaving L00 and SVX off, and bringing ISL to standby until further notice.


<!-- Date: Fri Apr 30 18:19:57 2004 -->
With chiller work done, and things looking pretty good, Silicon was brought back to standby.
<!-- Author: Pete -->
<!-- Comment: Fri Apr 30 18;34;10 comment by...Pete -->
With abort gaps about 17 and stable, brought silicon to on.  As we were coming up, losses started to climb again, so brought it right back down to standby.

<!-- Comment: Fri Apr 30 19;40;41 comment by...Pete -->
After much oscillation in the abort gap rates, and some scraping, abort gap losses are low and stable.  Silicon brought up.


<!-- Date: Fri Apr 30 19:55:16 2004 -->
<table><tr><td><a href=/elog/notebooks/silicon/Fri_Apr_30_2004_195501.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4042  align='top'></a></td><td>SVT plot for run 182287.</td></tr></table>
<!-- Author: Pete -->


<!-- Date: Fri Apr 30 20:15:07 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4043&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4043  width='300' align='top'></a></td><td>recent AVDD history for SB0W5L3.</td></tr></table>
<!-- Author: Pete -->


<!-- Date: Fri Apr 30 20:17:43 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4044&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4044  width='300' align='top'></a></td><td>recent AVDD history of SB5W5L3.</td></tr></table>
<!-- Author: Pete -->


<!-- Date: Fri Apr 30 21:00:56 2004 -->
No data on SB1W2L4 (again) in run following chiller work.
<!-- Author: Pete -->


<!-- Date: Fri Apr 30 21:20:37 2004 -->
No data on SB5W0L0 in run following chiller work.
<!-- Author: Pete -->
<!-- Comment: Sat May  1 17;42;08 comment by...Pete -->
Oops, this was no data on e503, not e500.
<!-- Date: Fri Apr 30 21:23:12 2004 -->
<center><a href='/elog/notebooks/silicon/Fri_Apr_30_2004_212243.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4046' ></a><a href='/elog/notebooks/silicon/Fri_Apr_30_2004_212255.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4048' ></a></center>
<!-- Author: Pete -->
<!-- Comment: Fri Apr 30 21;23;50 comment by...Pete -->
Occupancies for e500 phi and z side.


<!-- Date: Sat May 1 11:23:11 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4049&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4049' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4050&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4050' width='300'></a></center>
<!-- Author: Pete -->
<!-- Comment: Sat May  1 11;27;27 comment by...Pete -->
<pre>AVDD currents for SB5W5L3.  Looks like something has recovered.</pre>

<!-- Date: Sat May 1 11:30:54 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W5L3 
<li>problem n: 1251 
<li>Status: needs_observation
<li>Type: AVDD
<li>Action: IMON_limits
<li>entered by: petemc 
<li>description is: Current has moved back up from 500 to 600.  Adjusted the limits accordingly.<table border=1>
<tr><th>IMON LIMITS</th><th>Old</th><th>New</th></tr>
<tr><td><b>Nominal</b></td><td>495</td><td>600</td></tr>
<tr><td><b>Lower</b></td><td>465</td><td>570</td></tr>
<tr><td><b>Upper</b></td><td>510</td><td>615</td></tr></table> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W5&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat May 1 12:04:47 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4051&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4051  width='300' align='top'></a></td><td>Recent AVDD history of SB1W8L4.</td></tr></table>
<!-- Author: Pete -->


<!-- Date: Sat May 1 12:06:56 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4052&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4052' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4053&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4053' width='300'></a></center>
<!-- Author: Pete -->
<!-- Comment: Sat May  1 12;13;33 comment by...Pete -->
Longer term history of e184 AVDD.  Looks like this excursion has started around April 25.

<!-- Date: Sat May 1 12:27:30 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W8L4 
<li>problem n: 1235 
<li>Status: needs_observation
<li>Type: AVDD2
<li>Action: Diagnosis_update
<li>entered by: petemc 
<li>description is: Since about April 25, this ladder's AVDD current has been erratically moving between the nominal 1100 and ~1060.  See <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=12:04:47'> an example</a> and <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=193&frame=2&anchor=12:06:56'> history</a> 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W8&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat May 1 14:25:19 2004 -->
With new store, silicon brought up with lostp stable and 20.1 KHz.  High rate test coming up.
<!-- Author: Pete -->


<!-- Date: Sat May 1 14:31:09 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4054&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4054' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4055&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4055' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4056&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-4056' width='300'></a></center>
<!-- Author: Pete -->
<!-- Comment: Sat May  1 14;31;58 comment by...Pete -->
State of IMON before high rate test.

<!-- Date: Sat May 1 17:27:41 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L4 
<li>problem n: 1243 
<li>Status: needs_work
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: petemc 
<li>description is: This problem is back.  No data on all chips. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat May 1 17:33:15 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L3 
<li>problem n: 1254 
<li>Status: needs_work
<li>Type: Unknown
<li>Action: Incident
<li>entered by: petemc 
<li>description is: No data on phi side now, also. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sat May 1 17:51:03 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L3 
<li>problem n: 1254 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Monitoring
<li>entered by: petemc 
<li>description is: This was actually thread 1099. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Sat May 1 17:53:42 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L3 
<li>problem n: 1099 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: petemc 
<li>description is: Bit 7 error causes no data on all but first chip.  Transferring it to Detector-needs work. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->
<!-- Comment: Sat May  1 18;26;41 comment by...rainer -->
Not a clear cut bit7l - study with SVXDAQ during quiet time.
<pre>
e503 6afc 091d 0003 
          081d 071d 
          <b>86</b>13 3305 340f 3517 36f3 40f3 4131 4205 
          051d 2904 2a0e 2b3f 2c5a 2d4f 2e4f 2f51 303c 3141 323b     
               3349 3439 3560 3640 3704 3bf3 3c0e 3d55 3e67 3f27                
               400e 4110 420a 4309 440c 4508 460c 4708 4809 4908
              59f3 5a14 5b20 5c02 041d 7ff3 5f55 7f55 7955 4f51           
              7f55 
         7855 7f55 4fd0 d0c2 c2c4
0000 e504 </pre>
<!-- Date: Sat May 1 17:59:55 2004 -->
<h2> High Rate Test </h2> 
<li> we ran a test with the L1 trigger scaler limit moved to <b> 30 kHz </b>. The number of kicks allowed before the ghostbuster fires was moved from 10 to 8 kicks. The resonance detector did not fire (we got a few L2 w/o L1 we could HRR out of). <li> 
The highest rate we ran was about ~25Khz L1A rate @13% dead time  
<li>some DVDD currents came to pink level but went away when the rate was reduced again - also the corresponding AVDD was monitored and stayed flat. The jumper failures where masked 'IGNORE' in IMON. 
  
<!-- Author: Marcel, Pete, Rainer -->
<!-- Comment: Sat May  1 18;00;20 comment by...rainer -->
See plot 

<a href=
'http://www-cdfonline.fnal.gov/cgi/elog/elog.pl?nb=2004&action=view&page=289&frame=2&anchor=17:47:00.265'>
here </a> 



<!-- Date: Sat May 1 18:43:54 2004 -->
Entered in Silicon database: <ul>
<li>Ladder: SB5W0L3 
<li>problem n: 1099 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: petemc 
<li>description is: Also, run 182263 (where this started) was the first run following the trip caused by the clock glitch. 
<li>See <a href="http://www-cdfonline.fnal.gov/internal/usr/lmiller/cgi-bin/newproblemdb/DBreport.pl?detsys=SVX&wedge=B5W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Sun May 2 21:21:23 2004 -->
SVX compressor tripped off around 16:00 today.  It was resettable and is currently running.  Apparently the valve that we swapped out on Friday wasn't the root of its problems.  So we put the old SVX valve on the ISL chiller and now the ISL chiller runs (recall that when the ISL chiller 
failed before it failed hard and couldn't run at all --- so its 
valve very likely was the root of its problem).  The ISL chiller was valved back into the system, freeing up the spare again.  All silicon is OFF while we accrue some chiller operating time.  Nothing was done to the SVX chiller; a technician will spend some more time with it tomorrow morning to try and pinpoint its problem.
<!-- Author: Andy H. -->