Review the history log for any error messages generated by the instrument.
Relevant entries will be located under the "Error Table" heading.
If an error exists select "Yes". If it is a concern, copy the error message into the comments section along with any other
relevant information. (If there are multiple copies of the same error you only need to include one example).
Additional Information:
When filling out the checklist early in a UT day (late in a California night), be sure to look back to the previous UT day to check for information from the last 12 hours.
Error messages may have also generated a MOC ANS alert (see #3).
Review the history log for any limit violation messages.
Each limit violation notification will contain a limit type (yellow or red and high or low), the time at which the violation was
detected, and a message regarding which limit was violated.
If a limit violation occurred select "Yes" and copy the notification into the comments section along with any other relevant
information. If there are multiple copies of the same error you only need to include one example.
Additional Information:
When filling out the checklist early in a UT day (late in a California night), be sure to look back to the previous UT day to check for information from the last 12 hours.
These limit violations may have also generated a MOC ANS alert (see # 3).
Review the email log for any MOC ANS alerts issued to the ANS phones during the period of interest.
These alerts are usually either instrument error messages or RDL limit violations.
If an alert exists, select "Yes". If it is a concern, copy it
into the comments section along with any other relevant information.
If you are carrying a phone, check that you received the alert.
Additional Information:
Weekly FOT test message alerts sent on Thursday at ~18:00 UT are standard, but should still be noted.
Weekly EGSE test message alerts are sent to the phones on Wednesdays, but do not show up in the email log
Review the HMI "Main Bus Current - Combined" plot on the 48 hour plots page.
A nominal current plot will appear like a noisy signal, varying on the order of ±1 A. The average of the noisy signal should be
about 3 A when the instrument is under nominal thermal control.
Verify that the plot is up to date, with the x-axis extending to within 30 minutes of the current time.
Nominal (as of 7/26/2010) current plot example:
Additional Information:
If the signal is not noisy, check that the operational heaters are on and the temperature zones are at the correct temperature.
A sharp increase in the average current would suggest either that a heater zone has switched to 100% duty cycle, or that there has been a short.
Review the HMI "Motor Currents" plot on the 48 hour plots page
The minimum current should remain low at ~ 4 mA.
If the minimum current is not low then either an encoder on one of the wheels has failed, causing the wheel to spin continuously, or a mechanism is stuck.
Additional Information:
If the maximum current is ~50 mA or less then the sequencer has probably been stopped.
The typical current for stuck HMI mechanisms (at 15 V) is shown in the table below:
Review the HMI "Clock Drift WRT Ground" plot on the 48 hour plots page.
The clock should be within 50 ms of the ground time and the
data should extend to within 30 minutes of the current time.
Additional Information:
The actual limit on the clock drift is ±100 ms WRT ground, but it is still worth noting if the delta is beyond ±50 ms.
Plots are shown in UT Time: UT Time = Local Time + 8 (or + 7 during Daylight Savings Time)
If the plot is not up to date:
The spacecraft time file is probably not being updated because there is an error with Shelby.
You can use the “Clock Drift WRT SC” plot to determine the delta with respect to the spacecraft.
If possible, check the spacecraft time on the ASIST page and note how far
off the spacecraft clock is WRT ground. The real clock delta is [HMI
WRT SC – SC WRT ground].
The spacecraft clock adjusts to zero periodically. These
adjustments are apparent on the plot and can be used to estimate the HMI clock's drift rate (see diagram below).
You may also use the Clock Adjust Log to estimate the current SC time if you do not have access to the ASIST page.
Review the HMI "Optical Bench Temperatures" plot on the 48 hour plots page.
During nominal operations this plot typically shows a slow sinusoidal signal with a period of approximately 24 hours.
Temperatures should hover around the target temperature, safely in between the deadband low and high temepratures. However, heater zone 4 (TS39) typically runs about two degrees warmer and is not currently controlling (as of 1/14/2011) because it is being driven by other zones.
Review the HMI "CCD Temperatures" plot on the 48 hour plots page
The CCD temperatures should be below -60 C and vary about ±2 degrees per day.
If there is a sharp increase in temperature please check the "Master Screen" or "Power Screen" on the HMI Screen Page to see if all of the decontamination heater relays are off.
Review the HMI "ISS Average PZTs (A, B, and C)" plot on the 48 hour plots page
If the ISS is centered, the PZT voltages should be within their respective limits (see table below).
Short spikes in the voltage are expected during calibrations (which are performed at 6:00 UT and 18:00 UT) and when a cal-mode flat is taken. (Note that the 48 hour plots subsample the telemetry and thus may miss spikes.)
Nominal limits are generally between 30 and 40 V. If any of the limits are exceeded, then a leg adjustment must be performed.
Additional Information:
PZT Voltage Limits for nominal operations:
PZT
Lower Limit
Upper Limit
A
15 V
53 V
B
20 V
47 V
C
23 V
48 V
Explanation: As the spacecraft or HMI pointing varies, the PZT voltages change to keep the image centered. If the voltages diverge too much (more than 5 V), then the dynamic range of the PZT has been reduced enough that the mirror is likely to hit the end of travel during the PZT flat fields. If the voltages diverge this much then a leg alignment is needed to bring the pointing back to nominal.
Nominal PZT average voltages plot:
Review the HMI "ISS Average Errors (Y and Z)" plot on the 48 hour plots page.
The values between 40-70 mV are the nominal residual offset voltages when the ISS loops are controlling. These voltages change when the ISS loops are opened or if the ISS is unable to remove all of the pointing error. If the error voltages are constant then the loops are closed.
Spikes are sometimes created by the two daily calibrations when the calibration image (position 17) is taken. However, during normal operations these lines should remain low, with perhaps 1 DN variation. If it is not low this may indicate that the loops are open, the pointing is off, or the ISS is not properly configured.
Click the pink "Images Off" and "Details Off" buttons to display details and images. (The buttons should now be green
and read "Images On" and "Details On").
Set both the details section and the images section to "HMI".
Check that the images are up-to-date. One way to do this is to look at the "Last DCS Recieved" time. The typical lag time is around 3 minutes, but it can be on the order of hours if something is wrong. It is worth noting if the lag time is beyond 5 or 10 minutes.
Scan down the images and check that they appear nominal.
If any of the three Datamin=0 lines at the bottom of the page are not green, then send an email to hek_local[at]lmsal[dot]com so the issue can be addressed.
Review the HMI "Sequencer Framelist ID" plot on the 48 hour plots page
The nominal science framelist is 1021.
Every twelve hours, at 6:00 UT and 18:00 UT, HMI makes a calibration run for 135 seconds, using FTS 2021. This is just a preliminary check to make sure the calibrations are running.
Check to see if the ANS System indicators (aia-tnc-ANS-AlertUp, hmi-gse-ANS-AlertUp, etc.) are all green. If any of them are yellow or red
please refer to the AIA03789 document: How to Restart the ANS and GSE Alert System.
Click the pink "Images Off" and "Details Off" buttons to display images. (The buttons should now be green
and read "Images On" and "Details On").
Check that the images are up-to-date. One way to do this is to look at the "Last DCS Recieved" time. The typical lag time is around 3 minutes, but it can be on the order of hours if something is wrong. It is worth noting if the lag time is beyond 5 or 10 minutes.
Scan down the details and check that the various wavelengths are represented with nominal exposure times. (You may need to increase the number of images displayed in the "Images = " box in order to see all wavelengths.)
Scan down the images and check that they appear nominal.
Check to see if all the content on the SunToday page looks nominal.
If anything does not look right, then please send an email to hek_local[at]lmsal[dot]com.
Note that if you see the message "Light Curves not available for this date" and it is close to UT 00:00, then it's probably ok.
