Shane AO  

Welcome/Index | Architecture | Procedures | Problems | Features | Documents | Resources | Chronology  



Procedure: Start-up (Incomplete 2020-10-27)

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

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

Procedure: Start-up (Incomplete 2019-02-21)

  • Verify communications:
    • ping shanevnc.ucolick.org Support services (VNC servers, most GUIs) machine.
    • ping shred.ucolick.org Support services (motor dispatchers, power dispatcher) machine.
    • ping covert.ucolick.org Support services (Data disk; Ion pump; keyheader; Detector server; scriptproc) machine.
    • ping stealthie.ucolick.org ShARCS detector controller.
    • ping accession.ucolick.org Support services (KTL keywords, data back-up) machine.
    • ping shade.ucolick.org Support services (Peeko, TTPeeko) machine.
    • ping saorouter.ucolick.org ShaneAO router (communicating between Galil motor controller and saomot1, saomot2, saomot3 services).
    • ping mh-switch-ao.ucolick.org ShaneAO network switch.
    • 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-lantr-ip.ucolick.org Lantronix device.
    • 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 ao-agilent.ucolick.org ShARCS dewar temperature and pressure monitor.
    • ping musher.ucolick.org woofer controller.
    • ping real.ucolick.org real-time controller.
  • Verify ShaneAO power supplies:
    • 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:

      /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 : Note (2019-02-21): At some point the Agilent device was powered through Pulizzi [C4]. It is assumed that this is no longer the case.

    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
  • Prepare VNC session(s):
    • 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
  • Global start of dispatcher services on shark (formerly shred) and covert:

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

    and,

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

  • Start ShaneAO power dispatcher service in isolation on shadow:

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

  • Start ShaneAO motor dispatcher services on shadow:

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

  • Remotely connect to the (Windows) ShARCS detector control machine (e.g. stealthie) to start Cold Sidecar and Sidecar ASIC servers.
    • 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

    • In stealthie desktop, select the 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 be launched.
    • Click green play Start HAL button in top-left corner of IDE window 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.
    • Click yellow downward-pointing Firmware icon in Integrated Development Envirnment toolbar 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).
    • Click blue downward-pointing JADE Registers arrow to download the JADE registers. The System log should immediately report that the JADE2 registers have been downloaded.
    • Click 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, click 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.
      Click OK. The window should close.
    • Click 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).
    • Verify the Samba server is mounted on the Windows machine:
      • 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.
  • In ShARCS front end (sharcs_fe) GUI:
    • 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.
      • Click 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.
  • If power is cycled to ShaneAO Galil motor controllers for any reason (e.g. following mount/dismount of instrument), all saomot dispatcher services must be restarted:

    user@shred > ao restart saomot

    After a such a re-start, in the ShaneAO motor control GUI (saomot_gui) it is necessary to issue the Calibrate command twice to the brushless motor stages i.e:

    • lenslet
    • TTCamX
    • TTCamY
  • In 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).
  • Start shaneao real-time code (/usr/local/lick/bin/shaneao.

Change Log:

2019-10-03: Updated.
2019-02-21: Updated.
2014-05-09: First version.


This document last updated (UTC): Tuesday 04 March 2025