Dear all,

The EPS loop is running again with the last modifications concerning devices' names.

Thank you.

Dear all,

I will make an update on the EPS loop, it will take only a moment.

Thank you

EPS loop in SASE1 is running again

Dear all,

We need to update EPS SASE1 loop in order to finish the interlock communication for the experiments. I will do the update around 14h.

Thank you!

Dear all,

EPS and Motion loop have been updated to the last framework version with the last hotfixed. Vacuum loop would be done tomorrow in order to let the XGM work the hole night and part of the morning tomorrow.

Best Regards,

Below some clarifications from R. Bean on the issues reported in today's dispatch meeting:

- AGIPD suffered many problems which affected the operability (not really a problem of the scene). It was just operable, although not at all efficiently. Problems with the pipeline / DAQ and Karabo controls for the AGIPD suggest that some reasonable amount of work is required to find and solve the problems which may not be independent from each other

- CAS OCD point already addressed with previous email: They were available, just we needed them rather more than we should have done

- The CSS is the large rail that carries the detector. We cannot move it via the integrated system because of a misunderstanding in the implementation of limit / safety switches into the eplan design of the crate. The cabling between rack room / device seems to be fine (but of course not really tested properly because the crate is not correct). We have to use the test crate to move it right now, which is rather tedious since the encoders / limits cannot be handled properly by that system. I am available to discuss the proper implementation of switches / buttons such that we don’t need a fourth attempt at this crate

- For the smaracts we still have axes that are not controllable via the PLC. It is these that would be beneficial if they are fully integrated 

Interlock systems SASE3 - TÜV test

The pre test by D3 will be held on 20.06.

On 05.07.The TÜV Test for SASE3 will be done together with the SASE2 test and the repetition of the SASE1 test

I expect that some of us may need the weekend as a reserve (e. g. mirror installation). So we should probably say no. Let's discuss more tomorrow at 09:30 

Together with Nerea and Wajid and Alessandro

10:00 closed vatterflies at XTD9 and XTD2 from Karabo
Florian is at XTD9 next to the XGM 
XTD9: 
LOOP re-cycle
All valve closed and scroll off (turbos in unknown state; Florian in tunnel sees 990 Hz)
Scroll and turbos switched ON
Angle valve opened over Karabo
Problem to open gate-valve
Set Karabo offline
Nerea switched turbos at XTD2 ON (XTD9 were on) by PLC
Karabo is reconnected to PLC (brought online again)
XTD2: (with Alessandro) 
Scene optimized: Turbo speed, new prevac display, and preliminary scroll icon
Open KF angle and gate valve (follow "XGM vacuum incident procedure")
XTD9: (with Alssandro) 
Scene optimized: Turbo speed, new prevac display, and scroll icon
Open angle and gate valve (follow "XGM vacuum incident procedure")
New project created "SASE1-XGM" which contains both XTD2 and XTD9 XGM vacuum projects, thus scenes from both can be opened from one GUI simultaneously.

11:55 XTD9 vatterflies OPEN 
12:00 XTD2 vatterflies OPEN  
      (V10120V could only be opened after shutdown of device and re initialization) 
 
Maybe upper pressure probes need new calibration -> Check formula 
Prevacuum pressures: 
XTD9: 6.4E-4 mbar (G11081P)
XTD2: 2.5E-2 mbar (G10100P) and 1.2E-3 mbar (G10101P)

Summary : both XGMs in XTD2 and XTD9 are now back in normal pumping operation, and they were never exposed to more than a few 10E-6mbar. Good. But it took 2 hours and 4 experts.

The PLC is still not completely error free.

It is considerably better performing than the last days:

the current average pressure as measured by the Ion Pumps is 4.21e-09 mBar

there are Currently 96 ion pumps in the Tunnels as seen by the PLC:

3 cannot properly communicate with the PLC

SA1_XTD9_VAC/IPUMP/P10510I

SA1_XTD9_VAC/IPUMP/P11130I

SA1_XTD9_VAC/IPUMP/P12120I

3 have an ambiguous control name:

SA1_XTD2_VAC
SA1_XTD9_VAC2
SA1_XTD9_VAC0
 

And 4 have no channel assigned in the Karabo inteface (CAS to solve this)

SA1_XTD2_VAC/IPUMP/P10340I
SA1_XTD2_VAC/IPUMP/P10350I
SA1_XTD9_VAC/IPUMP/P10370I
SA1_XTD2_VAC/IPUMP/P10360I

The remaining 86 replied and:

Average pressure is  4.210e-09 mBar

Maximum pressure is  2.60-08 mBar

Minimum pressure is  8.90e-10 mBar

 Vacuum loop:

- Interface between PLC and Karabo is not functioning.

The fault currently resides in the PLC behaviour, the self-description sent out is badly formatted (due to a buffer overrun)

The misbehaviour is confirmed, the PLC TCP Client from AE is also ailed by the same problem.

Motion Loop:

- As of Friday, the motor parameters were not completely sent to AE. In attachment the data collected by N. Jardon (AE). Input needed for PSLIT motors.

Tobias Freyermuth and me worked on the system and as of last night, we found two new issues between Karabo and the PLC interlock:
 - one is a Karabo issue from the Interlock PLC interaction, the Karabo device waits for a PLC response that does not come when the PLC is interlocked (i.e. Karabo wants to open a valve but the PLC correctly refuses and ignores the command)

 - one is a PLC issue, the interlock is not triggered in all cases after testing (e.g. a ion pump out of set point does not closes a gate valve closure as specified).

The first one was reproduced with the BeckhoffSim simulation. It can therefore be fixed by CAS without dependencies from AE (except for the next integration test).

 Dear all,

it seems that this morning was somehow a misunderstanding. The XTD9 Gas Section Interlock test was succesfully finished the last 26th of April (see e-log message nr. 179).

There´s no further activity planned for this system.

Regards.

r.

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

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.

Dear All,

During the afternoon CAS has a group activity. Any support can be requested via my phone number: 9-6776.

See you,

Sandor 

 Dear All,

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
}