The HIRES VME crates, hmotcrate and hccdvmep, control all of the motorized stages and the CCD image taking functions of the spectrograph. This document describes how to access and boot the crates, and warning signs for error conditions.

Contents

  1. Telnet'ing to the VME Crates
  2. Rebooting the VME Crates
  3. Tasks and Error Conditions

Telnet'ing to the VME Crates

There are two ways to directly access a VME crate console session, described below. Note that the HIRES user menus contain entries to either TIP (terminal server connection) or Telnet (ethernet connection) to the crates, under Engineering -> TIP Motor Crate, for example.

Ethernet hostname (or IP address) connection

For the HIRES motor crate: telnet hmotcrate

For the HIRES CCD crate: telnet hccdvmep

Note: additional information is available at the HIRES Network Info page.

lehoula{hireseng}37: telnet hmotcrate
Trying 192.168.4.8 ...
Connected to hmotcrate.
Escape character is '^]'.

VxWorks login:
The login name and password can be obtained from a Support Astronomer. At a future date all VME crates will utilize identical login parameters to minimize confusion. To log out of an ethernet session simply type "logout"

Terminal Server (TIP) connections

The HIRES VME console is connected to through a direct line from the K1 terminal server 'tserver1'. The channels for HIRES access are 3012 (hmotcrate) and 2009 (hccdvmep). To connect to the motor crate through this TIP line, type the following:

For the HIRES motor crate: telnet tserver1 3012

For the HIRES CCD crate: telnet k1consoles 2009

For example:

lehoula{hires}62: telnet tserver1 3012

Trying 128.171.95.140 ...
Connected to tserver1.
Escape character is '^]'.

One must hit "Enter" to activiate the session. To exit, type "Control-]". If the session is active, the arrow prompt appears:

->
If you do not get an arrow prompt, then there is an error in the terminal server connection. If another user owns the connection the following message results: 
telnet: connect: Connection refused
If you cannot get into an active session, connect to the VME crate via ethernet.

Rebooting the VME crates

There are two fundamental ways to reboot a VME CPU.

From the TIP or ethernet connection

The crates can be booted directly from any login session (TIP or ethernet), by simply typing "reboot": 
-> reboot
The behaviour of the two types of session under reboot is different, however. The TIP session is a "live" connection to the console, so you will see the auto-boot countdown and parameter table scroll by. Do not type anything in the window during the TIP session reboot. During the countdown the default boot parameters can inadvertantly be modified. In fact, it is best to get your cursor out of there during the boot-up.

If your connection is via ethernet, the session will hang, and log itself out, so you must reestablish the connection if you want it.

The startup scripts for either crate load automatically.

Hitting the Reset switch on the CPU

The HIRES VME crates are in a single rack in the instrument electronics enclosure on the RNAS deck of Keck-1. The SPARC CPU's can be rebooted by hitting the "Reset" switch that is somewhat hidden by adjoining connections on the board. It is a spring-loaded toggle switch. When the CPU has been successfully rebooted, the red LED's will blink in a recycled row.

Tasks and Error Conditions

The active processes for the two crates under normal operating condtions are:

Motor crate (hmotcrate, 3012)

 
->i
    
  NAME        ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY
---------- ------------ -------- --- ---------- -------- -------- ------- -----
tExcTask   _excTask       3f8ea0   0 PEND          32800   3f8cf0  3d0002     0
tLogTask   _logTask       3f6d48   0 PEND          32800   3f6b98  3d0002     0
tShell     _shell         3c5d90   1 READY         4c4e4   3c5780       0     0
tRlogind   _rlogind       3d3a28   2 PEND          694e4   3d3658       0     0
tTelnetd   _telnetd       3d1b50   2 PEND          694e4   3d18b0       0     0
tTelnetOutT_telnetOutTa   3ff028   2 READY         694e4   3feb70  3d0002     0
tTelnetInTa_telnetInTas   3ceff0   2 READY         693e0   3cea78  3d0001     0
tNetTask   _netTask       3f1d00  50 READY         69e00   3f1a98  3d0001     0
rshd       _rshd          1547a0  90 PEND          694e4   1543f8  3d0001     0
tPortmapd  _portmapd      3d0610 100 PEND          694e4   3d0320      16     0
MLOG_MEMBUF_start_mlog_   231bc8 100 PEND          32800   231690  3d0001     0
MLOG_STDERR_start_mlog_   219370 100 PEND          32800   218e40  3d0001     0
MLOG_LFILE _start_mlog_   200b18 100 PEND          32800   2005e8  3d0001     0
MLOG_MUSIC _start_mlog_   1e82c0 100 PEND          32800   1e7d80  3d0001     0
cserv      _cserv         16f8c0 100 PEND          694e4   16f398  3d0002     0
killer     _killer        157068 100 DELAY         6ae5c   156758  360003   175
responder  _responder     13d770 100 PEND          32800   13c488  3d0002     0
ENCWRAPMON _dc_stage_wr   124f18 100 READY         6ae5c   124dc8  3d0002     0
MONDCMAN   _mon_dc_stag   122650 100 READY         6ae5c   122500  3d0002     0
SYSWARN    _monitor_mai   11fd88 100 READY         6ae5c   11fbd8  3d0002     0
UPS        _monitor_mai   11d4c0 100 DELAY         6ae5c   11d310  3d0002   218
POWER      _monitor_mai   11abf8 100 DELAY         6ae5c   11aa48  3d0002   237
TEMPRACK   _monitor_mai   118330 100 DELAY         6ae5c   118180  3d0002   236
TEMPLAMP   _monitor_mai   115a68 100 DELAY         6ae5c   1158b8  3d0002   244
TEMPTV     _monitor_mai   1131a0 100 DELAY         6ae5c   112ff0  3d0002   244
TEMPCOOL   _monitor_mai   1108d8 100 DELAY         6ae5c   110728  3d0002   249
AIRALARM   _monitor_mai   10e010 100 DELAY         6ae5c   10de60  3d0002   248
IONPUMP    _monitor_mai   10b748 100 DELAY         6ae5c   10b598  3d0002   247
ENVIRON    _monitor_mai   108e80 100 DELAY         6ae5c   108cd0  3d0002   247
BMONDCIO   _bmon_dc_sta   1065b8 100 READY         6ae5c   106460  3d0002     0
BMONAIO    _bmon_analog   103cf0 100 READY        3898e8   1037c8  3d0001     0
BMONDIO    _bmon_digita   101428 100 READY         6ae5c   1012d0  3d0002     0
BMONLAMP   _bmon_lamp_s    feb60 100 READY         6ae5c    fea10  3d0002     0
xdserver   _server         f3f78 100 PEND          694e4    f3ce8   d0003     0
value = 3953296 = 0x3c5290
->

CCD crate (hccdvmep, 2009)

-> i
    
  NAME        ENTRY       TID    PRI   STATUS      PC       SP     ERRNO  DELAY
---------- ------------ -------- --- ---------- -------- -------- ------- -----
tExcTask   _excTask       3f8ea0   0 PEND          32800   3f8cf0  3d0002     0
tLogTask   _logTask       3f6d48   0 PEND          32800   3f6b98  3d0002     0
tShell     _shell         3c6318   1 READY         4c4e4   3c5d08   30065     0
tRlogind   _rlogind       3d3a28   2 PEND          694e4   3d3658       0     0
tTelnetd   _telnetd       3d1b50   2 PEND          694e4   3d18b0       0     0
tTelnetOutT_telnetOutTa   23cbd0   2 READY         694e4   23c718  3d0002     0
tTelnetInTa_telnetInTas   23b690   2 READY         693e0   23b118  3d0002     0
tNetTask   _netTask       3f1d00  50 READY         69e00   3f1a98  3d0002     0
ccdClock   _ccdClock      247060  90 READY         6ae5c   246f18  3d0002     0
tPortmapd  _portmapd      3d0610 100 PEND          694e4   3d0320  2f0005     0
MLOG_STDOUT_start_mlog_   278110 100 PEND          32800   277be0  3d0002     0
cserv      _cserv         25f8b8 100 PEND          694e4   25f390  3d0002     0
responder  _responder     22f830 100 PEND          32800   22e548  3d0002     0
dewar_fill _dewar_fill    2140f0 100 DELAY         6ae5c   213f10  3d0002    23
killer     _killer        20dd90 100 DELAY         6ae5c   20d480       0   134
broad_mon  _broadcast_m   20b4c8 100 DELAY         6ae5c   20b398  3d0002    34
rccd       _rccd          238d38 150 PEND+T        694e4   238a98  3d0002    18
value = 3954644 = 0x3c57d4
->
The CCD crate has a monitor task running, "dewar_fill", that checks the LN2 levels of the 3.8 liter CCD dewar, and the 50 liter storage dewar. Messages are printed every 10 seconds of the form: 
dewar_fill[0]: Monitoring for 6256 mins. Control enabled for last 6256 mins.
dewar_fill[0]: dewar is   98.6 percent full  tank level is   71.8 percent full
dewar_fill[0]: dewar temperature is -120.0 degrees C
dewar_fill[0]: 30 minutes since last fill
If you should log onto the crate and NOT see these messages posted every 10s, then automatic dewar fills will not be enabled, and the CCD crate should be rebooted immediately.