Note: These instructions should work for both k1obsao@k1aoserver-new and k2obsao@k2aoserver-new.

OBS reboot and startup: 20-30 minutes
If there is no critical reason to shutdown the OBS, leave it up!
We have found that some failure modes can only be mitigated by rebooting the OBS crate (and the PMACs) about once per month .
OBS can be power-cycled remotely
  • Bring up an SC GUI from kNaoserver-new terminal.
      kNscgui
  • Turn OFF power to the servos and encoders (in this order!)
    1. SC GUI → AO → OBS dm → VMIC (bring upthe GUI to ther digital i/o board)
    2. Line 9 - turn OFF servo power
    3. Line 5 - turn OFF encoder power
  • From a kNobsao@kNaoserver-new xterm, type cycleOBS1 or cycleOBS2
The OBS is a VME crate that takes about 10 minutes to boot
  • Look for: Done executing startup script
Restart SC IOC
  • As kNobsao@kNaoserver-new: kNscReboot.csh
Once the OBS VME crate is powered up and the SC IOC has been restarted, follow these instructions:

  1. OPTIONAL: Verify initialization of the Bancomm timing board:
    In the obs telnet session, type: dbior "drvBc635", 2
    • It should return a line that says: Interrupt level is 6 (0 = all interrupts disabled)
    • If it returns Interrupt level is 0 (0 = all interrupts disabled), the you should reboot again, since all interrupts have been disabled! This would cause the rotator not to track properly (see nightlog K1-18273)
    • Also verify that the telnet terminal shows the correct date and time in UT

  2. OPTIONAL: Check for suspended tasks:
    • In the obs telnet session, type i to list all tasks
    • In any kNaoserver-new terminal as user kNobsao, type:
      cdn; grep -i suspend telnet-obs2.
      This should bring an empty list.
    • If the list is NOT empty, reboot OBS again

  3. Turn on encoder and servo power :
    • On SC GUI top menu: AO → OBS dm screen → VMIC
    • Power up the device encoders; item 5 and 9 (in this order!):
      1. Line 5 - Encoder +5VDC
      2. Line 9 - Servo Power

  4. Initialize OBS stages:
    1. Do NOT use the "Overall Init" function
    2. From the SC GUI screen, click INIT for WF (FCS)
    3. Once FCS is initialized, click more and send obwf to, at least, +40mm
    4. Initialize the big stages: RT (ROT) and TS (TSS)
    5. Once these two are done, you may click INIT next to every other stage
    6. Wait till devices are INIT-ed, watching for problems.
    7. Repeat INIT command for any device that faults.
    8. For repeat problem during the INIT sequence, please check with an AO person experienced with OBS init problems.

OBS should be up and running at this point
  • You are free to run either the Cal Setup or Nighttime Script.