<!-- Title: 10:15:51  Mon Jun  6 2005 -->
<!-- Crewchief: Tuula -->
<!-- Op1: Rong-Shyang -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
Take good data.

<!-- Date: Mon Jun 6 10:43:18 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W1L1 
<li>problem n: 1478 
<li>Status: needs_observation
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Cap ID problem (=bit errors?) for 73% of events in Run 199025; problem gone in the following run.  Monitor. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Jun 6 11:00:15 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W2L1 
<li>problem n: 1178 
<li>Status: fixed
<li>Type: FE_amp_osc
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Checked second half Z-side was really chopped in SVXMon.  Plots can be found <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=251&frame=2&anchor=17:11:31'> here</a>. </p>  <p>The latest read out time for this ladder is 3.6uS.  The chip chop worked and the read out time is OK. Now closing this thead.</p>    
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Jun 6 11:13:39 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB0W4L4 
<li>problem n: 1233 
<li>Status: needs_study_time
<li>Type: DRO_00F3
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>Two problems spottted during quiet time. First of all all the ISEL bits for this ladder in SVXMon were all set to zero. After setting the ISEL bits to their default values, I could recreate the problem seen in the DS Err Mon.  We seem to have 00f3 problems with chip 8d.</p>    
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B0W4&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Jun 6 11:18:39 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W2L0 
<li>problem n: 868 
<li>Status: needs_study_time
<li>Type: Chip_capid
<li>Action: Diagnosis_update
<li>entered by: amitra 
<li>description is: <p>During quiet time, we confirmed the problem exists. Chip 82 has stuck Cap-ID. Chip 83 has bit 5 low in Read All mode.  Would like to stufy furthur before declaring this thread unfixable.</p> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W2&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Jun 6 11:51:18 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6762&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6762' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6763&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6763' width='300'></a></center>
<!-- Author: sasha -->
<!-- Comment: Mon Jun  6 11;53;04 comment by...sasha -->
<pre>these are avdd & dvdd currents for SB4W7L0 (e470).
current limits were changed on may 08, so they are holding steady</pre>

<!-- Date: Mon Jun 6 11:58:18 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W7L0 
<li>problem n: 1473 
<li>Status: fixed
<li>Type: AVDD
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: avdd & dvdd currents are holding steady since the time they were changed. <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=252&frame=2&anchor=11:51:18'> link to avdd & dvdd currents</a> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W7&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Jun 6 12:07:30 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6764&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6764  width='300' align='top'></a></td><td> </td></tr></table>
<!-- Author: sasha -->
<!-- Comment: Mon Jun  6 12;09;18 comment by...sasha -->
<pre>current is going down since the limits were changed on 05/26/05. as one can see the current seems to be stable before that.</pre>

<!-- Date: Mon Jun 6 12:13:27 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W2L1 
<li>problem n: 1359 
<li>Status: needs_observation
<li>Type: BIAS
<li>Action: Currents_investigated
<li>entered by: sasha 
<li>description is: the current seems to go down a little bit after the limits were changed on 05/26/05. needs more observation to see if it settles.  <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=252&frame=2&anchor=12:07:30'> link to a bias current plot </a> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W2&layer=L1">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Jun 6 12:19:52 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB1W0L3 
<li>problem n: 1032 
<li>Status: needs_study_time
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: sasha 
<li>description is: changing to need_study_time. we want to see if we can reproduce it.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B1W0&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Jun 6 12:41:24 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB4W10L3 
<li>problem n: 1407 
<li>Status: needs_observation
<li>Type: DRO_00F3
<li>Action: Monitoring
<li>entered by: sasha 
<li>description is: error rate was very low in the beginning, but then it started increasing a little bit. However, recently the error rate reduced back to ~1%. we'll look on this ladder in ~1 week again. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B4W10&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Mon Jun 6 13:39:59 2005 -->
Found the error window poped behind SVXMon. 
------------------------------- 
<pre> 
Please read and follow the instructions below.  
 
 
UNBIASED CHIPS ALARM from SvxMonRunCompare:  
 
1 chips were NOT BIASED IN THE PREVIOUS RUN (run 199041). 
 
Please check with the ACEs & SciCo: if the Silicon was supposed to be biased  
and give physics quality data during run 199041, PAGE THE SILICON EXPERT! 
 
In any case, please make an entry in the elog. 
 
The complete log is in /data1/consumer/results/SVXMon//run_compare_199041.log 
 
 
################################################# 
# ALARM : THE FOLLOWING CHIPS WERE NOT BIASED!  # 
################################################# 
# daq name :   offline name    : mean : stdev : stdevVar : occup 
SB1W2L2C4 : west east 2 3 phi 4 : -4.7 : -2.4 : -3.1 : 8.7 
 
</pre> 
---------------------------------------- 
should double check if something is wrong.
<!-- Author: Rong-Shyang -->
<!-- Comment: Mon Jun  6 13;58;46 comment by...boveia -->
When ADCMon processes this run I'll check.


<!-- Date: Mon Jun 6 17:16:41 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6765&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6765' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6766&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6766' width='300'></a></center>
<!-- Author: Rong -->
<!-- Comment: Mon Jun  6 17;18;51 comment by...Rong-Shyang -->
<pre>Charge distribution of SB1W1L2(e112) which was complained by SVXMon that chip4 had lower mean and occupancy during data taking. So it's clear that chip4 started disappearing during run 199041.</pre>


<!-- Date: Mon Jun 6 17:25:17 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6767&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6767' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6768&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6768' width='300'></a></center>
<!-- Author: Rong -->
<!-- Comment: Mon Jun  6 17;25;55 comment by...Rong-Shyang -->
<pre>The occupancy of SB1W1L2(e112) for run199041 and 199042. So it almost gone for current run.</pre>

<!-- Date: Tue Jun 7 02:59:11 2005 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 410
Calibration type  : standard
Run period tag    : Jun_2005
DPS-off run       : 199044
DPS-on run        : 199045
Requested by      : Clark Cully
Main process id   : 22671
Comment           : Ran fine
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->


<!-- Date: Tue Jun 7 02:59:11 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 410 FAILED.

Job info
--------
Calibration type : standard
DPS-off run      : 199044
DPS-on run       : 199045
Requested by     : Clark Cully
Submitted        : 2005-06-07 02:58:10
Completed        : 2005-06-07 02:58:40
Status           : FAILURE
Comment          : Ran fine

Last processing stage reported : checking silicon configuration
Failure diagnostics :
Inconsistent dps mode for run 199044. Check your argument order.
Exiting.
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->


<!-- Date: Tue Jun 7 03:03:19 2005 -->
<p><font size=+1> D-mode Calibration Job Started </font>
<p><pre>
Job id            : 411
Calibration type  : standard
Run period tag    : Jun_2005
DPS-off run       : 199045
DPS-on run        : 199044
Requested by      : Clark Cully
Main process id   : 29753
Comment           : Ran Fine
</pre>
<!-- Author: CDF silicon D-mode calibration job server v1.4 -->



<!-- Date: Tue Jun 7 05:29:45 2005 -->
New store came in with initial L=54.0, Silicon on from the beginning.
<!-- Author: Tuula -->


<!-- Date: Tue Jun 7 07:03:49 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6769&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6770  width='300' align='top'></a></td><td>SVTSpymon plot for store #4195.</td></tr></table>
<!-- Author: Tuula -->


<!-- Date: Tue Jun 7 07:06:15 2005 -->
<pre>SVXMon Status: OK 
--------------------------------------- 
Run 199061, Tue Jun  7 07:05:22 
SVX 
Status: OK 
ISL 
Status: OK 
L00 
Status: OK 
</pre>
<!-- Author: Tuula -->

<!-- Date: Tue Jun 7 10:53:16 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: LB1W3L0 
<li>problem n: 631 
<li>Status: fixed
<li>Type: RX
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Bit 1 problem gone for now. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=L00&wedge=B1W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 10:55:20 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W1L4 
<li>problem n: 185 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Fixed.  It was easy! 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W1&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 10:56:49 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Not seen for 30 days. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 10:56:49 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W3L2 
<li>problem n: 1136 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Not seen for 30 days. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W3&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 11:03:03 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W1L2 
<li>problem n: 928 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Rate is around 5-10%. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 11:07:11 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W2L3 
<li>problem n: 436 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: If the problem continues at this low frequency, I think we can live with it.  Is it correlated with operating conditions? 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W2&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 11:11:20 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W11L3 
<li>problem n: 643 
<li>Status: needs_work
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: boveia 
<li>description is: No. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W11&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 11:13:24 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W0L4 
<li>problem n: 1476 
<li>Status: fixed
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W0&layer=L4">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 11:15:01 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W1L3 
<li>problem n: 184 
<li>Status: fixed
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Fixed. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W1&layer=L3">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 11:25:51 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W11L0 
<li>problem n: 1475 
<li>Status: fixed
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Gone. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W11&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Tue Jun 7 11:42:26 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L2 
<li>problem n: 1479 
<li>Status: needs_observation
<li>Type: Chip_capid
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Chip 86 has the wrong cap ID (correct value - 1) for nearly all events in recent runs (e.g. 199041.)  If this persists, pass to Detector. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Tue Jun 7 11:54:13 2005 -->
Silicon will be put to Standby a couple of minutes before MCR powers down a booster sector at 12:30. An hour later the booster sector will be restored. Last time they did such a power up, they lost the store. 
<!-- Author: Tuula -->

<!-- Date: Tue Jun 7 12:36:28 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 411 finished successfully.

Job info
--------
Calibration type : standard
DPS-off run      : 199045
DPS-on run       : 199044
Requested by     : Clark Cully
Submitted        : 2005-06-07 03:02:51
Completed        : 2005-06-07 12:36:14
Status           : SUCCESS
Comment          : Ran Fine
</pre>
<!-- Author: D-mode script run_calib_analysis.tcl -->


<!-- Date: Tue Jun 7 16:39:38 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W1L2 
<li>problem n: 1480 
<li>Status: needs_work
<li>Type: Unknown
<li>Action: Incident
<li>entered by: rong 
<li>description is: Chip 86 is gone during data taking, see <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=252&frame=2&anchor=17:16:41'> elog</a>. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Jun 8 01:54:01 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W1L2 
<li>problem n: 1480 
<li>Status: fixed
<li>Type: Unknown
<li>Action: Incident
<li>entered by: boveia 
<li>description is: Mistaken entry.  Belongs to e122. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W1&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Jun 8 01:58:49 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L2 
<li>problem n: 1479 
<li>Status: needs_work
<li>Type: Unknown
<li>Action: Incident
<li>entered by: boveia 
<li>description is: Chip 86 is gone during data taking. <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=252&frame=2&anchor=13:39:59'> e-log</a> 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Jun 8 09:21:33 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB3W11L3 
<li>problem n: 643 
<li>Status: needs_access_2hr
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: marcel 
<li>description is: ok, we still have bit 7 and occasionally bit 3 high. I suggest to track this down in the next access doing the standard programme 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B3W11&layer=L3">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Jun 8 10:00:07 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6771&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6771' width='300'></a><a href='/elog/notebooks/silicon/Wed_Jun__8_2005_095948.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6775' ></a></center>
<!-- Author: boveia -->
<!-- Comment: Wed Jun  8 10;04;17 comment by...boveia -->
<pre>e250 adc distribution in run 199060 for chip a1.  First plot = output of ADCMon.  Second plot = output of daqana, rotated 90 degrees.  Taking the quiet time studies into account, I conclude that the missing data problem on a1 is an artifact of ADCMon and is not real.</pre>

<!-- Date: Wed Jun 8 10:08:18 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W5L0 
<li>problem n: 1472 
<li>Status: fixed
<li>Type: Chip_bit_error
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: chip a1 <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=252&frame=2&anchor=10:00:07'> is ok</a> despite ADCMon plots to the contrary.  The problem in the previous entry (and likely the a1 problem as well) is due to the unfixable bit 6. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W5&layer=L0">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Jun 8 10:43:05 2005 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Jun__8_2005_104303.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6777  align='top'></a></td><td>SB1W2L2 data by SVXdaq.</td></tr></table>
<!-- Author: Rong -->
<!-- Comment: Wed Jun  8 10;45;44 comment by...Rong-Shyang -->
<pre>Chip86 is responding to front-end setting change but doesn't have any reaonable noise. Either some control command is missing or something is dead in the frontend?</pre>

<!-- Date: Wed Jun 8 10:49:53 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB4W3L0 
<li>problem n: 1457 
<li>Status: fixed
<li>Type: Other
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: For future reference, bumps are due to hot channels 41 and 44 on chip 1, channel 79 on chip 2.   
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B4W3&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Jun 8 10:54:23 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L2 
<li>problem n: 1479 
<li>Status: needs_work
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: rong 
<li>description is: Chip 86 looks pretty much dead druing quiet time study. Various setting change could not help it, see<a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=252&frame=2&anchor=10:43:05'> elog</a>. If no other idea, sparse it in the HWDB and close the thread. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L2">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Jun 8 11:09:57 2005 -->
<table><tr><td><a href=/elog/notebooks/silicon/Wed_Jun__8_2005_110954.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6779  align='top'></a></td><td>Ha, e122 chip86 is back after power cycle.</td></tr></table>
<!-- Author: Marcel, Rong -->

<!-- Date: Wed Jun 8 11:12:01 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W2L2 
<li>problem n: 1479 
<li>Status: needs_observation
<li>Type: Chip_other
<li>Action: Diagnosis_update
<li>entered by: rong 
<li>description is: Spoke too fast earlier. Chip86 is back after power cycle, see <a href= 'http://www-cdfonline.fnal.gov/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=252&frame=2&anchor=11:09:57'> elog</a>.    
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W2&layer=L2">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Wed Jun 8 11:30:57 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB2W2L4 
<li>problem n: 1423 
<li>Status: fixed
<li>Type: DRO_00F3
<li>Action: Monitoring
<li>entered by: boveia 
<li>description is: Ok. 
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B2W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->



<!-- Date: Wed Jun 8 14:56:34 2005 -->
<pre>Blinky board on tstsvx1 is working again (power cables were unwelded after LA was moved inside the rack).</pre>
<!-- Author: Sebastian -->


<!-- Date: Wed Jun 8 17:25:29 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6780&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6781  width='300' align='top'></a></td><td>SVTSpymon plot for store #4198. Initial luminosity 90.5.</td></tr></table>
<!-- Author: Tuula -->
<!-- Comment: Wed Jun  8 17;27;51 comment by...Tuula -->
<pre>And there are no yellow cells in SVXMon.</pre>


<!-- Date: Thu Jun 9 11:14:32 2005 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6782&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6782' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6783&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6783' width='300'></a></center>
<!-- Author: Rong-Shyang -->
<!-- Comment: Thu Jun  9 11;14;57 comment by...Rong -->
<pre>So, e122/chip86 is recovered.</pre>


<!-- Date: Thu Jun 9 15:03:32 2005 -->
<h3>Fun with Crate 7 </h3> 
This afternoon, crate 7 lost communication. Sung-Won called me and I had a look, keep in mind, this is the crate with serial  
console hooked up.<br> 
 The first message from svxinter is the usual 
<pre> 
 Caenet_write: Error number -1 ffffffff received 
group_info:cr_n = 7, response = -1 
 Caenet_buffer: Error number 7 7 received 
group_info:cr_n = 7, response = 7 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -251 ffffff05 received 
group_info:cr_n = 7, response = -251 
 Caenet_write: Error number -1 ffffffff received 
group_info:cr_n = 7, response = -1 
 Caenet_write: Error number -1 ffffffff received 
group_info:cr_n = 7, response = -1 
WARNING: found a power supply in the crate, which is not connected to a wedge in the detector, or absent in CAEN.map,  cr_n = 7, bd_n = 2 
 Caenet_write: Error number -253 received 
 
cr = 7, bd = 2,Errcode 10 
WARNING: found a power supply in the crate, which is not connected to a wedge in the detector, or absent in CAEN.map,  cr_n = 7, bd_n = 6 
 Caenet_write: Error number -253 received 
</pre> 
 
Then I looked at the Laptop: 
<pre> 
 
 
         C.A.E.N.       SY527        V4.05                   Crate 07 
 
                             Hardware Status 
 
Memory       Test   PASSED                         Power  +5V  + 5.136  OK 
EEPROM       Test   PASSED                         Power +12V  +11.771  OK 
CAENET       Test   PASSED                         Power -12V  -11.928  OK 
Port A       Test   PASSED 
Port C       Test   PASSED 
Timer        Test   PASSED                         Parity Error 
LCD Display  Test   PASSED 
DAC          Test   PASSED 
ADC          Test   PASSED 
ADC FPGA     Load   PASSED 
1st DAC FPGA Load   PASSED 
2nd DAC FPGA Load   PASSED 
 
Firmware installed on FLASH EPROMs                 UART Chip: 16550 
Installed RAM: 256 Kbytes                    A464 FIFOs size: 4     Kbytes 
 
Test is not OK; (C)ontinue or (R)epeat Test ? [ ] 
</pre> 
So for me it looks like, the CPU has already rebooted itself, because this looks a lot like a normal CAEN bootup sequence. However it keeps complaining about the parity. I could however talk to the crate (tested this by just p0ressing return).I just ended up in the normal CAEN screen. I hockerized the crate and everything is fine. When I came upstairs, the crate was still grey, it only recovered after the reboot (i was too fast to get in the control room again). So things to check next time are the state of CAENNET versus Serial (it seems the serial survives ...) and try to recover without resetting .
<!-- Author: Marcel -->


<!-- Date: Fri Jun 10 10:37:35 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6784&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6785  width='300' align='top'></a></td><td>SVTSpymon plot for store #4201, initial luminosity 92.</td></tr></table>
<!-- Author: Tuula -->
<!-- Comment: Fri Jun 10 14;28;16 comment by...Tuula -->
<pre>SVXMon Status: OK
---------------------------------------
Run 199187, Fri Jun 10 14:27:44
SVX
Status: OK
ISL
Status: OK
L00
Status: OK
</pre>


<!-- Date: Fri Jun 10 22:20:28 2005 -->
SB2W2L4 DVDD tripped second time soon after the first trip. I adviced the monitoring ACE to try instructed trip recovery once again. No trips since then.
<!-- Author: Tuula -->


<!-- Date: Fri Jun 10 23:50:27 2005 -->
<pre>We got trigger inhibit from IB5W5L0. I came in, and didn't find out reason for inhibit. I paged Rong, and he instructed to hockerize the crate 10. It helped.</pre>
<!-- Author: Tuula -->
<!-- Comment: Fri Jun 10 23;55;56 comment by...Rong -->
<pre>There is no error message in PSGui, either. Don't know the reason. Anyway, hockerization is the easy way to reset things.</pre>

<!-- Comment: Sat Jun 11 00;16;55 comment by...Marcel -->
Pretty obvious, what happened 
The readback of one of the bias lines got garbled, that usuall causes an inhibit (You might see only 10 Volts instead of 90). Anyway, Hockerization is the way out of this



<!-- Date: Sat Jun 11 14:25:41 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6786&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6787  width='300' align='top'></a></td><td>SVTSpynon for store #4202, initial luminosity 107.</td></tr></table>
<!-- Author: Tuula -->


<!-- Date: Sat Jun 11 14:28:55 2005 -->
<pre>No yellow cells in SVXMon.</pre>
<!-- Author: Tuula -->


<!-- Date: Sat Jun 11 16:18:33 2005 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6789&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-6790  width='300' align='top'></a></td><td>Very high losses at Tevatron. Silicon was put on Standby by shift crew when the high losses occured.</td></tr></table>
<!-- Author: Tuula -->
<!-- Comment: Sat Jun 11 16;19;50 comment by...Tuula -->
<pre>Beam has been stable ever since, and we are taking data with Silicon.</pre>


<!-- Date: Sun Jun 12 11:28:34 2005 -->
<table><tr><td><a href=/cgi/elog/elog.pl?nb=2005&action=view&page=-10193&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/elog.pl?nb=2005&action=view&page=-10193 width='300' align='top'></a></td><td>Bulkhead 10 missing in run 199223 for SVX L0-L3. OK in 199218 (last physics run)</td></tr></table> <BR> 
CO found yellow cells for SB0W10 wedges. The weired thing is that SVT doesn't show a hole there. 
<!-- Author: Tuula and Rong -->
<!-- Comment: Sun Jun 12 11;43;32 comment by...Tuula -->
<pre>I power cycled SB0W10, and now there are no yellow cells in SVXMon.</pre>

<!-- Comment: Sun Jun 12 11;50;48 comment by...MArcel -->
<pre>data is ok as well
&lt;pre&gt;
4afce0a0
      964: 00f38322 511c5007 535b52a0 55065416
      968: a1228222 0808a022 0a13090f 0c0f0b13
      972: 0e170d4c 7ff30f03 e0a1c1c1 85224afc
      976: 842200f3 4d184c07 4f1a4ecc 83225009
      980: 4c03a222 4e124d0f 50344f18 521d5123
      984: 54085337 a022a122 c1c17ff3 4afce0a2
      988: 00018922 35103404 371c3612 39143859
      992: 3b043a0c 3e133d08 401c3f13 422b4128
      996: 440a4327 76024504 780b770b 7a0f790d

     1000: 7c077b0f 87228822 85228622 2605a422
     1004: 28082716 2a162912 2c162b46 2e072d07
     1008: 30132f0e 321e3110 342a331f 36113519
     1012: 68083701 6a12690c 6c086b10 6e036d11
     1016: a222a322 a022a122 c1c17ff3 4afce0a3
     1020: 00f38922 87228822 85228622 5bf38422
     1024: 5df35c31 7e357d08 a3227f06 a122a222
     1028: 5208a022 540e5310 56085511 c1c17f02
     1032: 4afce0a4 00f38d22 8b228c22 0a088a22
     1036: 0c520b0c 0e030d12 26048922 28022709
     1040: 87228822 290a2801 67062af3 6908680d
     1044: a522a622 6d09a422 6f5c6e0c 71077028
     1048: a222a322 a022a122 c1c1
&lt;/pre&gt;</pre>


<!-- Date: Sun Jun 12 12:34:54 2005 -->
<pre>Wedges SB0W7-9, SB0W18-9 and SB27-8 turned OFF when ACE pressed "End of Store" button  in HVSummary. Silicon PSGui was also frozen. So I restarted PSGui, turned the wedges to STANDBY and confirmed coldstart. Now everything is OK. 
 
 
 
 
</pre>
<!-- Author: Tuula -->
<!-- Comment: Sun Jun 12 12;36;48 comment by...Marcel -->
and this time, it was crate 6


<!-- Date: Sun Jun 12 16:13:51 2005 -->
<pre>Several ladders tripped from STANDBY to OFF.</pre>
<!-- Author: Tuula -->
<!-- Comment: Sun Jun 12 16;22;17 comment by...Tuula -->
<pre>I turned the ladders to STANDBY, and performed coldstart. Some ladders tripped soon after I turned them STANDBY, so I had to turn them to STANDBY a couple of times. PSGui got frozen couple of times, so I had to restart that also. Now everything is OK.</pre>

<!-- Comment: Sun Jun 12 16;36;02 comment by...Tuula -->
<pre>Some wedges had all layers tripped, some only had one layer tripped. </pre>

<!-- Comment: Sun Jun 12 18;18;36 comment by...Marcel -->
an IMON snapshot would have been useful to understand this trip



<!-- Date: Mon Jun 13 14:12:40 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: SB1W10L0 
<li>problem n: 1167 
<li>Status: needs_observation
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: we checked sb1w10l0 (e1a0) with SVX daq. After running 10K events in the 'nearest neighbor mode' we didn't see any errors. Passing this back to the monitoring group.  If it's error free then it should be declared FIXED.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=SVX&wedge=B1W10&layer=L0">report</a></ul>
<!-- Author: Problem DB -->


<!-- Date: Mon Jun 13 14:35:28 2005 -->
Entered in Silicon database: <ul>
<li>Ladder: IB0W2L4 
<li>problem n: 110 
<li>Status: needs_access
<li>Type: Chip_bit_error
<li>Action: Diagnosis_update
<li>entered by: sasha 
<li>description is: we could confirm the problem with the SVX daq. We actually see that   same garbage is everywhere. see example: 00bf00bf or 20fb20fb. We'd like to do a fiber swap to check if it's a daq or detector problem.  
<li>See <a href="http://b0sili01.fnal.gov/cgi-bin/pdb/DBreport.pl?detsys=ISL&wedge=B0W2&layer=L4">report</a></ul>
<!-- Author: Problem DB -->