I will update the SASE3 MOV1 loop in 30 minutes. Please let me know if you would like me to postpone the update.

Best regards,

Marijan

The XTD2 CRL is now aligned and cabled.

Motor cabling is complete and ready for local testing. Encoder and PT100 cabling at rack to be completed by the middle of week 11.

The LENS_3X limit switch (switched when driving towards the chamber center) is broken and must be replaced, hence further work is required on the next JJ visit 9/10 Jan (TBC)

The in vacuum components also need further work during the above visit. The lens that lost alignment during commissioning was also found to be more severley damaged than anticipated - the B4C guard is cracked and this deposited some fragments under the lens. All lens cassettes will be exchanged, rebuilt and realigned in Jan.

The patch panel has been removed for rework (to switch motor direction)

The Be lenses seem to be in exactly the same condition as 'new'

The upgrade of the switches is finished to the extend that it allows Advanced Electronic group to work on KMono (Nerea is informed)

However, during the upgrade of the network one switch got stuck and this is the switch in XTD2 tunnel. The IP network in the XTD2 tunnel is not reachable at the moment (Beckhoff loops are fine) and we are going top the tunnel soon.

Dear All,

In XTD10 there are now office network ports available in each rack. These can be used to connect your regular laptops with a network cable without special configuration and registration of your laptop.

The list of racks and corresponding port numbers is listed below. Please, note that in lead racks (3.4, 3.7, and 3.13) you need to plug the cable directly to the office switch port 24. This port is located in the bottom row, most to the right.

As discussed offline with NOC, Monday schedule was already fixed and not movable to Tuesday. Therefore, the network maintenance will take place on Monday 7:00 - 9:00.

During that time, no stable network is guaranteed.

After the network maintenance, the foreseen update and restart of all control server will take place, which take approx. ~2 hours. The exceptions are sase1 control servers and plc gateways as well as data logger and brokers and probably most importantly, exflgateway. These will be done after the work in sase1 (KMONO integration) is finished.  

All control servers, brokers, dl and finally gateway were updated and restarted.

We would like to take the oportunity of the shutdown period and update the online storage next week on Monday 9th Oct. This will take approx. half a day. During that time the online storage will not be available on the online computing cluster as well as on pclayer servers used for DAQ. In the same way, the nfs export for data logger is also affected.

Regarding data collected on the online cluster, although it should not have any influence, but as a precautionary measures, please make sure that all relevant data from all past proposals  are migrated to offline storage, which in practice means requesting migration via metadata catalog web interface. If there are still issues with particular runs not being able to be migrated, please contact ITDM.

regards,

Janusz 

After today's discussion with WP75 group, we decided to postpone the update of the online storage to the next Monday 16th October.

Hi

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
 

Tomorrow, 5.04, between 9:30 and 12:00 there will be urgent maintenance of one of the two redundant main switches for the control network. The network connectivity during that time is not guaranteed, but also any major interruptions are not expected. For the two switches in sase1 tunnels with only one uplink, there could be short (~1min) interruption.

Best, 

Janusz

On Friday, 6.04, there will be a maintenance of the online storage system. This will tackle the issues we had just before the last user beamtimes, when we decided to apply workaround to keep the system working. The availability of the storage system is not guaranteed, especially when faulty h/w parts needs to be exchanged.

Best, 

Janusz

Not really official, but in emergency case you can call 96993 for vacuum group. Next week Martin is back and I think we will have official on call service.

Have a nice weekend with hopefully no problems :-)

exflplcgwSA1 seems not reachable. This inhibits support for the PLC systems.

___________________________________________

Bernard Baranasic

This is the current (w5) progress at DESY concerning the analysis of the serious XGM resistor issue (summary; a detailed report by DESY is available):

• The new “pulser test” was verified at an operational XGMD at FLASH. The test method is (unfortuately) OK. This means that the test results with issues from last week on all our XGMs are REAL.
• 25% of all resistors in XBPMs affected, 0% of resistors in HAMPs affected, no capacitors affected.
• Since no HAMP resistors are damaged, damage by environmental conditions (venting, humidity etc.) can be excluded. The main differences to the affected resistors are the HV-conditioning and the experienced HV-values of the resistors (typically XBPM resisotors are tested up to 12kV, HAMP resistors each see much lower voltages).

• An XGMD chamber at FLASH was tested-to-destruction-of-resistor by applying a large differential voltage (>3kV) between neighboring electrodes, e.g. on mesh_e and FC_e. These resistors (Caddock MS220) have a nominal voltage breakthrough rating of ~500V but never had issues. They are used in all our XGMs.
• New, other resistors (Ohmite MOX-1N-13) with higher voltage breakthrough rating of 10kV were procured and arrived tuesday
• The new resistors were built into the tested-to-destruction XGMD at FLASH, unit is now pumping, will be retested with applying pulsed HV (on both Caddoc and Ohmite resistors) when at suitable pressure.

Further plan (w5end + w6) concerning the XGM resistor issue:

• If the new resistors survive the test, then next monday the XGM01 at HERA-S will be opened, the tested-defect resistors will be checked and replaced with the new resistors.
• If all tests on XGM01 are then ok including an acceptable RGA, all other XGMs (XBPM chambers) will be opened and resistors exchanged. Even ok-tested resitors would be exchanged to avoid future unexpected failures. HAMP chamber resistors will not be exchanged (large number >20 of resistors, no failures).
• If the RGA is not acceptable, the resistor Ohmite MOX-1N-16 is another alternative, but has increased delivery time.

Presentation for SASE1readiness-Meeting

on XGM resistor issue progress (w5) and plan (w6)

Information posted on behalf of Torben Falk (WP74 cabling)

Wir haben nun alle Kabel für den XGM in XTD2 am Beckhoff angeschlossen.

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.