SUBMODE CHANGE PROCEDURES

Last Updated: 17 May 2007

For notes on "emergency" submode changes, see the section at the end.

Scheduling the Submode Change

Shouldn't be scheduled for a D27 pass (a non-D27 pass must be available for CDS recovery).

Must not be done during an SSR dump (FOT can't do submode change during VC4 dump) - it is possible but not desirable to ask for a pause in the dump.

Must have at least 1.5 hours of NRT after submode change time if CDS crashes.

CDS should be available to send the RPR for the submode change.

LASCO can also send the RPR and so can the FOT (write an OCD for this), but CDS must arrive shortly thereafter in case of a crash.

CDS must be IDLE before the submode change can happen.

Remind the CDS operator to compensate for the 10% rule when making the plan.
Note that CDS has made a TSTOL called cds_submode_prep that will (with FOT permission) allow the FOT to determine if CDS is not idle and send an abort command.

CDS, LASCO/EIT, SUMER must all agree on a time.

Nobody else can command during before/after submode change time.

Prior to Submode Change

Have a CDS limit violation sheet prepared in case they crash.

SUMER should submit a limit violation sheet to ignore all limits during ramp up/door work.

Changing from SM5 to SM6

Half an hour of NRT for SUMER to shut down and close - nobody else can command

SUMER will power down detector (should take just a few minutes)

Make sure CDS, LASCO/EIT are ready for submode change

NOTE: when any RPR (Remote Procedure Request) is sent, SOC gets permission from team to tell FOT to run procedure and tells FOT to run it

If SUMER closes its door:

SOC gets NRT for the SUMER door to be closed then they run their procedure which does the following:

send RPR to enable heater #82 to 30% s_fl_thc82ena.prc
tell FOT to use closed door limit set
close door
send RPR to disable ESR flags: s_fl_flag_dis

CDS will send the submode change RPR c_sm5to6

SOC notes the time that telemetry stopped for SUMER

Get NRT

Wait to see if CDS crashed

If CDS crashes:

FOT may say CDS had an OBDH toggle bit error
SOC turns in limit violation sheet
CDS has dedicated NRT for ~1.5 hours

See if LASCO needs to command

Changing from SM6 to SM5

Make sure CDS, LASCO/EIT are ready for submode change

NOTE: when any RPR is sent, SOC gets permission from team to tell FOT to run procedure and tells FOT to run it

CDS will send submode change RPR c_sm6to5

SOC tells FOT that CDS has sent its RPR to do the submode change and we are ready for the NRT pause (~5 minute pause)

SOC notes the time that telemetry started for SUMER

Get NRT

Wait to see if CDS crashed

If CDS crashes:

FOT may say CDS had an OBDH toggle bit error
SOC turns in limit violation sheet
CDS has dedicated NRT for ~1.5 hours

If SUMER door is already open, SOC will get NRT so SUMER detector can be powered up.

If SUMER door is closed:

SOC gets NRT for the SUMER door to be opened then they run their procedure which does the following (not sure of order):

send RPR to enable ESR flags: s_fl_flag_ena
open door
tell FOT to switch to nominal limit set
send RPR to turn off heater #82 s_fl_thc82dis.prc

SUMER may want OBT and will send RCR s_set_lobt

SUMER will need ~12 hours to become thermally stable before useful observations can begin.

Emergency submode changes - notes on CDS Status Before and After

When CDS is idle because it's between observations, the CKCMODE is 60 (hex) and CK5STAT is 162 (meaning "completed").

If a CDS study is aborted, CKCMODE will be something else (indicating "aborted") and CK5STAT will still be 162 (i.e. "completed").

CDS operator can abort the plan via NRT or can give the FOT a command that they can send to abort the plan.

After the submode change to check if CDS has crashed, check the value CKTMOBTS to ensure that it is incrementing each format for 4 formats.

FOT may be able to tell if CDS crashed because they may see an OBDH toggle bit error.

Location: /u/ecs/soc/SVM/submode_change_info.html