Документ взят из кэша поисковой машины. Адрес оригинального документа : http://www.apo.nmsu.edu/Telescopes/SDSS/shakedown5.html
Дата изменения: Thu Mar 30 18:50:22 2000
Дата индексирования: Sat Apr 9 22:56:11 2016
Кодировка:

Поисковые слова: mercury program
SDSS Shakedown Tests

SDSS Shakedown Tests

The SDSS Observers

0   Introduction

0.1  Scope and Goals

The purpose of the SDSS shakedown tests is to ensure that the 2.5 meter telescope, its instruments and instrument handling systems are operational after an extended shutdown, or after repairs or changes to systems. Tests are broken down by different instruments and their systems. After an extended shutdown, we recommend that all of the tests described here be performed. After engineering modifications to one or a few systems, a subset of tests should be selected from those listed here.

0.2  Pre-test Requirements

Prior to testing, we require that certain maintenance procedures be completed. These include, but are not limited to:
  1. The primary and secondary mirrors must be cleaned.
  2. The optics must be collimated.
  3. The fiducials must be cleaned.
  4. The telescope must be balanced.

1  Primary Mirror

  1. Run Yorke Brown's diagnostic program to check the system voltages.
  2. Check the MIGs against historical values.
  3. Check the dessicant condition, and look for condensed water in the lines.
  4. Check air pressure gauge and vacuum gauge values.
  5. Investigate the mirror oscillation problem and address as needed. Check MIGS at various altitudes to see if oscillations can be induced.

2  Secondary Mirror

The following are taken from R. Owen's document ``Mirror Control Checkout''
  1. Test the limit switches.
  2. Home, test and center the transverse actuators.
  3. Home, test and center the axial actuators.
  4. Move individual actuators and check that the correct actuator moves.
  5. Manually trigger over-force switches during a move.

3  Interlocks

Many of these tests can be made concurrently with other system tests. Robert Lupton's interlock display tool will be needed to see if the PLC is getting all interlock information. Many variable names were changed during the interlock upgrades. Both the interlock display tool and the MCP code need to be modified accordingly.

3.1  Positive Tests

These are tests where soft limits are purposefully defeated to ensure that they work.
  1. Check that all switches report proper status. A list of all switches, their functions, soft and hard limits, physical locations and logical names is needed.
  2. Run the telescope to soft limits in all axes. Can we back off the limits with the MCP?
  3. Check that e-stops are functional. Check the lights on the interlock chassis.
  4. Find out which interlocks cannot be overridden. Check override status on all interlocks.
  5. Check and record current stow position.

3.2  Negative Tests

These are tests that can be run concurrently with other system tests. If a problem is encountered, see if it is repeatable and document it. Did the PLC register the problem?

4  MCP

4.1  From the MCP Menu

  1. Set and clear the brakes in both Az and Alt. Make sure the brakes engage and clear properly.
  2. Move the telescope 2-3 degrees using the j and k commands in increments of 1000, 5000 and 10,000 counts. Change the increment while the telescope is moving as well as setting the increment before starting telescope motion. Do this for Alt, Az and Rot axes.
  3. Move the telescope to 10 ° , 30 ° , 90 ° (Alt, Az and rotator) and 120 ° (Az and rotator only) using the destination commands at various velocities (100,000, 150,000, 200,000 counts as well as 250,000 counts for the rotator). Moves should be tried in both the clockwise and counterclockwise directions.
  4. Use the hold command to stop telescope motion in increasing and decreasing directions for moves in Alt, Az and Rot. Do not use ``h'' for calculated moves (i.e., when using the ``d'' followed by''m'' commands).
  5. Use the stop command to stop telescope motion in increasing and decreasing directions for moves in Alt, Az and Rot. (Brakes should engage when stopping motion in Alt and Az?)
  6. Cross primary fiducial in all three axes (Az, Alt, Rot) and make sure the fiducial is read and the position is set properly.
  7. Cross primary fiducial in each axis (Az, Alt, Rot) several times using the ``j'' command (increasing direction) at an increment of 10,000 counts and make sure the position changes less than 1 arcsec between fiducial settings (after the initial fiducial setting).
  8. Cross all fiducials in all three axes to verify that all fiducials are functional. Compare the logged fiducial values to historical ones.
  9. Test setting the counterweights using the ``!'', ``@'', ``#'', ``$'', ``^'' commands. Counterweights should be commanded to higher and lower positions.
  10. Test the ``%'' command for testing the command for stopping counterweight motion. Attempt aborting moves commanded using the ``!'', ``@'', ``#'', ``$'' and ``^'' commands. Abort counterweight moves in the increasing and decreasing directions.
  11. Test the ``w'' command to check that the proper instrument counterweight values are read from the MCP lookup table.
  12. Test that the alignment clamp engages and disengages properly, using the ``+'' and ``-`` commands. Check that the interlock display shows the correct status.

4.2  From the TCC Interface

  1. Axis init to see if brakes clear. Axis status should return TCC and AXIS positions.
  2. Make several slews in both clockwise and counterclockwise directions for Az and increasing and decreasing directions for Alt. Use the following coordinate systems: mount, observer, fk5.
  3. Issue an axis stop after axis init and while tracking. Motion should stop but brakes should not come on.
  4. Issue an axis stop while slewing in both directions for the Az and Alt axes. Make slews of 40 ° and issue axis stop after slewing 10 ° , 20 ° and 30 ° . The telescope should coast < 2 ° before stopping.
  5. Hit an E-stop axis init, during a slew and while tracking. Brakes should engage.
  6. Let telescope track for an hour near zenith and 15 degrees from the rails ( @ 35 ° Alt) in the following coordinates: observer and fk5.
  7. Use the offset object and offset calib commands to offset in Az, Alt and Rot by these increments: +/- .01, .1, .2, .3, .4, .5, 1, 2, 5 ° . Observer should watch the Alt offsets carefully to see if the telescope hits the wind baffle.
  8. Use the rotator object and rotator calib commands to offset the Rotator by these increments: +/- .01, .1, .2, .3, .4, .5, 1, 2, 5 ° .
  9. Try offsetting in a diamond pattern as SOP tries to do when calculating an instrument block for guiding. This test should be tried right after an MCP reboot and after the telescope has been tracking/slewing for several hours. (After a full night's observing would be ideal.)

4.3  Balance Test

This test should be executed with the TPM logging all servo system data. The voltages of the servos should give us an idea how well the telescope is balanced at each position.

Command the MCP (via the Menu interface) to the following positions in Alt: 10 ° , 15 ° , 30 ° , 45 ° , 60 ° , 75 ° , 90 ° . At each of these positions, exit the Menu and start the TCC, issue an axis init from the TCC. The telescope should not fall or rise. If it does the brake should engage. Note how many degrees the telescope moved before the brakes engaged (use axis status). Reissue the axis init command and see if the telescope rises and falls. Record the number of degrees it moved if it did. Exit the TCC and return to the MCP Menu. Use the ``j'' and ``k'' commands to move the telescope a few minutes of arc in the increasing and decreasing directions in increments of 1,000 counts.

5  TCC

  1. Check that show status commands give realistic information.
  2. Check that the track command works.
  3. Check that the guide command works.
  4. Test that the mirrors can be moved from the TCC.
  5. Test that the flat field system works, especially the flat field screen.
  6. Check that offset commands work.
  7. Request slew positions beyond soft limits. Check that they are rejected.

6  Wind Baffle Motion Control

  1. Move the telescope from the MCP Menu and the TCC. Does the wind baffle follow?
  2. Check that the wind screen forces telescope motion in manual mode. Make sure telescope can return to stow position.
  3. Change the acceleration and jerk values. Can the wind baffle keep up?

7  Counterweights

  1. Check that each moves from the MCP.
  2. Check that each can be moved from the controls in the lower enclosure.
  3. Check that the limit switches are operational.
  4. Check that the different instrument positions look correct.

8  Engineering Camera

  1. Aliveness test: Hook up all connections and take bias/dark frames.
  2. Try to use image acquisition and display tools.
  3. Check that we can talk to the camera stage and make the camera move.
  4. Mount the camera.
  5. Verify that the values in the instrument block are good.
  6. Take a star image. Check that we can centroid.
  7. Take a pointing model.
  8. Check tracking and jitter with the engineering camera in video mode.

9  TPM

  1. Monitor different systems using the Real-Time Display tools, systematically changing as many of the parameters as possible.

  2. Critical Systems include, at a minimum, motor currents, mirror position, axis position.
  3. Check that TPM can log data correctly, using both the real-time and TPM log archive display tools.

10  Imager

Note: We need release notes/list of changes to IOP and AstroDA as of Jan 24, 2000.
  1. Verify that the lift and mounting systems are operational.
  2. Check that we can talk to the imager.
  3. Verify that the values in the instrument block are good.
  4. Check that the focus loop can be activated.
  5. Check that frames are written to pool and tape properly.
  6. Take >= 20 bias frames daily, once the camera is cold, and ship tapes to FNAL for analysis, following standard tape delivery methods.
  7. Drift scan while parked. Ship tapes to FNAL for reduction, following standard tape delivery methods.
  8. Do a powered equatorial drift scan. Items5 and 6 should be the same FASTT field. Ship tapes to FNAL for reduction, following standard tape delivery methods. Also, have data analyzed by Munn at USNO.
  9. Do an off-equatorial drift scan. Ship tapes to FNAL for reduction, following standard tape delivery methods.
  10. Do a backwards scan. Ship tapes to FNAL for reduction, following standard tape delivery methods.
  11. Complete three 2-hour imaging runs and ship tapes to FNAL following standard tape delivery methods. Upon acknowledgement from FNAL that reduction was successful, complete one 8-hour scan and ship tapes to FNAL for reduction, following standard tape delivery methods.

11  Spectrographs

  1. Verify that the lift and mounting systems are operational.
  2. Do a cartridge fit test for each cartridge plus corrector.
  3. Verify that the values in the instrument block are good.
  4. Check mechanicals (slit head doors, latches, Hartmann screen, shutters, etc).
  5. Check DA by taking biases/darks (for a baseline against SOP modifications).
  6. Verify that bias and dark counts are normal. Take >= 20 biases and 5 darks of 15 minutes each, at night, as soon as the spectrographs are pumped and cooled. Ship tapes immediately to FNAL for analysis disribution.
  7. Check for light leaks. Take 15 minute dark frames with:

  8. a) shutter closed, Hartmann mask in place.
    b) shutter open, Hartmann mask in place.
    c) shutter open, no Hartmann mask.
  9. Check that flat-field screen and lamps are operational.
  10. With the secondary in place, take a sequence of arc lamps at different times after lamps are turned on, to determine optimal lamp warm-up time.
  11. With the secondary in place, take a sequence of flats at different times after flat lamps are turned on, to determine optimal lamp warm-up time.
  12. Take sparse-fiber flats to determine spatial profiles. Repeat with collimator out-of-focus.
  13. Check that we can slew to a field and acquire stars down fibers.
  14. Check that we can guide.
  15. Check that we can get real data-quality spectra. Ship tapes to FNAL following standard tape delivery methods for pipeline reduction.

12  Follow-Up

At the end of each night, a summary of the tests that were performed and their results will be included in the observers' night log. Any problems that were encountered will also be noted therein. In addition, problem reports will be filed through the SDSS Bug Database on the same night that problems are discovered. Any test results or analyses completed after the night log is filed will be sent, immediately upon completion, to the same distribution list as the night log, and filed as an addendum to the night log. This assures that all interested parties will have ready access to the information.

When all tests have been completed for a given telescope system, the night logs will be compiled and a report will be written.


File translated from TEX by TTH, version 2.60.
On 25 Jan 2000, 18:25.