TableOfContents(2)

PACS bolometer operation from the commanding point of view

T. Mueller, D. Cesarsky; 08-Nov-2006

1. Short functional tests

1.1. SFT Warm: Sorption Cooler and Bolometer detector chain

- PACS_Phot_SFT_Cooler_Warm_OBS, calling PACS_Phot_SFT_Cooler_WarmBR

- PACS_Phot_DPU_DMC_Setup_OBS, calling PACS_Phot_DPU_DMC_SetupBR - PACS_Phot_Switchon_OBS, calling PACS_Phot_SwitchonBR - PACS_Phot_Sequencer_Setup_OBS, calling PACS_Phot_Sequencer_SetupBR - PACS_Phot_SPU_Setup_OBS, calling PACS_Phot_SPU_SetupBR - PACS_Phot_Warm_Startinputsignal_OBS, calling PACS_Phot_Warm_Startinputsignal (Duration: 637 sec)BR - PACS_Phot_SPU_Reset_OBS, calling PACS_Phot_SPU_ResetBR - PACS_Phot_Switchoff_OBS, calling PACS_Phot_SwitchoffBR

Note: No specific autonomy functions are involved here (except AF#6 to check for the communication between DMC and BOLC)

1.2. SFT at HeI: Sorption Cooler and Bolometer detector chain

- PACS_Phot_SFT_Cooler_OBS, calling PACS_Phot_SFT_CoolerBR

- PACS_Phot_DPU_DMC_Setup_OBS, calling PACS_Phot_DPU_DMC_SetupBR - PACS_Phot_Switchon_OBS, calling PACS_Phot_SwitchonBR - PACS_Phot_Sequencer_Setup_OBS, calling PACS_Phot_Sequencer_SetupBR - PACS_Phot_SPU_Setup_OBS, calling PACS_Phot_SPU_SetupBR - PACS_Phot_Cold_Startinputsignal_OBS, calling PACS_Phot_Cold_Startinputsignal (Duration: 637 sec)BR - PACS_Phot_SPU_Reset_OBS, calling PACS_Phot_SPU_ResetBR - PACS_Phot_Switchoff_OBS, calling PACS_Phot_SwitchoffBR

Note: No specific autonomy functions are involved here (except AF#6 to check for the communication between DMC and BOLC)

1.3. SFT at HeII (cooler not recycled): Sorption Cooler and Bolometer detector chain

- PACS_Phot_SFT_Cooler_OBS, calling PACS_Phot_SFT_CoolerBR

- PACS_Phot_DPU_DMC_Setup_OBS, calling PACS_Phot_DPU_DMC_SetupBR - PACS_Phot_Switchon_OBS, calling PACS_Phot_SwitchonBR - PACS_Phot_Sequencer_Setup_OBS, calling PACS_Phot_Sequencer_SetupBR - PACS_Phot_SPU_Setup_OBS, calling PACS_Phot_SPU_SetupBR - PACS_Phot_Cold_Startinputsignal_OBS, calling PACS_Phot_Cold_Startinputsignal (Duration: 637 sec)BR - PACS_Phot_SPU_Reset_OBS, calling PACS_Phot_SPU_ResetBR - PACS_Phot_Switchoff_OBS, calling PACS_Phot_SwitchoffBR

Note: No specific autonomy functions are involved here (except AF#6 to check for the communication between DMC and BOLC)

2. Nominal operations

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

- currently done with tcl-script PACS_Switch_On.tcl (maintained by FGB)BR - after execution: PACS is in SAFE mode, the bolometer groups are off, but the temperature sensors are onBR

Note: Autonomy function #6 is enabled to check for the communication between DMC and BOLC

2.2. Cooler recycling (only at HeII temperatures)

- starting out of SAFE mode (groups off, temperature sensors on) BR - CUS script:BR

• mode BOLO_cooler_OBS calling the CUS procedure BOLO_cool_recycle:BR

  • - no sub-procedures are called, the groups and temperature sensors are not touchedBR - HK_list is set to PHOT_HK and reset to "NON-PRIME" in the endBR - autonomy function 14 is enabled, Duration: 7928 secBR

- ending up in SAFE mode (groups are off, temperature sensors on, HSP heater current at 1.18 mA)BR

Note: At the end of the recycling the autonomy function 14 is enabled. It checks for TEMP_EV, TEMP_FPU1, TEMP_FPU2:BR

• --> HK DEC SOFT is generated if one or more are out of the range [260,320] mKBR --> GO SAFE is generated if one or more are above 400 mKBR

2.3. General Setup for Photometer Operation (after cooler recycling)

- starting out of SAFE mode (groups off, temperature sensors on)BR - CUS script:BR

• block PHOT_setup calling the following CUS procedures:BR

  • - procedure PHOT_dpu_dmc_setupBR - procedure PHOT_dmc_setupBR

    • - procedure PHOT_fltw_conf BR - procedure CONF_chopper BR - procedure CONF_cs BR

    - procedure PHOT_switchon_groupsBR - procedure PHOT_set_bias (*)BR - procedure PHOT_seq_setupBR - procedure PHOT_change_data_modeBR - procedure PHOT_change_seq_modeBR - procedure PHOT_set_gain(**)BR - procedure PHOT_spu_setupBR

• (*) the bias tables to be loaded might change!BR (**) the gain setting can be 'high' or 'low'

• - ending up in PHOTOMETRY mode, but SPU processing has not yet startedBR - Note: filter is in position "A", chopper at position "0"BR - calibration sources are set to default values, but need 40-50 min stabilisation time!!!BR

Note: At the end of the PHOT_setup the autonomy function 17 "generate_event_pwr" is enabled. It checks for the HK entries: PC_PWR_ANA_P_#, PC_PWR_ANA_N_# and PC_PWR_DIG_#, with # = [1,2,3,4,5,6,7]

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

2.4.1. start/stop of bolometer data flow

• CUS scripts:BR

  • block PHOT_spu_setup_OBS calling procedure PHOT_spu_setup ---> bolometer data flow running BR block PHOT_spu_reset_OBS calling procedure PHOT_spu_reset ---> bolometer data flow stopped BR

2.4.2. Change of the bolometer data/sequence mode and gain

• CUS scripts:BR

  • - procedure PHOT_change_data_modeBR - procedure PHOT_change_seq_modeBR - procedure PHOT_set_gainBR - or via MSTK with individual commands

2.4.3. Take data with manual chopper & filter movements

• CUS scripts:BR

  • block PHOT_spu_setup_OBS calling procedure PHOT_spu_setup ---> bolometer data flow runningBR

    • - block PHOT_fltw_move_OBS calling procedure PHOT_fltw_moveBR - command Pacs_DMC_MOVE_CHOP_ABSBR - command Pacs_DMC_MOVE_CHOP_RELBR

    block PHOT_spu_reset_OBS calling procedure PHOT_spu_reset ---> bolometer data flow stoppedBR

2.4.4. Take data with pre-defined OBCPs

• CUS scripts:BR

  • block PHOT_spu_setup_OBS calling procedure PHOT_spu_setup ---> bolometer data flow running BR

    • - block OBCP_chopped_photometry_OBSBR - block OBCP_chopped_photometry_dither_OBSBR - block OBCP_phot_freezeframe_OBSBR - block OBCP_phot_cal_I_OBSBR - block OBCP_phot_cal_II_OBSBR - block OBCP_phot_cal_III_OBSBR - block OBCP_phot_staring_OBSBR - block OBCP_phot_chopper_scan_OBSBR

    block PHOT_spu_reset_OBS calling procedure PHOT_spu_reset ---> bolometer data flow stopped BR or

    block PHOT_spu_setup_OBS calling procedure PHOT_spu_setup ---> bolometer data flow running BR

    • - block PHOT_all_aots_OBSBR

    block PHOT_spu_reset_OBS calling procedure PHOT_spu_reset ---> bolometer data flow stopped BR

• Note: all OBCPs can be started with default parameters via the generic tcl-script; the key-OBCPs can also be
  • started with freely selectable parameters via specific tcl-scripts

2.4.5. Execute AOT observations

• CUS scripts (to be finalised):BR

  • PHOT_AOTBR

    • - PacsPhotDefaultsBR - PacsPhotEstimatorOBCPnBR

      • - PacsDureeOBCP5BR

        • - DMC_phot_2_3_chopBR

        - PacsDureeOBCP7BR

        • - DMC_staring_photBR

      Logic chooses and issues a pointing mode out of:BR

      • - composite_noddingBR - repeated_raster_with_holdBR - line_scan_with_holdBR

      - WriteOBSIDBR - PacsPhotSlewCalBR

      • - PHOT_aot_prologueBR

        • - PHOT_spu_setupBR

        - PHOT_fltw_moveBR - OBCP_chopped_photometryBR

      - PacsPhotCommandOBCP7BR

      • - OBCP_staring_photometryBR

      - PacsPhotCommandOBCP5BR

      • - OBCP_chopped_photometry_ditherBR

      - PHOT_aot_epilogueBR - WriteEndIDBR - PacsPhotNoiseRMSBR - PacsMessageCenterBR

2.5. Reset after photometer operation

• - PACS is in PHOTOMETRY or any other modeBR - execute mode PHOT_switchoff_groups_OBS calling procedure PHOT_switchoff_groupsBR

  • (this will reset the biases sequentially, disable the AF 17, and switch off the groups)BR

  - going into SAFE modeBR

  • (this will disable the AF 14 for the FPU temperature checks)BR

  - after execution: PACS is in SAFE modeBR

2.6. Instrument switch-off

• - currently done with the tcl-script PACS_Switch_Off.tcl (maintained by FGB)BR

  • (this will disable the AF 6 for the DMC-BOLC communication check)BR

  - after execution: PACS is switched offBR

3. NOTES

• - the SFT tests are described in PACS-ME-TP-007BR - 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 libraryBR - the AOT related CUS-scripts are still under testing