We use the following list of sources for calibration of the Xray detectors:

- 241Am_low [40.5 kBq (3%), 01.10.2020 12:00 UTC] [URL=https://elog.gsi.de/esr/X-Ray+Lab/201006_131944/20-007_241AM_40kBq.pdf]SpecSheet[/URL]

- 241Am_high [OM 666, 430 kBq (3%), 19.09.2006]

- 133Ba_low [40.8 kBq (3%), 01.10.2020 12:00 UTC] [URL=https://elog.gsi.de/esr/X-Ray+Lab/201006_131944/20-003_133Ba_40kBq.pdf]SpecSheet[/URL]

- 57Co [427 kBq (3%), 01.10.2020 12:00 UTC] [URL=https://elog.gsi.de/esr/X-Ray+Lab/201006_131944/20-005_57Co_400kBq.pdf]SpecSheet[/URL]

Was another 133Ba source used???

in the LAB:
- setup of DAQ in GSI network
- presetup of remote control (HV, DAQ, LN2, etc)
- particle detectors + source tests
- setup and test trigger logic

in ESR:
- xray detector installation + calib.
- LN2 cooling system
- telescope installation @ target
- recoil det. installation downstream target
- DAQ rack and cabling
- cabling documentation

The proposal as submitted to G-PAC in 2020 as well as the Letter of Recommendation from G-PAC.

192.168.0.1 ESR Gateway (atpnuc004)


192.168.0.66 CAEN HV 1 (telescope)
192.168.0.67 CAEN HV 2 (recoil)

The remote control of several devices is done via the private ESR network. The following list of devices is currently in use:

device	interface	comment
HiVoltage [Telescope + FissionBottom]	IP: 192.168.0.66:1470    [CAEN66 via HVbackend]	normal control via the HV_gui, fallback plan is direct telnet connection
HiVoltage [Heavy Residual]	IP: 192.168.0.67:1470    [CAEN67 via HVbackend]	normal control via the HV_gui, fallback plan is direct telnet connection
HiVoltage [FissionSide + FissionBottom]	IP: 192.168.0.68:1470    [CAEN68 via HVbackend]	normal control via the HV_gui, fallback plan is direct telnet connection
LowVoltage [Telescope + FissionBottom] IP: 192.168.0.115	control via the LV apps, no fallback remote control
LowVoltage [Heavy Residual]	IP: 192.168.0.113	control via the LV apps, no fallback remote control
LowVoltage [FissionSide + FissionBottom]	IP: 192.168.0.114	control via the LV apps, no fallback remote control
Power Switch of ESR network gateway [atpnuc004]	IP: 10.99.1.87  [http://ws-mbs-1]	power cycle the gateway via the web interface http://ws-mbs-1
Power LN2 filling [LN2 valve control]	IP: 192.168.0.21  forwarded to atpnuc004:9921	used for remote LN2 filling via the LN2_filling app
VME Crate [power cycle]	IP: 192.168.0.40	use the curl script vme_crate.sh to toggle power state
Detector Scale 1	forwarded to atpnuc004:5000/TTYUSB0	used by the LN2_filling app to measure LN2 level
Detector Scale 1	forwarded to atpnuc004:5000/TTYUSB1	used by the LN2_filling app to measure LN2 level
WebCam LN2	IP: 192.168.0.60 forwarded to atpnuc004:9925	used to monitor LN2 filling via app
WebCam DAQ	IP: 192.168.0.53 forwarded to atpnuc004:9924	used to monitor the LED status on VMMR and DAQ


HighVoltage Control

The HV control works via a backend service that runs on atpnuc004 and listens at atpnuc004:5555. This service collects current data from the 3 Caen HVs and allows sending commands.
HV backend

to be updated
HV GUI

The HV_gui can be run on any lxg-linux-computer at GSI using the litv-exp user.

start script: /u/litv-exp/experiments/e0028/HV_gui.sh
LowVoltage Control

The LV control for the MMR power currently works via 3 independent apps, one for each device.

start scripts:

/u/litv-exp/experiments/e0028/MMR_FisSideTop.sh

/u/litv-exp/experiments/e0028/MMR_TelFisBot.sh

/u/litv-exp/experiments/e0028/MMR_HeavyRes.sh
LN2 Control

The LN2 control app for filling the X-ray detectors enables the filling via valve control, LN2 level measurement via scale readout and the monitoring of the filling process via webcam.

start scripts:

/u/litv-exp/experiments/e0028/LN2_control.sh
DAQ camera

The DAQ can be monitored via the WebCam using the script below. The lights at the ESR target have to stay on for this to work properly.

start scripts:

/u/litv-exp/experiments/e0028/DAQcam.sh