<!-- Title: 06:28:15  Mon Sep 10 2001 -->
<!-- Crewchief: The Usual Suspects -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
<pre>Start with beam angle scans</pre>


<!-- Date: Mon Sep 10 06:45:10 2001 -->
<pre>A long entry for the scan; see also the CDF main shift log. 
 
Cooperating with Bruce Hannon in MCR.  Start with 
Magnet HB11 current at -41 A, where limit is -50 A.   
From BeamMon on run 126126, initial tilts are 
+465+-100 in x, -342+-100 in y. 
 
First try to increase HB11 to -35 A, start with horizontal (x) 
 
1250 Angular bump complete, wanted -500 urad in x, but due to sign error in translation to accelerator, was +500. 
 
0110 Run starts with high losses.  Run did not go to look area. 
 
0123 Start a run at +500 to go to look area. 
 
0205 Start run at truly -400 urad.  HB11 at -47, HA46 at -21. 
 
0321 Move beam position parallel -400 um to get more room on HB11. 
HB11 -28 A, HA49 14 A.  Took run, confirmed parallel motion. 
 
0405 Tried to move to -1 mrad.  Encountered huge losses at -540 urad.  Tried to back off to  -200 um offset but doesn't help. 
Will scrape the beam later. 
 
Move to testing vertical 
 
0440 Two spurious silicon cooling foghorn alarms.  One may have been associated with an air separator pressure. 
 
0445 Move vertical angle by +0.25 urad.   Find large losses (pbar!) going much more than this in positive direction.  Take run at this setting. 
 
0513 SB5W3 L0 DVDD Overcurrent Trip 
 
0520 More vertical angle to -0.55 urad from start.  Take run here. 
 
0555 End run to take a final centered run (using settings -400 urad in x, +150 urad in y).  PS doesn't respond, reboot  
svxinter downstairs. 
 
0610 Turned on SVX and began run 
 
0640 End run, turn to standby for scraping. 
 
</pre>
<!-- Author: ADF -->
<!-- Comment: Thu Sep 13 10;15;54 comment by...ADF -->
<pre>Losses in the last hand-knb-turning limit study</pre>
<!-- Date: Mon Sep 10 06:46:34 2001 -->
<pre>SB1W1 L4 software protection trip</pre>
<!-- Author: ADF -->


<!-- Date: Mon Sep 10 07:00:02 2001 -->
<pre>0648 Scraping finished, try to find limits scanning correctors by hand, looking for the limits in losses. 
 
Start with +0.4 urad, move positive toward +0.55 urad (note accel has relative sign wrt us) 
 
+0.725 is about the limit as far as losses go. (i.e. 325 um of play, on _our_ negative side, their positive) 
 
Now try vertical 0654 it's at accelerator +0.15 (also our +0.15) 
 
+0.65 is still safe, 0.60 is definitely safe. 450-500 urad of play in vertical. 
 
On other sides, there's plenty of room (&gt;1 mrad) 
 
Success! 
</pre>
<!-- Author: ADF -->


<!-- Date: Mon Sep 10 07:27:35 2001 -->
<pre>Turned SVX to OFF in preparation for opening the plugs.</pre>
<!-- Author: ADF -->


<!-- Date: Mon Sep 10 07:33:31 2001 -->
<pre>Angles from this evening's scan.  The positions are not shown. 
 
All angles in microrad, settings are measured from starting point, measured is angle wrt COT axis.  Results from CSL BeamMon. 
 
Run 	Xset	Xmeas		Yset	Ymeas 
126126	0	466+-108	0	-343+-121   Start 
126131	504	790+-185	0	166+-210 
126132	0	98+-179		0	-298+-193 
126134	-400	-128+-179	0	-136+-202 
126136	-400	113+-172	0	-288+-199   400 um shift 
126137  -400	-171+-196	250	268+-199 
126138	-400	-31+-197	-550	-919+-218 
126141	-400	-3+-209		150	222+-209 
 
Thanks to devlin for compiling the list.	</pre>
<!-- Author: ADF -->


<!-- Date: Mon Sep 10 15:26:46 2001 -->
<pre>CAEN POWER supplies are LOTT"d off by unplugging the 
5V enable power supplies.  This is because of AR-Ethane in  
the COT while the baggies are off.  Until the baggies are 
back, we can't run the silicon.  However, Rob and Matt  
can do local tests with the load boxes.</pre>
<!-- Author: jean -->


<!-- Date: Mon Sep 10 15:58:08 2001 -->
<pre>I have started the new version of the GUI, including the L00  
power supply design, in the Silicon squad room.</pre>
<!-- Author: Andrew -->


<!-- Date: Mon Sep 10 17:58:49 2001 -->
<pre>After Mary fixed the GUI code for the hardware DB, I put 'comp dir' back on for the three test ladders.</pre>
<!-- Author: Petra -->


<!-- Date: Tue Sep 11 08:59:09 2001 -->
<P>Came in this AM and found an alarm message on the GUI: 
<pre>ALARM L00 B0 W2 L0 is reported off, but low/high voltage is above 2/5 Volts</pre> 
The message occured last night at 21:18.  While I was typing this entry I got another one on B1 W5 L4.  Checking its full status shows 2 volts on the 2V DOIM.  This is disturbing since to my knowledge neither of these PSs is enabled right now.  I am going downstairs to check the crate now.
<!-- Author: Napora -->
<!-- Comment: Tue Sep 11 09;44;32 comment by...Napora and Del Gamba -->
<p>Went to check on this downstairs.  The crate reported 2.03 volts as well.  We hooked up the patch board; during this process the voltage dropped to .25 volts.  Then we hooked up a volt-meter and the voltage dropped the rest of the way to zero as we watched.  It looks like this might be a real, capacitively stored voltage on the PS.  How it got there is anyone's guess since it hasn't yet been turned on.

<p>We are going to hold off on installing the remaining L00 supplies until this is understood better.


<!-- Date: Tue Sep 11 11:36:02 2001 -->
 <h1>HDI failures over weekend of 9/7/01 to 9/10/01</h1> 
Did some studies of the HDI initialization failures.  Starting 
last Friday, for every failed HDI Initialization the 
expected and received bitstreams are published to the  
smartsockets subject "/hdiError" and I started a simple 
spy program to dump them into a file.  The resulting 
file is /data1/svxData/hdiError.log, and I have looked 
through it and tried to correlate with the PS logs 
in ~svxii/daq/PSanywhere/log.  General Results: 
<ul> 
<li> The silent retry of the initialization after a failure does not work at all.  We had the code doing up to 4 retries, and 
we never saw less than 4 attempts.  This is not well understood- 
perhaps we need to move the retry further up-to the Fib level? 
<li> The returned Bitstreams were either all 0xFF or 0x00, no 
garbled bitstreams or single bits missing.   
 
<li> Some but not all are clearly associated with PS problems, 
some are somewhat but not totally correlated. 
</ul> 
 
Here is the laundry list: 
<table> 
<tr> <th> HDI</th> <th>Date</th> <th>Time</th> <th>00s/FFs</th> <th>Anything in PS log?</th> </tr> 
<tr> <td> SB0W0-0 </td> <td>9/9 </td> <td>23:22:08</td> <td>00s</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/10</td> <td>02:49:06</td> <td>00s</td> <td>Nothing </td> </tr> 
<tr> <td> SB0W0-1 </td> <td>9/7 </td> <td>20:36:06</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB0W0-3 </td> <td>9/9 </td> <td>16:40:34</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB0W0-4 </td> <td>9/8 </td> <td>13:51:04</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/9 </td> <td>15:40:39</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB0W0-1 </td> <td>9/7 </td> <td>20:36:06</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB0W1-0 </td> <td>9/8 </td> <td>23:43:23</td> <td>FFs</td> <td>SB0W1-0 turned ON at 9/8 23:50:57* </td> </tr> 
<tr> <td>         </td> <td>9/8 </td> <td>23:46:18</td> <td>FFs</td> <td>SB0W1-0 turned ON at 9/8 23:50:57* </td> </tr> 
<tr> <td>         </td> <td>9/8 </td> <td>23:46:39</td> <td>FFs</td> <td>SB0W1-0 turned ON at 9/8 23:50:57* </td> </tr> 
<tr> <td>         </td> <td>9/8 </td> <td>23:46:56</td> <td>FFs</td> <td>SB0W1-0 turned ON at 9/8 23:50:57* </td> </tr> 
<tr> <td>         </td> <td>9/8 </td> <td>23:47:15</td> <td>FFs</td> <td>SB0W1-0 turned ON at 9/8 23:50:57* </td> </tr> 
<tr> <td> SB0WA-1 </td> <td>9/8 </td> <td>23:43:30</td> <td>00s</td> <td>External TRIP 9/8 23:39:59 </td> </tr> 
<tr> <td> SB0WA-2 </td> <td>9/8 </td> <td>23:43:47</td> <td>00s</td> <td>External TRIP 9/8 23:39:59 </td> </tr> 
<tr> <td> SB0WA-3 </td> <td>9/8 </td> <td>23:44:03</td> <td>00s</td> <td>External TRIP 9/8 23:39:59 </td> </tr> 
<tr> <td> SB0WA-4 </td> <td>9/8 </td> <td>23:44:20</td> <td>00s</td> <td>External TRIP 9/8 23:39:59 </td> </tr> 
<tr> <td> SB1W0-2 </td> <td>9/10</td> <td>06:13:14</td> <td>00s</td> <td>External TRIP 9/10 06:14:22 </td> </tr> 
<tr> <td>         </td> <td>9/10</td> <td>06:14:37</td> <td>00s</td> <td>External TRIP 9/10 06:14:22 </td> </tr> 
<tr> <td> SB1W8-1 </td> <td>9/8 </td> <td>23:46:18</td> <td>00s</td> <td>Software TRIP High DVDD L4 9/8 23:43:22  + 23:43:33 </td> </tr> 
<tr> <td> SB1W8-3 </td> <td>9/8 </td> <td>23:46:26</td> <td>00s</td> <td>Software TRIP High DVDD L4 9/8 23:43:22  + 23:43:33 </td> </tr> 
<tr> <td> SB1W8-4 </td> <td>9/8 </td> <td>23:46:32</td> <td>00s</td> <td>Software TRIP High DVDD L4 9/8 23:43:22  + 23:43:33 </td> </tr> 
<tr> <td> SB2W2-1 </td> <td>9/9 </td> <td>15:41:07</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB2W2-1 </td> <td>9/9 </td> <td>15:41:07</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB3W0-3 </td> <td>9/9 </td> <td>23:18:43</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/9 </td> <td>23:25:43</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB3W1-0 </td> <td>9/7 </td> <td>18:00:00</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> SB3W1-3 </td> <td>9/7 </td> <td>19:46:32</td> <td>00s</td> <td>Nothing </td> </tr> 
<tr> <td> SB3W5-1 </td> <td>9/8 </td> <td>13:00:10</td> <td>00s</td> <td>Nothing </td> </tr> 
<tr> <td> SB3W5-3 </td> <td>9/9 </td> <td>17:16:32</td> <td>00s</td> <td>Nothing </td> </tr> 
<tr> <td> IB0W3-2 </td> <td>9/7 </td> <td>17:27:32</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/8 </td> <td>13:51:40</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/8 </td> <td>13:52:06</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> IB5W0-3 </td> <td>9/9 </td> <td>17:16:31</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> IB5W1-4 </td> <td>9/8 </td> <td>12:58:14</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/8 </td> <td>14:17:06</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/9 </td> <td>18:58:14</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> IB5W2-1 </td> <td>9/7 </td> <td>20:01:14</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td> IB5W4-0 </td> <td>9/10</td> <td>01:07:17</td> <td>00s</td> <td>Nothing </td> </tr> 
<tr> <td> IB5W4-1 </td> <td>9/8 </td> <td>22:52:10</td> <td>FFs</td> <td>Nothing </td> </tr> 
<tr> <td>         </td> <td>9/10</td> <td>03:29:46</td> <td>FFs</td> <td>Nothing </td> </tr> 
</table> 
*No idea if it was OFF or STANDBY  
<!-- Author: SCN -->


<!-- Date: Tue Sep 11 13:27:51 2001 -->
Some work on SRC polling causing Bus Errors in the SCPU<BR> 
We have set up a test in the 2nd floor test crate, and  
have reproduced Bus Errors in the SCPU while polling on 
the SRC.  Right now we don't have a real clue of what is 
going on, but it looks like the SRC is throwing BERR  
for some reason.  We are now polling on the FFO in the same 
crate while the SCPU is reading out the VRB, to see if 
this gives bus errors.  Please do not disturb the test crate.
<!-- Author: SCN -->


<!-- Date: Tue Sep 11 16:03:14 2001 -->
<pre>Inspected the west side after ISL cooling work finished. All junction cards look sound. COT face clearance looks good. 
</pre>
<!-- Author: David and Matt -->


<!-- Date: Tue Sep 11 17:22:48 2001 -->
<pre>Andy and I measured the remote sense cables of SB2W4 and SB5W5: 
--------------------------------------------------------------- 
we didn't have the pinout, but if the connector (at the PS) is  
oriented like this: |\  then these are the resistances from  
                    | | top to bottom pairs: 
                    | | 
                    |/ 
 
SB2W4                       SB5W5 
=====                       ===== 
open                        open 
open                        open 
1100                        1200 
880                         1.1MOhm 
1200                        1200 
750                         1.1MOhm 
1200                        1200 
870                         1.1MOhm 
1200                        1200 
880                         1.1MOhm 
1200                        1200 
880 (0.9MOhm @ 2nd meas.)   1.1MOhm 
1.6MOhm                     13MOhm 
4MOhm                       14MOhm 
open                        open 
open                        open 
open                        open 
0.2Ohm                      0.2Ohm</pre>
<!-- Author: Petra -->


<!-- Date: Tue Sep 11 17:40:05 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>Run Plan foir next 2 days - please check if anything is forgotten 
 
1. ISL work is finished, cooling reestblished by Jim E. 
2. Petra and Andy have done the cable probing. 
3. Rob, Valeria, Matt will work until late on L00, ISL power supplies. 
   Request is being sent to ops managers for hall access Wednesday to 
   finish the work. 
2. Baggy goes up about 20:00.  PsiCo will page Mircea.  He and Eva 
   will cool the system done 5 deg/hour to -5 deg. 
3. Wednesday 16:00 search and secure 
4. Wednesday day - Rob, Matt, Valeria finish up with L00/ISL 
5. Wednesday morning - remove LOTO on SVX.  Andy will get SVX running 
   again. 
6. Once SVX is established again, Steve N., Colin, Anton work on x-mode 
7. Rob etal by definition finish ISL/LOO by 16:00. 
8. Wednesday late afternoon/evening. integrate new ISL layers. 
   Find stable integrated set. D-mode and X-mode calibrations. 
      Petra/Chris/Lester/Steve 
      (Petra can only stay until 6:30 or 7:30 so ask Lester/Steve 
           for later) 
9. Thursday morning - depends on beam conditions.  Present plan is for 
   shot setup Thursday PM.  get stable x-mode set, etc. 
 
</pre></td></tr></td></table>
<!-- Author: Jean, Andy -->


<!-- Date: Tue Sep 11 19:26:34 2001 -->
<pre>Configured L6 for bulkheads 1 and 4 to trip when turned on. 
L7 can now be run 
 
IB1W0  No bias adaptors 
IB1W1  empty 
IB1W2  empty 
IB1W3  No bias adaptors - new supply needs LIB test   
IB1W4  good 
IB1W5  good 
 
IB4W0  good 
IB4W1  good 
IB4W2  good 
IB4W3  empty 
IB4W4  good 
IB4W5  good 
</pre>
<!-- Author: herndon and napora -->
<!-- Comment: Wed Sep 12 14;42;38 comment by...Napora and Herndon -->
<p>Updated below.  IB1W2 is no longer empty, but needs load-box test.
<!-- Date: Wed Sep 12 11:30:21 2001 -->
On Mary's suggestion, I tossed a "FIB_CHIP_RESET (0x12)" command 
to the enabled DDRs just before clocking down the Initialization 
Stream.  I also took out the retry since it currently doesn't 
help.  I would like to test these out ASAP.
<!-- Author: SCN -->
<!-- Comment: Wed Sep 12 11;54;48 comment by...SCN -->
This code is now in effect <B>for b0fib00 only</B>.  Lets see if it
helps.  Of course, it will also take effect for any other
crates which get rebooted between now and then.


<!-- Date: Wed Sep 12 12:17:39 2001 -->
Just rebooted b0fib02 because it does not seem to have  
booted properly last time...<pre> 
-> i                                                                             
                                                                                 
  NAME        ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY  
---------- ------------ -------- --- ---------- -------- -------- ------- -----  
tLogTask   logTask        efbdc0   0 PEND         29d118   efbcf8       0     0  
tExcTask   excTask        efe738   0 PEND         29d118   efe660       0     0  
tShell     shell          ed2a20   1 READY        286de8   ed26a8       0     0  
tRlogind   rlogind        ed98c8   2 PEND         283424   ed9508       0     0  
tAioIoTask1aioIoTask      eee6a8  50 PEND         283898   eee600       0     0  
tAioIoTask0aioIoTask      ee74a0  50 PEND         283898   ee73f8       0     0  
tNetTask   netTask        edd0b8  50 PEND         283424   edd008       0     0  
tAioWait   aioWaitTask    ef58b0  51 PEND         283424   ef5758       0     0  
tPortmapd  portmapd       ed8338 100 PEND         283424   ed81c8      16     0  
value = 0 = 0x0                                                                  
-> reboot  
</pre> 
 
This means that it too will have a failed COLDSTART and 
the above code changes.                                                                     
<!-- Author: SCN -->


<!-- Date: Wed Sep 12 14:19:12 2001 -->
<pre>new cable measurements from ANdy and me about SB2W4 and SB5W5: 
 
this time we measured the resistance within one line between  
LV and sense cable, everything looked as expected apart from an open on both AVDD4 lines in SB5W5. 
 
during the next access we should run a new sense cable to these  
wedges and check that out.</pre>
<!-- Author: Petra -->


<!-- Date: Wed Sep 12 14:40:57 2001 -->
<p>An ugly three days for the PS guys. 
<ul> 
<li>Due to the problems with the new L00 flavor PSs they have all been removed for further testing. 
<li>Until the GUI situation is properly resolved the two Ersatz L00 (SVX flavor) PSs have been ejected from the backplane. 
</ul> 
On the good side: 
<ul> 
<li>Two new SVX PSs were installed in SB5W0 and SB5W11.  They have been tested, cabled, enabled and are ready for integration. 
<li>A second ISL PS was installed in IB1W2, but has not been load-box tested yet. 
<li><b>All</b> installed barrel 1 and 4 ISL power supplies have been jumpered and tested so that only layer 7 components can be powered.   
</ul>  
<!-- Author: Napora and Herndon -->



<!-- Date: Wed Sep 12 15:01:12 2001 -->
I changed some VRB code slightly so that  
Read Busys and Scan Busys get reported to Run Control  
at Halt-only half of it will be propogated to the Vrbs  
next time someone reboots.  It should do no damage-page me 
if it does...
<!-- Author: SCN -->


<!-- Date: Wed Sep 12 15:46:03 2001 -->
<pre>More on the PS GUI issue:  We had a choice: 
    a) old code with SVX style L00 PS but no spontaneous on 
       warnings 
    b) New code with L00 supplies and spontaneous on protection 
     
We ( Andy, Matt, Jean, Rob, Andrew) opted for b) so the SVX L00     supplies were pulled out 1".  
 
Andy has put the spontaneous on protection back into the  
SVX-L00 PS code but now he needs time to test it.  I suggested tomorrow AM. 
 </pre>
<!-- Author: Jean -->


<!-- Date: Wed Sep 12 19:29:16 2001 -->
<pre>Testing L7 ladders with intention of integrating them into run 
control. 
 
1) Test that L6 PS chan trips due to hardware short 
implemented by MH and RN. 
 
IB1W4 - ok 
IB1W5 - ok 
IB4W0 - ok 
IB4W1 - ok 
IB4W2 - ok 
IB4W4 - ok 
IB4W5 - ok 
 
2) Power to standby, init, verify bias settings, bias 
 
IB1W4 - ok 
IB1W5 - ok 
IB4W0 - ok 
IB4W1 - ok 
IB4W2 - does not init all HDI: AVDD, DVDD currents do not change. This was ok at time of JC connection (5/7), but had to be re-seated at least once. 
bund 
IB4W4 - ok 
IB4W5 - ok 
 
*Leakage current scale is uA.  Most channels drew &lt; 1uA, so 
verifying bias was not entirely possible. 
Some channels drew &gt; 1uA, however, indicating that at least some 
were gettting biased. 
 
**Could not take data due to VRB problems.  Petra & I attempted 
to fix the problem to no avail.  Steve N. notified. 
 
***PS GUI bug noticied.  Turn off IBXWY and IBXWY-1 will turn bias to standby.  Andrew I. notified.</pre>
<!-- Author: Chris Hill -->


<!-- Date: Wed Sep 12 21:58:15 2001 -->
<pre>There was a problem with turning ON power tonight. The problem 
has been resolved -- the SVX Interlock switch was OFF in the first 
floor. In the mean time the GUI was trying to bring power on in 
an infinite loop and therefore was frozen, I debugged and  
successfully tested this feature.</pre>
<!-- Author: Andrew -->


<!-- Date: Thu Sep 13 09:01:33 2001 -->
<pre>Found new ISL ladders are NOT in HWDB, contrary to reports. 
 
Could not power on IB0W1.  It spontaneously turns itself 
off.   
 
Managed to power to SBY all other wedges, they successfully 
initialized and were leftin SBY all night.</pre>
<!-- Author: ADF -->
<!-- Comment: Thu Sep 13 09;04;04 comment by...ADF -->
Symptoms of PS failure in IB0W1 are precisely the same as
Sept. 9's failure of SB4W9
<a href=
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=65&frame=2&anchor=19:33:52'>
Sept. 9th failure of SB4W9</a> 


<!-- Comment: Thu Sep 13 09;24;33 comment by...ADF -->
<pre>Only IB1W4 was entered into HWDB, and its FIB slot was not
set online.</pre>


<!-- Comment: Thu Sep 13 10;03;27 comment by...Petra -->
<pre>Chris just wrote that his tests were performed with the intention to put the ladders 
into the HDWDB, he never said he put them there; as he wrote we were 
not able to get any data out of them due to VRB problems!
</pre>
<!-- Date: Thu Sep 13 09:30:49 2001 -->
<pre>Removed IB0W1 from HWDB, took out HDI's 589 in Fib03 Slot 9 
Left in CAENvolts.dat</pre>
<!-- Author: ADF -->


<!-- Date: Thu Sep 13 09:39:00 2001 -->
<pre>Changing lookup table for the GUI-spy and cratematch.pl etc 
GUI-spy is running but the lookuptable to decode it needs a change. I'll put a new entry when this is in place. 
</pre>
<!-- Author: Saverio -->
<!-- Comment: Thu Sep 13 09;58;11 comment by...Saverio -->
<pre>The lookuptable for the new GUI (From Andy Hocker) is in place.
Switching back to the old GUI needs manual switch back to the old
GUI-spy AND to the old lookup_table.
./cratematch works again, all other scripts now need a flag to
tell which lookup table to use. This MAY (I don't know for shure)
include the voltage history plots.</pre>




<!-- Date: Thu Sep 13 10:16:51 2001 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-167&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-167  width='300' align='top'></td><td>Losses 09/10/01</a></td></tr></table>
<!-- Author: ADF -->
<!-- Comment: Thu Sep 13 11;17;44 comment by...ADF -->
<pre>This was during the hand knob-turning to find the loss limits in the beam angle scan just before dumping the beam.</pre>


<!-- Date: Thu Sep 13 11:19:08 2001 -->
<h3>Trying to get things running again</h3> 
<ul> 
<li> Started with the whole she-bang, found several wedges 
off and turned them on.  Found ISL had only IB1W4 active in the 
hdwdb. 
<li> Had to disable readback of initialization on SB0W1-2. 
Currents look ok.  New Fib Initialization does no harm it seems. 
Whether it helps or not remains to be seen. 
<li> Tried to run, continual problems with Slot 13 of b0svx08, 
where it seems to get hosed by the SRC-reports the wrong 
module ID, reports that it is in Calorimeter mode, etc. 
I believe this VRB services IB1W4. 
<li> Dave Stuart calls up and says he is worried that the GUI 
is not trustworthy-so I abandon ISL testing until he is  
satisfied it is safe. 
<li> Now running with just SVXII fib crates-getting reformatter 
errors claiming an "imposter" FIB ID.   
</ul> 
TBC...
<!-- Author: SCN -->
<!-- Comment: Thu Sep 13 14;08;51 comment by...SCN -->
Imposter FIB ID was tracked down to (not surprising I guess)
SB0W1-2.  IT wasn't wrong all the time, just occaisionally.
I took this ladder out.


<!-- Date: Thu Sep 13 14:19:09 2001 -->
Ran for 20 kEvents, SVXII.  Now rebooting Vrb crates to 
add in "Timeout Messages"<ul> 
<li> Vrbs who are <I>READ BUSY</I> 
at <B>HALT</B> time will be reported to the Error Monitor 
in a message which looks like<pre> 
Silicon Timeout !DONE Slots: x y z 
</pre> 
<li>Vrbs who are <I>SCAN BUSY</I> at <B>HALT</B> time will be 
reported to the Error Monitor in a message which looks like<pre> 
Silicon Timeout BUSY Slots: x y z</pre> 
<P> 
When done with reboot, will give Silicon to Level 3 to try reformatter and SCPU code.
<!-- Author: SCN -->
<!-- Comment: Thu Sep 13 14;19;39 comment by...HTML Screwup -->
</ul>


<!-- Date: Thu Sep 13 14:59:24 2001 -->
<pre>Message from David Stuart on the p/n gain situation 
 
Here is how I think we should proceed on the p/n gain question. 
  
First, we should take enough data in the current configuration to settle 
after the access. 
  
Then, we should change the n-side configuration to Tony's suggested 
values, and collect enough data to measure that gain change. 
  
Then, we should put the p-side back to the previous nominal to measure 
that "diagonal setup" gain, and take a couple runs. 
  
Then, we should understand the results and track down any culprits. I.e. 
if we find a bug, it is better to fix it than to change the settings to 
compensate for it. Either way, such a fix should be done all at once in a 
controlled manner rather than piecemeal. 
                                                                                </pre>
<!-- Author: Jean for David S. -->


<!-- Date: Thu Sep 13 15:28:26 2001 -->
<a href= 
'/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=66&frame=2&anchor=19:29:16'> 
The bug of the PS GUI </a> , mentioned by Chris Hill, turned out to be not reproducable. The Saverio spy program was not running yesterday, so that we are not able to see, what exactly happened.
<!-- Author: Andrew -->


<!-- Date: Thu Sep 13 15:30:35 2001 -->
<pre>Chris and Andrew tried to reproduce the GUI problem from last night but were unable to. 
 
Saverio's program was not spying on the GUI last night, so we have no records from last night, but it is running now. 
 
So, I think it is OK to turn ISL back on now. 
</pre>
<!-- Author: David -->


<!-- Date: Thu Sep 13 16:18:18 2001 -->
<pre>Set FIB01 Slot 09 Offline Flag to 0, taking out 
IB0W2 and IB0W3.  This is because b0svx08 slot 13 
gave trouble.</pre>
<!-- Author: ADF -->


<!-- Date: Thu Sep 13 16:54:23 2001 -->
<pre>Removed Fib01 Slot 11 (IB1W4, IB1W5) from HWDB. 
 
ISL Configuration is now same as before access, 
except IB0W1 (can't turn it on) and IB0W2/IB0W3 
(problem with VRB b0svx08 Slot 13)</pre>
<!-- Author: ADF -->


<!-- Date: Thu Sep 13 16:56:21 2001 -->
<pre>Plan: 
 
1. Get old ISL wedges powered / initialized 
2. Take D mode calibrations  
3. Take data integrated with CDF 
4. Add in new ISL wedges 
5. Take D mode calibrations with them 
6. Take data integrated 
7. Do Tony tests for gain</pre>
<!-- Author: Jean / ADF -->


<!-- Date: Thu Sep 13 18:36:52 2001 -->
<pre>I integrated the old ISL set. Switched ISL 5V enable on.  
IB1W3  happened to be still online, took it offline. 
Getting some RF errors from SVX wedges. 
Got 1 BTO with no message in the errorlogger - Stev? 
</pre>
<!-- Author: Petra -->


<!-- Date: Thu Sep 13 18:47:54 2001 -->
<pre>taking D-mode calibrations now with "old" set of SVX and ISL</pre>
<!-- Author: Petra -->
<!-- Comment: Thu Sep 13 19;29;32 comment by...Petra -->
<pre>DPS on: 126638 (0x1eeae)
DPS off: 126641 (0x1eeb1)

some beam in the machine (losses relatively low: spikes up to lostp&lt;12kHz)
no luminosity

</pre>
<!-- Date: Thu Sep 13 18:51:01 2001 -->
<pre>now the FIBs coldstart after the VRBs are finished, that is good,  
but they also wait for L3 to finish and that takes forever.  
I would suggest to send the signals to the FIBs before L3 starts/finishs!</pre>
<!-- Author: Petra -->
<!-- Comment: Thu Sep 13 18;59;27 comment by...Petra -->
<pre>It's getting interesting: when I do a coldstart and do a config. by 
hand to the FIBs after the VRBs are ready but before L3 is done, 
they turn green in the little toggle window and finally coldstart 
finishs. But after that, when I want to activate the run, the FIBs 
tell me that this statechange is not possible and they turn red... (actually I only observed that for the SVX FIBs...)</pre>



<!-- Date: Thu Sep 13 19:31:28 2001 -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>I got two IMPOSSIBLE one-liners! External trips in the following  
ladders (they only tripped these ladders, not the full wedges: 
 
SB2W1L1 DVDD 
SB3W1L3 AVDD 
 
they did not happen at the same time, but each happened when we  
were not running for a few minutes I believe!</pre></td></tr></td></table>
<!-- Author: Petra -->


<!-- Date: Thu Sep 13 23:41:10 2001 -->
<pre>Entered IB4W0, IB4W1, IB4W2, IB4W4, and IB4W5 into 
HWDB.  L0, L2, L4 in all cases.  IB1W4 and IB1W5  
were not entered due to VRB problems (See above.)</pre>
<!-- Author: ADF -->


<!-- Date: Fri Sep 14 01:52:31 2001 -->
<pre>Could not turn on ISL (same problem with spontaneous 
offs).  Decide to run integrated with only SVX FIBS</pre>
<!-- Author: ADF -->
<!-- Comment: Fri Sep 14 09;24;09 comment by...Petra -->
<table border=0><td><tr><td bgcolor=#e0e030><pre>there is no entry that somebody turned ISL off ! I left it in SB and running (the old wedges)!</pre></td></tr></td></table>
<!-- Comment: Fri Sep 14 11;17;21 comment by...ADF -->
<pre>Some slight confusion, my fault.  I wanted to turn on
ISL new wedges.  ISL old wedges were already SBY, so
I decided to turn ISL OFF, then back to SBY, to bring the
new wedges on (reading new powerset.dat).  However, after
turning it OFF, they would not come back on to SBY!  That
was the cryptic / hidden meaning of the original log
entry.</pre>
<!-- Date: Fri Sep 14 06:17:01 2001 -->
<pre>SB3W3 PC tripped off on an external trip.  However,  
the trip was not reported anywhere in the GUI! 
It somehow was reported to iFix, though, giving a 
tweety-bird alarm.  Juan-Pablo found the trip by 
going one-by-one through all the wedges. 
 
This is bad. 
 
Anyway, shot setup is now, so we are on standby and out of  
the run.  Next priority is to try to even just 
turn on the ISL, which I could not manage last night. 
Then priority would be to actually run the ISL, 
presumably unbiased since it is now shot setup.</pre>
<!-- Author: ADF -->


<!-- Date: Fri Sep 14 09:08:51 2001 -->
<pre>Removed IB4W2 from HWDB--shouldn't have put it in in the 
first place.  It does not initialize. 
 
Now ISL turns on, and everything initializes!</pre>
<!-- Author: ADF -->



<!-- Date: Fri Sep 14 10:43:24 2001 -->
<table><tr><td><a href=/elog/notebooks/silicon/Fri_Sep_14_2001_104314.ps align=top><img src=/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-173  align='top'></td><td>Residuals vs x-position with old and new geometry</a></td></tr></table>
<!-- Author: Amit -->


<!-- Date: Fri Sep 14 10:44:41 2001 -->
<center><a href='/elog/notebooks/silicon/Fri_Sep_14_2001_104314.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-173' ></a><a href='/elog/notebooks/silicon/Fri_Sep_14_2001_104354.ps'><img src='/cgi/elog/det-system-elog.pl?nb=silicon&action=view&page=-175' ></a></center>
<!-- Author: Amit -->


<!-- Date: Fri Sep 14 11:12:43 2001 -->
<pre> Steve "Eagle-Eye" Nahn noticed that the ISL central 
enable had tripped off on a temperature trip. 
David Stuart plotted the temperature on the 
central barrel RTD's, and saw that the L6 central temp 
went up when the new L7 ladders were powered (first 
time). The temp went straight up to 20 with no sign 
of leveling out; 20 is when Steve noticed it.   
 
 I turned the ISL OFF (everything).  We spoke with Mircea. 
The plan is to change the PLC so that when any Central 
barrel trips on the temperature, all 5V enables in 
that half of ISL are disabled.  This will take time. 
 
 On the iFix front, there IS an alarm which sounds when 
the RTD's reach 25.  This will be lowered by Mircea to 
trip at 20. 
 
 In the meantime, I removed all the new L7 ISL ladders from the 
HWDB (set ONLINE FLAGS for FIBs off), and x'ed them 
all out from caenvolts.dat.  This means from HWDB, 
turned off IB4W(0,1,2,4,5); in caenvolts.dat, x'ed out 
HDI's 0,2,4 for the same ladders, plus IB1W4 and IB1W5. 
 
 David Stuart would like to turn on, briefly, and under 
a careful watch, IB1W4 and IB1W5, for a run to get 
data so offline can check L7 reconstruction.  This will 
be later. 
 
 
</pre>
<!-- Author: ADF -->



<!-- Date: Fri Sep 14 11:37:12 2001 -->
<pre>Turned silicon to SBY (SVX + Old ISL)</pre>
<!-- Author: ADF -->


<!-- Date: Fri Sep 14 12:20:33 2001 -->
<pre>Going to shortly interrupt spying to update the program</pre>
<!-- Author: Saverio -->
<!-- Comment: Fri Sep 14 12;47;24 comment by...Saverio -->
<pre>GUI spy back in service.
few short interruptions of a few seconds each</pre>


<!-- Date: Fri Sep 14 12:52:39 2001 -->
<pre>Turned SVX +Old ISL ON. 
 
50% reformatter errors reported, along with a 
mystery CDF global alarm.  This alarm had the 
"Alarm: SVX" voice, but the SVX did not turn 
red.  Restarted the run. 
 
Reformatter errors were on SB4W1, where all 4 layers 
read out 0x0000000 for the header.  The ladder was 
confirmed powered ON at the time of the errors, by me.</pre>
<!-- Author: ADF -->