• Main INDEX
  • Monthly INDEX
  • PREV
  • NEXT

    User name Michaels/Camsonne

    Log entry time 11:35:34 on August 9,2006

    Entry number 178626

    This entry is a followup to: 178621

    Followups:

    keyword=clocks and helicity plugged in

    We took access and plugged in the following signals:

    105 kHz clock was plugged into EDTM scaler (slot 9) into 5th chan
    and also into slot 7 in 17th chan. These appear in this order
    in the TS11 readout at the 4th & 5th word after the old clock
    signal. So they are the last two in the readout if there are
    no scalers in that event.

    Noted that the fanout for clock to ROC3,4 was different from TS11
    and had a cable that led nowhere (possible reflection glitch).
    Fixed that. One of the new copies to TS11 comes from the same
    fanout that serves ROC3,4. It is the 2nd to last of the copies.
    The last copy comes directly from the clock unit.

    We also plugged in the helicity level to an ADC in ROC3 and ROC4.
    ROC3: slot 23 chan 48
    ROC4: slot 21 chan 48
    For convenience here is an event dump of TS11 for non-scaler event.
0x00000009  -- event type
0x00000030  -- TIR data (helicity,gate,QRT)
0x0006747c  -- 105 kHz clock
0x00000003  -- Counter
0x00002157  -- vxWorks clock
0x00000001  -- helicity bit (TIR & 0x10)>>4
0x0006747c  -- new redundant 105 kHz clock
0x0006747f  -- new redundant 105 kHz clock
0xcafe0000  -- a marker
0x00000003  -- event number
0xfb0b0000  -- a marker (becomes 0xfb0b0002 if scalers follow)