Dear all,

The OCD AE numbers for the following days will be:

PLC support: 9-8040 / 0151-68822383

DAQ Electronics (incl. timing, MicroTCA) Support:  9-6941

If there are any change in the numbers, we will let you know.

Thank you.

 Issues observed by PCT over the weekend (from H. Sinn entry in the PCT log)

- The interlock of the vacuum valves worked as expected. However, we had two times the gas section around the XGM tripping the beam, because the gate valves around the XGM were closing. The reason for these trips will be investigated (probably noise on one of the involved pressure gauges). In the future it would be good to change the Vacuum-to-MPS interlock such that V0 always closes, if any of the other gate vales closes. Then the accelerator permission would come automatically come back after the trip. However re-booting of the vacuum loop needs to be planned (trips the DESY beam permission and potentially shuts down the turbo pumps). 

- The SR Imager may loose steps when moving larger distances (speed too high?)

- Several general problems of Karabo were observed, which make live difficult: For example, the 'V0 closed' and 'B4C in' indication on our main screen may just lock, even when the state of the device is changing (was observed mostly on GUI server1). It means that the status displayed on a scene can be in general not be trusted. In many cases we observed that connecting freshly opened scenes to devices take unacceptably long times (many minutes or never).  The policy of saving projects and sub-projects leads to overwriting changes, if more people work on projects and projects stay open for longer time.  

- The fact that the PLC does actually not store values through a reboot causes many problems. It basically means that motor positions are lost (set to zero) at every reboot and can be only recovered, if homing or absolute encoders exist. Also that positions of motors cannot be reset to their theoretical values means that in practice the state before the PLC reboot cannot be recovered by resetting the values.

- The imagers, in particular the SR-imager, caused a lot of problems because they were often crashing and require advanced and complicated procedures to make them run again (e.g. setting after re-instantiating the imagers are lost and come up with wrong pre-sets). The SR-imager does auto-scaling on the intensity, also when this is disabled in the software. This make the imager only useful for qualitative studies (e.g. not for gain curve or flux measurements).

General

• Parameters of motors get lost after reboot of the PLC
• Setting trigger delays can currently only be done with special authorisation from DOOCS. 
• Suggested solution from AE: Hardwire the correct defaults in the firmware
• A better procedure is needed to communicate the parameters between hardware experts and AE
• L. Samoylova suggests that CAS person on call contacts BKR once per day to establish contact and get an overall impression
• The support of CAS during the weekend was greatly appreciated

Vacuum

• No calls to experts over the weekend
• Issue with the XGM vacuum (spurious triggers of the interlock) needs to be fixed 
• Interlock logic should be changed so that V0 always closes if one of the gate valves closes

Imagers

• SR Imager crashed frequently and was hard to bring back
• Auto-scaling of SR-imager cannot be switched off. This needs fixing with high priority

XGM

• Commissioning starts today
• See above about vacuum issues

PLC

• No calls over the weekend to the experts
• Firmware for MC2 lib (TECHNOSOFT motors) is prepared and waiting for tests

Karabo

• CAS was called a few times on the weekend
• Running more than one camera at the same time appears  to cause crashes. Possibly network bandwidth is insufficient
• A procedure can be set up to read out the motor parameters at a well defined point in time for storing them in the firmware 
• Setting trigger delays should be made to work from Karabo

Work for next days

• Karabo test with MC2 Lib in the lab. As soon as this is successful it will continue in XTD9. Will be done on the SPB attenuator as N. Gerassimova is not available for PBLM tests due to a beam time
• Fix the Photonics camera driver so that auto-scaling can be turned off

Dear all,

CAS phone numbers for OCD:

Friday: Alessandro (98054),

Saturday: Valerii (98053),

Sunday: Gabriele (98060),

thank you.

Dear all,

The OCD numbers for this weekend and today will be:

PLC Support: 9-8040 / 0151-68822383

DAQ Electronics (incl. timing, MicroTCA) Support: 9-8041 / 0151-68822386

Thank you.

V0 is open now!

Janni opened this morning at 11:00 the V0 valve towards the accelerator vacuum.

We removed the B4C absorber in front of the valve and now the spontaneous radiation can enter the Schenefeld vacuum. 

The interlock conditions for Vacuum loop and EPS loops towards the DESY MPS were tested and they are now enabled. 

This means that rebooting SA1 VACUUM  or EPS loop will stop the beam during the reboot (therefore call 4500 before you do it).

Focus of meeting is on SASE1 Instruments, Laser and Detectors

SPB (B. Weinhausen)

• All motors in the SPB tunnel loop have been commissioned except for one TECHNOSOFT motor where the updated driver was not yet available
• Comment by P. Gessler:
  • The updated MC2 lib was deployed yesterday evening. Testing should be possible now
• The second camera of the screen broke. Concern exists over possible overvoltage in the power that comes directly from the PLC
• All encoders are working
• The vacuum in the Optics hutch is closed
• Info by A. Violante:
  • All cabling in D02/D03 is done
  • There are a few damaged connectors that prevent pushing in the modules. This should be fixed on Monday
  • Pins are swapped in one connector. Will be fixed locally
• Comment by P. Gessler:
  • This week AE was busy with AGIPD and tunnels
  • Next week resources should be available to support start of commissioning loop 1 

FXE (A. Galler)

• E2E tests are progressing 
• A recent update of the Beckhoff firmware generated new problems with encoders
• Info from T. Korsch:
  • The vacuum in the hutch is closed and has reached 5e-7 mb
  • There is a minor leak in one of the bellows
  • Compressed air is working to operate the gate valves
  • Vacuum gauges can be read out remotely
• Attention should be paid to being able to read out detectors, e. g. diodes

Laser (D. Kane/M. Lederer)

• Slides were provided in INDICO with a detailed account of the status. Only Key points are summarised here:
  
  • Hutch infrastructure is working in general and temperature stability is ok but laser group is lacking access to controlling the parameters, humidity is oscillating and smoke detectors are not connected
  • Pre-assembly of PP laser is 75% done
  • Beam delivery to instruments is on the list now
  • Synchronisation with optical system might not be available before October
  • Control are generally working and software has improved a lot but some stages cannot be controlled and Karabo appears still to have some resource leaks

Detectors (M. Kuster)

• LPD is in E2E tests and AGIPD is still being integrated into the XFEL environment
• This week it was possible to run the DAQ chain on LPD for the first time
• All tests on LPD including data taking in the X-Ray chamber in HERA-S should be done by end June
• Situation with AGIPD is more difficult as basic integration is still not complete

Discussion

• Follow up on progress with instruments, laser and detectors will continue in S1R meeting from now on
• The S1R dispatch meeting takes place on Mondays 09:00 in BKR and on Wednesday 09:30 in XHQ 
• Groups that require help from AE and CAS and that need to coordinate with other activities should attend

I will ramp down the system and bring it back up during the lunch break after installing the
tag 2.1.10.

To install a new version of Karabo use the script attached on your terminal

move your the karabo directory to a backup or remove it.

to backup:
$ mv ~/karabo ~/karabo.bkp
 

to remove:
$ rm -fr ~/karabo

then execute:
$ bash PATHTO/download.sh

 The system is up.

The users using virtual machines will encounter problems installing karabo 2.1.10 in the way that was described.
Further instructions will come later in the day

 for Users with a VM:
- use the download script
- Remove the karabo directory:
   $ rm -fr ~/karabo 
- then execute:
   $ bash PATHTO/download.sh

Sorry for the delayed instructions

Find attached the Instrument Component priority list discussed this morning.

Regards,

Monica

Dear all,

Due to local test needed in Rack 1.18 for the Motion loop, the loop will be interrupted only in Rack 1.18 XTD9 from now till the people in the Tunnel finish the tests. It will not affect any other part of the Motion loop.

Thank you.

 We are in the BRK and corrected the vacuum interlock condition.

We will restart the SA1 vacuum loop in a few minutes

Plan of WP74 OCD contacts for May.
Assignments are subject to change.

Initially availability is 10h-18h on the given days.
This might be adapted as well for later weeks.

 Dear all, 

contrary to the rumor that I spread last Tuesday in the PBS meeting, the magnet tests in XTD2/4 will be NOT done coming Monday and therefore the XTD10 will be be NOT open. It is still the plan to have one access day in XTD10 per week in the future (Monday or Wednesday to be clarified with the magnet group), but this will start only later this month.

Best regards

Harald 

Dear all,

I will update the Motion loop to include the mc2 motors, it will be running again in few minutes.

Thank you!

CAS on call service for the night:

Gero Flucke: 9-8053

Could somebody please re-establish the karabo controls of the SASE1 tunnel VAC loop (connection with Beckhoff server) ?

The karabo devices for XGM vacuum XTD2 and XTD9 are still all in UNKNOWN STATE.

We urgently would like to check the XGM vacuum status and restart the pumps before they are vented.

Thanks,

Jan

 Jan,

We are working on it. 

Vacuum is up and running again.

Thank you

Sorry for disturbing you, but I will have to wait till WP74 group finish a training in order to be able to put the XGM up again .

Dear all,

The update of the Vacuum loop will take place in the next few minutes, later on, you would have access again to it.

Thank you.

EPS loop in SASE1 is running again

Dear all,

I will make an update on the EPS loop, it will take only a moment.

Thank you