Difference: DATAANALYSIS2008 (9 vs. 10)

Revision 102008-07-11 - unknown

Line: 1 to 1
 
META TOPICPARENT name="VeloTestbeam2007"

Testbeam 2008 - Data Analysis

Line: 57 to 57
  11/July/2008: Suggested solution to PCN problem (thanks to Lars!).
Changed:
<
<
Lars points out that the PCN# as readout from the TELL1 is from the beetle emulation i.e. is not necessarily forced (at this time) to be the same as thehardware number in the Beetles.
>
>
Lars points out that the PCN# as readout from the TELL1 is from the beetle emulation i.e. is not necessarily forced (at this time) to be the same as thehardware number in the Beetles.
 
Changed:
<
<
-- KarolHennessy - 10 Jul 2008
>
>
The numbers we were using from Vetra were the FEM PCN which is decoded on the Tell1 and were comparing them to the numbers we got from the header ADCs. We thought the FEM and the module beetles have the same PCNs but that's not necessarily the case. And the Tell1s are reset at slightly different times so the FEM pcns are different but the module beetles get their pcn from only one Tell1 (Tell8 which sends all the control signals) so they should be the same for both modules (and this is confirmed in the data).

So we see a difference in FEM pcns which is due to a delay (from ssh-ing from richdaq to the two Tell1s and configuring) ,
and we see the same pcn on the module Beetles because they receive the same signal at the same time from Tell8.
 
Added:
>
>
-- KarolHennessy - 10 Jul 2008
 
META FILEATTACHMENT attachment="p1v1p2.PNG" attr="" comment="" date="1215696622" name="p1v1p2.PNG" path="p1v1p2.PNG" size="3033" stream="p1v1p2.PNG" user="Main.ThemisBowcock" version="1"
 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback