1. PACS IQR 13 Jan 2005 PACS OBSW1/33 PACS On-board Software & User Manual A. Belbachir (UVIE/TUVIE, SPU) H. Feuchtgruber (MPE, SE) A. Mazy (CSL, DMC) S. Pezzuto (IFSI, DPU)

2. PACS IQR 13 Jan 2005 PACS OBSW2/33 Blue arrows: TC/SCI/HK Green arrows: TC/HK Red lines: power Black : analog lines - 5 commandable units - 6 interfaces - ~27 Mbytes memory (PROM,EEPROM,PRAM,DRAM) - Virtuoso RTOS - 2 different detection systems - Autonomous operation - Uplink bandwidth limit - Downlink bandwidth limit - Redundant units MTL

3. PACS IQR 13 Jan 2005 PACS OBSW3/33 DPU OBSW – Status (1) Last Version : 7.65 delivered on 25 th October 73 Requirements in last URD (Version 2.5) 88% implemented 5% missing specifications 4% no longer applicable 3% obsolete 34 OBCP available to activate subsystems, to enter specific observing/operative modes (incl. SAFE), to execute measurements, to calibrate the instrument, stand-alone test

4. PACS IQR 13 Jan 2005 PACS OBSW4/33 DPU OBSW – Status (2) Open Issues (Major) On time scale of 36/48 hours, a 1553 memory corruption occurs (SPR-0230); NCR raised and delivered to CGS on November 19 th Loading of OBCP implemented but not tested; AF not defined; this may have impact on OBSW PS-ICD V4 compatible apart from req. 1020-A1 on bit alignment are (necessarily) violated in HK packets Burst mode successfully tested with CDMS simulator provided by RAL; communications almost stopped with CDMU provided by SSBV already at nominal HK rate (1 packet/2 seconds). No reason identified yet

5. PACS IQR 13 Jan 2005 PACS OBSW5/33 DPU OBSW – Status (3) As part of the new contract ASI-CGS, IFSI provides the OBSW as subcontractor of CGS Version delivered to CGS is 7.63 (minor bugs wrt version 7.65, irrelevant for what the SW is aimed to, i.e. test tool for CGS HW) Version 7.63, Version 1 for CGS, is going to pass the whole SW verification and validation phase. The 1 st phase (test at IFSI with AVM1) has been done on 16/17 December; on 20/21/22 December test repetition at CGS premises with IFSI AVM1 first, and then with new AVM2, both tests were successful, only a minor SW update for the DPU reset was required to work on both models AVM 1 and AVM2. Upon acceptance Version 1 will be easily upgraded to Version 7.65

6. PACS IQR 13 Jan 2005 PACS OBSW6/33 DPU OBSW – CAPTEC Report Possible problems of interference between tasks when accessing global or static variables. These conditions have been isolated and solved in almost all cases. Minor problems will be corrected in future releases. Documents : missing parts have been inserted SW requirements matrix in SSD How to build a new image in SUM Improvement in documentation expected with new personnel

7. PACS IQR 13 Jan 2005 PACS OBSW7/33 DPU OBSW – Documents URD --> Issue 2.5, 1 December 2004 SSD --> Issue 2.2, 1 December 2004 SVVP --> Issue 3.2, 1 December 2004 OBS Test Report --> New issue after test activities with CGS SUM --> Issue 1.7, 15 September 2004 (1.8 in prep. for CGS) They follow guidelines given in BSSC(96)2 Modifications of SW Version 1 will proceed formally through CGS (via RID, SPR, NCR), to evaluate the impact on the documents and on the code. For Version 2 CGS only asks to be informed of changes in documents and to have the new versions. Delivery of SW Version 2 goes directly to Consortia.

8. PACS IQR 13 Jan 2005 PACS OBSW8/33 DPU OBSW – Next developments and maintenance Activities detailed in “DPU/ICU OBS Version 2 Development Plan” - CNR-IFSI-2004-PL001 Mainly: Version 1 : support to CGS activities (eg integration with next models); consolidation activities Version 2 : design and development activities toward FM Activities for version 1 and 2 will be covered by different contracts with ASI and CGS IFSI is looking for two SW engineers to help in all these activities, from SW coding to documentation.

9. PACS IQR 13 Jan 2005 PACS OBSW9/33 DPU OBSW – Boot and Application SW When DPU is switched on FPGA copies boot SW from PROM (EPROM in AVM) to 21020 Program Memory Boot SW checks PM, DM and EEPROM. If all the checks are OK, an event TM(5,2) is reported If the command FORCE BOOT is sent, the application SW is copied from EEPROM to PM and started Alternatively, a new image can be uploaded via service TM(6,2) Implementation of this service in the boot SW is not fully PS-ICD compliant. Version 7.63 (and also 7.65) requires 1368 TC. If all TC are correctly received (no event TM(5,4) is reported), after the command LOAD TC AND BOOT is sent, the application SW is copied from DM into PM, and started

10. PACS IQR 13 Jan 2005 PACS OBSW10/33 DPU OBSW – Default Status of Application SW (1) 1553 interface : nominal mode; burst mode only if commanded 1355 interface : SMCS332 initialized, links not started HK list : non prime (1 packet of 382 bytes /2 seconds); additional HK packet (1 packet equivalent to non prime HK every 10 seconds) OBCP : 34 available, ready to be started AF : 2 available, one for BOL (even if not used) and one for test purposes. By default AF are disabled (enabling each AF is supposed to be part of the transition from one operative/observing mode to another one)

11. PACS IQR 13 Jan 2005 PACS OBSW11/33 DPU OBSW – Default Status of Application SW (2) Available TM packets (not considering events) : 25 (19 are enabled); science transmission disabled. Each SPU array can be enabled separately. TM (1,1) and TM(1,2) can not be disabled (but TM(1,1) is generated only if a specific bit in the TC packet header is set). Also essential HK packet can not be disabled Events defined : 27 --> 24 are TM(5,1), 3 are TM(5,2), 0 TM(5,4). TM(5,2) are : request to switch off BOL-C; request to set PACS in SAFE mode; message to satellite “PACS ready to be switched off”. Each event can be disabled one by one.

12. PACS IQR 13 Jan 2005 PACS OBSW12/33 DPU OBSW – User Manual Main purpose : how to send commands to DPU, meaning of parameters (for DPU commands), understanding TM packets (TC verification, HK, events, science...) - How to build and load a new image - Content of HK packets - List of OBCP, functions and DMC sequences. Usage of special OBCP (starting 1355 links, writing image in EEPROM, starting application SW in subsystems) Structured following PS-ICD : if service (x,y) is used, operational instructions are found in Section 4.x.y while a more technical description is given in Section 5.x.y

13. PACS IQR 13 Jan 2005 PACS OBSW13/33 Summary Status of SPU HLSW SW actual version: 11.1 dated of 23-Jul-2004. SW configuration: –The CVS repository at Leuven has all SW versions, tools and release notes. –SW problems are reported through the SPR system. –All SW documents are at PACS Central File at Leuven. Documentation: –User Manual issue 11.1 dated of 23-Jul-2004. –SW Specifications issue 4.3 dated of 30-Mar-2004. –Release Note issue 11.1 dated of 23-Jul-2004. –User Requirements issue 3.1 dated of 29-Mar-2004. –Others: ICDs, Test Plan and Test Reports (see CIDL). CAPTEC Review on 05-06 April 2004 in Vienna

14. PACS IQR 13 Jan 2005 PACS OBSW14/33 Detailed Status of SPU HLSW Version 11.1 (1) The software has been tested on the AVM SPU and resides in its EEPROM; Boot SW – HLSW interfaces by command; Command/response, HK and science protocols DPU-SPU-DMC are tested and o.k. 13 different compression/reduction modes available and tested SW updates either directly to EEPROM or to RAM are possible and tested. One memory load command to both SPU processors is replicated inside the DPU and then sent to SPU-L and SPU-S as two independent commands. Test mode for spectroscopy and photometry available

15. PACS IQR 13 Jan 2005 PACS OBSW15/33 Detailed Status of SPU HLSW Version 11.1 (2) Open issues: –Compression ratio is too small and/or CPU workload becomes too high. Closer match to actual detector data required. –Sporadic misalignment of science data header vs. science data (not clear if SPU or DMC, however most likely SPU)

16. PACS IQR 13 Jan 2005 PACS OBSW16/33 SPU Documentation DocumentIssueDistribution Date Completeness SPU HLSW URD3.129.03.2004100 % SPU HLSW to DPU ICD5.116.04.2004100 % SPU HLSW SSD (incl. ADD+DDD+SRD)4.330.03.2004~100 % SPU HLSW SUM and release note11.123.07.2004100 % SPU HLSW Test Plan4.029.05.2002100 % SPU HLSW Module Test Report1.029.05.2002100 % SPU HLSW Communication Test Report1.013.03.2003100 % SPU HLSW Acceptance Test Plan and Report for AVM delivery 1.213.03.2003100 % SW PA Plan (from IFSI)1.008.01.2001100 %

17. PACS IQR 13 Jan 2005 PACS OBSW17/33 SPU Captec Review Consequences Captec reviewed HLSW version 8.6 Assessments: –SW code maps to the architecture –Configuration management procedure are working –CQM and FM ILT dates are compatible with ESA needs –Requirement, design and coding are 100% complete. –No planning for maintenance –The documentation (major open area) has been improved for HLSW 11.1 –Missing CIDL has been provided (issue 1.0 on Nov. 19 th,04) Major recommendations: –SW code commenting should be improved –Compression needs to be checked against latest 'noisy' detector data

18. PACS IQR 13 Jan 2005 PACS OBSW18/33 SPU User Manual Usage General overview Procedure for software installation and update Running confidence check for proper software installation List of software modules. Software input and output specifications Software procedure to handle 1355 links and how the SW operates when the connection is lost How to command the SPU SW. Detailed description of all commands and required parameters Summary of packet structure between DMC-SPU and DPU and SPU. HK list with default parameters Simulated data description Software memory map

19. PACS IQR 13 Jan 2005 PACS OBSW19/33 DMC Software status Version 5.023 –in EEPROM on DMC EM –In KUL CVS repository Full acceptance test passed with version 5.016 Delta acceptance test passed with version 5.020 Modifications since 5.020: –Changed default mechanisms controller parameters –Complete rebuild

20. PACS IQR 13 Jan 2005 PACS OBSW20/33 DMC Software status: open issues Open SPRs: –161 – Non nominal behaviour of DMC_FW_GRATHALL_A&B: not a software problem –250 – Swoff spectro array should never be rejected: accepted for implementation in future version Others: –Grating controller error detection still need some improvements –Some FPGA bug correction still need to be removed when the final version of the FPGA will be available

21. PACS IQR 13 Jan 2005 PACS OBSW21/33 DMC Software status: autonomy concept No autonomy in DMC OBS except for: –To protect grating from bad operation, the controller can be disabled by DMC OBS when some errors are detected.

22. PACS IQR 13 Jan 2005 PACS OBSW22/33 DMC Software status: SUSW – ASW interaction SUSW is used to copy from EEPROM to RAM or to upload new version of ASW in RAM (the writing in EEPROM is done in the ASW itself) SUSW does not have to know anything about ASW => no SUSW update required. Everything is done via commanding.

23. PACS IQR 13 Jan 2005 PACS OBSW23/33 Software status : default settings in DMC OBS All writeable parameters have default parameters. The mechanisms controller defaults values are for room T° operations All functionalities are available without overwriting any of the default values (except for the grating direction that must be inverted for grating QM) Simulated science test modes available

24. PACS IQR 13 Jan 2005 PACS OBSW24/33 Documentation status URD v2.2 (01/10/2003) SSD v1.0 (03/10/2003) SUM v3.3 (06/12/2004) Test Plan v1.4 (02/12/2004)

25. PACS IQR 13 Jan 2005 PACS OBSW25/33 CAPTEC review follow-up 2 bugs detected in HK generation URD-SSD update needed SUM updated with additional information

26. PACS IQR 13 Jan 2005 PACS OBSW26/33 User Manual overview Content: –Procedure to start/upload the software –Description of commands –‘How to use’ sections for grating, chopper, … –Description of telemetry

27. PACS IQR 13 Jan 2005 PACS OBSW27/33 TM/TC Status of BOLC No OBSW within BOLC, however it controls the photometer FPU and has its command and sync. interface via DMC. Commanding and HK defined in: –BOLC to DMC Electrical ICD, Sap-PACS-CCa-0046-01 Operations of the entire photometer are described in: – PACS Photometer FPU User manual, Sap-PACS-MS-0247-04 Testmode of science data available and tested

28. PACS IQR 13 Jan 2005 PACS OBSW28/33 TM/TC Status of BOLC Warm and cold functional tests, cooler recycling, setup and operation of the bolometer detectors has been successfully tested following the User Manual. Open Issues: –[Unexpected loss of the spacecraft powered 28 V line may cause irreversible damage to the bolometers] –Wrong and/or incomplete bias settings to the bolometers may cause irreversible damage to the bolometers. Although limit monitoring instructions are being provided within the user manual, a clear strategy to monitor and autonomously recover from failed bias commands does not exist yet.

29. PACS IQR 13 Jan 2005 PACS OBSW29/33 Qualification Status of PACS OBSW (1) PACS WE mounted on SVM Simulator panel BOLC DPU DMC SPU DMC

30. PACS IQR 13 Jan 2005 PACS OBSW30/33 Qualification Status of PACS OBSW (2) All latest PACS OBSW packages reside in KUL CVS with SPR system in place. DPU, mostly successful testing during AVM ILT 2 Problems: 1553 memory corruption and burst mode SPU, mostly successful testing during AVM ILT 2 Problems: Science data compression ratio (+ CPU workload), potential data misalignment in spectroscopy (SPU or DMC ?) DMC mostly successful testing during AVM ILT No major open problem at present, however the present software has built in corrections for FPGA misbehaviour which need to be removed in future versions. BOLC, successful testing during AVM ILT 2 Problems: (Unexpected switch-off), procedural handling in case of failed detector bias setting (missing specifications).

31. PACS IQR 13 Jan 2005 PACS OBSW31/33 Qualification Status of PACS OBSW (3) 19 out of the available 34 OBCPs have been tested during the ILT. (All OBCPs which are planned for use in actual AOTs have been verified.) Other OBCPs are either obsolete (6-7) and/or require updates according to the results of the ILT. The concept of OBCPs (service 18) in general has been verified.

32. PACS IQR 13 Jan 2005 PACS OBSW32/33 The “PACS” User Manual All information how to use and operate PACS is at present contained in 4 separate user manuals according to the individual WE sub-systems and a number of other documents.

33. PACS IQR 13 Jan 2005 PACS OBSW33/33 The “PACS” User Manual The way to go for a User Manual according to the OIRD (mostly to be collected from other already available documents): –Introductory, flow and descriptive information –Instrument interfaces and performance (heat diss., power cons. etc) –Instrument Operations Modes (details TBW) –Instrument failures, fault management and redundancy (TBW) –OBSW  pointer to sub-system SUMs, OBSM facility ? –Telemetry  pointer to DPU SUM, sub-system SUM and MIB –Telecommands  pointer to DPU SUM, sub-system SUM and MIB –Instrument Operations Procedures (Comm., Nom., Cont.) (Partly available as TOPE procedures, to be updated and TBW) –Instrument Budgets (power, data, mass, error and alignment, timing) –Instrument Science Data Definition