ELOG SASE1 Status and SASE3 Readiness

there was some miscommunication between us and DESY: only the Timing firmware and doocs server need to be updated, the RTM was already been replaced. This require update is similar to the one perform two weeks ago (see entry #449).

The time slot for this update is next Wednesday, 23rd January, between 16h and 17h. The update will affect all Timing Devices in SASE1. This operation should not take more than 10 minutes; during this time no timing signals will be generate (clocks/triggers/bunch patterns/etc.). Naturally, problems may occur during this update which will lead to increase down time.

If somebody sees a problem with the current schedule, please contact me.

Adriano Violante wrote:

General remarks:

Stable beam only to be expected starting from 1.03. for SASE1 instruments commissioning
There is no guarantee for parasitic beam delivery to the experiments. If it happens at all it will most probably be during the last week of Feb. This has to be agreed on the fly with the BKR and H.S/ T.T.

SPB/SFX:

Preparing D.02 for mirrors installation (next week)
Karabo being updated

Advanced Electronics:

Trigger delivered by DESY should be back and stable at 10Hz.
ATM for timing has to be replaced in the balcony rooms. Bruno Fernandes is trying to find a way to reduce the downtime down to 30 minutes. Will be scheduled in the next days.

ITDM:

1 line card has to be replaced. Probably happens on Wednesday this week during the DAQ tests.
Tuesday afternoon the online storage units will me remounted with the same path of the offline ones.
This week a proposal for the in-house commissioning is going to be circulated.

SASE1 Timing System Update

Dear all,

the update to the SASE1 Timing system has been perform with no problems. The Timing board is now running firmware 1.24.0 and the doocs server was updated to version 7.8. I also updated the MCH firmware to version 2.19

WP74 components in XTD2 - electrical connections

Status of WP74 components testing and wiring this week:

On Monday we tested SR Imager and K-Mono:

- issue with motor connect pinouts was discovered and I wanted to correct pinout today, but K-Mono and SR imager motor connectors are Lemo with soldering pins, which make pin changing more difficult than crimp version...

- this is still not done (we can exchange all connectors to crimp version or temporary change pins on crate side).

This week done:

- connected SR imager EPS switch (on the imager - not yet in the crate)

- On XGM Gas Panel is installed new HUBA gauge, and I connected it to the crate (now everything from Gas Panel is connected to Beckhoff terminals in WP73_VAC crate - Rack 1.3).

- FEL imager - EPS switch is connected properly, but Digital Input terminal in WP73 EPS crate - Rack 1.5 is defect (doesn't work at all).

- I placed cable for EPS switches of MCP detector, but not placed in the Rack (Rack needs to be opened - Roxtec feedthrough is closed)

To be done:

- K-Mono - switch pins 1 and 2 on Motor connectors (Y-1, Y2 and X).

- SR imager - switch pins 1 and 2, and switch pins 7 and 8 on all Motor connectors.

- SR imager - EPS switch connect from WP74 crate to WP73_EPS crate (one cable inside crate).

- XGM vacuum to HV crate interlock (inhibit) is still not connected (I am waiting for Beckhoff terminal, but this connection was not tested yet).

- MCP detector - EPS switch cable needs to be laid inside Rack 1.7 (Rack needs to be opened - Roxtec feedthrough is closed).

- MCP detector - vacuum to HV crate interlock (inhibit) needs to be connected - Beckhoff crate is prepared - missing cable from MPOD to Beckhoff terminals.

SPB - Loop 5 is back online

SPB Loop 5 is back online:

- but without crate BKF00095-SPB_IRU_CHL (there is missmatch of hardware and documentation (investigation is ongoin)),

- pumps: PUMP_TURBO4, PUMP_TURBO5, PUMP_TURBO8, PUMP_ROOT_1, PUMP_ROOT_2 ,PUMP_ROOT_3 and IRU_VAC/PUMP_ROOT_1 are without serial connection

Interlock is inlcuded and ready for testing.

Best Regards,

Bernard

Pop-In II-45 Karabo test

6.3.2017, Karabo tests in XTD2 with Wajid, Andreas

1. Karabo all devices, all scenes working, with restrictions.

2. Power supply, motor, LED working.

3. Scenes tested: Motor scene and camera scene need additional parameters. AK will edit a list of suggestions, improvements and bugs.

4. Bugs, observations, details in improvement list.:

- Homing not working, tried also old parameter set from prototype crate.

- Encoder position not correct, dragging behind.

- Parameter for braking switch missing “ALowSpeed”.

Karabo testing on Wednesday

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

XTD2, IMAG.2694.T9, Pop-In II-45: Acceptance test of motor control under Karabo, done. Camera device needs further explanations and testing.

Pop-In II-45 Karabo test

Trigger signal now available at imager. First Karabo tests of camera device with trigger successful. Detailed
tests continue.

Please inform on rack status 1.18

The rack 1.18 in XTD9 is not operational at the moment because Nicola is working on it. Nerea, Tobias or others let me know when it is fully operational again. This avoids checking it in the tunnel. Alternatively, let me know if I can check remotely.

XTD2, FEL imager with Wajid

Screen, motor, switches - ok, minor braking switch issue.

LED, camera power – ok.

Filter, motor, parameter issue, should be solved now, to be tested again today.

EPS tests and SR imager tests, to be done.

XTD9 cameras, no power, will check today with Bernard.

motion loop not working !?

Has anyone an idea why the motion loop is not working? Thanks Andreas

motion loop not working !?

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

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

Imager Status, 12.4.17

- All imagers tested, motors and cameras, motion loop, EPS loop, for 3 imagers XTD2, and 3 imagers XTD9.

- All blocking issues concerning tunnel closure solved.

- Remaining issues:

o Camera trigger, tbd. for 4 imagers.

o Camera driver for SR imager, Photonic Science, tbd.

o Camera of sa1-xtd9-imgpii45-cam-beamview not reachable via IP address, tbd..

o Camera display is now at around 2 Hz, not yet full speed.

o Store image function, tbd.

o Firmware update to operate braking switches for homing procedure, tbd.

Trigger and IP address

All trigger problems in XTD2 and XTD9 solved except for one: spb_xtd9_imgpi, probably a cabling issue on the camera side.

IP address problem for camera of sa1_xd2_imgpii45 solved.

Request for imager checks

Since tomorrow there is no beam I want to use the time for some checks of the imagers in XTD2. Please, let the motion loop up if possible until 10 am, otherwise let me know.

After the update of the PLC firmware, the imagers are in following status:

SR: auto gain off seems to work, correct image, screens are out. Beamview just crashed, I asked Alessandro and Dennis to have a look.

Pop-In: Everything fine.

FEL: strange image. We had this before, no idea what the reason is. I will keep trying.

Another update of the motion loop is planned later. Contact Nerea for details.

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

ELOG V3.1.4-7c3fd00