70 likes | 175 Views
Introduction. 1) PN specific 2) MOS specific 3) SCOS2000. PN specific – Offset tables. No fixed offset tables used for PN. Dump of the offset table inserted before the Start of the Observation: + offset data information always present for an observation - increased overhead:
E N D
Introduction 1) PN specific 2) MOS specific 3) SCOS2000
PN specific – Offset tables • No fixed offset tables used for PN. • Dump of the offset table inserted before the Start of the Observation: + offset data information always present for an observation - increased overhead: • ~7 minutes for FF,Ext.FF, LW • 45 seconds for SW, Ti and Burst • Repetition number changed from 100 to 50 for FF.
PN specific – EPCE unit • EPCE experienced an autonomous warm reboot in rev. 841: • Visible through a drop of the currents of the quadrant-dedicated converters in the EPVC • EPCE runs PROM version => reboot autonomous and smooth. No impact on science. • Investigations => same problem in rev. 741 • Actions: • NCR#114 raised • Explanation: SEU that stopped the code • Creation of a DP that detects any EPCE reboot(based on the parameter that counts the warm boot)
MOS specific – EMDH K • EMDH K successfully tested in flight and definitely uploaded in rev. 807. • EMDH K improvements: • Ability to upload up to 250 bright pixels instead of 50 with version J+ • Cover the possible impact of the failure of the CCD extended range temperature sensor
MOS specific – THIN1 filter assessment • Low energy patch observed on a bright source • Test to check whether this patch is due to a filter degradation (otherwise CCD degradation): • In rev. 900, on 1ES0102-72 • Filter wheel moved by 20 steps away from the THIN1 position, in the opposite direction to the calibration source. • THIN1 filter does not show degradation of its most exposed area.
MOS specific – filter wheel sanity check • Routine control of the filters sanity (degradation, micro holes,…) • Diagnostic Reset Per Pixel mode used
SCOS 2000 • XMM-Newton shall be operated with SCOS2000 • Rev. 940, fully executed via SCOS2000 (TC,TM) • All modes have been planned • TM comparisons with respect to SCOS1, FITS file comparison • Next rev. = rev. 954 • Expected to switch to SCOS2000 in phase 3 by April 2005 • Definite use of SCOS2000 (phase 4) 3 months later (July 2005)