Transcript 1/24/05 - Meeting (ppt)

GLAST LAT Project
Agenda for Jan 24, 2005
• Clock frequency variation test
• TEM/TPS functional check
• Stand alone Cal LPT and Tracker LPT
LAT System Engineering
1
GLAST LAT Project
Clock Variation Test
• 6.3 Tower Tests
– 6.3.1
Functionality vs Clock Frequency
• The Tracker and Calorimeter LPT will be performed at
three clock frequencies. The frequencies are low
(14Mhz), nominal (20MHz) and high (22MHz). The
nominal frequency test may be covered during the
normal CPT or LPT with the clock at the nominal
frequency.
LAT System Engineering
2
GLAST LAT Project
TEM/TPS Functional Test
•
The TEM interfaces and basic functionality will be demonstrated by
the following tests. Note that these tests cover interfaces or
functionality not covered by Tracker or Calorimeter tests
– The TEM registers will be set to non-default values and read back
– A TEM register will be set to a non-default setting, the TEM reset,
and the register read out to verify the reset line is functional
– The interfaces to the GASU for event data will be verified by Cal
and Tracker tests
• Tracker 3 in a row and event data tested tracker test TE401
(among other tests that read out events)
• Cal Lo and Cal Hi signals verified by TBD (Tests currently in
LPT do not guarantee the Cal Hi signal is functional)
– The flow control between the GASU and the TEM/TPS will be
verified by TBD (possibly based on TEM test)
– The TEM/TPS will be powered up by both primary and redundant
PDU. The TEM and TPS temperatures should match existing
conditions and the 3.3 volt telemetry line should match expected
values.
LAT System Engineering
3
GLAST LAT Project
Stand-Alone LPT for Cal and Tracker
•
•
The Assembly Sequence has a provision for an optional test for either Cal or
Tracker
– Tracker
• Test is used after installation when there is a possibility of a problem
that we want to check out before installation of the Calorimeter
• EM TEM/TPS temporarily installed and the Tracker LPT is performed
– Calorimeter
• Test used after installation but before Tracker electrical integration to
the TEMs to check for suspected Cal or TEM/TPS problems
• Also may want to run a LPT on Cal modules that have been in storage
for extended periods before integration
How to implement direction for this test
– Not currently in the Performance and Operations Test Plan
– Would likely be run as directed by an NCR (something would have
happened to make us suspect a problem)
– Are the Cal LPT and Tracker LPT procedures implemented so that it is
possible to run them separately?
LAT System Engineering
4