INCREASING THE GUIDER EXPOSURE TIME

1.  Go to the Architect console:   http://system1.ctio.noao.edu:7001/apps/architect_console/ [5]
2.  Find the System Control Box.  Replace the boxes that say:

Component         Device           Command: Press Enter When Complete

with:

GCS     GCS          set guideexptime nnnn

nnnn is the  time in ms. The default is 600 ms.

RESTARTING THE COMFORT DISPLAY

1.  Follow instructions here (bottom of page):  Instance Start-up For Experts [3]
2.  If there is no "comfort1" node and no "DISPIB" role to restart, first go to the architect console and replace

Component         Device           Command: Press Enter When Complete

with:

ARCHITECT     MANAGER          start_node comfort1

2a.  Connect to the VNC server on system1, display 2. Find the OCS Console and the Manager Console:

OCS Console: select ARCHITECT
MANAGER Console: start_role DISPIB comfort1
MANAGER Console: start_role DISPIS comfort1
MANAGER Console: select OCS

2b.   Go to the comfort display (comfort1) and make sure a desktop session is running. If not, start one using the DECamObserver account.  Open a terminal and enter the command

xhost +localhost   

RESTARTING THE DECAL COMPUTER

1.  Follow the instructions as outlined here: DECal Server Emergency Restart Procedure [6]

2.  If this does not work, you must unlink DECal and SISPI in order to take exposures.  To do this, go the architect console and replace

Component         Device           Command: Press Enter When Complete

with:

OCS                      OCS          remove_component DECAL

to add it back in:

OCS                       OCS         add_component DECAL,DECAL,DECAL

RESTARTING THE GUIDER GUI

Open a terminal on observer 1 and start a vnc viewer that connects to readout2.ctio.noao.edu:15

> vncviewer readout2.ctio.noao.edu:15

(password is on Andreas updated list, come to office 14 to pick up a copy)

If you vnc into the guider fui from home, please use this only when needed and then disconnect - sending the image data across the network uses resources.

RESTARTING CHECKING THE STATE OF VSUB (IE, IF VSUB BUTTON IS YELLOW)

Typically vsub is either on or off for the entire system (all 6 Monsoon crates, counting each split backplane as a crate). Sometimes the crates are in a mixed state – some on, some off. In this case the vsub indicator on the ObserverConsole GUI turns yellow. To find out which crate and which module (slot) in each crate has vsub on, use the command get vsub details.

Go to the Architect Console, select the OCS role and enter the command in the control section. This returns a string like this:
<pre>
FPANS:
SL4_CCD12_VSUB_ENBL 0.000000
SL3_CCD12_VSUB_ENBL 0.000000 << _decam_bkpf
SL4_CCD12_VSUB_ENBL 0.000000
SL3_CCD12_VSUB_ENBL 0.000000 << _decam_bkp4
SL4_CCD12_VSUB_ENBL 0.000000
SL5_CCD12_VSUB_ENBL 0.000000
SL6_CCD12_VSUB_ENBL 0.000000 << _decam_bkp5
SL4_CCD12_VSUB_ENBL 0.000000
SL5_CCD12_VSUB_ENBL 0.000000
SL6_CCD12_VSUB_ENBL 0.000000 << _decam_bkp1
SL4_CCD12_VSUB_ENBL 0.000000
SL5_CCD12_VSUB_ENBL 0.000000
SL6_CCD12_VSUB_ENBL 0.000000 << _decam_bkp3 GPAN: 0.000000 </pre> GPAN is the guider backplane (bkpg).

A 0.000000 indicates that vsub is off for this module.

A 1.000000 indicates that vsub is on.

QUICK REDUCE

The Reset button can be used to recover from unexpected errors.  If this does not work:

ssh quickreducequick1 [dot] ctio [dot] noao [dot] edu    (the password is on Andrea's list, not tested yet)

bash

ctio_portal_server.sh restart

If the problem remains send email to:  helpdesklinea [dot] gov [dot] br

Reference manual:  DES-doc 6705

USEFUL LINKS

1.  SISPI NEWS [7]

2.  Instance Start-up For Experts [3]

3.  Get-Ready Check List [2]

4.  Ann Elliot's Debugging throug the GUIs [8] page

5.  DECam Operations [9]

6.  Current SISPI Configuration [4]