1 / 3

GLAST Large Area Telescope: Tracker Subsystem WBS 4.1.4 MRB Concerning NCR 107 Robert Johnson

Gamma-ray Large Area Space Telescope. GLAST Large Area Telescope: Tracker Subsystem WBS 4.1.4 MRB Concerning NCR 107 Robert Johnson Santa Cruz Institute for Particle Physics University of California at Santa Cruz Tracker Subsystem Manager rjohnson@scipp.ucsc.edu. NCR 107.

pillan
Download Presentation

GLAST Large Area Telescope: Tracker Subsystem WBS 4.1.4 MRB Concerning NCR 107 Robert Johnson

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Gamma-ray Large Area Space Telescope GLAST Large Area Telescope: Tracker Subsystem WBS 4.1.4 MRB Concerning NCR 107 Robert Johnson Santa Cruz Institute for Particle Physics University of California at Santa Cruz Tracker Subsystem Manager rjohnson@scipp.ucsc.edu

  2. NCR 107 • Test failures on two MCMs at +60C. • MCM Serial Numbers 366 and 592 • Nonconformance: both MCMs had some event-data (from charge injection) read-back errors only when reading to the right-hand side and only in the +60C test (they were fine at -30C and 25C). • We found that the errors from SN-366 went away if the VDD voltage is raised to 2.65V, but the errors from SN-592 did not. • We tried some other relevant temperatures as follows: • Tracker Acceptance Test Limit: • 35C: Both function perfectly. • Tracker Qualification Limit: • 50C SN-366 functions perfectly but SN-592 has errors.

  3. Root Cause, etc., etc. • Suspected root cause: • no good ideas so far. • The MCMs are in burn-in and have not been studied any further. • Impact to inventory: minimal to worrisome, depending on how often it recurs (so far 2 out of 48 flight boards, no preproduction boards). • Schedule impact: none so far. • Recommended action: • Complete burn-in and final test on these units. • Put them into MRB storage, but make them available to the Tracker team, according to work orders, for additional study to try to find a root cause (or at least where the errors occur) and possible corrective action. • If possible, test at temperature with flight-like C0 cables (no connector savers) when they become available.

More Related