Access to XTD2, posted by Tobias Haas on 04 Apr 2017, 15:11
|
MPS informed me that they hit some problems and that they still need 30 mins to 1 h until we can go to XTD. |
|
Access XTD2 tomorrow, posted by Tobias Haas on 26 Apr 2017, 17:48
|
I added the requests that I was made aware of to the list of access requests for tomorrow. While the interlock in XTD2 will be broken and hence the tunnel is accessible without special procedures, please note the followoing
- Please make sure your request in in the DESY table of access requests
- You have valid access permissions and two (!) dosimeters, one from XFEL one from DESY
|
|
Acceptance test IMAGERS (FRIDAY 07-04-2017), posted by wajid ehsan on 07 Apr 2017, 19:13
|
SA1_XTD2_IMGPII45:
1) MOTOR/SCREEN(DONE)
2) Check operation of range of movement, defined by end switches (DONE)
3) Check repeatability (DONE)
4) Switch on/off LED (DONE)
5) Switch on/off camera (DONE)
6) Acquire images with a camera (DONE)
7) Hardware Trigger of camera (DONE)
8) EPS switch (DONE)
SA1_XTD2_IMGFEL:
1) Move all motors (DONE)
1.1) MOTOR/SCREEN (DONE)
1.2) MOTOR/FILTER (DONE)
3) Check operation of range of movement, defined by end switches (DONE)
3.1) END_ Switches/SCREEN (DONE)
3.2) END_Switch/FILTER (DONE)
4) Check repeatability (DONE)
5) Switch on/off LED. (DONE)
6) Switch on/off camera. (DONE)
7) Take images with a camera. (DONE)
8) Trigger of camera (DONE)
9) ESP switch (NOT WORKING, hardware issue, to be tested)
10) Braking switch_SCREEN_MOTOR (NOT WORKING, to be tested)
SA1_XTD2_IMGSR:
1) Test motors. (DONE)
1.1) Motor/Screen (DONE)
1.2) Motor/y (DONE)
1.3) Motor/ Focus (DONE)
1.4) Motor / IRIS (DONE)
2) End Switches:
2.1 Motor/Screen (DONE)
2.2 Motor/y (DONE)
3. Check repeatability(DONE)
4. Switch on/off LED (DONE)
5. Switch on/off camera (DONE)
6. Acquire images (NOT DONE, Photonic science camera device is not working but acquired images with eBus(low level driver))
7) EPS (DONE)
8) Braking switch_SCREEN_MOTOR (NOT WORKING)
|
|
Accelerator plans for the next 5 days, posted by Tobias Haas on 27 Apr 2017, 15:28
|
| 27/04 Th A | Beam operation to TLD 10 GeV, 1 bunches, 0.1 nC, 1 Hz; interlock
set XTD2-XTD4 | | 27/04 Th N | Beam operation to TLD 10 GeV, 1 bunches, 0.1 nC, 1 Hz, EOD shift | | 28/04 Fr M | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 28/04 Fr A | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 28/04 Fr N | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 29/04 Sa M | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 29/04 Sa A | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 29/04 Sa N | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 30/04 Su M | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 30/04 Su A | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 30/04 Su N | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 01/05 Mo M | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 01/05 Mo A | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz | | 01/05 Mo N | Beam operation to T4D 10 GeV, 1 bunches, 0.1 nC, 1 Hz |
Access to TLD: |
|
Accelerator Schedule for the next days, posted by Tobias Haas on 03 May 2017, 13:38
|
Author: Decking
Run Coordinators: W. Decking (93430), D. Sanzone
Tunnels XTIN, XTL, XTD2-4, XTD10 closed
Temporary access to XTL,XTD2-4, XTD10 possible on Wed, 4.5.
Next open access XTIN, XTL, XTD2-4, XTD10 on Wed, 10.05. 08-16
|01/05 Mo M | Beam operation to T4D 11 GeV, 1 bunches, 0.5 nC, 1 Hz
|01/05 Mo A | Beam operation to T4D 11 GeV, 1 bunches, 0.5 nC, 1 Hz
|01/05 Mo N | Beam operation to T4D 11 GeV, 1 bunches, 0.5 nC, 1 Hz
|02/05 Tu M | Beam operation to T4D 11 GeV, 1 bunches, 0.5 nC, 1 Hz; establish 6, 8 GeV File
|02/05 Tu A | Beam operation to T4D 6 GeV, 1 bunches, 0.5 nC, 1 Hz
|02/05 Tu N | Beam operation to T4D 6.4 GeV, 1 bunches, 0.5 nC, 1 Hz
|03/05 We M | Beam operation to T4D 6.4 GeV, 1 bunches, 0.5 nC, 1 Hz; study beam optics
|03/05 We A | Beam operation to T4D 6.4 GeV, 1 bunches, 0.5 nC, 1 Hz
|03/05 We N | Beam operation to T4D 6.4 GeV, 1 bunches, 0.5 nC, 1 Hz
|04/05 Th M | Beam operation to T4D 6.4 GeV, 1 bunches, 0.5 nC, 1 Hz
|04/05 Th A | No beam operation, tunnels closed
|04/05 Th N | No beam operation, tunnels closed
|05/05 Fr M | No beam operation, Acces to TLD for leak search, Temporary access to T2-T4 possible
|05/05 Fr A | No beam operation, Acces to TLD for leak search, Temporary access to T2-T4 possible
|05/05 Fr N | No beam operation, tunnels closed
|06/05 Sa M | No beam operation, tunnels closed
|06/05 Sa A | No beam operation, tunnels closed
|06/05 Sa N | No beam operation, tunnels closed
|07/05 Su M | No beam operation, tunnels closed
|07/05 Su A | No beam operation, tunnels closed
|07/05 Su N | No beam operation, tunnels closed
|08/05 Mo M | Beam operation to T4D 11 GeV, 1 bunches, 0.5 nC, 10 Hz
|08/05 Mo A | Beam operation to T4D 11 GeV, 1 bunches, 0.5 nC, 10 Hz
|08/05 Mo N | Beam operation to T4D 11 GeV, 1 bunches, 0.5 nC, 10 Hz |
|
AE PLC OCD, posted by Tobias Freyermuth on 22 May 2017, 11:06
|
From now on the PLC OCD contact person will have always the phone number:
9 8040 |
|
AE OCD Mai 5 -- Mai 8, posted by Nicola Coppola on 05 May 2017, 14:35
|
AE on call service:
Contact person:
Nicola Coppola
Phone:
9 - 5627
|
|
AE OCD Mai 19 -- Mai 22, posted by Nicola Coppola on 19 May 2017, 15:42
|
AE on call service:
Contact person:
Nicola Coppola
Phone:
9 - 5627 |
|
AE OCD April 29 - Mai 1, posted by Tobias Freyermuth on 28 Apr 2017, 14:31
|
AE on call service:
Contact person:
Tobias Freyermuth
Phone:
9 - 6822
|
|
1Hz Triggers , posted by Bruno Fernandes on 10 Jan 2018, 17:20
|
Hello everyone,
The main Timing System at DESY, which distributes all timing information to our systems, is right now configured to generate 1Hz trigger signals on Event #16. This is the trigger that is deliver to most detectors/cameras on our site.
DESY is testing a new Gun and wanted to use a slower trigger frequency during this evaluation.
We were not inform in advance about this reconfiguration. After a few colleagues from SPB approach us reporting this problem, we contacted DESY and got the update. We will take steps to make sure that future Timing changes done by DESY are communicated to XFEL ahead of time. |
|
*IMPORTANT* Change of plans re Access tomorrow, posted by Tobias Haas on 03 May 2017, 13:29
|
Due the recent results from XFEL, the urgent maintenance is shiftet from Thursday 4th to Friday
5th. On Thursday, there will be operation till 14:00, after 14:00 the machine will be
switched to standby. All the work planned will shift accordingly by one day. No ZZ before
Thursday 14:00.
The machine will be shut down Friday moring 7:00.
Interlock situation: The machine will stay in interlock, only the access to XTL from OSDORF will
be brocken.
XTL: Access from Osdorf
- activation measurement XS1 XTL/rear part by D3
- Leak search and repair in the TLD beamline by MVS
- A20 work by MHF-p (Exchange of filament heating, work on phase shifter)
- CS8 RF measurement on load (MHF-p)
- Repair of wire scanner relais
XTL: Access from Bahrenfeld
- Exchange of filter in the BCM monitors by MKS
- Repair of DCCT of a B2D quad
- Change of AMC board in A8 by MSK
XTD2:
- ZZ for repair of a BPM system
XTD10:
ZZ for Photon Beamline Work
All further work has to be agreed by the run or machine coordination.
|
|
switch software update - ITDM request, posted by Adriano Violante on 10 Sep 2018, 09:12
|
The office switched reported below have to be upgraded. Some of them belong to accelerator and some to us. Below you find the detailed list of the switches and the time schedule (assuming everything runs fine) for the update. ITDM needs feedback the latest today evening.
if you see problems with the upgrade, please reply to this e-mail. If we do not receive complaints until this evening, we assume that everything is fine.
Monday, 24.09.2018, 06:00 - 08:00 am:
sw-hh-al-324.desy.de XFEL_XHEXP1_SASE2_A21.UH3.03
sw-hh-al-325.desy.de XFEL_XHEXP1_SASE2_A22.UH7.02
sw-hh-al-323.desy.de XFEL_XHEXP1_SASE3_E21.UH2.03
sw-hh-al-322.desy.de XFEL_XHEXP1_SASE3_E22.UH3.01
sw-hh-al-274.desy.de XFEL_XHQ.1.174
sw-hh-al-298.desy.de XFEL_XSDU1_UG01.001_R01_3175m
sw-hh-al-295.desy.de XFEL_XTD1_SA2.R002_R26_2238m
sw-hh-al-296.desy.de XFEL_XTD1_SA2.R005_R16_2384m
sw-hh-al-297.desy.de XFEL_XTD1_T3.R007_R33_2500m
sw-hh-al-299.desy.de XFEL_XTD1_T3.R010_2.1_2581m
Tuesday, 25.09.2018, 06:00 - 08:00 am:
sw-hh-al-287.desy.de XFEL_XTD10_3.13_3297m
sw-hh-al-285.desy.de XFEL_XTD10_3.4_3141m
sw-hh-al-286.desy.de XFEL_XTD10_3.7_3209m
sw-hh-al-290.desy.de XFEL_XTD2_T4.R009_R14_2590m
sw-hh-al-293.desy.de XFEL_XTD3_T5.R005_R01_2846m
sw-hh-al-292.desy.de XFEL_XTD3_UN1.R002_R16_2740m
sw-hh-al-288.desy.de XFEL_XTD4_SA3.R001_R27_2838m
sw-hh-al-289.desy.de XFEL_XTD4_SA3.R002_R48_2888m
sw-hh-al-291.desy.de XFEL_XTD4_T4D.R006_R19_3057m
sw-hh-al-294.desy.de XFEL_XTD5_UN2.R001_R04_2972m |
|
motion loop not working !?, posted by Andreas Koch on 06 Apr 2017, 13:36
|
Has anyone an idea why the motion loop is not working? Thanks Andreas |
motion loop not working !?, posted by Andreas Koch on 06 Apr 2017, 14:32
|
| Andreas Koch wrote: |
|
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 |
|
motion loop not working !?, posted by Andreas Koch on 06 Apr 2017, 14:45
|
| Andreas Koch wrote: |
|
| Andreas Koch wrote: |
|
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,
It's working again.
It was the Wifi that slowed down.
Andreas
|
|
Karabo Names in Vacuum component list, posted by Tobias Haas on 24 Jan 2017, 08:23
|
Post on behalf of Alessandro Silenzi:
please find below the link to the first version of the master component list and the link to the direct download:
Please give your comments directly to me to avoid confusion.
The next steps after collecting your input, will be to implement a test in the Firmware project generation that will test the deviceIds against this list.
Best regards
Alessandro Silenzi
|
|
, posted by Adriano Violante on 14 Sep 2018, 13:38
|
| |
|