Alignment to HED: https://in.xfel.eu/elog/XRO+Beam+Commissioning/205

SA2 - divergence with various M2 bender positions  HED - https://in.xfel.eu/elog/XRO+Beam+Commissioning/200

SA2 - divergence with various M2 bender positions MID - https://in.xfel.eu/elog/XRO+Beam+Commissioning/196

Issues with HED PBLM blade in SA2: https://in.xfel.eu/elog/XRO+Beam+Commissioning/195

Vobration measurements could not be done https://in.xfel.eu/elog/XRO+Beam+Commissioning/207

End of shift:

SA2 left with preAbs in

machine wanted to increase intensity

Moved out MONO, aligned SDL without MONO

Looked at both beams on DES

Struggled to get the same beam size with SDL inserted compared to direct beam (~8 um); fixed by adjusting slits

Major beam-pointing issues w/ the upper branch on the x-ray eye, even when all `fine` motors were off

Experimented w/ turning off  certain `coarse` motors at a time

• Aligned both branches of the split-and-delay line.
• Brought the beam into the experimental hutch to image it on the x-ray eye; the sample hexapod is not moving (again?); the values keep changing, but the device clearly does not move

PLEASE INVESTIGATE TOMORROW

• Looked at the beam on the Zyla (Zyla is still in)

TODO for tomorrow:

• Make x-ray eye work
• Use the x-ray eye, measure pointing stability (both beams) until Bertram arrives
• With Bertram, do timing scans on x-ray eye and hope to see interference fringes

Achievements:

1. Beam in sample chamber, almost overlapping with ALAS

2. We saw signal on MCP and diode2

3. Sample Motors aligned close to the desired height in chamber

Problems:

1. Slow response of Screens and mirror motors, solved by restarting the Beckhoff of the mirror motors

2. Could not find signal of unfocused beam on SCS Pop-In

3. Acquiring data with the spectrometer for energy calibration does not work

4, Motor STZ of XRD does not allow halfclip of the beam.

5. No Fluorescence signal on the APD

6. In the DAQ we can not execute "assign" or "cofigure" action

Achievements

• Found coarse timing between XFEL and optical laser

Problems

• Did not see a observe fine timing signal from silicon nitride measurement

Plan for night shift

• Continue with liquid jet optimization and static measurements

Achievements

• Determined temporal overlap between the X-ray and laser
• measured Ti L-edge XAS and RIXS on samples for Asamara beamtime

Problems

• No problems

Plan for Next Shift

• Confirm spectrometer resolution at the O K-edge following spectrometer rotation
• Transfer user samples into XRD Chamber
• Check X-ray damage on user samples and begin user program

# Morning Shift Summary 21.10.23

Ben, Eugenio

Achievements
* Found maximum of CDW with theta scan
* set up for time-resolved measurements

Problems
* FEL was down most of the shift due. Beam delivered around 12:30

Staff: DM, CK, KK

X-ray delivery

• 7.8keV, 2.4mj, stable delivery, homogeneos intra train energy most of the time.
• SASE 3 background

Optical laser delivery

• no laser used

Achievements/Observations

• Aligned until IRU, until before full beam test

Issues

• Valve after AGIPD was disconnected elog:12718
• SASE 3 background affecting beam focus at IRU elog 12722
• AGIPD scattering, could not solve fully with slits, to be improved tomorrow

Instrument status

• AGIPD HV off.
• AGIPD gate valve closed and pinned.
• Attenuators set to thickest diamond.
• Vacuum valves closed.

To do for next shift

• Continue with alignment, then experiment.
• Check slits or other solution for AGIPD scattering
• Confirm the beam focus impact from SASE 3 background, after we moved NKB coating (verify if it remains)

After going in and reconnecting the camera, we observe att. 1.

According to logs the camera device server was restarted around 11pm, however the camera instance was never reinstantiated after the restart. The Karabo GUI did not indicate that properly, instead showed a frozen image that looked as if the camera works properly.

(see history of camera state in att. 2)

Device Server log shows that after camera connection was lost, the device server restarted?! Was this restart done on purpose?

2023-11-23T23:02:22.499 ERROR  karabo.AravisBasler2Camera  : SQS_AQS_UPP/CAM/A2A1920_2: Could not synchronize timestamp: GigEVision write_memory timeout
2023-11-23T23:02:27.504 ERROR  karabo.AravisCamera  : SQS_AQS_UPP/CAM/A2A1920_2: arv_device_get_float_feature_value failed: GigEVision read_memory timeout
2023-11-23T23:02:30.007 WARN  karabo.AravisCamera  : SQS_AQS_UPP/CAM/A2A1920_2: Control of the camera exflqr50765 is lost
INFO  Successfully loaded plugin: "libslsDetectors.so"
INFO  Successfully loaded plugin: "libaravisCameras.so"
2023-11-23T23:02:33.773 INFO  openMq  : Opened TCP connection to broker %s:%d.
2023-11-23T23:02:33.775 INFO  openMq  : Connection ping enabled (ping interval = %d second).
2023-11-23T23:02:33.778 INFO  openMq  : Connection connected to broker
2023-11-23T23:02:33.778 INFO  karabo.net.JmsConnection  : Opened TCP connection to broker tcp://sa3-br-sys-broker-2:7777
2023-11-23T23:02:33.779 INFO  karabo.core.DeviceServer  : Logfiles are written to: "/scratch/xctrl/karabo/var/log/cppServer/sqs_nqs_vmi_cam/device-server.log"
2023-11-23T23:02:34.785 INFO  karabo.xms.SignalSlotable  : Instance starts up in topic 'SQS' as 'cppServer/sqs_nqs_vmi_cam' - Karabo 2.16.6
2023-11-23T23:02:34.786 INFO  cppServer/sqs_nqs_vmi_cam  : DeviceServer starts up with id: cppServer/sqs_nqs_vmi_cam
2023-11-23T23:02:34.786 INFO  cppServer/sqs_nqs_vmi_cam  : Updated list of devices available: AlarmService,AravisBasler2Camera,AravisBaslerCamera,AravisCamera,AravisPhotonicScienceCamera,CameraImageSource,DataLoggerManager,FileDataLogger,FileLogReader,Gotthard2Control,Gotthard2Receiver,GotthardControl,GotthardReceiver,GuiServerDevice,ImageSource,InfluxDataLogger,InfluxLogReader,JungfrauControl,JungfrauReceiver,PropertyTest
2023-11-23T23:02:34.934 INFO  karabo.core.DeviceServer  : Sending instance update as new device plugins are available: AravisBasler2Camera,AravisBaslerCamera
2023-11-23T23:02:34.934 INFO  cppServer/sqs_nqs_vmi_cam  : Keep watching directory: "/scratch/xctrl/karabo/plugins" for Device plugins
2023-11-23T23:02:34.934 INFO  cppServer/sqs_nqs_vmi_cam  : Starting Karabo DeviceServer (pid: 235604) on host: sqs-rr-sys-con-cams-1, serverId: cppServer/sqs_nqs_vmi_cam, Broker: tcp://sa3-br-sys-broker-2:7777
2023-11-23T23:02:35.073 INFO  karabo.core.DeviceServer  : Successfully connected to time server 'SQS_RR_UTC/TSYS/TIMESERVER'

==> Status of Taylor Cone unknown for runs 334 - 401

We had to physically unplug and replug the ethernet cable to the camera to get it to work again.

REPAIRED / FIXED

Problem: The imager SPB_XTD9_IMGPII45 insertion motor lost steps and kept the machine to maximum 2 bunches per train.
Mitigation by DOC/EEE/PRC on 8 April 2023: made sure that screen seems actually out of beam and took imager out of interlock condition.
"Repair" by XPD on 10 April 2023 02h15:
a) recalibrated OUT position.
b) verified that EPS-OUT switch shows green when moving to OUT position in MDL.
c) put back the imager into the interlock conditions.
d) communication with BKR before and after the intervention (SPB and FXE didn't use the beam).
Repair instruction see: https://in.xfel.eu/elog/SASE1+technical+commissioning/2065

Achievements

• Characterized optical laser spot at sample

Problems

• FEL beam had very unstable intensity and spectrum. As a result no useful data could be collected during the night
  • FEL pointing seemed to be stable on all tunnel imagers. The issue was communicated to BKR, and they said that things looked fine from there perspective.
  • Large fluctuations in spectral distrubtion at SCS spectrometer were observed. See video at https://syncandshare.xfel.eu/index.php/s/emtwonCsQJJqpz6
  • Oth-order beam on SCS pop-in showed large intensity fluctuations with ~50% of the time showing no beam at all

SASE3 Summary of Maintenance Period and Ramp up activities

Maintenance

- Soft Mono motions (grating horizontal and grating pitch) were cleaned and lubricated

- Vertical slit encoders were double checked (without moving them) to exclude that Karabo errors are coming from them.

- Motors of Mirrors were inspected (without dismounting) to check if some strange noise is created during motion. The SA3 M2 Tx motor was very noisy at 0.035 speed and not anymore at 0.03. 

- Settings of acceleration and velocity was optimised together with EEE (Bernard). The noise at SA3 M2 Tx was disappearing even with 0.035 speed.

- M1 and M2 chillers had service (water filling) and were then set on again before closing the tunnel. For M5 and M6, cooling is off.

- Piezo controller for M1 was disconnected and removed. Therefore, the M1 piezos are unavailable at the moment. This was agreed with the experiments after it was found some instabilities in the beam position (beam was moving by itself sometime). 

- PBLMs were checked: https://in.xfel.eu/elog/XRO+Beam+Commissioning/76

Inst Dept Ramp up

- SA3 M2 RY was not moving. This took several hours to be solved. Temprary explanation: stepcounter value changed without any physical movement of the motor and later on, encoder was thought to be wrongly calibrated and thus adjusted. As a result, the motor position is lost and needs to be fiducialised again in the alignment.

- The performance of "Closed loop" and "Backlash Correction" was tested. The result is that the TY motors need to remain in open loop and with 'Backlash Correction' activated (value 2 microns). This is increasing the reproducibility of the positioning. The other motors could be used in closed loop if required, but then the Backlash Correction has to be deactivated.

- SA3 M6 RY encoder has an incorrect calibration at the moment. Please refer to the motor position only. We will work on a solution asap.

- The vertical slits (SCS, SQS, SXP) were checked and they move correctly.

- Several positions were fiducialised, that could be used as a starting point for Instruments fine alignment:
SXP 9mrad (8.9mrad) mono he premirror 937eV 
SXP 9mrad (8.9mrad) unfocused
SCS 9mrad (8.9 mrad) unfocused
SCS 9 mrad (8.3mrad) unfocused
SQS 9mrad (8.7mrad) unfocused
SQS 20mrad (18.5mrad) unfocused

- SEPS interlock was succefully tested: https://in.xfel.eu/elog/XRO+Beam+Commissioning/112


 

SASE2 Summary of Maintenance Period and Ramp up activities

Maintenance

- Many vibration tests were done.

- M1 chiller had service (water filling) and was then set on again before closing the tunnel. M2, M3 cooling is off.
 

Inst Dept Ramp up

- Positions reached:
MID 2.2 mrad at 9 keV 
HED - 9keV - 2.7mrad - B4C stripe

- checks for the stripes were done:
M3 verification of coating positions and horizontality or the mirror
MID alignment Pt stripe - vertical motion of mirrors with Euler

- for the stripes, we have now a watchdog telling if the mirrors are on the B4C or the Pt stripe (see image below)

We were set-up for 5.7 keV photon energy in SASE1. We made a test with BKR to change this energy to 9.3 keV. This had an effect on our two-color setup:

The first color pulse energy increased. See att 1. Green is the reference at 5.7 keV, blue is at 9.3 keV.

Att 2 shows the XGM history: pulse energy went up to 200 uJ in SQS XGMD during the change.

the users are unhappy about the increase of pulse energy in the pump pulse, because the ratio of pump versus probe is optimized with the setting where SASE1 operates at 5.7 keV.

we plan to record continuous delay scans (about 1 day for each scan) for the rest of the week, and pump-probe settings should be constant over time.

SASE1 Summary of Maintenance Period and Ramp up activities

Maintenance

- MC2 library update was deployed by EEE and most of the motors were tested afterwards
- Some motors were acting strangely: https://in.xfel.eu/elog/XRO+Beam+Commissioning/82
- As a rule, the Closed Loop and the Backlash Correction are atm incompatible and therefore you have to choose one of them. When a strong reproducibility is needed, the motor should remain in Open Loop and with Backlash Correction activated (2 microns for TY and 50 microns for TX, tipically): https://in.xfel.eu/elog/XRO+Beam+Commissioning/83|
- FXE mono1 bottom crystal was exchanged, realigned parallel to the beam. Recommissioning due WK5 together with FXE
- M1 and M2 chillers had service (water filling) and were then set on again before closing the tunnel. M3 is currently with cooling off.

Inst Dept Ramp up

- Several positions were fiducialised:
SPB alignment 2.41mrad 9keV
FXE alignment 2.4 mrad 9 keV

Attch 1: We were having trouble focusing at IRU chamber. After multiple attempts the best we could achieve was 2.9-3.1 um beam.

Attch 2: We then wanted to test if this was caused by the SASE 3 background, after them changing from >350 pulses to 1, we saw an instant improvement of ~0.5um down to 2.3 um beamsize.

Attch 3: After optimizing without SASE 3 background, we got down to 1.9 um (1 um less then with SASE 3).

Attch 4: Finally, after SASE 3 changing back to their <350 pulses the beam now changed from 1.9 to 3.9 um! (instead of the previous 3.1um)

This because the SASE1+SASE3 focus =/= SASE1 focus....

We did not have much time to tune the beam without SASE 3 background, we should think about managing this tomorrow during alignment, and also for data collection...

Bunch number control - SA3 FEL imager

As announced today in the XO meeting the SA3 FEL imager has a new feature, see screenshot, encircled:
- In case of danger for the YAG screen the bunches SA3 are set to "0" via the BunchPatternServer (SA3 Main scene).

What to do:
- Choose a different screen, BN or CBor, and again set the number of bunches needed.
- If operation with the YAG screen is wished reduce the pulse energy at the screen.

Further info:
- In general, danger to the YAG screen, even in single bunch operation, is avoided if the GATT is operated at <10% transmission. Observe the screen Watchdogs.
- This feature is installed at the SA3 FEL imager only, after new recent damages.
- Activate the device with "Start", deactivate the control with "Stop Monitoring".

In case of not-correct behaviour inform the PRC (Andreas Galler this week) or me.
This entry is copied to the ttfinfo logbook.

The SA3 EPS power limit at the Big brother was disabled to allow photon energy scans in SQS (due to Kr resonance at XGM, invalid power values are generated and then beam is blocked);

Action was performed by Lars F. (RC), Michaela Petrich (PRC) and F. Wolff-Fabris (XO) with Accelerator RPO.

It will be activated again on Monday 15.05.

**Update 15.05: the above mentioned rule is activated again at 08:10AM.

Data for the Horizontal jitter at the HED Pop-In was observed during beam delivery on cw05 (03-05.Feb) and cw07 (14-16.Feb) (see attached pictures). 

We have a similar base jitter in both periods of beam delivery to HED, ranging from a minimum of 50-60um to around 80-100um in both operational weeks.