1. XMM-Newton Status of EPIC Operations Guillermo Buenadicha & Pedro Calderón Mallorca 8-April-2008

2. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 2 Overview Routine operations New DB items Nominal OCR operations Not nominal events AOB’s

3. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 3 Routine Operations RBI clock resync every ~194 days –Last on December 10 th 2007, next on June 21 st. Eclipse season fully nominal. –Almost everything performed automatically by timeline. –Extra heating event happened because of human error on operations due to being in eclipse season, but not due to the eclipse itself. –Moon eclipse on 06/04/08 (last Sunday…) requiring to manually uplink the automatic commanding due to limited time available before perigee. Other than this, not bad

4. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 4 New ODB 5.9 Released on 17 th March Includes (at instrument level): –Refinements to avoid possible repeat of the extra heating event –New hot stuff for MOS and PN (Bright Pixels) –Sequences for MOS 3x3 offset calculation –Updated PN offset Activity (needed for mosaic) –New Activity for PN Mosaic observation mode (with CLOSE offset calculation followed by FW selection for OBS) First fully planned revolution at SOC shall be 1530, however some items (MOS) have been taken from 1520 (timeline at MOC)

5. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 5 New Hot Stuff New versions of the MOS Bright Pixel Tables –Now at version V10 –Numbers still well within the limit of 50 per CCD –Checking derived parameter upgraded New versions of the PN Bad Pixel Tables –Further reduction of the bright 64 column in CCD 11 Changes in place since Rev 1515 (March 17 th ) but they will be not in full use until Rev 1530 (April 16 th ) for PN, and 1520 for MOS.

6. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 6 PN MOSAIC observation mode  General idea: – –Calculate the offset tables in slow mode (100 repetitions) and with the FW=Closed – –Then observe continuously (with the requested filter) when the S/C moves from a pointing of the mosaic to the next one, and so on.  Will be offered in AO-8 (August this year).  The other instruments do not need operational modifications, impact only at Mission Planning level. OBS MODE FW X OFFSET FW CLOSE OBS MODE FW X OFFSET FW X OBS MODE FW X OFFSET FW X OBS MODE FW X OFFSET FW X

7. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 7 Last check of MOS1 CCD6 Agreement from Cal Meeting Oct 2006 to execute a CCD-6 health check periodically every 6 months Last check performed on February 22 th 2008 The operation was quick and easy (ad hoc Event Designator created in DB since March 2007) No changes in results (still full of AFFA hex events) Furthermore: We even tried with a non foreseen pseudo extraheating that did not resurrect broken CCD (surprised ???)… we’ll keep on trying… A nthony FFA bbey

8. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 8 CCD6 image from SOC

9. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 9 CCD6 data from MOC Obtained using LELA LELA has capabilities to monitor in Real Time the science data, but no archive or retrieval mechanisms

10. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 10 MOS noise reduction test  MOS low energy noise suppression tests were performed in revolutions 1453 and 1470 (16 th Nov and 18 th Dec).  Closing action from last Calibration from Meeting @Peguera November 2007  VID voltage of MOS-1 CCD2, MOS-1 CCD4, MOS- 2 CD2, and MOS-2 CCD5 were raised from the nominal 20V to 25V.  A Cal_Closed exposure was taken under this settings.  Looks like there is no improvement after data analysis (M. Stuhlinger).

11. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 11 Unintended “Extra” Heating  On 27 th January, just at the end of the last eclipse of the season, the EPIC CCD substitution heaters switch-OFF telecommand failed at ground (software problem, understood and now solved)  The operator did not realised the impact, and did not reissued the TC.  Also, reaction to subsequent triggering alarm was not adecuate  Both CCD substitution heaters (A + B) were ON along 4 hours affecting all three EPIC cameras  Maximum temps: PN –52 °C, MOS –75 °C  Looks like no impact was seen in subsequent CAL observations

12. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 12 Unintended “Extra” Heating

13. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 13 MOS into radiation, rev 1519  On 26/03/08 LELA system was not receiving TM due to a misconfiguration of system  No alarm raised. LELA is now source for radiation parameters based on instrument inputs – –19:01 z EDS001 / KDS001 went OOL (seen only at SOC the day after) – –19:32 parameter FD103 HL (MOC calculated) – –22:35 z Radmon alert – –3.5 hours impact  NCR-VIL-131 raised to cover it  LELA now connected to MCS system, task in XMCS detects if LELA stops issuing data (granularity 1 minute)  OOL Xref table upgraded to become even more robust and close MOS in case of PN closure for FD103 (HL) or FD131 (HH) NCTRS-ANCTRS-B LELAXMCS

14. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 14 MOS into radiation, rev 1519

15. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 15 MOS into radiation, rev 1519

16. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 16 MOS 3x3 OFFSET  Test on 19 th March, once the new ODB was available  Aim was to perform an offset calculation On Board by MOS instruments with settings set for 3x3 mode, followed by an small observation making use of the offsets derived.  Last offset calculation performed in 2000, and was 1x1 !!!  The current available 3x3 offsets were theoretically derived by T. Abbey back in 2006  2 problems (believed uncorrelated) found: – –MOS-1 offset patch from ground failed –understood, wrong TC used not allowed in IDLE mode. –A new DB is required in order to allow for one. –Offsets were calculated and sent to ground for all CCD’s, data under analysis. – –MOS-2 failed the offset calculation on CCD-1 (first one to be called). –Seems a controlled failure (event report sent to ground) –no further activity performed.

17. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 17 Anomalous image in MOS 2 MOS2 show an anomalous image when observing into a slew in Full Frame mode, and with the filter wheel in Cal Close position. PN show a bright source at almost the same time, when observing with FW=Medium (EFF). MOS1 saw nothing unusual with FW = Cal Close. The telemetry show a singly different time distribution for MOS1 and PN events (see APID_Statistics). Problem is… Why on MOS-2 and not MOS-1? Why so long period transmitting data (not compatible with slew FoV transit?)

18. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 18 Anomalous image in MOS 2 Analysis of the first minute of data Light curve shows 3 chunks of data, with two holes Consistent with information from counting mode 09:17:09 to 09:17:25 (16 seconds) 09:17:49 to 09:18:09 (21 seconds) Pattern analysis points to 31, Optical… Removal of pattern 31 Strong optical sources? YES, Canopus… See it in PN FOV… M. Stuhlinger, R. Saxton, M. Guanazzi

19. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 19 Anomalous image in MOS 2 What happened? 2008.056.09.14.32 CMD F0003 PN OBS 2008.056.09.14.59 CMD EU046 WD M1 2008.056.09.15.09 CMD E0049 FW PWR ON 2008.056.09.15.09 CMD KU046 WD M1 2008.056.09.15.14 CMD E0085 FW TO CLS CL 2008.056.09.15.29 CMD K0049 FW PWR ON 2008.056.09.15.34 CMD K0085 FW TO CLS CL 2008.056.09.16.14 CMD E0050 FW PWR OF 2008.056.09.16.19 CMD E0031 LOAD HBR 2008.056.09.16.24 CMD E0037 REP HBR 2008.056.09.16.29 CMD E0081 STOP SEQ 2008.056.09.16.34 CMD K0050 FW PWR OF 2008.056.09.16.39 CMD E0003 M1 OBS 2008.056.09.16.39 CMD K0031 LOAD HBR 2008.056.09.16.44 CMD K0037 REP HBR 2008.056.09.16.49 CMD K0081 STOP SEQ 2008.056.09.16.59 CMD K0003 M2 OBS M. Stuhlinger

20. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 20 Anomalous image in MOS 2 8 Kwords 48 Kwords Pinhole in the CLOSE filter Light entering through Cal Hole Light collected during FW movement in open filter positions and transmitted only after Enter Obs How is it possible to produce two counting periods? Where is all the data archived??? Size of buffers, including FIFO… Why just CCD 1??? Is the slew time compatible with this??? What is more fun. Enter OBS should reset the 8 Kwords FIFO, thus leading to no data up the chain. Also pointers in HBR should be reset Why is the CCD-1 data starting on frame 11? What now? Redefine the sequencer strategy during FW movement? Screen for data for other similar events? Does it affect start of exposure only in slews?  Slew survey. 1 event = 6 words Around 7000 events transmitted Counting accounts for 10000!!! 1 CCD slew 7 seconds

21. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 21 Anomalous image in MOS 2 Sequence of operational events: 2008.056.09.14.32 CMD F0003 PN OBS 2008.056.09.14.59 CMD EU046 WD M1 2008.056.09.15.09 CMD E0049 FW PWR ON 2008.056.09.15.09 CMD KU046 WD M1 2008.056.09.15.14 CMD E0085 FW TO CLS CL 2008.056.09.15.29 CMD K0049 FW PWR ON 2008.056.09.15.34 CMD K0085 FW TO CLS CL 2008.056.09.16.14 CMD E0050 FW PWR OF 2008.056.09.16.19 CMD E0031 LOAD HBR 2008.056.09.16.24 CMD E0037 REP HBR 2008.056.09.16.29 CMD E0081 STOP SEQ 2008.056.09.16.34 CMD K0050 FW PWR OF 2008.056.09.16.39 CMD E0003 M1 OBS 2008.056.09.16.39 CMD K0031 LOAD HBR 2008.056.09.16.44 CMD K0037 REP HBR 2008.056.09.16.49 CMD K0081 STOP SEQ 2008.056.09.16.59 CMD K0003 M2 OBS

22. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 22 Anomalous image in MOS 2 Possible explanations: Option 1 Light collected during FW movement in open filter positions and transmitted only after Enter Obs Requires careful analysis on MOS FW layers, and PN, MOS-1 and MOS-2 delta times. Only 20-30 seconds would be available, is this compatible? Is this compatible with data downloaded and HBR cleanup??? How is it possible to produce two counting periods? Seems to be the case, light curve from PN shows a peak of data from 09:16:20 to 09:16:38, fully compatible… So how comes this is seen as a collection of items from 19:17:03 to 19:18:10??? Option 2 Pinhole in the CLOSE filter Geometry such that stray light penetrates under this specific configuration Why not seen other times? Why not seen in pinhole analysis Depends heavily on knowing the PN detection times (i.e. if posterior to 09:16:34 then feasible) Option 3 Light entering through Cal Hole Why is it not seen other times or in MOS-1? I do not believe it… What now? Redefine the sequencer strategy during FW movement. Any further pinhole test??? Are we doing same things with sequencer on slew exposure or nominal one? Does it make a difference

23. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 23 Anomalous image in MOS 2 Option 1 Light collected during FW movement in open filter positions and transmitted only after Enter Obs Requires careful analysis on MOS FW layers, and PN, MOS-1 and MOS-2 delta times. Only 20-30 seconds would be available, is this compatible? Is this compatible with data downloaded and HBR cleanup??? How is it possible to produce two counting periods? Seems to be the case, light curve from PN shows a peak of data from 09:16:20 to 09:16:38, fully compatible… So how comes this is seen as a collection of items from 19:17:03 to 19:18:10??? Interesting to see that in PN the light curve is around 20 seconds, whereas the trace left in MOS fov is only compatible with around 6 or 8 seconds of data, more in line with a FW hole… Where is all the data archived??? Size of buffers, including FIFO… Is just CCD-1 or others also??? It would be OK if it passes through another, counting spread among CCD´s and better explanation to the first peak What is more fun. Enter OBS should reset the 8 Kwords FIFO, thus leading to no data up the chain. There was a BRAT change before, but should not be in place for this obs (10kbps to MOS) What now? Redefine the sequencer strategy during FW movement. Any further pinhole test??? Are we doing same things with sequencer on slew exposure or nominal one? Does it make a difference In CAL CLOSE is where we cycle through all FW positions… If this is due to the FW passing through open ones, it means that in some cases the first transmitted frames in a source are not time correlated properly… Is this the case? Am I doing something not correct? Again, is this all compatible with data throughput and buffering capability? Can we correlate counts with events??? The count rate given by M. Sthulinger is way to high for the transmission rate… I would expect lots of pile up

24. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 24 EPIC Engineering at ESAC 1998 – 20012000 – 20062006 – 20062006 – 20082007 – …

25. G. Buenadicha & P. Calderón SOC Operations Support Group XMM-Newton 8 Apr 2008Pag. 25 MOS2 +32V drop The voltage in the +32V line drop instantaneously to 0 volts in the middle of a normal observation, the CCD stop generating events, but any other telemetry parameter show any change or spike. After a switch OFF / switch ON the instrument return to full nominal. Happened a similar incident in MOS 1 on 2002 (NCR#105), but never again. MRB with Saclay, Leicester and ESAC Suspected a SEU in EMVC electronic ?? No further reocurrence No apparent impact on trend analysis parameters Several Procedures modified in order to prevent thermal impact on other instruments should this ever happen Hopefully more attention placed during next eclipse seasons…