Current Status of Each SOHO Instrument

First Version:
15 February 2006, Zamkoff & Haugan

Updated:
05 October 2007, Westenburger
08 March 2006, Zamkoff
09 March 2006, Zamkoff - final first version
09 March 2006, Zamkoff - CDS & UVCS QT increase due to UVCS current, LASCO QT increase for EIT bakeouts
24 March 2006, Zamkoff - make it html document and change document name
13 December 2006, Zamkoff - add SUMER detector A status and heaters on, MDI seeing SUMER temps, MDI on redundant TM/TC channel
17 July 2007, Zamkoff - change SWAN procedures for ESR
early October 2007, Gavin - added new TSTOLs info
16 October 2007, Zamkoff - change SWAN procedures with details on maneuvers, rolls
9 Jan 2009 EBZ - change GOLF heater 69 to be off
1 May 2009 EBZ - updated SUMER and LASCO
17 June 2009 EBZ - updated Exp LCL Mon note at bottom
22 June 2009 EBZ - Added note to UVCS about the LASCO debris issue
13 July 2009 EBZ - Added note about GOLF violation in Low Rate
30 July 2009 EBZ - Added note about C1 and FP for LASCO
25 Aug 2009 EBZ - Added note about ERNE BIAS2
09 Nov 2009 EBZ - Added note about new LASCO/EIT std mon channels

• Gets daily pulse and 2048 Hz signal
• Has 12.8 and 25.6 hour telemetry redundancy
• Closes PMOA covers often for cals, sometimes opens PMOB cover for cross cals - doors clang rather than a smooth motion
• Uses PMOB sparingly to save lifetime
• No internal clock so the science telemetry has no timestamp - there is an X in the .REL data files and the files have the received (ground) time in them instead of the observation time
• Uses TT commands only since they have no internal computer
• Sends a weekly delayed load of TT commands
• Commands sent only 1 per 6 minutes if you wait for verification because it has a 3 minute cycle
• If RTU reconfig, tell VIRGO because it messes up their timing
• No heater control - PLM does it
• Doesn't safe for maneuvers
• Doesn't receive ESR flag but FOT does some procedures when in ESR
• Doesn't like to be at non-nominal pointing for more than 16 hours for data continuity
• Don't close LOI door
• 2 types of latchup: instrument and DAS. Instrument will not fix itself and V02 must be run. DAS is false reading or power problem.

• Gets daily pulse
• All HK data is included in science telemetry
• Not sensitive to offpointing on the order of a few arcseconds
• Has 8 and 16 hour telemetry redundancy, but the 8 hour redundancy is movable and was moved to 12.8 to match VIRGO then moved back to 8
• Doesn't safe for maneuvers
• Receives ESR flag but doesn't respond
• GOLF ignores OBT except during turn-on procedure. If GOLF is turned off, it needs the OBT and that will reset it
• Door open since halo insertion
• No OBT in ESR as of 7/22/03
• Mechanisms are stuck so they are observing the blue wing only (as of October 2002). Quarter Wave Plate and Linear Polarizer electronics turned off (as of April 2005), so substitution heater (circuit 68) on at 30% (x_exp_prep_on now turns heater to 30% and does not enable substitution heater monitoring)
• Doesn't like to be at non-nominal pointing for more than 16 hours for data continuity
• When we transition to Low Rate (like in ESR), GTREARAD violates red high (probably ground system error)

• Doesn't observe often now (10-20%) - doors closed, high voltage low, ESR and offpoing flag disabled
• Can open doors two ways - the second one is to blow it open with explosive bolts - they may want to try this at the end of the mission
• Safes for maneuvers
• Receives ESR flag and safes
• Receives Offpoint flag and safes
• Detector decreased sensitivity - photons
• Detector high voltages ramped down and door closed when not observing
• Somewhat fixed in E/W direction because scanning mechanism degraded (operating in high current mode now) and it skips steps (Det A&B)
• Cross Delay Line (XDL) detector electronics not working properly - multiple rows of counts are accumulated in a single row - Det A
• Wavelength calibrations are very temperature sensitive - once we were in CRP and SUMER changed wavelengths and the offpoint flag was sent
• Detectors have virgin pixels that can be used
• Temps (including QTSI2A/B) drop when reboot
• If door closed when reboot, QTSI1B drops and may hit RL - run S02
• SUMER OBT jumps every 6-9 months and requires NRT to fix - RCR
• If a reboot & s_fl_safe.prc is performed with SUMER doors open, we can expect STMC4T3 to flag YH (25.2 C), which is at the top of the calibration curve for this mnemonic (originally it was higher but that didn't make sense - it was changed by OCD September 10, 2004). Some time after the safing, the temperature should return to green (b/c doors are closed). SIDEFL will flag YL after s_fl_safe (see email from 18 Oct 2005 for more info).
• SUMER changing mirror positions spikes MDI PZTs
• Used to have a default "emergency study" that kicks in after 30 mintues of being idle - not used now
• Can take data in submode 6 where it is stored in the on-board buffer and it is automatically downlinked as soon as we get to submode 5 thanks to a command sent during submode change (buffer is automatically downlinked when SUMER gets telemetry)
• Detector A is declared dead as of Nov 2006. Both detectors will be kept off when SUMER is not observing and substitution heater #82 is on at 30%
• SUMER TDC off spikes MDI PZTs
• Raster scan mechanism degradation during April 2009 campaign - sit and stare studies only, but pointing still possible

• Is on special OBT distribution list
• Has a config mon for motor current problem to notify MDI if violations
• Needs OBT after RTU reset
• Has ISS loop to have accurate pointing - self corrects via PZTs
• Structure will need to be restarted after going to Low Rate or RTU reset
• ISS loop needs to be open during large movements or maneuvers to avoid repeated banging of mirror
• Sees jitter from movements such as UVCS fast roll
• PZTs spike for certain things like SUMER mirror movement and CDS cals
• MIAEMTR motor current can get stuck - FOT monitor this with a config mon and there is a contingency script for it
• Runs 12.6 minute calibration of page dumps, cals, stored mags dump at start of transition to VC2 from IDLE
• Shutter was wearing out but it improved probably because there was a stuck particle that was ground down
• VC2 transition rules are complicated
• Do leg alignment prior to maneuvers
• Leg alignment may have lost steps (Oct 28 2005) - team is monitoring
• Runs a program for a very long time without needing to command
• Does monthly calibrations
• Has special requirements during continuous contact periods
• ESR - ISS loop is opened, structure is stopped, VCID is set to 0
• Maneuvers - ISS loop is opened automatically and manually by FOT - it is useful to send open loop command two times in case the first time doesn't stay because it was during an ALT mag so the command was lost
• Offpoint flag opens ISS loop
• MDI can send time tagged loads requiring special treatment from the FOT so we need to alert Gary when they come in - no OCD is needed
• FOT & MDI have twice seen a funny telemetry glitch/limit violation when doing limb figure delayed command load
• MDI sees a signature in their PZTs when SUMER TDC is cold
• MDI switched to redundant TM/TC channels in July 2006

• NIS/GIS glitches - detectors have high currents caused by outgassing - need to turn off voltages and gradually turn on to see if okay
• Have emergency study that should always be loaded that kicks in if instrument is idle for 1 hour
• FF calibration is not dedicated commanding - just no pauses
• Does monthly calibrations - lube study and FF cal (burn in)
• MCP high voltage CUVMCP problem - if too high it is most likely a faulty reading and will most likely return to green soon (GIS studies may cause prolonged readings)
• CDS synoptic causes a shadow onto the front part of the spacecraft that causes the front plate to have thermal flexing where the FPSS is (MDI sees this in their PZTs)
• Doors clang
• ESR - placed in emergency standby mode and FOT need to turn on heaters
• Maneuvers - safe by going to ready both mode, leaving on high voltages, point at sun center, close door
• Proton storms - turn off high voltage to NIS, has continuous CCD readout, GIS only if really bad
• Must wait 24 hours after last burn before opening door
• Door can only be opened or closed if LASCO is shut first (due to clang)
• CTM18 slit motor temperature - this is high because the position sensor is failing and the motor keeps trying to move - use open loop control now
• If command and control processor hangs, reboot is needed and reload tables and do checks and engineering
• GIS stepper motor skips steps
• Has internal ground limit alarm checking that isn't often monitored
• Snooze mode changes to standby in 3 minutes unless a command is sent
• 5% padding in plan for timing uncertainties in study duration
• Commands via internal time tag sequence onboard
• Lube study spikes MDI PZTs
• Door opening sometimes causes spacecraft wheel torque demand errors
• If UVCS draws extra current during safing, their electronics box gets warmer and the thermistor for UVCS and CDS near there is warmer (QTUR2 and QTCR3)

• Is on special OBT distribution list
• Gets OBT daily because clock is sometimes off
• They can have a time glitch in their data - we take no action except to tell Patty, Luis, and SWAN team
• When an ESR flag is received and SWAN has not been previously safed via the n_fl_llockin procedure (as is typical prior to a maneuver), both sensors will go into launch lock position. Note: n_fl_esrllin may not always work if their motor position calibration is off. 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
• n_fl_esrllin, n_fl_llockin, and n_fl_disabrest have been changed with adjusted NBSEQ1 parameters intended to prevent automatic observation restart after 48 hours. The values in n_fl_llockin, n_fl_esrllin, and n_fl_disabrest have been adjusted through the end of 2015
• SWAN will not reset itself if in launch lock for more than 48 hours.
• Does star observations to calibrate sensor sensitivity variations - likes the 180 degree roll for cross calibration of +/- Z sensors
• If the attitude if off, SWAN autonomously turns off the high voltage to its sensors
• FOT safes SWAN for maneuvers, don't recover until 2 hours after the burn
• SWAN isn't safed for rolls but does calibrations instead

• Is on special OBT distribution list
• LION must be turned off when the MDI door closes
• ESU Data Request Error often - H-07 is run for autonomous recovery
• ERNE warm, turned off xpanel heater
• EPHIN front detector shows leakage current
• Anomalies of Types 1 and 2 - type 1 can be recovered automatically, type 2 requires an ESU reset (H-09)
• EPHIN degredation over time because it is a semiconductor and MLI degrading too - temperatures increasing
• Gets ESR flag but has no response
• Not sensitive to thruster firings
• Running on BIAS2 (back up bias HED current) - Aug 2009

• Is on special OBT distribution list
• Not using CTOF (it is in manual mode) but uses telemetry elsewhere
• Gets OBT daily
• Heaters need to be on if sensors off
• ESR response can be set
• Gets ESR flag but ignores it and later FOT sends safing load
• Maneuvers - CTOF and MTOF safe only if huge burn (MTOF via NRT and CTOF via delayed command), STOF safes via delayed command most of the time when > 100 grams of fuel (TBC)
• CELIAS is sensitive to roll because of their opening angle and thus are slightly less sensitive to solar wind shocks when upside down

• Is on special OBT distribution list
• Door opening sometimes causes spacecraft wheel torque demand error
• Has config mons for nominal operations versus Lyman alpha detector ops
• Has a separate limits set for Lyman alpha detector
• Gets OBT monthly
• Degredation is from coating on MCPs wearing off and the MCP pores have wear
• XDL problems like SUMER - multiple rows of counts are accumulated in a single row
• Not using VLD
• Don't often use Lyman-aplha detector because MCP in Lyman-alpha has an increase in dark current that causes an increase in temperature that causes an increase in the mobility of impurities that causes an increase in dark current, etc (note: this is older information, LyA is used periodically)
• Problem of false telemetry readings - seen most often during ramping
• Ramps down their high voltage to load a detector mask
• Mask loads are not dedicated commanding
• Has automatic safing - turns off high voltage and enters software safe mode
• Maneuver and proton storm safing via NRT - rolls to engineering east, mirror is moved to 1.5Rs, occulter is moved to 1.7Rs, ramp down high voltages, partly close door, slits set to 100 microns, put into standby mode
• Gets ESR flag and doors close, detectors turned off - they get cold so FOT turns on their substitution heaters
• Offpoint flag turns off high voltages and enters software safe mode
• If they draw extra current during safing, their electronics box gets warmer and the thermistor for UVCS and CDS near there is warmer (QTUR2 and QTCR3)
• LASCO may see debris when door open/close so tell them

• Nov 2009 2 new std mon channels to reboot LASCO if sector wheel hang, and local team has 8 new RCRs to turn on/off these channels
• As of July 2009, C1 is on but the FP is off
• Is on special OBT distribution list
• Has sector wheel config mon
• Not using C1 because broken
• Has a bad clock - send an RCR to get OBT before each NRT session
• LSESWMOT violates when doors closing/opening - must be put on limit sheet for EIT bakeout
• LEB memory problem with calibrations (from Dec 05) - a portion of high address image buffer memory does not work (not telemetry buffer) - and LASCO had ground software version problems too
• Offpoint flag response is that the doors step closed but not all the way and the command queue flushes and no images taken
• Maneuvers - LASCO doors closed, EIT left observing - doors open 24 hours after last burn
• LASCO doors must be closed before CDS can do any door action
• ESR response is that LASCO doors are stepped closed but don't close all the way and command buffer flushes and no images taken - NRT is given to restart EIT observations and close LASCO doors and should be removed from ESR flag
• If LASCO/EIT is removed from the ESR warning flag list, they should always load a full resolution plan. Otherwise, subsequent ESRs will not flush, EIT will get behind, and when trying to catch up it may become overheated.
• Has an emergency study of 1 command that takes 195, C2, 195, C3, etc. to repeat for a long time
• Buffer takes about one hour to fully empty
• EIT does bakeouts to correct burn-in
• EIT sector wheel hang - an interprocessor communication issue where the motor stays energized, overheats, and needs a reboot to be cleared
• LEB has some problems and needs rebooting sometimes
• QTLI1A,1B,3A,3B all increase during EIT bakeouts
• Closes doors for UVCS door openings (and maybe closings) due to debris (Apr 2009)