INFO

As reported by the PRC (J. Gruenert) during the operation meeting this morning, due to the first lasing attempt in SASE2 no lasing of SASE3 is to be expected until the middle of next week.

As discussed with Wajid, I am availalbe tomorrow Wednesday the whole day to continue testing Karabo, motion loop. Wajid checked with Narea. I understand that there may be interruptions and that I have not first priority. Thanks, Andreas

End switch testing: the in-position end switch stopped devices working, also stopped gateway connection. Stroke of motor is not correct, parameter list to be checked. More details in "Improvements / bug list".

Here the link to the detailed list of issues: https://docs.xfel.eu/share/page/site/xfelwp74/document-details?nodeRef=workspace://SpacesStore/1733b825-e62e-47af-abba-fdef1ff9485d

Here attached the main SASE1 panel

Dear All,

We have a issue on the control servers and we are already working on it...

Best,

Hugo

Dear All,

We solved the incident and the services are running normally. We are still try to investigate, as far as we know we have some "zumbies" process running in the GUI servers and it was not consuming the HEATBEATs.

FYI

Below the E-Mail from Hugo Santos with the Karabo deployment dates.

Dear All,

I would like to call your attention to the fact that we made Karabo 2.2.3 available last Monday (04/04, and the changelog 06/04). From the last Readiness Meeting, I got informed that we agreed and are allowed to proceed with the Karabo rollout planning on SASE3 and SASE2. (SASE1 still needs agreement):

1. SASE3
   1. PRE-CONDITION: (AE) PLC version and (ITDM) DAQ should be interface-compatible, otherwise, the deployment will not be able to be performed. (No Karabo-DAQ and Karabo-PLC interface issues)
   2. Date: 13/04/2018 (Friday)
   3. Should be the first one because of the completeness of this system: VAC, PES, XGM and GAT loops, for instance, that have to be checked and run properly afterward.
   4. Downtime expected: 9:00 to 14:00. 
   5. (AE) PLCs version and (ITDM) DAQ should be interface-compatible, otherwise, the deployment will not be able to be performed.
   6. No major change regarding DET systems
   7. CAS Members for this specific task: Chris and Wajid.
2. SASE2
   1. PRE-CONDITION: SASE3 Deployment task must be done and Karabo 2.2.3 running with PLC and DAQ (No Karabo-DAQ and Karabo-PLC interface issues)
   2. Date: 16/04/2018 (Monday)
   3. Downtime expected: 11:00 to 13:00.
   4. (AE) PLCs version and (ITDM) DAQ should be compatible, otherwise, the deployment will not be able to be performed.
   5. No major change regarding DET system.
   6. CAS Members for this specific task: Chris and Wajid.
3. SASE1
   1. PRE-CONDITION: SASE2 and SASE3 Deployment tasks must be done and Karabo 2.2.3 running with PLC and DAQ (No Karabo-DAQ and Karabo-PLC interface issues).
   2. Date: (17/04/2018 - Tuesday - to be agreed)
   3. Downtime expected: to be defined. 
   4. (AE) PLCs version and (ITDM) DAQ should be compatible, otherwise, the deployment will not be able to be performed.
   5. No major change regarding DET systems.
   6. CAS Members for this specific task: Alessandro and Wajid

Finally, please, also see that as soon as we have the Karabo 2.2.3 running during the shutdown, we will have the most comfortable time to perform the setup, configurations and stabilize it, still, during the shutdown. This way we can handover the control system properly to the operators.

Please, if you do not agree or are not comfortable with something in this message, let me know as soon as possible. Otherwise, I will assume that it does not contain any showstopper and we (CAS) can proceed.

H.S.

Post on behalf of Harald Sinn:

 for the non-vacuum part of WP73 we have the following situation: 

I am working this morning on following projects:

SA1_KMONO_SYSTEM
SA1_XTD2_KMONO
SA1_XTD2_IMGSR
SA1_XTD2_FLT

Please don't save these projects !

 Karabo to PLC communication has been tested successfully in the SA1 Vacuum installation.

in attachment:

OK.png -> Initial Status, all OK

Url to the readthedocs documentation:

https://goo.gl/vsz9hu

Dear All,

I would like to inform that we released last Friday (22.06) the Karabo 2.2.4 version. We got around five days delayed to prioritize issues regarding Karabo-DAQ integration and MDL devices that were found in the last steps of the test cycle. However, fortunately, those issues are solved. 

Based on this run, the new dates that we (CAS) are proposing to start the deployment in operation will be:

• SA3: 28.06, Thursday (CAS references: Chris, Wajid, and Valerii)
• SA2: 02.07, Monday (CAS references: Chris, Wajid, and Valerii)
• SA1 + SPB + FXE: 03.07, Tuesday (CAS references: Alessandro, Dennis, Gabriele, Wajid)
  • SPB deployment should not impact AGIPD firmware test week, as agreed before.
• BKR: 28.06? (Wajid and Jan, could you please agree offline?)
• LAS, SQS and SCS dates have to be agreed with the respective contact persons.

-
Hugo

Hi all, for your information below a message from Chris Youngman concerning Karabo 2.2.3 installations in SASE3.

"preparation work has concluded and we will definitely try to deploy Karabo 2.2.3 on SA3 machines TODAY 13.04.. SA3 s/w will not work from 8:00 on. Hopefully we will finish during the morning.

SA1 and SA2 installations should continue as normal."

Dear All,

I would like to report that we started today to test (internally in CAS) the Karabo 2.1.15 version.

We got delayed to prioritise and solve a showstopper issue related to GUI Client. If our tests succeed, we are foreseeing to finish the tests and release tomorrow.

Best,

Hugo

 Author: Decking

Goals:
- Operation with 10 GeV, 500 pC, 5 kA, 30 bunch
- Increase gradient limits in RF stations
- Technical comissioning of north branch 

XTIN closed all week
XTL open till Tue, 11:00
XTD2 open till Tue, 15:00
XTD4 open till Tue, 15:00
XTD9&XTD10 open all week


|17/04 Mo M |  Easter shutdown
|17/04 Mo A |  Easter shutdown
|17/04 Mo N |  Easter shutdown
|18/04 Tu M |  Interlock pre-test CS8, set XTL interlock at 11:00, Injector beam operation
|18/04 Tu A |  A2 calibration after phase shifter change, Beam operation  to TLD 10 GeV, set interlock XTD2-XTD4
|18/04 Tu N |  Beam operation  to TLD 10 GeV, 30 bunches, 0.5 nC
|19/04 We M |  Slice emittance in BC2; Magnet PS test XTD2-XTD4 
|19/04 We A |  BCM, BAM EO, commissioning; Magnet PS test XTD2-XTD4 
|19/04 We N |  BCM, BAM EO, commissioning; Magnet PS test XTD2-XTD4 
|20/04 Th M |  Collimation set-up; Magnet PS test XTD2-XTD4 
|20/04 Th A |  BCM, BAM EO, commissioning; Magnet PS test XTD2-XTD4 
|20/04 Th N |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC; Magnet PS test XTD2-XTD4 
|21/04 Fr M |  Collimation set-up with 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|21/04 Fr A |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|21/04 Fr N |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|22/04 Sa M |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|22/04 Sa A |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|22/04 Sa N |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|23/04 Su M |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|23/04 Su A |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|23/04 Su N |  Beam operation  to TLD 12 GeV, 30 bunches, 0.5 nC, 5 kA; Magnet PS test XTD2-XTD4 
|24/04 Mo M |  Beam set-up 12 GeV, 1 bunches, 0.1 nC, 1 Hz
|24/04 Mo A |  Beam operation  to TLD 12 GeV, 1 bunches, 0.1 nC, 1 Hz
|24/04 Mo N |  Beam operation  to TLD 12 GeV, 1 bunches, 0.1 nC, 1 Hz

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

The access will resume at 13:30.

As previously announced we will deploy KARABO 2.1.13 in tunnel under topic SA1. The system will go down in 10 mins. I will announce it again as soon the system is up again.

Regards,

Wajid Ehsan

The system is up and running.

Regards,

Wajid 

During the first K-Mono test with Karabo on Friday the first goniometer THETA1 (Elmo controller) moved beyond the CW limit switch and stopped  at the CCW switch. So the goniometer was trapped between both switches with a movement range of a few degrees. Movement of encoder and motor were opposite. This behaviour is not understood and under investigation.

Now the goniometer is back within the nominal range and movement of motor and encoder reading is consistent. CCW limit switch at 117.5° / CW limit switch at ~182°.