Dye of the laser system has been changed. UV laser power increased from ~8 mJ to 11 mJ pulse energy.

My guesthouse phone number: 06159-71-2957

The Xuv-detector cabel channels seem to be 
wrongly labeled in the Messhütte (see 
picture) and are propably also wrongly 
connected. Need to be relabeled and reconnected either in the 
messhütte or in the laserlab. I will look for the best 
solution tomorrow morning. 

I co controlled all detector signals and 
adjusted the threshold to be just above 
the noise. I will double check this when 
the detector can be moved in and we have a 
beam. 

The UV-LED of Münster was connected over 
channel 8 to the Messhütte. 6V are 
supplied by the power supply (picture 2). 
The Led is located at the xuv detector 
(picture 1).

Some further information regarding the 
xuv-detector and its components.

Count rates were measured for the XUV-
detector for a full circle:
Cathode: -5V, shields: 0V, main coil 8A, 
sec coil 2A, 
No beam - pos 0mm: ~10 Hz
Hot beam - pos 0mm: ~5 kHZ
Cool beam - pos 147mm: ~200Hz

Some Default Settings for the XUV 
Detector. The copper 
mirror should always move fully in.

Possible positions: Between 0mm and 147mm. 
Background was 
very high for anything higher than 100mm 
in the last 
experiment. 50mm was optimal. This should 
be tested again 
with repaired and modified shields. 

Good default values for the XUV detector 
parameters have 
been proven before to be:

Cathode: -5V
Movable shield: 0V
Fixed shield: 0V
Main coil: 8A
Secondary coil: -2.4A

(negative values set in hardware, only 
positive software 
inputs are possible)

A lot of cables were wrongly or not 
connected to the DAQ 2. 

Channels are now for both DAQ:
0 XUV-Back
1 XUV-Anode
2 XUV-Anode-delayed
3 PMT-South
4 PMT-Middle
5 PMT-North
6 PMT-Cu
7 Part-det-south
8 Part-det-north
9 1kHz
10 -
11 -
12 Delay-common-stop
13 PD-NO
14 PD-SO
15 Q-switch

All data taken by the DAQ2 has to be 
considered as faulty up to now. 

Carsten was furious.

When the XUV-detector has to shut down unexpectedly, it can happen that the Mesytek power supply crashes and can't be 
communicated with. If this happens the Mesytec PS needs to be restarted from hand inside of the ESR. This can be done by 
restarting the crate located at the bottom of the XUV-detector. 

This crash happened during the night shift today and the Mesytec should be restarted today as soon as possible. For 
example when the laser stabilization gets fixed.

In normal operation this should never happen if no mistakes are made. 

For somebody who knows the DAQ1 code: Go4 resets the histograms with each laser step. Can there be additional histograms where the data gets accumulated?

And possibly a histogram where important detectors are plotted against the laser steps? The read back wavelength of the wavemeter is not very precise. 

newest version V2 - valid since Mo 04.April 2022

Beam settings:
primary beam 
copper stripper
I_el=300mA
U_el=205.490kV (Ohm_labs)
3.5e7 ions at injection


MSCF/ADC settings: 
ch2 < Mid PMT x10
ch6 < Mid PMT x100
see attachment (setting_e142....) for detailed MSCF settings

Files/Runs [DAQ2]:

------------------new file-----------------
229Th0022.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40

no corresponding file in DAQ1

------------------new file-----------------
229Th0023.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40
laser scan active:
- steps: 21
- cycles: 5

file in DAQ1:
...7768.lmd

------------------new file-----------------
229Th0024.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: out (-127)
-NA pos: -10
-Ni pos: 40
laser scan active:
- steps: 21
- cycles: 5

file in DAQ1:
...7770.lmd

------------------new file-----------------
229Th0025.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40
laser scan not:

VUPROM -> delay stop trigger ch12 

file in DAQ1:
no file

no laser scan

------------------new file-----------------
229Th0026.lmd
bunched beam [ESR in manip. at 7]
beam scraped using detector drives
-SA pos: 0
-NA pos: -10
-Ni pos: 40
laser scan active:
- steps: 21
- cycles: 5

VUPROM -> delay stop trigger ch12 

file in DAQ1:
...7772.lmd

attached are the current shaper settings.

list of currently connected channels:
ch2: mid x1
ch4: Cu  x1
ch6: mid x2
ch8: Cu  x2
ch9: XUV x1
ch10:XUV x2

The additional signals from PMTs and XUV detector needed for spectroscopic analysis in the second DAQ are patched to AP Messhütte (MH) via the red patch panel at the inside of the target region. The patch channels F1 to F8 (also labeled A to H in red on white) are used and extended by a cable bundle to reach below the mirror chamber. Inside the MH the signals arrive at the red patch panel and are forwarded to the blue patch panel close to the laser DAQ using channels 1 to 8 (also labeled A to H).
 
The entire connection for these 8 channels from the mirror chamber to the blue panel has been tested with a pulser signal of ~115mV amplitude. After transfer the amplitude has decreased to ~40mV, see also attached fotos.

The signal transport time from the mirror chamber to the blue panel is ~407 ns. This was measured by patching a logic puls from ESR to MH and back to ESR, as show in the delay_ESR... foto attached.  

The MesyTec Shaper & Constant Fraction (MSCF) is used to process the PMT/det signals for the ADC in the second DAQ.
It can be setup on its front panel, but single channel setup is very tedious.
Remote control of the settings is possible using an epics server and client.

All of the following is done with the "litv-exp" user:

server: atpnuc001 (in the screen session "E142")
client: lxg1275 

The server should run undisturbed, but in case of a power failure, you can start the server like this:
> ssh litv-exp@atpnuc001
> cd e142
> ./E142_start_ioc.sh

To check server:
> ssh litv-exp@atpnuc001
> screen -x (CTRL-a CTRL-d to leave screen)

To connect the client gui for remote control, do:
> ssh litv-exp@lxg1275
> E142_epics
The panel is more or less self-explaining. 
One thing has to be noted: the Monitor Channel selection is shifted by -1.
I.e., [ch 1] is button [0], etc.

The MSCF settings can be stored and loaded to/from file by using a bash-script.
The settings will be saved/loaded from: 
/u/litv-exp/e142/mscf_settings/
files names are "setting_e142.<linux_timestamp>"

The scripts are also in /u/litv-exp/e142/mscf_settings/
use 
./mscf_save.sh                   for saving the current settings to a new file
use 
./mscf_load_last.sh              to load the last settings file (by timestamp in the filename) 
use 
./mscf_load_file.sh <filename>   to load the settings of a specific file

we had no injections in the ESR again 

it turned out that the injection kicker of the ESR has a problem 

since shortly after 7 AM we have no beam in the ESR
(reason unclear) 

Both DAQs also crashed. 

Beam back in ESR at 7:20 or so 

Problems with restarting DAQ1 

Problems with restarting DAQ2 

Files names 7801 and 7804 and 0047 and 0050 cannot be used