1 / 24

EPICS @ DESY/ XFEL An Overview

EPICS @ DESY/ XFEL An Overview. EPICS Collaboration Meeting San Francisco, October 5th, 2013 Matthias Clausen, DESY Cryogenic Control Group. Overview. Control Systems for the XFEL News from Cryogenic Controls CSS Developments Trent Plotter Synoptic Display Studio (SDS)

yetta
Download Presentation

EPICS @ DESY/ XFEL An Overview

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. EPICS @ DESY/ XFELAn Overview EPICS Collaboration Meeting San Francisco, October 5th, 2013 Matthias Clausen, DESY Cryogenic Control Group

  2. Overview • Control Systems for the XFEL • News from Cryogenic Controls • CSS Developments • Trent Plotter • Synoptic Display Studio (SDS) • CAJ – deadlocks • DAL -> DAL-II • Alarm System • Archiver • IOC Redundancy

  3. DESY-Bahrenfeld: • Start of the3,4 km long XFEL Schenefeld: • Science with X-ray flashes Osdorfer Born: • first split of the tunnel XFEL: OneMachine/ Threecontrolsystems Creating X-rayFlashes Elektron-Accelerator

  4. The XFEL Tunnel

  5. The real XFEL Tunnel

  6. CSS Developments: Trend Plotter • Addingnewfeaturesto Trend Plotter • Displayingarchivedeadbandforeachchannel(Monitor Deadbandfor online/ live channel) • Interface toMySql Database

  7. CSS Developments: New SDS Widget: X/ Y Plot ExyampleofColdCompressorCharacteristic Diagramm

  8. CSS Developments: New SDS Widget: X/ Y Plot Prototype ofColdCompressorCharacteristic Diagramm

  9. CSS LessionsLearned: CAJ - deadlocks • CSS isrunning in thecontrolroomasprimaryoperatorinterface • Over the last twoyears CAJ deadlockswerecausing a lotoftrouble • Communication with Matej improved: • Prepared fixes makeitintothecode • New bug fixes aredistributedfaster

  10. CSS LessionsLearned: DAL -> DAL-II • Lessionslearnedfrom DAL: • DAL isnecessarytointerfacetoseveralcontrolsystemprotocols • Support for metadata/ characteristics for severalprotocolsrequires a commoninterface • DAL-I was overloadedwithtoomuchfunctionality • Redefiningrequirementstothebasicneeds • A completerewriteofthe DAL layeris on theway

  11. Alarm System • Everythingis a message • (alarm-; systemLog-; putLog-;snlLog;log4JLog…) • Messages are all transportedas JMS messages • Messages canbedisplayed in tables (andtrees) • Messages getwrittento Oracle (jms2Ora) • Messages become Alarms whenprocessed in the Alarm Management System (AMS)

  12. Alarm System • Developments: • DAL2JMS – (nowusing DAL-II) • Channel-Lists getmonitoredandwrittento JMS (as Message) • Configurationsimilartoalh • Synchronized Alarm-Table/ Alarm-Tree • Alarm Treesimilartoalh Alarm Tree • AMS – Continuousimprovementdrivenbycontrolroom • Time basedmessagefilternsGeneratealarmwhenstateisactiveformorethen ?seconds • Attachalarmdetailstomessageandforward on different topic

  13. Archiver • Running in fullproductionmodesince March 2013 • Basic requirements • Data retrievalforanyintervaltakesnomorethan 3 sec • Display archivedeadbandforeverychannel • Implementation: • MySql Database on Sun Cluster • In additiontothe ‚raw‘ data, westoremeanvalueson a hourlyandminutebasis • Define ‚related‘ channelswhicharchivethedeadbandofthemainchannel • ReplacepvManagerby DAL-II (1Q 2014)

  14. Redundancy • First mentionedduringthe EPICS Meeting atArgonne 2006: • 2006 – Presentation: • From the preamble of the design specification: • … last and most importantly one major design goal must be matched: • Any redundant implementation must make the system more reliable than the non redundant one. Precaution must be taken especially for the detection of errors which shall initiate the failover. This operation should only be activated if there is no doubt that keeping the actual mastership will definitely cause more damage to the controlled system than an automatic failover.

  15. Redundancy: initialstates IOC-B pref Slave IOC-A pref Master is:?? Prof-II Prof-II C P U Prof-I C P U Prof-I is:?? Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  16. Redundancy: Startup IOC-B pref Slave IOC-A pref Master is: booting Prof-II Prof-II C P U Prof-I C P U Prof-I is: booting Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  17. Redundancy: Running IOC-B pref Slave IOC-A pref Master is: Master Prof-II Prof-II C P U Prof-I C P U Prof-I is: Slave Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  18. Redundancy: Master CPU Failure IOC-B pref Slave Master CPU failure Watchdogreset IOC-A pref Master is: Master Prof-II Prof-II C P U Prof-I C P U Prof-I is: Slave Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  19. Redundancy: Master CPU Failure – Slave detectsfailure IOC-B pref Slave Master CPU failure Watchdogreset Reset Profi I + II IOC-A pref Master 4. Slave detectmasterfailure is: Master Prof-II Prof-II C P U Prof-I C P U Prof-I is: Slave Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  20. Redundancy: Master CPU Failure – Slave takingmastership IOC-B pref Slave 7. Master CPU booting IOC-A pref Master Slave detectmasterfailure Start Master Start Profibus I+II is: booting Prof-II Prof-II C P U Prof-I C P U Prof-I is: Slave Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  21. Redundancy: Master CPU Failure – Slave active/ prefmaster passive IOC-B pref Slave 7. Pref Master CPU booting 8. Pref Master detect Master 9. Become Slave IOC-A pref Master Slave detectmasterfailure Start Master Start Profibus I+II is: booting Prof-II Prof-II C P U Prof-I C P U Prof-I is: Slave Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  22. Redundancy: Master CPU Nettask Crash 1. Nettaskcrash Detect ‚specialnettaskcase‘ Find existing Profi ‚stand bymaster‘ StopWatchdog Reset CPU andProfibus I+II IOC-B pref Slave IOC-A pref Master Detect Master is OFF Profi Master still active Cannottakeover is: Master Prof-II Prof-II C P U Prof-I C P U Prof-I is: Slave Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  23. Redundancy: Master CPU Nettask Crash 1. Nettaskcrash Detect ‚specialnettaskcase‘ Find existing Profi ‚stand bymaster‘ StopWatchdog Reset CPU andProfibus I+II IOC-B pref Slave IOC-A pref Master Detect Master is OFF Profi Master still active Cannottakeover 9. Take over is: booting Prof-II Prof-II C P U Prof-I C P U Prof-I is: Slave Profibus - I private link Profibus - II Ethernet B Ethernet A Ethernet Ethernet File Server

  24. Redundancy • The currentimplementationisrunningsincethreeyears in three IOCs in production. • Production: • 6kW@4K Helium plant • 3MW primarycompressor power • All (PID) controlloopsrunning in the IOC • SNL programscontrollingsequencesandsupervisorycontrolloops • PLCs onlyused for hardware interlock • helpedustosurvive 6 nettaskcrashes

More Related