MODS Instrument Support Utility Programs

This page describes instrument support tools for MODS.

*These should never be run by observers except under the direct supervision of LBTO observing support or MODS team personnel.*

modsMask - Operate the Slit Mask System for Mask Exchanges

modsMask is used by support personnel to operate the slit mask mechanism during slit mask exchanges.

Usage: modsMask modsID cmdStr

where: modsID = 1 (MODS1) or 2 (MODS2)
       cmdStr = mask command to execute

Mask Commands:
   status - report the status of the mask system
   reset  - reset the mask system, leaving mask 1 at the load port.
   mask N - position mask N at the load port, N=1..24
   in     - insert the active mask into the beam (alias: insert)
   out    - extract the active mask into the storage cassette (alias: stow)

Flags:
   -V   - print version info and exit (alias: --version)
   -h   - print help info and exit (alias: --help)

Examples:
   modsMask 1 status  -  report the status of the MODS1 mask system
   modsMask 2 mask 4  -  position MODS2 mask 4 at the cassette load port

modsAGW - Operate the MODS AGw Stage

modsAGW allows access to MODS AGw stage functions for use by the Telescope Operator or support personnel during technical nights when they wish to use the MODS AGw system without having to operate the entire MODS instrument.

Usage: modsAGW modsID cmdStr

where: modsID = 1 (MODS1) or 2 (MODS2)
       cmdStr = AGw command to execute

Mask Commands:
   status - report the status of the MODSn AGw Stage
   home   - home the MODSn AGw stage (stows the guide probe)
   open   - put MODSn into observing mode, opening it to the sky
   close  - close MODSn ("calibration mode") and stow the AGw stage
   getxy  - report the XY coordinates of the MODSn guide probe (in mm)
   setxy x y - set the MODSn guide probe to the requested XY position (in mm)
   getfilter - report the MODSn AGw guide camera filter
   setfilter filtID - set the MODSn AGw guide camera filter
                      must be one of {Clear F525LP B_Bessel ND1.0}
   wfs [ON|OFF] - report or change the power state of the MODSn AGw unit's
                  WFS CCD camera controller.
   gcam [ON|OFF] - report or change the power state of the MODSn AGw unit's
                   Guide Camera CCD camera controller.

Flags:
   -V   - print version info and exit (alias: --version)
   -h   - print help info and exit (alias: --help)

Examples:
   modsAGW 1 status
       Report the full unfiltered status of the MODS1 AGw stage.
   modsAGW 1 getxy
       Report the current XY position of the MODS1 AGw stage.
   modsAGW 2 setfilter clear
       Put the clear filter into the MODS2 guide camera beam.
   modsAGW 2 gcam
       Report the power state of the MODS2 guide camera CCD controller

modsTemps - Read MODS Critical Temperatures and Pressures

modsTemps take a quick reading of the current suite of MODS critical temperatures and pressures: CCD dewar temperature and vacuum pressure (plus HEB box temperature and detector head temperature), and the instrument glycol coolingsupply and return temperatures and pressures.

Usage: modsTemps modsID cmdStr

where: modsID = 1 (MODS1) or 2 (MODS2)
       cmdStr = command to execute

Mask Commands:
   red    - report MODSn Red CCD dewar temperatures and vacuum pressure
   blue   - report MODSn Blue CCD dewar temperatures and vacuum pressure
   glycol - report MODSn instrument glycol supply and return status
   inst   - raw, unfiltered instrument ESTATUS (engineering only)

Flags:
   -V   - print version info and exit (alias: --version)
   -h   - print help info and exit (alias: --help)

Examples:
   modsTemps 1 red
       Report the MODS1 Red CCD dewar temps and pressure
   modsTemps 2 glycol
       Report the MODS2 glycol supply and return temps and pressures

If you get an error, check:
  1. that the DOS machines are on - checked from logging in to the KVM; turn on with power button if not on
  2. the HEBs are on - from an xterm, run:
     isisCmd m1.ie util heb_b and/or isisCmd m1.ie util heb_r
    to see the state ON/OFF

    Turn them on with:
     isisCmd m1.ie util heb_b on and/or isisCmd m1.ie util heb_r on
  3. the DOS machines are running the IC program - see the screenshot
    The modsTemps will not see the info if the IC program is not running.

DOS IC program running correctly:
MODS-M1.BC-KVM.png



If it seems hung in this state (no values updating in right hand corner):
DOSScreenshot-badICState.JPG


1. Try typing quit and then ic to restart

2. Try cntl-alt-del to reboot, then ic to restart

3. If you had to turn on the DOS machine or power-cycle it, type IC when it boots to the DOS prompt.

Once you get the M1.RC> (or .BC prompt if blue), type
   tedpower on
   igpower on

These should happen by default, but just in case Rick does them anyway (like rubbing a rabbit's foot - force of lab habit)

Then
   estatus 

to see the HEB status

Low Power States

If instrument cooling is going to be off, then the appropriate low-power state to use is:

  • HEBs: Off
  • AGC: Off
  • WFS: Off
  • LLB: On (so long as lamps and the laser are off, it draws little power)
  • IEBs: On (if motors are idle, it draws little power)
  • AGw camera controllers: Off
  • IMCS agents and calibans stopped (cb_red and cb_blue, since if the HEBs are powered off these don't need to be running)

The AGw guide and WFS camera controllers (AGC and WFS) are little toasters and leaving them on with cooling off just warms up the IUB unnecessarily. If we aren't observing, there is no need for the controllers to be on.

So, low-power state prior to dismount is:

Services:
  • Running: isis, IE, AGw, modsenv
  • Stopped: red/blue IMCS, red/blue Caliban, modsUI, lbttcs

This gives you enough to watch the environmental sensors (except in the HEBs), and operate the mask select system to remove custom masks, if required.

Power Outage - modsShutdown

If an emergency (or unanticipated) power outage is impending, the automatic UPS script will take care of putting the instrument into a safe configuration and powering off the mechanisms and computers.
See Facility Instruments in the Event of a Power Outage
Since this procedure does not home all of the mechanisms, a full reset of the MODS system is required when the power is returned - home all mechanisms, then send to nominal configuration positions.

If you want to manually power down MODS, outside of an impending UPS event, you should use the modsNShutdown.pro script.
It homes all of the mechanisms one after another, parking them at their home positions. Only a few of them move in parallel during a reset (e.g., for each collimator mirror, all 3 TTF actuators run in parallel). Depending on the starting point, this can take up to about 8 minutes for all mechanisms to be parked, all CCD parameters cleared (that is pretty fast, actually, about 5 seconds), and then the various system shutdowns. The longest homing operations are the collimators and the AGw stage actuators, depending on where the stage starts from.

1) Park all the mechanisms, clear the CCD parameters, and power off
 execMODS mods1Shutdown.pro 

 execMODS mods2Shutdown.pro 

The scripts are located in the /home/modseng/modsScripts/Support directory. This script powers off the agw and wfs camera controllers as well as the hebs (plus the lamp & laser box and IEBs). It can take up to about 8 minutes to run. Longest homing operations are the collimators and the AGw stage actuators, depending on where the stage starts from.
It will also take you through clearing the CCD parameters (that is pretty fast, actually, about 5 seconds).

The script executes these commands, but if you wanted to manually power off the agw, guider and head electronics:
isisCmd -mods1 m1.ie util agc off
isisCmd -mods1 m1.ie util wfs off
isisCmd m1.ie util heb_b off
isisCmd m1.ie util heb_r off 

2) Stop the software systems

mods1 stop imcs
mods1 stop cb_blue
mods1 stop cb_red
mods1 stop env
mods1 stop tcs

3) Stop the other systems

Stop IC's
mods1 stop agw
mods1 stop ie
mods1 stop isis 

4) power off mods1, mods1 data, and power off m1.rc and m1.bc
power off mods2, mods2 data, and power off m2.rc and m2.bc
See also : MODS1 Computer Power-Down Procedure



-- RichardPogge - 02 Nov 2011
Topic attachments
I Attachment Action Size Date Who Comment
DOSScreenshot-badICState.JPGJPG DOSScreenshot-badICState.JPG manage 278 K 07 May 2014 - 22:57 UnknownUser MODS IC screenshot in bad state
MODS-M1.BC-KVM.pngpng MODS-M1.BC-KVM.png manage 54 K 07 May 2014 - 23:15 UnknownUser MODS IC screenshot in good state
Topic revision: r10 - 13 Jun 2017, KelleeSummers
This site is powered by FoswikiCopyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding Foswiki? Send feedback