Dear all,

Vacuum loop is up and running, we would wait till Raul check the interlock of the "OK" signal for the Vacuum and then, if everything is correct, we would put again the XGM controlled by the Vacuum PLC.

Thank you!

Dear all,

EPS and Motion loop have been updated to the last framework version with the last hotfixed. Vacuum loop would be done tomorrow in order to let the XGM work the hole night and part of the morning tomorrow.

Best Regards,

Dear cllougues,

we will run an update of the EPS-loop, in order to have a proper solution for the latest hotfix, as it was announced this morning in the standup meeting.

Cheers,

    Tobias

Dear all,

Right now both XGMs are into the loop and would be running. The loop must run continuously, in case you should do any work, just let me know in advanced.

Thank you,

The karabo services will be down for an upgrade for an hour.

The access will resume at 13:30.

Tunnel Open.

Mirrors:

Status:

• Both mirrors M1 & M2 installed
• Vacuum being closed in M2 today should be ready for ion pumps tomorrow
• Surveying work going on (see email by M. Schlösser below)

Vacuum Loop:

Status:

• Needs reconfig for XGM in XTD9
• Interlock tests on XGM in XTD2 should go on. 
• 2 Turbopumps still have a communication problem (J. Tolkiehn is working on this)
• 6 Ion pumps in XTD9 still have communication problems (list was given by AS to JE)
• Systematic testing according to the list by J. Eidam with V. Bondar starting this afternoon

EPS Loop:

Status:

• One terminal needs to be exchanged for FEL Imager 
• Description of EPS interlock still missing. It is planned to start with just one imager in for first beam commissioning
• One fiber connection from Balcony room to DESY still to be done by DESY. AFter this testing of communication should start

Motion Loop:

Status:

• Quick fix for motors not stopping was deployed on Friday. Now TF is working on a better fix to be deployed this evening

Imagers

Status:

• EPS switch on FEL imager should be checked after exchange of terminal
• Photonics camera driver still not working but not critical for tunnel closure
• Work should now concentrate on SR imager

Karabo:

Status:

• New version with TCP fix needs to be deployed. This should also be done to the local software run by users.

Tasks for today:

Note: Loop reconfiguration and updates of Karabo to be done in the morning. Testing can resume after lunch. Status updates should please be recorded in the log

• Reconfigure vacuum and motion loops (updates for XGM interlock, motors not stopping)
• Replace broken terminal in EPS loop for FEL imager 
• Continue test XGM interlocks (N. Jardon, M. Planas, T. Matsopoulos)
• Go through systematic test of the vacuum components (J. Eidam, V. Bondar)
• Continue tests with PBLM in the tunnels (M. Jidda)
• Test motion system of the imagers in the tunnels (A. Koch and W. Ehsan)
• Monitor stability and responsiveness of GUI Server and Log Servers (A. Silenzi)
• Set up monitoring of temperatures and pressures overnight (A. Silenzi)
• Test communication between XFEL and DESY MPS once fiber connection from Balcony rooms to MPS is available (B. Fernandes)

Tasks for tomorrow:

• Put XGM into the vacuum interlock
• Continues testing of all interlock conditions for the vacuum

Other topics

• Surveying is going on for mirror chambers M1 and M2 in XTD2
• We need a well defined startup configuration of PLC, Karabo, Parameters, List of devices (A. Silenzi)

Email by M. Schlösser re alignment

Hi Tobias, hi Markus, Hi Winni,

Tobias, we discussed briefly the schedule for the T9 and T10 beamlines for the next few days, when we met in the tunnel yesterday.

From what i understand it is impossible to finish T10 until April 11th from the alignment and vacuum side. And probably more important, this also holds true for T9. There is at least one major problem with the alignment of the mirror chambers of T9 in XTD2, which will need some additional days to solve.
From my understanding at least the T9 beamline should be closed and aligned before putting SASE1 in operation. While it will of course be possible to send electrons down to the XSDU2 dump, it will not be possible to send photons to the experimental hall with the current state of the beamline.

Since it is not possible to work in XTD10 while the SASE1 electron beamline is in operation, i would propose to also finish this beamline before SASE1 electron startup. Since there is major work to do in XTD10 to finish the beamline, there is no hope to  do the remaining work during maintenance days. Finishing the beamline would require a major shutdown of the SASE1 branch later.

Since there will be no alternative to send the beam to (e.g. SASE2) for the next year (?), it does not make sense to stop work in XTD10 now, just to continue later then, without any overall benefit for the machine.

Of course i don't have a complete overview of all the machine schedule, but from my point of view it would make more sense to finish work in the northern branch, at least to align all components and to close the vacuum system, even if that means some more weeks before the SASE1 startup.

cu
Markus

Dear all,

The Vacuum loop is running again, now with XGM XTD9 included. We will be testing interlocks in XGM XTD2, so could be needed another upload.

Thank you,

Dear all,

I will update the Vacuum loop in order to add the XGM XTD9 into it. It will be running in few minutes again.

Thank you.

Dear collogues,

all loops are up and running after deploying the hotfix.

Have a nice weekend,

    Tobias

 Confirmed from Karabo side.

Dear collogues,

we have added a hotfix to the framework, to make sure, that no motor can be moved if the feedback signals are missing. This update will be done due to the mentioned issue in the readiness meeting this morning.

We will update the loops again after the weekend, with a proper solution.

The hotfix will send all devices of a loop into error if the feedback of a terminal in the loop is missing.

I will write a new entire in the Logbook, if we are done with the updates.

Cheers,

    Tobias

I have deployed the Karabo master (the HEAD of our development) in the control network for the Vacuum loop device server.

During last weeks Karabo was not able to cope with the data coming from the PLC for this loop (our biggest to date)
and would become unresponsive after 5 to 10 minutes.

The current system is online since 3.5 hours and is still responsive.

Please note:
This is a partial release and the GUI might show unwanted behaviour.
Please leave the vacuum loop untouched during the weekend.

In attachment you can find an example of unwanted behaviour and the DPS gui

Thank you very much and have a nice weekend!

Alessandro

Dear all, EPS loop is again up and running.

Thank you!

Dear all, I will update EPS loop in order to integrate new hardware changes. I will post a new entry when the work is done.

Thank you!

I have made an update for the Motion loop requested to test correctly the Attenuators. Now the loop is running again.

Thank you and sorry for inconvenience.

Has anyone an idea why the motion loop is not working? Thanks Andreas

Hello Andreas,
please use redmine for bug reports. I opened a redmine issue for this:

https://in.xfel.eu/redmine/issues/16265

Please log in and give more details on what you experienced.

In case of emergency contact your main contact person Wajid.

Cheers

Alessandro

 Thanks, Alessandro,

 Tunnel Open.

Mirrors:

Status:

• Vacuum will be closed on M1
• M2 installation tomorrow or latest on Monday

Vacuum Loop:

Status:

• Loop is up
• XGM was integrated but tests needed on the interlocks. Hence valves to DPS now in manual mode (overrides interlock)
• Interface to MPS has been successfully tested
• Need to test fast valve connection to VAC and to MPS (Status re cabling was unclear this morning)
• A few pumps still  have communication problems (to be discussed between AE and CAS)

EPS Loop:

Status:

• AE did most of the missing wiring
• Description of EPS interlock still missing. It is planned to start with just one imager in for first beam commissioning
• One fiber connection from Balcony room to DESY still to be done by DESY

Motion Loop:

Status:

• Problem on ELMO motors with linear drive persists. Needs additional testing

Imagers

Status:

• Both motors working on FEL imager
• Work should now concentrate on SR imager

Karabo:

Status:

• Problem in TCP implementation identified that is suspected to cause the long delays observed e. g. with the imagers. Now needs extensive testing
• Still no data recording achieved
• Stability still needs monitoring

Tasks for today:

• Work on GUI for the vacuum loop (J. Eidam, V. Bondar)
• Test XGM interlocks (N. Jardon, M. Planas, T. Matsopoulos)
• Continue tests with PBLM in the tunnels (M. Jidda)
• Test motion system of the imagers in the tunnels (A. Koch and W. Ehsan)
• Monitor stability and responsiveness of GUI Server and Log Servers (A. Silenzi)
• Set up monitoring of temperatures and pressures overnight (A. Silenzi)
• Push DESY to install fiber connection from Balcony rooms to MPS (P. Gessler)

Tasks for tomorrow:

• Put XGM into the vacuum interlock
• Perform careful testing of all interlock conditions for the vacuum

Other topics

• Regular SASE1 readiness meeting at 09:00 tomorrow in XHQ E1.173
• Need to perform tests with EPS interlock conditions
• Need to test fast valve connection to VAC and to MPS
• Gas system for diagnostics needs to be flushed

-

XTD2, FEL imager with Wajid

Screen, motor, switches - ok, minor braking switch issue.

LED, camera power – ok.

Filter, motor, parameter issue, should be solved now, to be tested again today.

EPS tests and SR imager tests, to be done.

XTD9 cameras, no power, will check today with Bernard.

I expect that some of us may need the weekend as a reserve (e. g. mirror installation). So we should probably say no. Let's discuss more tomorrow at 09:30 

test finshed.

both stages were moved.

voltage value and position read out from encoder opposite in directionality

some strange limitation on the postiion range seen.

both stages are now at around the 0 position with few mm error.

XD to ask alio/nanoomotion on the matter

XD will provide few lines of comment