Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

  1. Stop and close the following VIs.
    1. LCW Monitor — It takes 30-60 seconds to stop.
    2. Cryo Control Panel — Click the "Stop All Subsys" button and then the "Stop This" button.
    3. BOS+EOS Handler — See the procedure written below.
  2. Shut down the OS.
  3. Shut Ask the SpinQuest network admin to shut down the following Sea/ SpinQuest servers, if the network admin allows us to take care of them.
    1. e1039scrun — Use SSH and the "poweroff" command
    2. e906-gat1, e1039gat1 — Use SSH and "poweroff"
    3. e906-db1 — Use SSH and "poweroff"
    4. SeaQuestDsk0 (/data2) — Long-press the hardware power button until the power goes off

...

  1. Make sure that the following Sea/SpinQuest servers are up and running.  If not, contact the network admin or boot them up if allowed.
    1. SeaQuestDsk0, e906-db1 — Wait until SeaQuestDsk0 becomes up.
    2. e906-gat1, e1039gat1
    3. e1039scrun
  2. Make sure that the slow-control rack and the magnet rack are up and running.
  3. Boot up the OS.
  4. Login as "e1039daq".  Only the UVA members know the password.
  5. Click "SX Virtual Link" in the taskbar to open it.  It connects to all remote USB devices automatically.
  6. Start the following VIs.
    1. BOS+EOS Handler — See the procedure written below.
    2. Cryo Control Panel — Double-click "CCP_Main.vi" on the desktop and click the VI "Run" button.LCW Monitor — Double-click "LCW_Flow_Mon_Main.vi" on the desktop and click the VI "Run" buttonicon.

Trouble Shooting

  1. VI shows an error about "/data2".
    1. "/data2" does not get mounted if it is not online when booting up the OS.  There is a way of mounting it manually.  But for now please reboot the OS.
  2. VI shows an error about COM/Ethernet/USB communication with a device.
    1. Make sure that the device is ON.
    2. Open and close "Instacal" (whose icon is in the taskbar) if the device is MCC E-TC.
    3. Close, open and run the VI.  If this does not help, try the next step.
    4. Close all VIs and LabVIEW itself.  Then open and run all VIs.  It is because some devices are recognized by LabVIEW only when LabVIEW starts. 

...