ELOG SASE1 Status and SASE3 Readiness

Group Selection Page HELP DOC Controls Group Data Analysis Group ITDM WP76 DET Vacuum XRO EEE WP78 WP74 FXE SCS SPB MID HED SQS SXP Sample Environment Photon Commissioning Team Operation PSPO XO TS

Technical integration and coordination SASE1 Status and SASE3 Readiness

Joint Operation and Readiness Logbook, Contact: T.Haas, A. Violante, G. Wellenreuther, Page 29 of 30

Not logged in

List | Find | Login | Help

Full | Summary | Threaded | Hide attachments

597 Entries

Goto page Previous 1, 2, 3 ... 28, 29, 30 Next

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
}

For record, the last message was me (DG)

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 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

For record, the last message was me (DG)

A deeper look into the dev namespace provides only pciedev0 and pciedevs3 are available. (DG)

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

CAS OCD from today to Monday

Dear all,

CAS phone numbers for OCD:

Friday: Alessandro (98054),

Saturday: Valerii (98053),

Sunday: Gabriele (98060),

thank you.

In case of any problems, please, call the CAS personnel on 9-6443, 9-5630, or 9-6840.

Have a nice week-end, Sandor

CAS on call service for the night:

Gero Flucke: 9-8053

CAS on call service for the night 98057

Here is a information from Sandor on CAS OCD Numbers
(this info is copied from the SASE1 commissioning logbook):

during the day: 98053 (8:00 - 16:00)

overnight: 98054 (11:00 - 8:00 next day)

during the weekend it is #53 or #54 (Saturday #53 8:00 - 8:00 next day, Sunday #54 8:00- 8:00 next day)

CAS - On-Call Duty Planning - Valerii, Gabriele and Wajid

Dear All,

I would like to share the CAS members on the OCD from 29/04 to 01/05:

Saturday 08:00 to Sunday 08:00 - Valerii - Phone: 95471
Sunday 08:00 to Monday 08:00 - Gabriele - Phone: 96894
Monday 08:00 to Tuesday 08:00 - Wajid - Phone: 95630

Best,

Hugo

Big issue with XGM vacuum in both XTD2 and XTD9 !

Both XGMs were and are on manual control (but the remote cables into the turbo pump controllers remained plugged in as usual) = both XGMs are "out of the VAC loop". 

In XTD2, I saw around 13h that both turbos were off (0 Hz) and the pressure was at 10E-4 mbar !

The green light above the ON-button was flickering. 
I switched parameter 023 (Motor TMP) to ON and restarted both pumps. The green light above the ON-button 
 stops flickering and goes steady green. 
 
---going to XTD9 
 
In XTD9, I saw that the upstream turbo was off (0 Hz) and the pressure was in the lower 10E-6mbar. 
The downstream turbo in XTD9 was still operating. 
Parameter 023 to ON, and restart pump. 
 
---going to XTD2 
 
Error codes 6, 6, 98, 2, 37 on one pump, error codes 6,6,6 on the other (XTD2).
I unplugged the REMOTE cables in XTD2 and XTD9 to avoid further trouble as long as we are on "manual". 
This info was also sent by email to the involved experts.

BeckhoffDevices back to responsive

I reproduced the behaviour of the PLC on beckhoffSim. This reproduces the same behaviour seen in the tunnel devices (devices hang).

Implemented the fix and verified the correct behaviour with beckhoffSim.

Fixes will be verified next Monday with the tunnel system.

Have a nice weekend

Alessandro

ps: For future reference:

beckhoffSim tags/1.1.0-1.4 (implements the recent plc behaviour (framework tag N/A Could not find tobias))

beckhoffDevices tags/2.0.1-1.4 hangs

beckhoffDevices tags/2.0.2-1.4 does not

2017.02.13 19:30 Status:

- Self-Description back in shape.

- Bad SelfDescription reproduced in BeckhoffSim (Karabo implemented PLC communication) and solved in BeckhoffCom (Karabo "PLC Client").

- The build status of the Firmware is not ok. roughly 90% of the PLC soft devices are in error. It is a fault in the automatic Firmware build procedure.

Nerea and Jan will work on this until it is fixed.

137

11 Apr 2017, 18:38

Ra�l Villanueva-Guerrero

XTD2

Feedback

Beam Stopper and V0 valve test - SUCCESSFUL

The Interlock conditions for these two components has been positively tested but not exhaustively done:

The triggering of both via the actuation on the Fast Valve----------------->DONE and OK

Their triggering via HV down of each of the 6 ion pumps------------------>Partially DONE and OK: Partially means that only one of the pumps randomly chosen has been deactivated. The agreement is that the other remaining 5 can be done later, also from the office since the correspondence between the devices and the physical components has been confirmed.

Also, the individual actuation of both, Beam Stopper and V0 valve has been proof showing a consistent behaviour regarding the interlock definition.

Finally the XFEL Vacuum OK signal is available but AE is currently improving it. By the moment is not automatically sent to DESY, but instead it needs to be activated manually. According to AE feedback this should be corrected in the following days.

Automatic logbooks for beamtimes

Logbooks for the first two upcoming proposals in FXE and SPB instruments have been set up and all missing users in the past 6 proposal have been corrected. From now on, user registration is disabled, logbooks for next proposal will be set up automatically once the proposal info is migrated from UPEX to MdCnix. Any subsequent changes (like a new user added in MdCnix to a given proposal) has to be done on request either by admin of particular logbook or ITDM.

Standard setup of beamtime logbooks is the following

Admin list contains ITDM staff, instrument support group (as given by relevant instruments), PI and Main proposer as given in UPEX
User access is given ITDM staff, instrument support group and all participants of a given beamtime.

All subsequent customisation, including adding extra users, should be made by logbook admins.

Regarding logbooks for the past proposals in September, not all was corrected according to the above defaults, especially there may be wrong email addresses put at that time by users during registration -this can be fixed as well, taking info from UPEX.

Also HELP logbook was updated.

This change affects also XFEL internal usage of ELOG, as from now on, a new user has to be added by a relevant admin.

Cheers,

Janusz

Access to tunnels updated

XTD9 will be open until Friday this week 13:30. Check https://docs.xfel.eu/share/page/site/PSC/wiki-page?title=Tunnel_access_schedules

295