Dell Precision Tower 5810
(Spare: Dell OptiPlex 3060, being used for the PLC system)

Turn-Off/On Procedure

Turning Off

1. Stop and close the following VIs.
   1. LCW Monitor
   2. Cryo Control Panel
   3. BOS+EOS Handler
2. Shut down the OS.

Turning On

1. Make sure that the network disk (/data2) is online.  Ask the NM4 network manager if you are not sure.
2. Boot up the OS.
3. Login as "e1039daq".  Only the UVA members know the password.
4. Open "SX Virtual Link" in the taskbar.  It connects to all remote USB devices automatically.
5. Open "Start Menu" → "Measurement Computing" → "Instacal" and immediately close it.  This step might not be necessary.
6. Start the following VIs.
   1. BOS+EOS Handler
   2. Cryo Control Panel
   3. LCW Monitor

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" if the device is MCC E-TC.
   3. Restart the VI.  It is because some devices are recognized by LabVIEW only when LabVIEW starts. 

BOS+EOS Handler

A program to detect the BOS & EOS signals to update the BOS, EOS & SPILLCOUNTER variables on EPICS.


The following VI file should be kept running; "D:\e1039\labview_work\TestIR\bos_eos_mostreal_atBOS.vi".
It is to

The turn-off/on procedures below are temporary as the configuration is being changed.
The procedure is described by Misha in DocDB 7683 also.  We had better merge the documentation when appropriate.

Turning Off

1. Click the "STOP" button.  It might show an error, but it is fine for now.
2. Close the VI file, by clicking the right-top Close button of the window.  Do not  save any change, if asked.

Turning On

1. Make sure that the NIM bin with the gate generator for BOS/EOS is on.  It is in the bottom of the right most rack.
2. Double-click "bos_eos_mostreal_atBOS_sid_saved.vi" (which is a shortcut) on the desktop.
3. Click the VI "Start" icon.
4. Right-click "monitor_spill.ps1" on the desktop and click "Run with PowerShell".  It pops up a small text terminal.
5. Wait for one minute at max to confirm that the text terminal shows new records of BOS, EOS and SPILLCOUNTER.

Communication with Slow Control Devices

All devices in the slow control rack are connected with the target computer through the interface converters.  The hardware configuration is explained in README.md, note_converter.md, etc. in this repository:

https://github.com/uva-spin/Temperature-Pressure-VIs

All virtual USB devices are usually disconnected.  You have to connect/disconnect each device before/after you use it via "SX Virtual Link".  You can click the icon in the taskbar to bring up the user interface like this. 

Usage of Git Repository

The "uva-spin" GitHub repository ( https://github.com/uva-spin ) is cloned at "github" on desktop.  Our default software to manipulate the repository is "Git Bash" in "Git for Windows" ( https://gitforwindows.org/ ).

You can right-click the desktop and click "Git Bash Here" in the menu, or you can click the icon of "Git Bash" in the task bar.  Once a text terminal of "Git Bash" is opened, you can do "cd github/e1039-target-controls", "git pull", etc.

Environmental Variables for EPICS

The target computer has to communicate with the EPICS server to set BOS, EOS and SPILLCOUNTER.  We follow this procedure.

1. Search for "env" in the search box.
2. Bring up "Edit the system environment variables".
3. Click the "Environment Variables..." button.
4. Add or modify the EPICS variables; EPICS_BASE, EPICS_CA_ADDR_HOST and EPICS_HOST_ARCH.  Example.
5. Reboot.

NFS Mount

The target computer mounts the E906/E1039 network disk (i.e. "/data2") to record slow-control data.  The disk is automatically mounted when the main user logs in.  It was configured on 2021-11-21 by the following procedure.

1. Collect the information on the network disk.
   • Network path = "192.168.24.160:/mnt/seaquestdsk0" — Found in "e1039gat1:/etc/fstab"
     
   • UID = 500 (e1039daq) and GID = 10391 (e1039sc) — Found by "ls -n /data2/e1039_data/slowcontrol_data"
2. Search for "turn windows features on or off" on the task-bar search box, and click it.
3. Enable "Services for NFS".
4. Enable the write permission.

   • Open "regedit" from the task-bar search box.

   • Expand HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> ClientForNFS -> CurrentVersion -> Default.

   • Create a new DWORD value (via right-click menu), with name = "AnonymousUid" and value = "500".

   • Create a new DWORD value (via right-click menu), with name = "AnonymousGid" and value = "10391".

5. Reboot the OS.
6. Mount the network disk manually for test.
   • Open "command prompt" from the search box.
   • Execute this command: "mount -o anon -o nolock -o fileaccess=775 \\192.168.24.160\mnt\seaquestdsk0 Z:".  Note that "-o anon,nolock,fileaccess=775" does not work!
   • Screenshots: Command prompt. and Z: folder.
7. Set up an automated mount via startup
   • "Start Menu" → "Run" → Enter "shell:startup".

   • Create "nfsmount.bat" with the following contents:

     mount -o anon -o nolock -o fileaccess=775 \\192.168.24.160\mnt\seaquestdsk0 Z:

   • Reference: https://dop-amine.com/posts/persistent-nfs-windows/

Notes:

• The mount option "-o nolock" was necessary to avoid an error when creating a file: "0x80070021: The process cannot access the file because another process has locked a portion of the file."
• "UID = GID = 65534" didn't work since the write permission of "/data2/e1039_data/slowcontrol_data" is not granted.
• It is a bit anxious that any user on the target computer can (re)move any network files by mistake, where such mistake can happen more easily on graphical interface.  A precaution is wanted.
• The registry can be edited via the command prompt.  Have a try next time:
  
  • New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousUID -Value 500 -PropertyType "DWord"
  • New-ItemProperty HKLM:\SOFTWARE\Microsoft\ClientForNFS\CurrentVersion\Default -Name AnonymousGID -Value 10391 -PropertyType "DWord"
  • Reference: https://blog.edie.io/2018/06/16/mounting-nfs-shares-in-windows-using-identity-mapping/
• Reference: https://docs.datafabric.hpe.com/61/AdministratorGuide/MountingNFSonWindowsClient.html

Disabling Automatic Windows Update

There are several ways of disabling the automatic Windows updates on Windows 10 Pro.  Let's use "Group Policy" on the target computer.  It was disabled by the following procedure on 2021-10-25.

1. Search for "gpedit.msc" (using the task-bar search box) and execute it.
2. Go to "Computer Configuration" -> "Administrative Templates" -> "Windows Components" -> "Windows Update".
3. Double click "Configure Automatic Updates" policy setting and select "Enabled".
4. Choose "2" ("Notify for download and notify for install") under "Configure automatic updating" section.
5. Click "Apply", followed by "OK".

Reference:  https://answers.microsoft.com/en-us/windows/forum/all/how-permanently-disable-windows-10-pro-64-updates/18727670-db05-4267-80fb-cf2622eee8c1

The standard configuration about the Windows update is available at "Settings" -> "Update & Security" -> "Advanced Options".  It allows us to only postpone an update up to 35 days.

Change in Target Computer Setup

kind of a log-book.