Issue, posted by Peter Zalden on 28 Feb 2024, 06:57 
|
Not sure if this is the cause of the fringes reported before, but at 5.6 keV there are clear cracks visible on the XTD2 Attenuators 75 umm and 150um
CVD, see attached. There is also a little bit of damage on the 600 um CVD, but not as strong as the others.
At 5.6 keV we will need to use the thin attenuators. I will mention again in case this causes problems downstream. |
|
Issue, posted by Romain Letrun on 04 Mar 2024, 09:42
|
The number of bunches during the last night shift kept being changed down to 24 by the device SA1_XTD2_WATCHDOG/MDL/ATT1_MONITOR020 acting on SA1_XTD2_BUNCHPATTERN/MDL/CONFIGURATOR.
This was not the case during the previous shifts, even though the pulse energy was comparable. Looking at the history of SA1_XTD2_WATCHDOG/MDL/ATT1_MONITOR020,
it looks like this device was started at 16:26:25 on Friday, 1st March. |
|
Issue, posted by Harald Sinn on 15 Mar 2024, 00:07
|
SASE1 bunch number was reduced to 10 pulses for no obvious reason.
Traced it back to a malfunctioning of the watchdog for the solid attenuator (see attached error message)
Deacttivated the watchdog for SASE1 solid attenuator. Re-activated it again. |
|
Issue, posted by Romain Letrun on 15 Mar 2024, 07:08
|
There are now two watchdogs for the XTD2 attenuator running at the same time
SA1_XTD2_WATCHDOG/MDL/ATT1_MONITOR020
SA1_XTD2_OPTICS_PROTECTION/MDL/ATT1
that are configured differently,
which results in different pulse limits (see attachment). |
|
Issue, posted by Harald Sinn on 16 Mar 2024, 12:12
|
11:15 SASE1/SPB called that they observed and issue with the SASE1 XGM/XTD2: about every 35 seconds the power reading jumps from 4 Watts to zero and
back. It seems to be related to some automated re-scaling of the Keithlyes, which coincides. The fast signal and downstream XGMs do not show this behavior.
The concern is that this may affect the the data collection later today. |
|
Issue, posted by Frederik Wolff-Fabris on 20 Mar 2024, 12:41
|
BKR called PRC around 06:10AM to inform on vacuum issues at SA1 beamline leading to a lost beam permission for the North Branch.
VAC-OCD found an ion pump in the PBLM / XTD9 XGM presented a spike in pressure that triggered valves in the section to close.
After reopening valves the beam permission was restored; further investigations and monitoring in coming days will continue. Currently all systems |
|
Issue, posted by Chan Kim on 28 Mar 2024, 14:56
|
| Pulse energy fluctuation observed after full train operation in SA2 starts. |
|
Issue, posted by Romain Letrun on 30 Mar 2024, 06:59
|
DOOCS panels are again incorrectly reporting the FXE shutter as opened when it is in fact closed. This had been fixed after it was last reported in February
(elog:24), but reappeared now. |
|
Issue, posted by Chan Kim on 30 Mar 2024, 22:02
|
Continuous pointing drift in horizontal direction.
It may trigger a vacuum spike at SPB OH (MKB_PSLIT section) at 21:07 pm.
|
|
Issue, posted by Andreas Galler on 01 May 2024, 16:39
|
840 pulses not possible at SXP due to big brother settings for the EPS Power Limit rule. The minimum pulse energy was assumed to be 6 mJ while the actual
pulse XGM reading is 550 uJ.
Solution: The minimum assuemd pulse energy had been lowered from 6 mJ to 2 mJ. This shall be reverted on Tuesday next week. |
|
Issue, posted by Raśl Villanueva-Guerrero on 08 May 2024, 13:51
|
Dear all,
Due to a probable issue at the SA1 Transmissive imager, the "OUT" and "YAG" position indication signals seems to be not responsive.
After the FXE team noticed that MODE S was interlocked, the root cause has been narrowed down to this component. Later, further investigation |
|
Issue, posted by Rebecca Boll on 10 May 2024, 00:04
|
our pp laser experienced timing jumps by 18 ns today. this happened for the first time at ~7:30 in the morning without us noticing and a couple of more
times during the morning. we realized it at 15:30 due to the fact that the signal on our pulse arrival monitor (X-ray/laser cross correlator downstream
of the experiment) disappeared. we spent some time to investigate it, until we also see this jump in two different photodiodes different triggers (oscilloscope |
|
Issue, posted by Andreas Koch on 14 May 2024, 09:56
|
EPS issue for Transmissive imager SA1 (OTRC.2615.T9) w.r.t Operation eLog #96
The motor screen positions w.r.t. the EPS switches had been realigned (last Wednesday 8th May), tested today (14th May) and the EPS is again
enabled for the different beam modes. All is back to normal. |
|
Issue, posted by Rebecca Boll on 25 May 2024, 02:38
|
Today in the afternoon, SASE1 was tuned (a description of the activities in att 4). We now realize that this has in some form changed the SQS pulse parameters.
att 1 shows ion spectra recorded under nominally the same photon parameters before (run 177) and after (run 247)
it's also visible in the history of the SASE viewer that the behavior of the SASE3 pulse energy is different before and after 15:45, which |
|
Issue, posted by Harald Sinn on 24 Jul 2024, 10:26
|
In SASE2 undualtor cell 10 has issues. Suren K. will do a ZZ at 11:30 to fix it (if possible). Estimated duration: 1-3 hours.
Update 12:30: The problem is more severe than anticipated. Suren needs to get a replacement driver from the lab and then go back into the tunnel
at about 14:00 |
|
Issue, posted by Harald Sinn on 24 Jul 2024, 11:35
|
The control rack of the soft mono at SASE3 has some failure. Leandro from EEE will enter the XTD10 at 12:00.
Beam will be interupted for SAS1 and SASE3.
Estimate to fix it (if we are lucky) is one hour. |
|
Issue, posted by Harald Sinn on 27 Jul 2024, 09:10
|
SASE1: Solid attenuator att5 is in error. When it is tried to move it out, the arm lifts, but does not reach the final position before the software time-out.
We increased the software time-out from 4 seconds to 7 seconds, which didn't help. We suspect that there is a mechanical problem that prevents
the att5 actuator to reach the out position. |
|
Issue, posted by Romain Letrun on 10 Aug 2024, 07:19
|
The SASE1 HIREX interlock is not working as expected.
At the position 'OUT' (step 2 in HIREX scene) and while none of the motors are moving, the interlock SA1_XTD9_HIREX/VDCTRL/HIREX_MOVING
is triggered, which prevents the use of more than two pulses. |
|
Issue, posted by Peter Zalden on 08 Sep 2024, 20:30
|
We observe a continuous horizontal beam drift in SA1 after the M1 incident. It seems not to converge, so one can wonder where this will go....
Attached screenshot shows the M2 piezo actuator RY that keeps the beam at the same position on the M3 PBLM. These are about 130 m apart, The
drift is 1V/12 hours. 0.01V corresponds to a beam motion by 35 um. So the drift velocity is 0.3 mm/hour. In the past days this had at least once lead to |
|
Issue, posted by Peter Zalden on 09 Sep 2024, 23:19
|
| Finally, the drift velocity of the pointing reduced approx a factor of 2 as compared to yesterday, see attached. Possibly it will still converge... |