Search
Text Size:
Smaller Text Normal Text Larger Text

Facebook page

Twitter profile

YouTube channel

Troubleshooting HiRAC

Author: Tim Abbott, 21 August 1999


NOTE: These troubleshooting suggestions come without guarantee and should be executed ONLY by NOT personel, or with their supervision and/or direct permission.


Failure mode 1:

Loss of serial communication with HiRAC controller unit.

Symptoms:

One or more of:
  • Shutter no longer functions, but images are still collected, all appearing as biases.
  • Filter changes fail.
  • BIAS crashes spewing garbage on the status window (indicative, but not diagnostic).
  • BIAS will not restart without crashing (indicative, but not diagnostic).
  • BIAS restarts, but cannot initialise filters nor change them.


Fix 1: failure is caused by s/w.

Power cycle, serial test, restart.

  1. Exit BIAS, logout of elizabeth.
  2. Turn off power to HiRAC filter controller unit and CUO CCD controller.
  3. Wait 30 sec.
  4. Turn on power to HiRAC filter controller unit and CUO CCD controller.
  5. Log in again on elizabeth as obs1.
  6. In an xterm, do the following:
    % cd ~hirac/aux-files
    % ./ttyS0
    (ttyS0 is a program which allows direct communication with the ttyS0 serial port. Similar programs are in the same directory for the ttyS1, ttyS2 ports in the event that the HiRAC controller is connected to one of these instead. BIAS reports the port name it is trying to use on startup.)
  7. Hit return, you should be rewarded with a "!" prompt.
    If you do not get a "!" prompt, you do not have serial line communications, proceed to Fix 2.
  8. type XI (Ecks-Eye) to initialise the probe X position. The "!" prompt should return. Then do YI, ZI, SI, FI, to initialise the Y, Z, shutter and filter controllers respectively. If you get a XY or XN back from an X command, the communication is alive.
  9. Hit Control-X to exit the ttyS0 program.
  10. do:
    cd ~/hirac
    startbh
    to restart BIAS.
  11. Hopefully now all is working. If not, try this sequence once more, and maybe again before proceeding to Fix 2.


Fix 2: failure is caused by h/w.

Test HiRAC controller and serial line.

If you are about to try this, you have convinced yourself that an ordinary BIAS communications error is not the problem and you want to test the integrity of the serial link hardware.

  1. Collect the serial line tester from the metal cabinet in the telescope machine room. This is a yellow plastic box, about 8cm X 12cm X 2cm, with slider switches and LEDS on the front, ribbon cables extend a short distance from each side and there should be sex changers and 9-pin D-connector adaptors attached.
  2. Use the serial line tester to verify that there is power on the serial line at the following points:
    • The HiRAC control box input (the red, 9-pin D-connector at the end of the box furthest from the power input).
    • The fibre-optic/serial multiplexer patch panel on the telescope.
    • The fibre-optic/serial multiplexer below elizabeth in the TCS room.
    • At the input of the serial cable to elizabeth.
    Simply connect the serial line tester in line with the cables and see if the TD/RD lights show on both sides.
  3. Next try communicating with the HiRAC controller directly with the laptop dumb terminal. This laptop requires a key and a password. Obtain these from whoever you can wake up.
    • Connect the serial port of the laptop to the serial input at the HiRAC controller.
    • Run the program "Z"
    • Hit Return to get the "!" prompt.
    • Give the XI, YI, ZI, SI, FI as from ttyS0 in Fix 1. You should hear the components inside HiRAC initialising.
    • If any of this fails, something is wrong with the HiRAC controller. Check your connections and try again, just to be sure, then wake someone up.
  4. Repeat the previous step with the laptop connected to the serial line from the point at which it connects to elizabeth. If this fails, but the previous step did not, then there is a hardware problem with the serial line. Time to wake someone up.
  5. If everything appears to work, reconnect everything as per normal
  6. repeat Fix 1.

Back to top Last modified: May 31 2023