ID |
Date |
Author |
Location |
Severity |
Subject |
248
|
18 May 2017, 15:30 |
NEREA JARDON | General | Information | OCD AE Group | Dear all,
The OCD AE numbers for the following days will be:
PLC support: 9-8040
DAQ Electronics (incl. timing, MicroTCA) Support: 9-8041
If there are any change in the numbers, we will let you know.
Thank you.
|
250
|
18 May 2017, 16:36 |
NEREA JARDON | General | Information | Motion loop | Dear all,
I have already contacted Andreas Koch, and Alessandro has contacted the BKR in order to do a new update of the motion loop because of one small bug detected.
I will do the update in the next few minutes.
Thank you, |
251
|
19 May 2017, 11:30 |
Tobias Haas | General | Information | Status and plans after SASE1 Readiness Meeting | General (T. Haas)
- Due to problems with interlock cabling the approval date with the TÜV on 1 June has been cancelled
- The MB, SASE1 Instruments, AE, CAS and PSPO met yesterday and agreed that in view of the schedule risks with technical commissioning the focus of the next weeks should be enabling both FXE and SPB/SFX to accept beam for doing radiation safety measurements no later then end of June.
- SPB/SFX were asked to identify the minimum functionality for this goal. The respective components will be marked in the component priority list
FXE (A. Galler)
- So far work has concentrated on motors
- This week PSLITs and BIU2 successfully underwent E2E tests
- JJ was back this week to fix some problems on patch panels
- Johan spectrometer is back in the hutch
SPB (B. Weinhausen)
- Work continued on the tunnel loops.
- The power supply problem with photonics cameras has been solved by AE (Additional 12V terminals installed)
- Triggers for the cameras are working
- Valve between optics hutch and tunnel vacuum was opened for the first time
- There is still the unsolved problem with the TECHNOSOFT motor.
- Work will now move to the optics hutch.
Laser (T. Jezynski)
- Alarm systems are (smoke, gas etc) are now connected
- Big problems with AC systems. The effort with FM to stabilise the humidity now results in temperature swings of up to 2 degrees. The same problem also appears in the instrument laser hutches
- AC problems lead to large instabilities of the laser
- Alignment beam is now delivered to both instrument laser hutches
- No new information was received on the topic of optical synchronisation
Detector (M. Kuster)
- Management decided that LPD will be moved to FXE in June, in weeks 23/24 to allow further testing of AGIPD in HERA-S
- Interlock test on AGIPD continue
- CAS is working on integrating the DAQ of AGIPD. When this is done an update of Karabo is needed. This will not happen this week and hence not before S. Hauf is on holidays
Electronics (P. Gessler)
- There is still some work for the tunnels:
- For integration of MCP tests were done in the lab yesterday. One of the two axes is working, the other one not yet
- Tests for PBLMs could not be done as there was no common window between on N. Gerassimova and M. Umar. Tests could be done by M. Umar if N. Gerassimova agrees. She is on holidays for two days next week
- The interface of the vacuum loop and the EPS loop to the DESY MPS requires additional work for XTD9 in the next days
- Work also continues on AGIPD for one more day
- There are some absences due to sickness and holidays that also slow down the work
Karabo (A. Silenzi/B. Brockhauser)
- There will be a swap of the GUI server today to allow debugging the issue that the device states are sometimes not properly shown. People will need to re-connect
- Tests of TECHNOSOFT motor were successful. (Does not include encoder needed for SPB motor)
- There is a fundamental problem with the Photonics camera used in the SR imager. It has a rolling shutter that does not allow to get well-timed, triggered images. The same issue might be persent for the HIREX camera
- The KARABO/DOOCS driver has been re-established. This should allow to set time delays directly from Karabo again
Discussion/Next Steps
- SPB should start with technical commissioning of OPTICS hutch
- Instruments identify components needed for beam in the hutch for radiation safety measurements
- AE finishes pending tunnel work and then focus on SPB/SFX and FXE
- Displatch meetings on Monday and Wednesday at 09:30 in XHQ/MCR (*not at DESY*)
|
252
|
19 May 2017, 12:46 |
Monica Aresté | General | Information | Update of Instrument component priority list |
Find attached the Instrument Component priority list discussed this morning.
Regards,
Monica
|
Attachment 1: 170519_Instrument_Components-Priority-list.xlsx
|
253
|
19 May 2017, 15:42 |
Nicola Coppola | General | Information | AE OCD Mai 19 -- Mai 22 | AE on call service:
Contact person:
Nicola Coppola
Phone:
9 - 5627 |
254
|
21 May 2017, 15:02 |
David Hickin | XTD2 | Information | CAS OCD: Support requested starting SA1_XTD2_MCP/ADC/MCP3 | Contacted at home 21:30 19.05. Request for support starting SA1_XTD2_MCP/CDC/MCP3 on cppServer/sa1_utca_17.
Located project and device server. Attempted to start SA1_XTD2_MCP/CDC/MCP3. Issue was missing fastAdc plugin. Found info on sa1_utca_17 in commissioning guidelines: say server is exflutc106.
Tried to ssh in to exflutc106 unsuccessfully. Phoned back 23:49 to give status. Informed that accelerator not running due to lightning. Suggested that if I couldn't fix issue soon they should contact next OCD person from 8:00.
Tried further to fix problem. Found section in commissioning guidelines: tried ssh -Y -l xctrl.Still couldn't access exflutc106. Wrote up notes. Sent to next contact. Stopped work 1:45. |
255
|
21 May 2017, 16:28 |
David Hickin | XTD2 | Information | CAS OCD: Support requested starting SA1_XTD2_MCP/ADC/MCP3 |
David Hickin wrote: |
Contacted at home 21:30 19.05. Request for support starting SA1_XTD2_MCP/CDC/MCP3 on cppServer/sa1_utca_17.
Located project and device server. Attempted to start SA1_XTD2_MCP/CDC/MCP3. Issue was missing fastAdc plugin. Found info on sa1_utca_17 in commissioning guidelines: say server is exflutc106.
Tried to ssh in to exflutc106 unsuccessfully. Phoned back 23:49 to give status. Informed that accelerator not running due to lightning. Suggested that if I couldn't fix issue soon they should contact next OCD person from 8:00.
Tried further to fix problem. Found section in commissioning guidelines: tried ssh -Y -l xctrl.Still couldn't access exflutc106. Wrote up notes. Sent to next contact. Stopped work 1:45.
|
* Apparently the device installation failed with ansible on utca_17. Even worse, the requested utca_18 is not even know, cannot be pinged and nothing is documented.
** Global problem: Karabo develop, checkout and install both return zero exit status from git.
** Device problem: The dependency was declared wrong in the fastAdc
FastAdc installed by hand, dependency built by hand.
Devices can now be instantiated. For the record, with the following problem
INFO SA1_XTD2_MCP/ADC/MCP2 : Reset simply calls initialize() method now.
INFO SA1_XTD2_MCP/ADC/MCP2 : Connecting to hardware driver, setting up the device's namespace...
ERROR SA1_XTD2_MCP/ADC/MCP2 : Cannot create IibusMap object for /dev/pciedevs6 and maps in /home/utcaadm/maps since:
1. Exception =====> {
Exception Type....: IO Exception
Message...........: Open '/dev/pciedevs6' : No such file or directory
File..............: /[...]/src/IibusMapImpl.cc
Function..........: utca::IibusMapImpl::IibusMapImpl(const string&, const string&, bool)
Line Number.......: 32
Timestamp.........: 2017-May-21 14:59:57.856975
}
INFO SA1_XTD2_MCP/ADC/MCP2 : Reset simply calls initialize() method now.
INFO SA1_XTD2_MCP/ADC/MCP2 : Connecting to hardware driver, setting up the device's namespace...
ERROR SA1_XTD2_MCP/ADC/MCP2 : Cannot create IibusMap object for /dev/pciedevs6 and maps in /home/utcaadm/maps since:
1. Exception =====> {
Exception Type....: IO Exception
Message...........: Open '/dev/pciedevs6' : No such file or directory
File..............: /[...]/src/IibusMapImpl.cc
Function..........: utca::IibusMapImpl::IibusMapImpl(const string&, const string&, bool)
Line Number.......: 32
Timestamp.........: 2017-May-21 15:56:50.638370
}
|
256
|
21 May 2017, 16:29 |
David Hickin | XTD2 | Information | CAS OCD: Support requested starting SA1_XTD2_MCP/ADC/MCP3 |
David Hickin wrote: |
David Hickin wrote: |
Contacted at home 21:30 19.05. Request for support starting SA1_XTD2_MCP/CDC/MCP3 on cppServer/sa1_utca_17.
Located project and device server. Attempted to start SA1_XTD2_MCP/CDC/MCP3. Issue was missing fastAdc plugin. Found info on sa1_utca_17 in commissioning guidelines: say server is exflutc106.
Tried to ssh in to exflutc106 unsuccessfully. Phoned back 23:49 to give status. Informed that accelerator not running due to lightning. Suggested that if I couldn't fix issue soon they should contact next OCD person from 8:00.
Tried further to fix problem. Found section in commissioning guidelines: tried ssh -Y -l xctrl.Still couldn't access exflutc106. Wrote up notes. Sent to next contact. Stopped work 1:45.
|
* Apparently the device installation failed with ansible on utca_17. Even worse, the requested utca_18 is not even know, cannot be pinged and nothing is documented.
** Global problem: Karabo develop, checkout and install both return zero exit status from git.
** Device problem: The dependency was declared wrong in the fastAdc
FastAdc installed by hand, dependency built by hand.
Devices can now be instantiated. For the record, with the following problem
INFO SA1_XTD2_MCP/ADC/MCP2 : Reset simply calls initialize() method now.
INFO SA1_XTD2_MCP/ADC/MCP2 : Connecting to hardware driver, setting up the device's namespace...
ERROR SA1_XTD2_MCP/ADC/MCP2 : Cannot create IibusMap object for /dev/pciedevs6 and maps in /home/utcaadm/maps since:
1. Exception =====> {
Exception Type....: IO Exception
Message...........: Open '/dev/pciedevs6' : No such file or directory
File..............: /[...]/src/IibusMapImpl.cc
Function..........: utca::IibusMapImpl::IibusMapImpl(const string&, const string&, bool)
Line Number.......: 32
Timestamp.........: 2017-May-21 14:59:57.856975
}
INFO SA1_XTD2_MCP/ADC/MCP2 : Reset simply calls initialize() method now.
INFO SA1_XTD2_MCP/ADC/MCP2 : Connecting to hardware driver, setting up the device's namespace...
ERROR SA1_XTD2_MCP/ADC/MCP2 : Cannot create IibusMap object for /dev/pciedevs6 and maps in /home/utcaadm/maps since:
1. Exception =====> {
Exception Type....: IO Exception
Message...........: Open '/dev/pciedevs6' : No such file or directory
File..............: /[...]/src/IibusMapImpl.cc
Function..........: utca::IibusMapImpl::IibusMapImpl(const string&, const string&, bool)
Line Number.......: 32
Timestamp.........: 2017-May-21 15:56:50.638370
}
|
For record, the last message was me (DG) |
257
|
21 May 2017, 16:50 |
David Hickin | XTD2 | Information | CAS OCD: Support requested starting SA1_XTD2_MCP/ADC/MCP3 |
David Hickin wrote: |
David Hickin wrote: |
David Hickin wrote: |
Contacted at home 21:30 19.05. Request for support starting SA1_XTD2_MCP/CDC/MCP3 on cppServer/sa1_utca_17.
Located project and device server. Attempted to start SA1_XTD2_MCP/CDC/MCP3. Issue was missing fastAdc plugin. Found info on sa1_utca_17 in commissioning guidelines: say server is exflutc106.
Tried to ssh in to exflutc106 unsuccessfully. Phoned back 23:49 to give status. Informed that accelerator not running due to lightning. Suggested that if I couldn't fix issue soon they should contact next OCD person from 8:00.
Tried further to fix problem. Found section in commissioning guidelines: tried ssh -Y -l xctrl.Still couldn't access exflutc106. Wrote up notes. Sent to next contact. Stopped work 1:45.
|
* Apparently the device installation failed with ansible on utca_17. Even worse, the requested utca_18 is not even know, cannot be pinged and nothing is documented.
** Global problem: Karabo develop, checkout and install both return zero exit status from git.
** Device problem: The dependency was declared wrong in the fastAdc
FastAdc installed by hand, dependency built by hand.
Devices can now be instantiated. For the record, with the following problem
INFO SA1_XTD2_MCP/ADC/MCP2 : Reset simply calls initialize() method now.
INFO SA1_XTD2_MCP/ADC/MCP2 : Connecting to hardware driver, setting up the device's namespace...
ERROR SA1_XTD2_MCP/ADC/MCP2 : Cannot create IibusMap object for /dev/pciedevs6 and maps in /home/utcaadm/maps since:
1. Exception =====> {
Exception Type....: IO Exception
Message...........: Open '/dev/pciedevs6' : No such file or directory
File..............: /[...]/src/IibusMapImpl.cc
Function..........: utca::IibusMapImpl::IibusMapImpl(const string&, const string&, bool)
Line Number.......: 32
Timestamp.........: 2017-May-21 14:59:57.856975
}
INFO SA1_XTD2_MCP/ADC/MCP2 : Reset simply calls initialize() method now.
INFO SA1_XTD2_MCP/ADC/MCP2 : Connecting to hardware driver, setting up the device's namespace...
ERROR SA1_XTD2_MCP/ADC/MCP2 : Cannot create IibusMap object for /dev/pciedevs6 and maps in /home/utcaadm/maps since:
1. Exception =====> {
Exception Type....: IO Exception
Message...........: Open '/dev/pciedevs6' : No such file or directory
File..............: /[...]/src/IibusMapImpl.cc
Function..........: utca::IibusMapImpl::IibusMapImpl(const string&, const string&, bool)
Line Number.......: 32
Timestamp.........: 2017-May-21 15:56:50.638370
}
|
For record, the last message was me (DG)
|
A deeper look into the dev namespace provides only pciedev0 and pciedevs3 are available. (DG) |
259
|
22 May 2017, 11:06 |
Tobias Freyermuth | General | Information | AE PLC OCD | From now on the PLC OCD contact person will have always the phone number:
9 8040 |
260
|
22 May 2017, 13:31 |
Tobias Haas | General | Information | Status and Plans after 09:30 Meeting | General:
- No break this week on Wednesday. (Wednesday breaks for XTD10 should start next week)
- Possibility of ZZ access to XTDs on Tuesday from 0700 - 1500. Harald organises the access for vacuum and
diagnostics. No ZZ without previous experience
- Expect XTD9 to close next week.
XTDs:
- SR imager crashed several times on the weekend. D. Görries spent a lot of time investigating and found that
when the configuration of the camera is set to mono-8 it runs stably. This indicates that there is a network
bandwidth issue
- D. Görries also had to restart the KARABO server for the MCP. One motor was working but the other one had
hardware problem and requires an access to the tunnel
- Tests for ELMO motor on PBLMs this week by Mahadi and A. Silenzi. N. Gerassimova is on holidays but agreed to
the test
- A. Parenti would like to deploy SW with added debugging functionality for imagers
FXE
- A. Galler and W. Gawelda are not available this week
- D. Görries reports that there are still problems with controlling the vacuum, I. e. gauges, pumps, valves,
fast valve. Some are related to cabling problems that are currently being fixed
- A firmware upgrade is requested for the commissioning crate. Will be discussed in detail with AE
SPB
- Work by AE on AGIPD for this week was called off as detector consortium wants to work on the hardware
- AE will concentrate on commissioning loops 1&2 for the optics hutch
- Firmware for loops 1&2 needs to be first regenerated
- All cabling problems should be solved by tonight
- All crates can then be pushed in
- All cables should be done except for 4 or 5 in the instrument hutch
KARABO
- The bug that results in devices not updating in the GUI server still persists
- Users are requested to inform A. Silenzi as soon as they discover this behaviour
Plan for the next days
- Start with SPB optics hutch
- Update firmware of FXE commissioning crate
- Test ELmo motor in XTD9 |
261
|
24 May 2017, 09:06 |
Tobias Haas | General | Information | Reminder: SASE1 Readiness Dispatch @ 0930 today | see you there |
262
|
24 May 2017, 10:39 |
Tobias Haas | General | Information | Status after 0930 meeting | General:
- DESY will try to lase again at higher energies during the next days
- XTD9 will searched an interlocked this afternoon at 1400 as PCT will try to transport photons as far as possible
- Company Wille has started to work on the radiation interlocks in SASE1. New TÜV date on 20 June and rehearsal on 14 June
- Instruments should be prepared that on these days
XTDs:
- CAS (A. Parenti) is still working on the instability problem of the SR imager. For the moment the workaround with reduced resolution (mono-8) seems to acceptable
- One (non-existing) pump needs to be removed from interlock conditions in XTD9. Otherwise interlock blocks one gate valve
- Filter was taken off the pop-in in XTD2
- Tests for PBLMs still need to be done in XTD9 when it re-opens next week
FXE:
- Problems exist with vacuum controls. J. Tolkiehn is currently working on it
- Firmware of commissioning crate was upgraded
- Test of Johan Spectrometer was done with test crate
- CRL test are next
SPB:
- Still waiting for firmware for loops 1&2. AE is almost ready and will deploy today
- All cables are ready for Optics hutch
- AE is currently pushing in the crates
PLC:
- DESY MPS claims that a cable from the interlock to an AE crate is still missing.
- AE got vital information from MPS just a few days ago and is still waiting for info from the laser interlocks
KARABO:
- CAS is working on a version with bug fixes for stability. Will be deployed when appropriately test and when a break is available
- X2 timer interface still has issues. A. Sienzi is working on it
ITDM:
- An update of network switches is needed. This will be scheduled for next week. Details to be discussed during Monday 1500 BKR meeting
|
263
|
26 May 2017, 18:01 |
Gabriele Giovanetti | General | Information | CAS OCD phone numbers for the weekend |
- Friday 7 PM - Saturday 8.00 AM : 98060
- Saturday 8.00 AM - Sunday 8.00 AM : 98054
- Sunday 8.00 AM - Monday 8.00 AM : 98055
|
264
|
27 May 2017, 16:31 |
Harald Sinn | General | Information | Status of beam commissioning | We got the beam to the end of XTD9 onto the SPB screen and FXE Pop-in (the SPB pop-in does not work).
Everything looks quite good and the beam is quite stable.
Lasing photon engery is around 6.2 keV and 200-300 mJ per pulse.
Harald
|
265
|
29 May 2017, 16:30 |
Tobias Haas | General | Information | Status and Plans after 09:30 meeting | General
- Photon tunnels are open until Wednesday afternoon due to the flooding on the weekend.
- The down time should be used to do important fixes/upgrades
- XTD9 can stay open all week depending on the decision of the PCT
- Photon commissioning successfully brought beam to the end of both the SPB and FXE beam lines
XTDs
- Stability problem of SR imager is still being worked on by A. Parenti (CAS)
- A new version of Karabo with many fixes is currently being tested and will be deployed once the test results appear satisfactory
- Test of the PBLM motors still need to be done in XTD9. This requires an update of the motion loop that should be done today or tomorrow
- There is also the need of an update of the vacuum loop. This should also be done during the down time
FXE
- Problem still exist with vacuum controls. The problem appears to be understood and seems to be on the PLC side. FXE uses ion pumps with an analog output that does not interface with the alarm level settings.J. Tolkiehn is working on it
- Work progresses on motor testing
- FXE requests firmware for loop 7. But this work interferes with the priority on the vacuum.
SPB
- Loop 1 is now fully available with all modules
- Loop 2 is available with only the first module. The other modules are away for modification
- Due to the flooding the connectors cannot be attached until cables have dried and have been re-tested
PLC
- AE will work again on AGIPD this week. This limits resources for the instruments
KARABO
- Problem with X2 timer interface is solved. But PCT apparently still uses the DOOCS interface.
- Waiting for the go ahead to release the next KARABO version
- Work progresses in parallel to intergrate DAQ into KARABO. This will be the next version after the bug-fix version
ITDM
- The announced update of the network switches will be done on Tuesday morning and will result in a 5 minute network interrupt
|
266
|
30 May 2017, 10:56 |
NEREA JARDON | General | Information | Vacuum Loop | Dear all,
It is needed to add two digital input terminals in Rack 1.17 and 1.18 in XTD9 for the vacuum loop, and Denis will do it in the next minutes. Therefore you will loose communication for those motion racks.
Thank you
|
267
|
30 May 2017, 11:08 |
NEREA JARDON | General | Information | Vacuum Loop | Dear all,
Sorry, my last message was not correct. We will do the hardware changes when we have prepared the Vacuum update also.
Thank you |
268
|
30 May 2017, 15:52 |
NEREA JARDON | General | Information | Vacuum Loop | Dear all,
We will run the update of the Vacuum loop in the next half hour.
Thank you! |
269
|
30 May 2017, 18:14 |
NEREA JARDON | General | Information | Motion loop | Dear all,
I will make an update of the Motion loop in the next minutes, all the systems are in safe state.
Thank you |
|