140 likes | 261 Views
Overview of HIFI ILT. Willem Luinge TRR 15 – 16 August 2006, Groningen. Outline. Big picture Documents Short Test overview Status Testequipment Test team Organogram analysis teams Open, critical items. Big picture. Current Set up. WU rack. Documents. Reference documents, VCM
E N D
Overview of HIFI ILT Willem Luinge TRR 15 – 16 August 2006, Groningen
Outline • Big picture • Documents • Short Test overview • Status Testequipment • Test team • Organogram analysis teams • Open, critical items
Documents • Reference documents, VCM • AIV plan • Detailed AIV plan (FM ILT): under configuration control after this review • HIFI ILT Integration and Functional Test Procedure (calls for the scripts): under configuration control after this review • “HIFI ILT Performance Test Procedure” • FM ILT CUS scripts, including documents (e.g. a description: CUS scripts for HIFI FM tests), configuration files • MIB(’s) • IA use cases document and IA tools • Various integration, configuration procedures, manuals • A list of websites was added to the TRR data package • Issue for TRR: content of procedures for ILT and approach
Short Overview of the various tests • Tests after integration of various subsystems • Not complete • This TRR: No emphasis on integration • Integration and Functional test • Get HIFI functioning, incl. tunings, OBSW, scripts, EGSE, • One frequency per sub band • Integration (first time FT): implement in scripts effect of thermal time constants, harness • Beam measurements • Alignment with telescope • Radiometry • Stability • Spectral tests • Operational procedures
Man power support FM ILT campaign • Mechanical integration: RvdS, ME, LM, WH • Operation, installation of LO sources: NW, WJ, PD, MJ • Alignment issues: BK, MJ, RH, ME • Test equipment handling (vacuum & cryogens): WH, FW • Electrical integration: HS, AN, HG • EGSE, MIB: LD (back up NB, AdJ) • Operators: NB, RH, (MB), back up: AdJ • ICC (software infrastructure, database, IA, etc): AdJ, KE, PZ and others • CUS scripts: DT • Analysis & reporting: Testengineers, system engineer, calibration group, others • General: Contact persons for various subsystems
Remarks • Part time involvement of almost all • TE is responsible for plans, preparations (test equipment, availability of scripts, procedures), quick look analysis, analysis, evaluation, reporting • Script testing: // set up for off line activities and script testing: not (fully) operational • Analysis is done with IA, Wiki page for discussion • An overview plan – scripts – tools is summarized by Peter Roelfsema (tools not fully tested during DM, QM) • Test operators are running test scripts according to procedure only. No manual commanding • In case of non conformance: NCR or SPR first, notify TE, discuss the next steps (correct script, MRB, diagnostics (via extra script), ..; no manual commanding!) • Every step in the procedure is logged in an electronic log • All other activities in room 50 are logged as well • Safety: separate agenda item
Major open items Test equipment • [qualification of test equipment during DM, QM, FM1, 2] • Stable operation of FPU cryostat • Change to TEI controlled operation of re-imager: incomplete, untested • Gas cell modifications: incompletely tested • Linearity tests never exercised (beamspliters in LO beam or via reimager); parts available • Matching optics re-imager (pupil-to-field never used with re-imager) not used so far (fit check soon) • Absorption in nitrogen gas flushed cryostat coupling (2 window version of the LOU/FPU cryostats): adequate? • Hermetic rack (e.g. isolation and cooling plate modification): adequate?
Critical issues • Safety issues • a.o. drill to solve a problem in the proper, safe way (see Remarks); operator: no signed procedure: no test • Implementation of grounding and shielding plans, electrical handling • Back up for key persons • Stability of EGSE/Test control • Reliability of scripts before use: ‘NO’ debugging on flight hardware
Plan of attack: • Procedure and scripts to be signed off by author before use • Use test harness (prepared, not operational) • Test on parallel set up (as far as possible) • Test engineer to ‘read’ the scripts/procedure • Last line of defense: S/S cannot be damaged by wrong commands: no single, manual commands!