1. PACS bolometer operation from the commanding point of view

T. Mueller, D. Cesarsky 19-May-2006

1. Instrument switch-on and connection of the warm electronic boxes

• - currently done with tcl-script "PACS_Switch_On.tcl" (maintained by FGB): - after execution: PACS is in SAFE mode

1. Cooler recycling (only at HeII temperatures)

• - starting out of SAFE mode - CUS script: BOLO_cool_recycle
  • (no sub-procedures are called)
  - ending up in SAFE mode

1. General Setup for Photometer Operation
   • (at warm, HeI, HeII temperatures and after cooler recycling)

• - starting out of SAFE mode - CUS script:
  • block PHOT_setup calling the following CUS procedures
  • (will be renamed to PHOT_orbit_prologue):
    • - procedure PHOT_dpu_dmc_setup - procedure PHOT_dmc_setup
      • - procedure PHOT_fltw_conf (*) - procedure CONF_chopper (*) - procedure CONF_cs (*)
      - procedure PHOT_set_bias (*) - procedure PHOT_seq_setup - procedure PHOT_change_data_mode - procedure PHOT_change_seq_mode - procedure PHOT_set_gain - procedure PHOT_spu_setup
    (*) certain parameter values depend on the temperature
    • environment!
  - ending up in PHOTOMETRY mode, but SPU processing has not yet
  • started. Note: filter is in position "A", chopper at position "0", calibration sources are set to default values, but need 30-40 min stabilisation time!!!

1. Operation of the bolometers (starting out of PHOTOMETRY mode)

• A) start/stop of bolometer data flow
  • CUS scripts:
    • - procedure PHOT_spu_setup

    • ---> bolometer data flow running

      • - procedure PHOT_spu_reset

  Change of the bolometer data/sequence mode and gain

  • CUS scripts:
    • - procedure PHOT_change_data_mode - procedure PHOT_change_seq_mode - procedure PHOT_set_gain

  C) Take data with manual chopper & filter movements

  • CUS scripts:
    • - procedure PHOT_spu_setup

    • ---> bolometer data flow running

      • - procedure PHOT_fltw_move - command Pacs_DMC_MOVE_CHOP_ABS - command Pacs_DMC_MOVE_CHOP_REL
      • - procedure PHOT_spu_reset
  D) Take data with pre-defined OBCPs
  • CUS scripts:
    • - procedure PHOT_spu_setup

    • ---> bolometer data flow running

      • - block OBCP_chopped_photometry - block OBCP_chopped_photometry_dither - block OBCP_phot_freezeframe - block OBCP_phot_cal_I - block OBCP_phot_cal_II - block OBCP_phot_cal_III - block OBCP_phot_staring - block OBCP_phot_chopper_scan
        • (not yet available!!!)
      • - block PHOT_all_aots_OBS
      • - procedure PHOT_spu_reset
  E) Execute AOT observations
  • CUS scripts (to be finalised):
    • PHOT_AOT

      • - PacsPhotDefaults - PacsPhotEstimatorOBCPn

        • - PacsDureeOBCP5
          • - DMC_phot_2_3_chop
          - PacsDureeOBCP7
          • - DMC_staring_phot
        Logic chooses and issues a pointing mode out of:
        • - composite_nodding - repeated_raster_with_hold - line_scan_with_hold
        - WriteOBSID

        - PacsPhotSlewCal

        • - PHOT_aot_prologue
          • - PHOT_spu_setup
          - PHOT_fltw_move - OBCP_chopped_photometry
        - PacsPhotCommandOBCP7
        • - OBCP_staring_photometry
        - PacsPhotCommandOBCP5
        • - OBCP_chopped_photometry_dither
        - PHOT_aot_epilogue - WriteEndID - PacsPhotNoiseRMS

        - PacsMessageCenter

1. Reset after photometer operation

• - PACS is in PHOTOMETRY or any other mode - going into SAFE mode:
  • CUS scripts:
    • - block OBCP_SAFE
  - after execution: PACS is in SAFE mode

1. Instrument switch-off

• - currently done with a dedicated tcl-script (maintained by FGB) - after execution: PACS is switched off

1. NOTES

• - there are more CUS scripts related to the SFT warm, HeI and HeII
  • which are not mentioned here (see PACS-ME-TP-007)
  - some specific photometer tests, like the thermal behaviour
  • measurements, start directly out of SAFE mode, while most of the tests will be executed after the "PHOT_setup"
  - the above mentioned CUS scripts (with a few exceptions) have been
  • tested and are available in the CUS database and from the CVS library
  - the AOT related CUS-scripts are still under testing