<!-- Title: 13:21:52  Tue Jun 15 2004 -->
<!-- Crewchief: Pulsar folks -->
<!-- Op1: &nbsp; -->
<!-- Op2: &nbsp; -->
<!-- Op3: &nbsp; -->
<!-- Op4: &nbsp; -->
<!-- Op5: &nbsp; -->
<!-- Op6: &nbsp; -->
<!-- Notes: -->
Start a new page after the big Pulsar meeting on June 11, 04. 
Pulsar production storm is over. VME readout migration (to new 
readout) is finally getting close to be finished...  
<a href= 
"http://hep.uchicago.edu/~thliu/projects/Pulsar/"> Pulsar web page </a> can be found here. Talks at big Pulsar meeting 
on June 11th can be found: 
 
<a href= 
"http://hep.uchicago.edu/~thliu/projects/Pulsar/L2_upgrade_meeting.html"> here</a>.


<!-- Date: Tue Jun 15 13:53:22 2004 -->
<pre>two boards which had problem with SVT hold line during 
production testing were sent to HR by Burkard to replace 
the LVDS/TTL chip. I checked the hold line again after 
the chip is replaced at HR, and now both of them work. 
(board# 2121, and 2154). 
 
We have another one, board#88 (or 2146) used for SVT road warrior, which had problem with SVT hold line. We will need to replace the chip as well. At this point, I don't know what causing the hold line problem on this board. The hold line sometimes oscillate when the long cable is unplgged from upstream.... but the hold line works when the cable is fully plugged in.</pre>
<!-- Author: Ted -->


<!-- Date: Fri Jun 18 18:17:17 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-105&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-105  width='300' align='top'></a></td><td>different number of clusters through fibers in the same event</td></tr></table>
<!-- Author: vadim -->
<!-- Comment: Fri Jun 18 18;21;09 comment by...vadim -->
<pre>more fun with clist input stage ...(!!!!)

LVDS-8 and HOTLINK-8 (ignore the names they are irrelevant) show the HSC for fibers 2 and 3 in the event. Fiber 2 sees 5 clusters while fiber 3 sees only 4. This explains why the slink part of the clist firmware bombs out. 

I don't undersntad how we did not see such events in the input DAQ. We ran over ~500000 total. We have seen two or three instances when the simulation and the number of clusters in TP2D disagree. However, they were consistent throughout different fibers. Unless such events are not readout someway. 

Problem of the week.</pre>


<!-- Date: Tue Jun 22 16:26:51 2004 -->
<pre>while trying to make sense some of the recent data with 
Pulsar SVT Rx with VTM timing measurements, I decided 
to look on scope how the VTM signals look like wrt L1A. 
the assumption of this timing measurement is that for 
every L1A, there is a correspong VTM pulse, leading 
edge indicates the arrival time of SVX data and trailing 
edge indicates the end of SVX data for this event and 
for a given wedge. 
Since there is no buffer number coming with VTM signal, we  
rely on the number of VTM pulses (wrt number of L1As) to  
keep track of the buffer numbers. This was 
verified with a VTM signal coming from SVX test crate  
setup by Steve Nahn. And I have checked that the timing 
data from Pulsar SVT Rx makes perfect sense (Shawn has run 
over those data). now we have the VTM signal directly coming 
from one of the SVT crate, and I couldn't make sense of  
the timing data anymore.  looking on scope, that assumption 
doesn't seem to be true. there are cases where for a given L1A, 
there seem to be more than one VTM pulses... 
will email Steve Nahn about this. will post a few 
screen capture below.</pre>
<!-- Author: Ted -->
<!-- Comment: Tue Jun 22 17;25;05 comment by...Ted -->
<pre>one way to explain all these events is that the missing
L1As are due to sampling rate of the scope. I tried to
zoom in to make sure the scope catch every L1A, but then
cannot see much of the history... need a better setup to
double check this... will do this later as I am still sick.</pre>
<!-- Date: Tue Jun 22 16:28:38 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-106&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-106  width='300' align='top'></a></td><td>the top trace is L1A (picked up from the back of crate,  
pin A12), bottom trace is the VTM signal before it goes 
into Pulsar Aux card. Note that it looks like there are 
three VTM pulses after the first L1A.</td></tr></table>
<!-- Author: Ted -->


<!-- Date: Tue Jun 22 16:33:01 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-108&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-108  width='300' align='top'></a></td><td>another one. there are two VTM pulses after the first 
L1A. the time between the first L1A to the first 
VTM pulse is about 9 us, consistent with the expectation 
that the first VTM pulse belongs to the first L1A (not earlier one).</td></tr></table>
<!-- Author: Ted -->


<!-- Date: Tue Jun 22 16:34:47 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-109&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-109  width='300' align='top'></a></td><td>another case, with more L1As in the window. here it 
seems to be clear that there are two VTM pulses 
after the fourth L1A.</td></tr></table>
<!-- Author: Ted -->


<!-- Date: Tue Jun 22 16:35:27 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-110&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-110  width='300' align='top'></a></td><td>one more example.</td></tr></table>
<!-- Author: Ted -->


<!-- Date: Tue Jun 22 16:36:56 2004 -->
<table><tr><td><a href=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-111&button=yes target='xxx' onclick='jswindow()'; align=top><img src=/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-111  width='300' align='top'></a></td><td>here is an interesting case where there are 4 L1As close 
in time, and there are four VTM pulses... in this case, 
it looks ok. but it is interesting to see the timing 
of each pulse.</td></tr></table>
<!-- Author: Ted -->



<!-- Date: Thu Jun 24 08:07:50 2004 -->
I spent a little time addressing Ted's quandry. I compared the 
SVT version of VTM DAV (<font color=green>the green trace </font>) with the SVXII version,(<font color=purple>the purple trace </font>) using the teststand crate FIB as a source, connected to the SVXII SRC.  Later, I added the FIB L1A (<font color=yellow>the yellow trace </font>).  Essentially I proved to myself that Ted's  
quandry is an issue of Scope resolution, and have the pictures to 
convince you too
<!-- Author: SCN -->


<!-- Date: Thu Jun 24 08:10:22 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-112&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-112' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-113&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-113' width='300'></a></center>
<!-- Author: SCN -->
<!-- Comment: Thu Jun 24 08;12;55 comment by...SCN -->
Here is just a comparison of SVX vs SVT, on a fairly long time scale.  On the left, you see two mismatches, but the SVX signal is
very short (32 * 20 nS).  On the right, I increased the width of
the SVX signal by a factor of 7.5, and the mismatches go away.  I b elieve Ted was having some of the same problems.  So I believe both VTMs are working the same way.


<!-- Date: Thu Jun 24 08:15:15 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-114&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-114' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-115&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-115' width='300'></a></center>
<!-- Author: SCN -->
<!-- Comment: Thu Jun 24 08;17;01 comment by...SCN -->
Here's just some more examples of the two VTMs agreeing.  I triggered on both the SVX VTM (left) and the SVT VTM (right).  No
disagreements seen (One could make a stronger statement with a Logic Analyzer, but I don't see the need).


<!-- Date: Thu Jun 24 08:19:36 2004 -->
<center><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-116&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-116' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-117&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-117' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-118&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-118' width='300'></a><a href='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-119&button=yes' target='xxx' onclick='jswindow()'><img src='/cgi/elog/det-system-elog.pl?nb=l2upgrade&action=view&page=-119' width='300'></a></center>
<!-- Author: SCN -->
<!-- Comment: Thu Jun 24 08;33;03 comment by...SCN -->
Now I added <font color=yellow>L1A</font> (picked off from the FIB backplane), but notice my sample rate is 100 MS/sec which is 20x that of Teds pictures.  With this in place, I saw no missing L1A triggering on SVT VTM DAV, nor any extra SVT VTM DAV triggering on L1A.  So I think it is all good.  Again, a logic analyzer with suitable depth/resolution could
make a stronger statement (requiring some pretty kludgy cable adaptation) but I don't think it is needed. 

<!-- Comment: Thu Jun 24 15;34;40 comment by...Ted -->
<pre>Steve:

 this is very good. looks like the problem with recent data
is most likely due to the recent VME readout code changes,
and possible also the offline software compatibility...
will look into this when i come back.</pre>


<!-- Date: Thu Jun 24 15:35:16 2004 -->
<pre>Update of Pulsars in the Level2 Pulsar crate: 
 
now all boards have a header word in Control output DAQ RAM  
I took a short run in standalone with the software event builder, 
that's fine. I requested Cosmic/L2Torture after the current  
store. This will give us an estimate of the readoutime, probably  
we will have to turn some DAQ buffers off, before we go into beam . 
 
  
here the current card editor setup  
 
run 184378 (the sevb test run): 
 
                fiber    Ctrl    Ctrl   DataIO1 DataIO1 DataIO2 DataIO2 board 
         Slot   nchan    Output  DAQ 2    DAQ 1   DAQ 2   DAQ 1   DAQ 2  ROL 
Muon:       5  :   1   :   -1  :   -1  :   256 :    0  :   256 :    0  :  0   
RECES:      7  :   1   :   21  :    0  :    16 :    0  :    16 :    0  :  0  
SVT:        9  :   1   :   -1  :   -1  :    -1 :    0  :     0 :    0  :  0  
Cluster:   14  :   1   :    0  :    0  :     0 :    0  :    48 :   -1  :  0  
Merger:    21  :   1   :   -1  :    0  :    -1 :   -1  :    -1 :   -1  :  0  
 
 
header  words as read found in TP2D bank  
as first words of card n*6 (with n=0,1,2,3,4,5,...) 
 
    2b020043     Muon haeder word 
    2f024043     RECES header word 
    2e022043     SVT header word 
           0     Cluster header word (just empty for now) 
    2f018043     Slink Merger header 
 
used decoding: 
  bit ( 7: 0) bunch counter  happens to be bunch cross 0x43 in this event 
  bit (18:13) board serial number 
  bit (31:23) board type 2f0..... -&gt; 94: Merger Rx (also used on RECES)* 
                         2b0..... -&gt; 86: Muon/XTRP/L1 Rx IIb 
                         2e0..... -&gt; 92: SVT Rx 
 
* the RECES Rx board Control FPGA uses the same firmware as for 
  the SlinkMerger   
 
 
 
the relevant parts of an dump of the TP2D bank, showing the 
header words "in situ": 
 
found TP2Ddescribed:  for event=1 in run 184378 
         0           1           1 
         1           3           3 
         2         3c3         963 
         3          1e          30  # blocks (=5*6) 
         4          20          32  1 1 (=Muon Rx Pusar) 
         5          52          82  2 
         6          58          88  3 
         7         158         344  4 
         8         158         344  5 
         9         258         600  6 
        10         258         600  1 2 (=Reces Rx Pulsar) 
        11         26d         621  2 
        12         26d         621  3 
        13         27d         637  4 
        14         27d         637  5 
        15         28d         653  6 
        16         28d         653  1 3 (=SVT Rx Pulsar) 
        17         2a9         681  2 
        18         2c1         705  3 
        19         2e0         736  4 
        20         2e0         736  5 
        21         2e0         736  6 
        22         2e0         736  1 4 (=Cluster Rx Pulsar) 
        23         2e1         737  2 
        24         2e1         737  3 
        25         2e1         737  4 
        26         2e1         737  5 
        27         311         785  6 
        28         346         838  1 5 (= Slink Merger) 
        29         366         870  2 
        30         366         870  3 
        31         390         912  4 
        32         3a5         933  5 
        33         3a5         933  6  
        34         3c0         960  end of last card 
        35    2b020043   721551427  Muon haeder word 
         : 
       603    2f024043   788676675  RECES header word 
         :     
       656    2e022043   771891267  SVT header word 
         :                         
       739           0           0  Cluster header word (just empty for now) 
         : 
       841    2f018043   788627523  Slink Merger header 
</pre>
<!-- Author: Burkard -->


<!-- Date: Thu Jun 24 23:58:48 2004 -->
<pre>tonight I took some L2 Torture and Cosmic runs  in different setups for the  readout of 5 board. 
 
Muon, Reces, SVT, Cluster, Merger. 
 
the Merger inputs record the Muon, Reces and SVT output, 
the Merger merges Muon and Reces, the Merger output is recorded by the Slink input on the SVT Rs board  
 
 
 
 
TeV studie with some beam in the machine, need to play a bit with presecales 
 
 
run 184381 L2Torture[16,466,444] 
 
coldstart: i: slot: channel : ctrl1: ctrl2 : dataio1_1 : dataio1_2 : dataio2_1 : dataio2_2: pulsar_rol 
         0:   5   :   1   :   -1   :   -1   :   256   :   0   :   256   :   0   :0 
         1:   7   :   1   :   21   :   0   :   16   :   0   :   16   :   0   :0 
         2:   9   :   1   :   -1   :   -1   :   -1   :   0   :   0   :   0   :0 
         3:   14   :   1   :   0   :   0   :   48   :   -1   :   48   :   -1   :0 
         4:   21   :   1   :   -1   :   0   :   -1   :   -1   :   0   :   -1   :0 
 
readout time: 1.2 ms 
reformatter errors: 0 
 
184384  nochamal w/o beam in the machine 
 
 
disable RECES and Slink Merger fiber inputs 
 
run 184389: 
coldstart: i: slot: channel : ctrl1: ctrl2 : dataio1_1 : dataio1_2 : dataio2_1 : dataio2_2: pulsar_rol 
         0:   5   :   1   :   -1   :   -1   :   256   :   0   :   256   :   0   :0 
         1:   7   :   1   :   21   :   0   :   0   :   0   :   0   :   0   :0 
         2:   9   :   1   :   -1   :   -1   :   -1   :   0   :   0   :   0   :0 
         3:   14   :   1   :   0   :   0   :   48   :   -1   :   48   :   -1   :0 
         4:   21   :   1   :   -1   :   0   :   0   :   0   :   0   :   0   :0 
 
readout time: 1.1 ms (just a little bit better) 
 
 
try board level readoutlist 
run 184390 
 
coldstart: i: slot: channel : ctrl1: ctrl2 : dataio1_1 : dataio1_2 : dataio2_1 : dataio2_2: pulsar_rol 
         0:   5   :   1   :   -1   :   -1   :   256   :   0   :   256   :   0   :7 
         1:   7   :   1   :   21   :   0   :   16   :   0   :   16   :   0   :7 
         2:   9   :   1   :   -1   :   -1   :   -1   :   0   :   0   :   0   :0 
         3:   14   :   1   :   0   :   0   :   48   :   -1   :   48   :   -1   :0 
         4:   21   :   1   :   -1   :   0   :   -1   :   -1   :   0   :   -1   :0 
 
readout time 0.6 ms 
 
same setup cosmic 
 
run 184391 
 
</pre>
<!-- Author: Burkard -->