Log entry time 16:21:42 on May 09, 2011

Entry number 358722

This entry is a followup to: 358715

I checked several terms to make sure that the R-HRS timing works 
properly: 
 
1, L1A0 .vs. Retiming strobe signal: L1A comes 50ns earlier than strobe 
signal, which is still correct as long as it comes before strobe. 
 
2,RT0 .vs. Retiming strobe signal: I triggered on strobe signal and look 
at the RT0 which will sent into TM to generate ADC gate and TDC STOP. I 
can see that time of RT0 is determined by strobe signal. (If I 
disconnect the strobe signal from RT module, RT0 signal is jumping 
around)  
 
3, TDC STOP signal .vs. S2m TDC: S2m TDC signals come ~700ns before TDC 
STOP. The value in my notebook shows that the difference is about 740ns, 
which is not very big differet but since we now see the S1&S2m TDCs come 
60ns earlier so we should notice this change.  
 
4, S1 ADC signal .vs. ADC gates (the same as TDC STOP): My previous 
calculation shows that if taking into account time difference from 
signals to scope and signals to fast bus, ADC signal should be ~150ns 
later than ADC gate from the scope (hence 60ns late from the fast bus), 
but now I can see that the ADC signal comes ~220ns later than ADC gate. 
Since delay values of ADC signals are fixed by long cables, ADC gate (or 
TDC stop) comes ~70ns earlier than what I recorded before.  
 
5, TDC STOP .vs. Retiming strobe signal: If I trigger on strobe signal, 
most of the TDC STOP signals come earlier than strobe signal, which 
should be incorrect since retimed-L1A0 (RT0) has to go through a TM 
module to generate TDC STOP (and ADC gate). As I remember, signals going 
thought RT module(~30ns) and TM module would cause more than 100ns 
delay. 
 
 
Summary: I don't have an idea that what is going on. We have a bad TM 
module?