Instrument Operations

On this Page:

• Resources
• Scripts and Tables
• STOLs
• Clocks
• Weekly Calibrations
• Semi-Regular Operations
• HMI Retunes
• HMI Heater Adjustments
• Regulus Offpoint
• Spacecraft Calibrations and maneuvers

Resources

• JSOC Operations Overview
• Documents Directory
• Commanding Tutorial/Refresher
• How to find corrupt images via Lookdata
• Secrets of the clock plots

Scripts and Tables

• AIA Script list
• HMI Script list
• How to upload scripts and tables
• Script system user's guide
• Deconstruction of an HMI script

Canceling a timed script

To cancel a sript, the command is:
/[AIA/HMI]_SS_CONFIGURE ABORT=SELECTED SELECTED=####
Where "####" is the number of the script you wish to abort.

The safest way to cancel a script is to do it via STOL, following these steps:


1. In the EGSE console, enter
   perf aia_ops
2. Select "Set up or cancel a timed script"
3. Select "Get script system info" You will get a log file with the currently loaded timed scripts:

READ Active Script Slot Info:
TIMED SLOT=1 SCRIPT=3106 SECS=1691612434 MSECS=0 ERROR=SUCCESS LINE=0
TIMED SLOT=2 SCRIPT=3102 SECS=1691612734 MSECS=0 ERROR=SUCCESS LINE=0
TIMED SLOT=0 SCRIPT=3104 SECS=1691611234 MSECS=0 ERROR=SUCCESS LINE=0
4. Click "Script Number: " and enter the script number
5. Click "Send Command to Abort Script ####", where #### is the script number you entered.
6. Repeat for each script you wish to cancel. Each cancellation command will be echoed in your log file:

/AIA_SS_CONFIGURE ABORT=SELECTED SELECT=3104
7. Get script system info again. the output for a cancelled script should look like this:
   
   ERROR SLOT=0 SCRIPT=3104 SECS=1691611234 MSECS=0 ERROR=SS_ABORTED LINE=0
8. Log whatever you did in the H&S blog

File system issue

• 19-Dec-2011 at 19:29:30 UTC Author: Paul
  Also, we uploaded a new version of the synop_dk framelist that uses AEC type 1 to specify the dark frame exposure time. It should take effect during today's daily darks.
  In the process, we discovered that an old version of A_SYN_12.GZ (which contains the framelists used for the standard synoptic and daily darks) was in onboard RAM (both 1.7 and 1.10 were on board). When we uploaded version 1.11, it deleted 1.10 and allowed us to post the new version, but it still had the old version there. We "manually" deleted it (by issuing the ERASE_RAM command without the wild card), so now there is only one version of A_SYN_12 on board. Not sure how we got to have two there; might be worth checking with Gary.
• Gary says: "I think you are allowed to have multiple versions of the same filename. I think the childname error only occurs if the name (including version number) are the same. The only funny here seems to be why the wildcard erase did not get the 1.7 version. I wonder if somehow the * did not pick up the single digit 7."
• Action: Look at sdo_dir history to see where the second version was loaded. Then look in the log files to see what happened to allow that. Test on the testbed to see if child name error is generated with different file versions, and if wildcard erase gets confused by single digit numbers, or if it really only erases the latest one.

HMI File System Conventions

FTS table

• The FTS table (H_FTS_V0#) is updated in version number whenever lines are removed. If lines are added, the same version number is used.
• Once a framelist is assigned to an FTS ID number in the FTS table, it cannot be changed. You Can remove that line from the FTS table, or rename the framelist and assign it to a different number, but you cannot reassign the ID to a different framelist.

STOLs

• Useful HMI STOLs (not comprehensive).
• Useful AIA STOLs (not comprehensive).
• The most up-todate version of the EGSE User's Guide can be found on the JSOC-IOC machines at /egsesw/egse/tasks/EGSE_User_Guide.pdf

upload_to_stol

• Directions for running upload_to_stol can be found here: How to upload scripts and tables.
• HMI tuning updates (or the H_TUNE load for HMI retunes ) are now done on the Linux workstations.

Earlier issues with the old Sun workstations required a different version of upload_to_stol for HMI tuning updates. Previous versions of software may be checked out of CVS, if needed, using the -r switch:
• > cd ~/stol_users/username/UPLOADS/TOOLS
• > cvs update -r 1.117 upload_to_stol.spp
• > make update

Clocks

• Adjust the clock drift rates to keep the time difference as close to 0 as possible.
• An increase of 1 DN will speed up the clock oscillator, causing a time difference delta of about +10 ms/day.
• A decrease of 1 DN will slow down the oscillator, causing a time difference delta of about -10 ms/day.
• If you want the plot to go down, lower the increment, if you want the plot to go up, increase the increment.
• Here is how to adjust the clock increment rates.
• The clock oscillator is temperature-sensitive.
• Colder temperatures make the oscillator speed up, thus increasing the time difference. This happens during offpoint maneuvers or eclipses, when solar radiation is blocked or limited, or if mechanisms that usually run are not running (like if one of the ATAs stops taking pictures during a bakeout).
• Warmer temperatures make the oscillator slow down, decreasing the time difference. This happens if temperatures are directly increased, or if mechanisms are working more or faster than usual, like for a special sequence.
• For detailed physics information, see the HMI Timing Verification Report here.
• Here is how the clock plots work.
• There are no EGSE or ANS limits on the clock drift, because it is computed for many different telemetry points. There IS a limit on the Spacecraft clock drift. (yellow at +/- 35 ms, red at +/- 50 ms).
• The clocks go especially crazy during eclipse season because they react to the battery voltage change and to the fluctuating temperatures. Here is more information on that.

Weekly Calibrations

Resources

Semi-Regular Operations

HMI Retune

• When necessary (about bi-annually) HMI retunes are performed during EVE Cruciform maneuvers.
• Use the HMI Retune procedure, which needs to be printed out and filled in with appropriate values for each retune.
• A retune requires a new flight_v0#.s and flight_v0#.w table. These are run through upload_to_stol together to make a new H_TUNE_V0# load.
  • See notes on upload_to_stol for special directions about making the retune load.
• The .w table contains the tuning numbers for HWL[1234]POS (which can be seen in lookdata):



• The numbers in the .s table correspond to the first column "Id" in the .w file. The WT1P, WT2P, etc. values can be verified in Lookdata:





• The wlt_id change can be verified in IDL by plotting 'HMI_SEQ_ID_WLT':

HMI Heater adjustments

• Managing HMI Heater Zones

HMI Regulus Offpoint

• Regulus Offpoint Memo with required camera settings for the Regulus framelist. IMPORTANT!

Spacecraft Calibrations and Maneuvers