Shane AO  

• user@shanevnc.ucolick.org > stop_vnc_servers
• user@shanevnc.ucolick.org > start_vnc_servers ao large 24
• user@gouda.ucolick.org > start_lick_viewers shane

• ping ao-agilent.ucolick.org ShARCS dewar temperature & pressure monitor.
• ping ao-lantr-ip.ucolick.org (Lantronix device).
• ping ao-power-1.ucolick.org (ShaneAO Pulizzi A).
• ping ao-power-2.ucolick.org (ShaneAO Pulizzi B).
• ping ao-power-3.ucolick.org (ShaneAO Pulizzi C).
• ping ao-serial-1.ucolick.org (Lantronix device communicating between Thorlabs Tip-Tilt filter wheel (TT Filter) and saomot5 service.
• ping ao-serial-2.ucolick.org (Lantronix device communicating between Thorlabs Science filter wheel (Sci Filter) and saomot5 service).
• ping mh-switch-ao.ucolick.org (ShaneAO network switch).
• ping musher.ucolick.org (woofer controller).
• ping real.ucolick.org (real-time controller).
• ping saorouter.ucolick.org (ShaneAO router) communicating between Galil motor controller and saomot1, saomot2, saomot3 services).
• ping stealthie.ucolick.org (ShARCS detector controller).

• ping shanevnc.ucolick.org (CentOS Linux host supporting VNC servers, most GUIs).
• ping karnak.ucolick.org (Linux Mint host supporting Peeko, TTPeeko, imageSharpen).
• ping covert.ucolick.org (CentOS Linux host supporting ShARCS user interface; Data disk; Ion pump sharcspump; Keyheader ao_keyheader; Detector server; scriptproc).
• ping shark.ucolick.org (CentOS Linux host supporting monitor: saomon, sharcstherm).
• ping shadow.ucolick.org (CentOS Linux host supporting motor dispatchers saomotX, power dispatcher saopower).
• ping accession.ucolick.org (Linux host supporting KTL keywords ao_keygrabber; data back-up).

• Start the ShaneAO Power Controls GUI (/usr/local/lick/bin/saopower_ui).
• Initially after a re-start, the status displayed in the GUI may be stale. To encourge the status to refresh, either:

  user@shadow: /usr/local/lick/bin/ao restart saopower

  or,

  [B8] White Light: Cycle ON, OFF a few times until yellow background warnings cease.

The GUI should eventually reflect the following status, where functions in bold are powered.

Pulizzi A:

[A1] Galil DMC 40x0 motor controllers (3)

[A2] 24V brake power supply

[A3] 24V motor power supply

[A4] 5V DC logic power supply

[A5] +/- 12V servo power supply

[A6] Jade card 5V power supply

[A7] Stealthie (computer)

[A8] Ion pump

Pulizzi B:

[B1] rtc/real computer

[B2] musher computer

[B3] TT camera

[B4] WFS camera

[B5] Woofer

[B6] Heartbeat failsafe

[B7] 635 nm diode laser

[B8] White light

Pulizzi C:

[C1] TT filter wheel

[C2] ShARCS filter wheel (external, not currently installed)

[C3] Lantronixes (TT f/w ShARCS f/w, ion pump)

[C4] Argon Lamp

[C5] Aquistion (flea) camera

[C6] MEMS pico motors

[C7] FM3 pico motors

[C8] Phase screen

• user@shadow > ao restart saomot

• lenslet
• TTCamX
• TTCamY

• Start the ShaneAO motor control GUI (saomot_gui).
• Load-in most recent set-up from:

  /local/u/user/observers/lgs/saomot_setups/

• Start Message log (tail -f /var/log/messages).

• user@shadow.ucolick.org: /usr/local/lick/bin/ao start all
• user@shark.ucolick.org: /usr/local/lick/bin/ao start all
• user@covert.ucolick.org: /usr/local/lick/bin/ao start

• To start ShaneAO power dispatcher service in isolation on shadow:

  user@shadow.ucolick.org > /usr/local/lick/bin/ao start saopower

• To start ShaneAO motor dispatcher services on shadow:

  user@shadow.ucolick.org > /usr/local/lick/bin/ao start saomot

• To start ShaneAO Loop Control GUI:

  Select (saocon_gui).

• To start shaneao real-time code:

  Select (shaneao) or /usr/local/lick/bin/shaneao.

pdv_*_image ... timeout

Then this indcates communication failure to/from either the WFS camera, the TT camera, or both.

• exit() the Peeko and/or TT Peeko service(s).
• exit() the shaneao software.
• In ShaneAO Power Controls GUI, set TT Camera [B3] and/or WFS Camera [B4] outlets to OFF.
• Wait 10--30 seconds.
• In ShaneAO Power Controls GUI, set TT Camera [B3] and/or WFS Camera [B4] outlets to ON.
• (Re-)start shaneao software.
• (Re-)start Peeko and/or TT Peeko service(s).

• To start ShARCS front end GUI:

  Select (sharcs_fe).

• To start ShARCS display GUI:

  Select (sharcsdisplay).

Connect to stealthie:

• In an xterm window connect to the (linux) support machine (e.g. ssh user@covert.ucolick.org).
• As user on the (linux) support machine, use the rdesktop protocol to connect to the (Windows) detector control machine, e.g.

  rdesktop stealthie.ucolick.org

• Select Sidecar ASIC IDE shortcut icon.
• The Sidecar ASIC Integrated Development Environment (IDE) dialogue box should appear. In lower right, select Open.
• The dialogue box should open to the following location:
  C:\Program Files\Teledyne Scientific\SidecarASIC IDE\
  If not, navigate to this subdirectory.
• Open folder: Test.
• Select file: Test.soln. In response, assembly files listed under the JADE and ASIC tree should launch.
• In top-left corner of Interactive Development Environment (IDE) window, select green play Start HAL button to launch Hardware Abstraction Layer (HAL) server.
  When selected, this option should fade to grey, and a corresponding red (square) Stop HAL button should become available.
• From IDE toolbar, select yellow downward-pointing Firmware icon in order to download necessary firmware into the FPGA of the JADE2 card.
  Wait circa 15 seconds for download to progress to completion (observe progress bar in lower-right). System log also indicates status of download.
  When JADE2 firmware has been successfully downloaded a green circle appears in the JADE2 tree next to the JADE2 text (replacing a yellow caution triangle).
• Select blue downward-pointing JADE Registers arrow to download the JADE registers. The System log should immediately report that the JADE2 registers have been downloaded.
• Select the Config button (two small, downward-pointing, black arrows) in the right hand side of the toolbar.
  If the file:
  HxRG_Main.mcd is present in the bottom left box, select OK and proceed to the next step.
  If MCD file is not present, click Browse... and select the file HxRG_Main.mcd, which should be in the following sub-directory:
  C:\Program Files\Teledyne Scientific\SidecarASIC IDE\
  Click the two downward-pointing arrows icon underneath the top-left box. File HxRG_Main.mcd should move to the bottom left box.
  Browse, select and add HxRG_Main_ShARCS.mcd and ShARCS_Voltages.mcd to the bottom left box.
  Select OK. The window should close.
• Select the purple downward-pointing MCD arrow to download the HxRG_Main.mdc instructions to the Sidecar microcontroller. The System log should indicate Download of mcd file(s) complete.
  When download is complete, a green circle appears in the JADE2 tree next to the ASIC1 text (replacing a yellow caution triangle).
• IDE start-up complete. Minimize window (IDE must continue to run in the background).

• Select the Windows Start option.
• Select My Computer.
• Listed under the heading Network Drives, should be:

  public on 'Samba Server Version X.X.X-XXX (covert)'(Z:) Network Drive

  If this is not the case, then left-click the text public on 'Samba... to mount the disk.

• If operating the detector cold, double-click desktop Cold SidecarServer shortcut icon.
  If operating the detector warm, double-click desktop Warm SidecarServer shortcut icon.

• Select Windows...; Setup...
• In Setup window:
  • Ensure AsicCfg keyword is set to appropriate configuration file:
    a) If cold, C:\SHARCSColdSidecarControlConfig.xml
    b) If warm, C:\SHARCSWarmSidecarControlConfig.xml
  • Ensure UnixRootDir keyword is set to /data
  • Ensure WinRootDir keyword is set to Z:\
  • Ensure Outdir keyword is set to sharcs
  • If Connected keyword is set to No or if upper right corner of sharcs_fe indicates Lost Server, click the connect button. The button should turn yellow while attempting to connect, and should turn red if there are connection problems.
  • Select the Init button to initialize the system. The Initing keyword should change to Yes during initialization. If the process is successful the SidecarInit keyword will read Success.
  • Close Setup window.

• As user@shimmy.ucolick.org, execute start-up script:

  /u/user/observers/lgs/scripts/daily_startup.tcl

• As user@shimmy.ucolick.org, execute shutdown script:

  /u/user/observers/lgs/scripts/daily_shutdown.tcl