Minutes of the May 5, 2005 US ROD meeting

Follow up on action items

  1. Jim has not yet started talking to JT about scripting the
    comparison between ARCS and rod data.
    Steve Jaditz working on it now.

  2. Opens at FNAL can be seen OK, need to re-check UCSB
    UCSB: at warm T OK, but common mode noise still high.
    Still need to check low T.
    News on noise at UCSB: much better on SR after some OFEDS
    have been switched to different VME crate.

  3. UCSB: Sort out problem with bad lemo.
    Only affects DS rod, so not terribly urgent, but should be followed up.
    Can't seem to find what problem is.

  4. UCSB: DS rod bad noise. But using modules that went through severe cycles.
    Need to put new modules on it and retest.
    On back-burner until modules become available.
    In the meantime take a couple of these modules off and see what they look like on ARCS.
    Not yet.

  5. UCSB: Redundancy test. Getting errors. Check with Ryan
    Ryan sees same thing as UCSB.
    Guido checked and claims we are seeing software feature.
    Case closed.

  6. UCSB: Tests of rod 178 (header-error rod from FNAL) continue. Swap
    module that gives errors to try to correlate with either rod or module.
    Put this on back-burner now that production has started.

  7. Lt SW bug that causes bad pulse shape. Valeri on it.
    No news

  8. DS rod with 3rd cooling plate runs cooler, but T ~ 40 C on hybrid,
    T ~ 55 on DCU. Sent mail to experts for advice.
    Mark Raymond says that APV within specs of process -- although no real data on it.
    Experts say DCU is OK too.

  9. FNAL: Tested bunch of new HPK rods in SR. Two out of six have broken or shorted
    termistor. Strange because Lenny says that these are chcked on rod frame.
    Possibilities: bad check on rod frame, or bad connection through flat cable, or bad DCU on hybrid.
    Check module fast-test
    Probe with multimeter
    No news

  10. UCSB needs to to implement connectivity test in SR.

UCSB

Twenty rods made and tested in SR. 1 solid I2C errors, 3 sporadic.
Always on position 6. Connectivity test not run.

Six rods went into freezer for cold-cycling. One more showed I2C errors.

Will send rod with solid I2C errros to CERN.

Stopped rod production.

FNAL

Made 4 production rods. 3 tested in SR. 2 have I2C errors.
Position 6, but not always same APV.
Errors show up on connectivity test first.

Is it module or rod?

Are these I2C errors new?
UCSB saw them a long time ago, but not more recently (before start of production).
FNAL always had them at some level, but focus was on header errors.
It should be noted that before start of production FNAL exercised the
system more thoroughly and with more rods than UCSB.

If rod production stops, FNAL will be running out of plates soon.
UCSB has same problem, thinking of making a bunch of simpler plates for storage.