Attached you find a manual for the software used to control the movement of the XUV detector and the copper mirror detector. 
The software is also used to set the electrode voltages and coil currents of the XUV detector. 

> Attached you find a manual for the software used to control the movement of the XUV detector and the copper mirror detector. 
> The software is also used to set the electrode voltages and coil currents of the XUV detector. 

We tested the remote access to the raspberry pi as explained in the manual attached to the original entry of Volker. It was tested from
the linux machine LXG1050. Attached you can find a screenshot of the running program.

The connection to the XUV and Cu were lost during the nightshift.

The XUV detector was in the park position,
BUT the Cu mirror was in the "Measurement position" (moved in / active).

This could be one of the main problems that we had much lesser ion beam intensity since the UNILAC and SIS18 failures last night.

we checked the UV laser power at 10:15 am. It was only 8.5 - 9 mJ. Pumping power was 460 mJ, which is the maximum output of the current system. We should change the flashlamps soon

Konstantin and I generated a signal in the Messhütte and sent it to the ESR. 
There, we used a 44m BNC cable that was sufficently long to reach all detectors. 
Our signal was connected instead of the PMT/PD. Hence, it was a roundtrip measurement.
In the Messhütte we checked the delay between the generated signal.

PD North 1460(1)ns
PD South 1455(1)ns
Particle North 1239(1)ns
Particle South 1179(1)ns
UV North 1322(1)ns
UV Middle 1322(1)ns
UV South 1321(1)ns
Cu 1322(1)ns

We also checked the time delay of our cable to the detectors by measuring the reflection of the unterminated cable. 
Function generator to detector: 1520(5)/2 ns
Function generator to scope: 5.1(5) ns
Total: 765(3) ns

It is planned to change the scan range of the laser wavelength from 322.41 - 322.0 nm to 322.01 - 321.6 nm @ 4 a.m. 

We changed the LV code so that the Cobra Set Wavelength is permanently sent. Before it was only sent once at the beginning of each laser step. This, however, lead to too much data for the LV->MBS server.
This was fixed by inserting a 250 ms wait in LV (in Krypton data VI). Basically, all LV values are now updated every 250 ms, which works fine with MBS

After changing to h=1
The frequency manipulation #5: f=242.021487MHz (124th harmonic) [no bunching]
Manipulation #7: f=242.021812 MHz [with bunching]

Primary beam is in the ESR now. Markus and the team are tuning the ESR.

I just performed a backup of all data (+log-Files) that were collected until now to the two RAID HDDs.

For DAQ1: /media/sdc2 - last file 229Thor7889.lmd. Please note, that the naming sceme on DAQ1 is inconsistent - please look for the filenumnbering
For DAQ2: /media/sdd2 - last file 229Th0153.lmd

Since we cannot write on lustre, as a temproal solution two RAID 1 (mirror) USB hard disks  with cpacity 6 TB each are installed.
The disk on the lxg1297 the disk can be accessd at /meida/sdd2
an on the lxg0155 at /media/sdc2
Regular backups should be written to these disks but NOT during data taking.

If we run out of local disk space /data.localx on the machines they could also be used as target for mbs.

Pleae check regularly if there is enough spance on the local disks.

All pressuzied air drives are tested now and are working properly

We cross-checked the laser-ion alignment. The horizontal position was optimized. However, 
since the laser beam is much larger than the ion beam, this was not an issue for measurements, which
have been performed during the last shifts.
The modified parameters of the stabilization system are attached.