|CDS||Before||LASCO will be safed first then UVCS then CDS. FOT will send c_fl_submode_prep then c_fl_shutdoors. To close doors manually via NRT takes about 10 minutes.|
|After||Wait more than 2 hours once the burns are complete before returning to nominal operations. FOT will send c_fl_opendoors before LASCO is opened.|
|Old Notes|| In the event of an operator emergency in which a CDS operator is not present
at the EOF to close the doors, the following commands are to be sent via FOT
with 30 second interval pauses between each command, which should close the
doors with no problems:
These instructions are formalized in OCD#463 on file to be used in event the operator is unable to be here to safe the instrument themselves. Some CDS representative must be reachable by phone prior to execution.
|Before||Will safe prior to a maneuver ONLY if the fuel estimate of the burns is > 2000 grams. Safing is performed by FOT sending f_fl_m_safe.|
|After||Recovers by FOT sending f_fl_man_mnvrec at least 6 hours after last thruster fire|
|Old Notes||There also exist RCR's: f_mtof_safe.pcs and f_mtof_mcp110.pcs|
|Before||If fuel usage is above 100g, FOT will safe STOF with delayed command load CEL_ESR_SAFE.DEL.|
|After||Recovers via delayed command load CEL#_RECOVR.DEL sent by the FOT at least 6 hours after burns.|
|Old Notes||Have been using CEL_ESR_SAFE.DEL for safing lately, but may also choose to send a normal load.|
|CEPAC||Not sensitive to thruster operations. If MDI closes its door, LION needs to be turned off first.|
|GOLF||Not sensitive to thruster operations.|
|LASCO||Before||Will close the C2 and C3 doors via FOT TSTOL l_fl_safelasco. They will close their doors prior to CDS and UVCS closing their doors. The experiment offpoint warning function is disabled (Maneuver Preparation Script, Step 4) before the maneuver, though the team may request disabling at another time via RPR or OCD.|
|After||Recovery via NRT or l_fl_recoverlasco.prc if it exists. Wait 1 hour after CDS and UVCS doors are open. LASCO is to be added to the experiment off-pointing function following the burns, but prior to opening their doors (Maneuver End, Step 5).|
|Old Notes|| Door opening/closing is co-ordinated with CDS & UVCS so to avoid insulation particles
thrown from (or shaken loose by) CDS & UVCS when CDS & UVCS closes their doors.
If the LASCO operator is not present, the FOT can send the following procedure: l_set_esr to close the LASCO doors - however a LASCO representative should be contacted via phone prior.
|EIT||Not sensitive to thruster operations.|
|MDI||Before||The MDI ISS loop must be opened prior to any thruster activities. This can be performed either via NRT commanding, or by the FOT after notifying MDI team (Maneuver Preparation Script, Step 4). The experiment offpoint warning function is disabled in the next script line. This should only be done after the ISS loop is open.|
|After||After the offpoint flag has been enabled (Maneuver End Script, Step 5), the MDI ISS loop should be closed. This can be performed either via NRT commanding, or by the FOT, upon MDI approval.|
|Notes|| VC2 telemetry is * not * required to open and close the ISS loop.
TSTOL procedures that can be used for opening/closing the ISS loop are: m_fl_issopen, m_fl_issclos.
In the past, MDI used to perform "jitter tests" during momentum
managements which required VC2 telemetry and NRT for them to
command and manually open their loop. These jitter tests
are no longer performed.
|SUMER||Before||Will close aperture door and turn detector high voltage off, via NRT commanding. Thirty minutes of NRT is needed if enabled. The experiment offpoint warning function is disabled (Maneuver Preparation Script, Step 4) before the maneuver, though a team may request disabling at another time via RPR or OCD.|
|After||If resuming observations, SUMER should be added to the experiment off-pointing function (Maneuver End Script, Step 5). Opens door and turns on detector high voltage no sooner than 12 - 24 hours after the last burn, depending on the amount of fuel used. At least 30 minutes of NRT commanding is needed.|
|Notes||If SUMER operator is not present, the FOT can send the following command: /SBSESR . This mimics an ESR response and is preferred rather than the other procedures: s_fl_safe and s_fl_emergen . However, this is "not official" and we should have SUMER write an OCD for this, if an early morning safing should ever occur again (doubtful).|
|SWAN||Before||If SK/MM are done: will be placed in launch lock position using the TSTOL procedure n_fl_llockin and will use ESR limit set (Maneuver Preparation Script, Step 3). IF ONLY A ROLL WILL HAPPEN, skip all this.|
|After|| If SK/MM are done: no sooner than 2 hours after the last burn, return to
nominal limit set, run TSTOL procedure n_fl_llockout, and run
TSTOL procedure n_fl_manrec (Maneuver End Script, Step 6).
|Notes||If SWAN has a bad motor offset they can send a delayed command to put them in IDLE (with the heaters still on) and then they can send a delayed command to restart things - SOC would do OCD's|
|UVCS||Before||After LASCO is safed, UVCS will safe. Refer to U-08 for safing. If under 100g of fuel, UVCS will be safed via TSTOL u_fl_hvoff.prc that will determine which detector is on and turn off its high voltage. If over 100g of fuel, UVCS will be safed by the FOT triggering the PATROL function which will do a hard-safe and close the door. UVCS can safe the instrument via NRT commanding in about 45 minutes.|
|After||UVCS will recover via NRT for either method of safing. If safed by u_fl_hvoff.prc, they will recover at a later time.|
|Old Notes||In this past, the following was done: Due to the expected S/C sun-center off-set during past momentum management maneuvers, the UVCS sun-sensors are expected to trigger the safing loop that switches the UVCS s/w mode from OPS to SAFE. This safing loop will be left armed during the momentum management for test purposes. At the time that the loop will activate, no change in the UVCS status will occur, in that the instrument will be already in safe configuration (e.g., HVPS off). However, for test purposes, they like to check the change of s/w mode (TLM mnemonic: USMD) in their telemetry data.|
|VIRGO|| Not sensitive to thruster operations.
Note: If VIRGO ever wanted to close SPM and PMO covers, the FOT would run the procedure v_fl_covclose.prc